FinanceFree to read online

Corporate Finance and Financial Modeling Explained

Name: Corporate Finance and Financial Modeling Explained
Availability: InStock
Author: Michael Thompson

A practical reference on building forecasts and using them to guide investment, financing and payout decisions

This ebook explains how corporate financial models are built and how they feed decisions about investment, financing and payouts. It covers the three statement backbone and schedule layer, the differences between discounted cash flow, trading comparables and precedent transactions, and how capital structure affects both cash flows and discount rates. Readers also see where errors usually enter a model, how to test assumptions, and how analysts build credibility with managers and other decision makers.

Michael Thompson, Academic Expert, Finance
19 min read
25 pages

Start reading

What you will learn

Describe what a financial model is and how corporate finance decisions depend on it
Explain how the three statements and schedule layer connect in a typical model
Compare discounted cash flow, trading comparables and precedent transactions
Recognize common modeling errors and apply basic checks and stress tests
Communicate model results clearly so decision makers can act on them

vaayaa Guide

vaayaa

Finance · Reference Guide

Corporate Finance and Financial Modeling Explained

A practical reference on building forecasts and using them to guide investment, financing and payout decisions

Michael ThompsonAcademic Expert, Finance

Orientation

001

What the Field Covers

Financial modeling is the craft of turning a business story into a set of connected forecasts. A model usually projects sales, costs, assets, debt and cash, then links those lines so that a change in one place flows through the rest. The result is a numerical argument about how the business may perform under stated conditions.

Corporate finance is the discipline that decides what those forecasts should drive. Its core questions are which projects to fund, how to pay for them with debt or equity, and how much cash to return to owners. A forecast without a decision attached is only a spreadsheet, while a decision without a forecast rests on guesswork.

A model is an argument about the future, so its assumptions deserve more attention than its formulas.

The two fields meet in practice. Analysts build models to test an investment, judge a financing plan or value a company for a sale or purchase. Throughout this ebook, the model is treated as an argument. Its quality depends less on formula speed than on whether its assumptions are reasonable and clearly stated.

Business story

Forecasts

Valuation

Decision

From story to decision

Orientation

002

Where Models Sit

Most corporate models share a backbone of three linked statements: an income statement, a balance sheet and a cash flow statement. Revenue and cost assumptions drive the income statement, which carries net income into equity and cash. The balance sheet must balance, and that check is one of the strongest signs the links are sound.

Around the three statements sits a schedule layer. Schedules handle items that need their own logic, such as fixed asset roll-forwards, working capital balances, debt repayment and tax calculations. Keeping schedules separate makes the model easier to audit because each block has one clear job.

Good structure makes a model easier to check, change and trust, even before anyone tests its numbers.

Outputs then flow to decisions. Valuation sections read free cash flow, financing sections read debt capacity, and summary pages present results to managers. Seeing the path from inputs to outputs helps a reader know where to look when a result seems wrong.

Inputs

Three statements

Schedules

Decisions

How the model connects

Orientation

003

Why Assumptions Drive Results

Two analysts can use the same formulas and reach very different answers because their assumptions differ. A small change in long-run growth or margin can move a valuation far more than a minor error in a single formula. That is why assumptions deserve the most review time.

The bars below are illustrative, not measured. They show how a reviewer might rank the influence of each input in one hypothetical case. The point is the ranking habit, not the exact numbers. Revenue growth and margin often dominate, while tax rates tend to matter less in a stable business.

Every assumption should carry its source, its reasoning and the range that was tested, so reviewers know what to challenge.

Good assumption work states each input, gives its basis, and links it to evidence such as history, contracts, industry data or management plans. It also records the range tested. A reader should be able to see which numbers are facts, which are judgments and which are placeholders.

Revenue growth

Operating margin

Working capital

Capital spending

Tax rate

Illustrative sensitivity ranking (Illustrative)

Orientation

004

Who Uses Models

Financial modeling sits at the center of several career paths. Equity research, investment banking, corporate finance and private equity hiring all rely on the skill, and a related survey found that many respondents linked validated modeling ability to career progress. The shared core is the same across these roles, even though the questions differ.

In FP&A work, models support planning, budgeting and rolling forecasts. Analysts update projections as actual results arrive and explain variances to managers. In corporate finance, models test capital projects, financing options and dividend or buyback choices. In transaction work, models value targets and show how a deal changes the buyer's cash flows.

Most modeling projects follow the same arc, from a clear question to a recommendation someone can act on.

Each role follows a similar arc. The analyst begins with a clear question, gathers data, builds the model, tests the answer and makes a recommendation. The timeline below shows that path. Knowing where a task sits in the arc helps a learner decide what level of detail is needed.

Define question

Gather data

Build model

Test cases

Recommend

Typical modeling project arc

Core Concepts

005

Three Valuation Lenses

Discounted cash flow, or DCF, estimates value from the cash a business is expected to generate, discounted back at a rate that reflects risk. It answers an intrinsic question: what is this stream of cash worth today? Its results depend heavily on forecast assumptions and the discount rate chosen.

Trading comparables apply valuation multiples from listed companies that look similar. They answer a market question: how are comparable businesses priced now? The method is quick and grounded in current prices, but it is only as good as the peer group. A weak peer set can make a poor company look fairly priced.

Each valuation method answers a different question, so the right choice depends on the decision being made.

Precedent transactions look at prices paid in earlier deals for similar businesses. They answer a control question: what have buyers been willing to pay for a whole company, including any premium for control? Because deal terms and timing vary, precedent work needs careful selection. The matrix shows how each lens fits each question. Ratings describe relative fit, not a score of quality.

	Intrinsic value	Market pricing	Control price
Discounted cash	●●●	●	●
Trading comps	●	●●●	●
Precedent deals	●	●●	●●●

Which method answers which question

Core Concepts

006

Parts of Model Design

A useful model has a small number of clearly separated parts. Inputs hold every assumption in one place, so a reader can find and change them without hunting through formulas. Statements and schedules perform the calculations. Outputs present results in a form a manager can read quickly.

Checks are a part that many new models lack. They include balance tests, cash tie-outs and sign tests that confirm the model behaves as its design implies. Scenarios let a user switch between cases, such as a base case and a downside case, without rebuilding the model. Scenario design also forces the builder to name the drivers that really matter.

Separating inputs, calculations, checks and outputs turns a model from a black box into a tool others can test.

The mindmap summarizes these parts. Each branch connects to the others. Inputs feed statements and schedules, checks read the statements, scenarios change the inputs, and outputs display the result. A model with a clear map is easier to hand over and far easier to review.

Model
Design

Inputs

Statements

Schedules

Checks

Scenarios

Outputs

Parts of a sound model

Core Concepts

007

Where the Effort Goes

Building a model takes effort in several areas, and experienced builders plan for that spread. Much of the time goes to assumptions, because they require research, judgment and discussion with the business. Structure takes effort too, since the links between statements and schedules must be clean from the start.

The donut below is illustrative. It shows one plausible split of build effort in a single model. Actual projects vary widely with the size of the business, the quality of source data and the number of decisions the model must support. The chart is meant to prompt a question: where is my time going, and is that the right place?

Time spent on assumptions usually pays back more than time spent on formatting, because weak inputs spoil every output.

Formulas and presentation complete the work. Formula writing should be straightforward when the structure is sound, while presentation makes results readable for managers. Learners who spend too little time on assumptions and too much on formatting often produce models that look polished but are hard to trust.

Assumptions 40%
Structure 25%
Formulas 20%
Presentation 15%

Illustrative build effort split (Illustrative)

Core Concepts

008

Linking Cash, Capital and Rates

Capital structure is the mix of debt and equity used to fund a business. It matters to corporate finance for two reasons. First, interest on debt changes the cash that flows to equity holders, and interest is often tax deductible, which changes net cash flow. Second, the mix changes the risk borne by each investor, which changes the rate used to discount cash flows.

The diagram shows where these three elements overlap. Cash flows are the numbers being valued. Discount rate is the lens through which those numbers are valued. Capital structure sits at the intersection because it touches both. A model that changes debt levels without updating the discount rate, or the reverse, will give an in complete answer.

A financing change alters both the cash that is valued and the rate used to value it, so the model must reflect both.

Analysts usually handle this by linking the financing schedule to both the cash flow lines and the discount rate calculation. They also test how value responds when debt changes. The method is not a formula to memorize. It is a habit of checking whether a financing change has been carried through every part of the model.

Cash
flows

Discount
rate

Capital
structure

Where three choices overlap

Core Concepts

009

Layers Beneath the Decision

A model supports an investment or financing decision in layers. At the base sit assumptions: growth rates, margins, working capital days, capital spending and financing terms. Above them sits the forecast, which combines those assumptions into projected statements. The valuation layer reads the forecast, and the decision layer at the top uses the valuation to recommend an action.

The pyramid makes a simple point. A weak base weakens every layer above it. An elegant valuation built on an unexamined growth rate is still fragile. Reviewers therefore start at the bottom, asking whether each assumption is defensible before they look at the valuation result.

Each layer of a model rests on the one below it, so the most fragile input sets the ceiling on confidence.

This layered view also helps communicate limits. A decision memo can say which layer carries the most uncertainty. When the forecast depends on one contract or one product line, the memo should say so. Stating that dependence openly builds credibility with decision makers.

Investment choice

Valuation

Forecast

Assumptions

Each layer rests on the one below

Core Concepts

010

The Model Improvement Loop

Models are rarely finished in one pass. Analysts often move through a repeating loop: they state assumptions, build the forecast, test the results and revise what the tests reveal. Each pass sharpens the model and the reasoning behind it. The loop also keeps the model honest, because revision follows evidence rather than preference.

The cycle diagram shows the four steps in order. Assumptions come first because every later step depends on them. Forecasting turns them into statements. Testing checks the output against expectations, historical patterns and logic. Revising then corrects the assumptions or structure, and the loop begins again.

Repeating the assume, forecast, test and revise loop turns a rough draft into a model others can rely on.

The loop works best when each pass leaves a record. A short note can list what changed and why. Over time that record becomes a useful history, showing reviewers how the view evolved. It also makes it easier to explain a sudden change in the valuation to a manager who has not followed every step.

Assume

Forecast

Test

Revise

Model improvement loop

Methods

011

Building the Core Model

A common build sequence starts with inputs and links. The builder places assumptions in one sheet, then connects them to the income statement, balance sheet and cash flow statement. Links should point in one direction where possible, so that a reader can trace any number back to its source without following loops of references.

Schedules come next. Fixed assets, debt, equity and working capital each get a schedule that handles their movement from period to period. The balance sheet check follows. Assets must equal liabilities plus equity in every period. When it fails, the cause is usually a missing link, a sign error or a schedule that does not close.

A balance check that passes after a stress test is strong evidence that the model's links are working as designed.

The process ends with a stress test. The builder changes key inputs to extreme but plausible values and checks whether the model still behaves sensibly. Cash should not turn negative without a visible reason, and ratios should move in the expected direction. A model that survives stress testing is more likely to hold up under real questions.

Link inputs

Build schedules

Check balance

Stress test

Build sequence for a model

Methods

012

Connecting Debt to Cash

Debt is one of the most common sources of model errors because it creates links in several places at once. A debt schedule tracks opening balance, new borrowing, repayment and closing balance. Interest expense comes from that schedule, and interest flows into net income. Net income then affects cash, which may affect how much debt can be repaid.

The flow diagram traces that path in order. A change in the debt schedule moves interest, which moves net income, which moves the cash balance. Following the chain by hand is a useful test. If a reader cannot explain how a change in borrowing reaches cash, the link is probably missing or hidden.

Tracing a single change in borrowing through to the cash balance is one of the fastest ways to test a debt schedule.

Many models avoid circular references by calculating interest on opening balances, or on average balances with a controlled switch. A circular reference can make a model unstable and hard to debug. Choosing one method and documenting it keeps the debt logic transparent for everyone who reviews the model later.

Debt schedule

Interest expense

Net income

Cash balance

How debt reaches cash

Methods

013

Driver Choices and Weight

Driver-based forecasting ties revenue and cost lines to a small set of operating drivers, such as growth rates, margins, receivable days and capital spending as a share of sales. Driver choice matters because it decides which numbers a reviewer will challenge. A model driven by unclear or hidden assumptions is hard to defend, even when its arithmetic is correct.

The bars below are illustrative. They show one hypothetical weighting of drivers in a forecast, where revenue growth carries the most influence and tax rate the least. The purpose is to help a builder ask which drivers deserve the most careful research. Real weights depend on the business, its industry and the decision at hand.

A short list of well explained drivers usually beats a long list of loosely justified inputs.

Good driver work keeps the list short. Each driver should be measurable, linked to the business, and easy to explain in a sentence. When a driver cannot be explained, it is often a sign that the model is adding complexity without adding insight.

Revenue growth

Gross margin

Days receivable

Capex share

Tax rate

Illustrative driver weighting (Illustrative)

Methods

014

A Valuation Work Sequence

A valuation project has a natural order. The analyst begins by gathering financial statements, market data and any deal information. Next comes the choice of method, which depends on the question, the data available and the company's stage. A mature business with stable cash flows may suit discounted cash flow, while a company with few comparable peers may lean on precedent transactions.

After the model is built, the analyst compares results across methods. Agreement between methods builds confidence, while large gaps call for explanation. A gap may reveal an aggressive forecast, an unusual peer group or a deal premium that does not apply to the current question. The comparison is often more informative than any single number.

Comparing methods side by side often reveals more about a valuation than any single result does.

The last step is the memo. It states the answer, the main assumptions, the range of outcomes and the sensitivities that matter most. A good memo is short enough to read in one sitting and specific enough that a manager can challenge it. The timeline shows this order from start to finish.

Gather data

Pick method

Build model

Compare results

Write memo

Valuation work sequence

Methods

015

Choosing a Forecast Approach

Forecasts can be built in several ways, and each has tradeoffs. A top-down forecast starts from a total market or total company figure and allocates it to lines. It is fast and useful for early screening, but it hides the operating logic. A bottom-up forecast builds from units, customers or contracts. It is more rigorous but takes longer and requires more data.

Driver-based forecasts sit between these two. They use a manageable set of operating drivers to link assumptions to outputs. They are flexible enough to support scenarios and detailed enough to show why results move. Many corporate models combine approaches, using top-down checks on a bottom-up build.

No single forecast approach is best everywhere, so the choice should follow the decision and the data available.

The matrix rates each approach on speed, rigor and flexibility. Ratings are relative. A top-down approach scores high on speed but low on rigor, while a driver-based approach balances all three. The right choice depends on the decision's stakes, the time available and the quality of the underlying data.

	Speed	Rigor	Flexibility
Top down	●●●	●	●
Bottom up	●	●●●	●●
Driver based	●●	●●●	●●●

Relative strengths of approaches

Methods

016

Checks That Catch Errors

Model checks are deliberate tests that confirm the model is internally consistent. A balance check confirms that the balance sheet balances in each period. A cash link check confirms that the cash flow statement ends at the balance sheet cash figure. A sign test confirms that outflows are negative where the design expects them to be, and that no cost has been entered as a gain.

Checks also cover the scenario switch. A reviewer should be able to move between cases and see the statements update without errors appearing. Version logs and peer review add human checks. A second builder reads the model cold, looking for logic that seems strange, even when the numbers pass every automated test.

A model with visible checks shows its own weaknesses, which is far more persuasive than a model that claims to be correct.

The mindmap lists the most useful checks. Each one is simple, and each catches a different class of mistake. Together they make the model's behavior visible, which is the foundation of trust with decision makers who did not build the model themselves.

Model
Checks

Balance
check

Cash link

Sign test

Scenario
switch

Peer
review

Version
log

Checks that catch errors

Applications

017

Decisions Modeling Supports

Corporate finance uses models to support three broad families of decisions. Investment decisions ask which projects or acquisitions to fund, and how their cash flows compare with the cost of capital. Financing decisions ask how much debt to carry, in what form, and what risk that adds. Payout decisions ask how much cash to return to owners through dividends or share repurchases.

The donut below is illustrative. It shows one hypothetical share of a finance team's modeling time across these decision families. Real splits vary by company, industry and season of the business cycle. The chart is a prompt for thinking about where a team's models are most needed, not a benchmark.

Investment, financing and payout decisions all reach the same three statements, so each must be modeled with the others in view.

Each decision family connects to the three statements. Investment changes capital spending and asset balances. Financing changes debt schedules and interest. Payouts reduce cash and equity. Seeing these links helps a learner explain how one choice affects the whole company, which is the core skill of corporate modeling.

Investment 40%
Financing 35%
Payout 25%

Illustrative decision modeling split (Illustrative)

Applications

018

Shared Skills Across Roles

Several finance roles draw on the same modeling core, even though their daily work differs. Corporate finance teams use models to evaluate projects and set capital plans. Investment banking teams use them to value companies and prepare deal analysis. FP&A teams use them to plan budgets and explain variances against forecast. The overlap is large, and workers who move between these areas often find their skills transfer well.

The venn diagram shows the shared center. Core skills include building linked statements, understanding valuation methods and presenting results clearly. Each role adds its own emphasis. Banking emphasizes transaction context, corporate finance emphasizes capital allocation, and FP&A emphasizes planning cadence and operating detail.

The strongest modeling skills are portable, because linking evidence to logic is valued in nearly every finance role.

Practitioners in each role also recognize the same warning signs: unclear assumptions, unreconciled totals and outputs that do not match the story. A professional who can name those signs, and fix them, earns credibility quickly. Modeling skill is portable because the discipline of linking logic and evidence is shared across industries.

Corporate
finance

Investment
banking

FP&A

Shared modeling skills across roles

Applications

019

Who Relies on the Model

A model usually serves several audiences, and each one needs a different level of detail. At the base is the source data from accounting systems, market feeds and contracts. Above it sits the management plan, which translates data into operating assumptions. The model output presents results in a form that managers can compare across options.

The pyramid places the board decision at the top, where a short summary and clear recommendation matter most. Lower layers hold the evidence that supports the summary. A board member rarely reads every formula, but should be able to trace the headline result back to a clear assumption and a clean source.

Decision makers trust a model when the headline result can be traced cleanly back to its sources and assumptions.

Analysts earn trust by respecting each audience. They keep the source layer traceable, they make management plans explicit, and they write outputs that answer the question a decision maker actually asked. When a summary and its evidence agree, the model becomes a shared tool rather than a private calculation.

Board decision

Management plan

Model output

Source data

Who relies on what

Applications

020

Keeping a Model Current

Models go stale when the business changes and the model does not. New contracts, cost shocks and altered financing terms can each make an old forecast misleading. Keeping a model current is therefore an on going discipline, not a one-time task. Teams that treat updates as routine find it easier to answer urgent questions quickly.

The cycle below describes a practical update routine. The team first updates inputs with new actuals or assumptions. It then reconciles the model to reported figures, so that historical periods still tie. Review follows, with a second person checking changed logic and new links. Finally the team communicates what changed and why.

Routine updates with reconciliation and review keep a model useful, and a change log keeps its history honest.

Communication closes the loop. A short change log shows which assumptions moved and how outputs responded. This lets decision makers see whether a new valuation reflects better evidence or simply a different input. Clear updates protect the model's credibility over time.

Update

Reconcile

Review

Communicate

Routine model update cycle

Applications

021

From Model to Recommendation

A model becomes useful when it leads to a recommendation. The process starts by framing the question precisely. Is the team asking whether to buy a business, whether to borrow for a plant, or whether to raise the payout? A vague question produces a model that answers nothing in particular. A precise question tells the builder which outputs and sensitivities matter.

Next the analyst builds a base case and tests the range around it. Downside and upside cases show how sensitive the recommendation is to key drivers. If the answer changes sign under a plausible downside, the memo should say so. Monitoring follows the decision, comparing actual results with the model's expectations and flagging drift early.

A recommendation should name its main risks and the signals that would change the view, not only the preferred outcome.

The process diagram shows these steps in order. Recommendation is the point where analysis meets judgment. A good recommendation names the decision, the reasons, the main risks and the signals that would change the view. Presenting the model as a tool for that judgment keeps the work honest and useful.

Frame question

Build case

Test range

Recommend

Monitor

From model to decision

Practice and Review

022

Practice Review Path

Learning this field works best as a review path rather than a list of facts. A learner can start with an assumption sheet, write down the source and range for each input, and then trace how those inputs reach the statements. Each step is small, but together they show the full logic of a corporate model.

The flow below gives a simple practice path. Start with assumptions, then build the model from them, review the links and checks, and finally write a decision note. Repeating this path on a few different companies builds judgment faster than memorizing formulas. The same questions return in each case: what drives value, what could go wrong, and what would change the answer.

Repeating the same questions on different models builds the judgment that separates a reliable analyst from a formula user.

Review also means reading other people's models critically. Ask whether the structure is clear, whether the checks are visible and whether the recommendation matches the evidence. A learner who can explain why a model should be trusted, or why it should not, has learned the central skill of the field.

Assumptions

Model

Review

Decision

Practice review path

Practice and Review

023

Common Errors to Avoid

Modeling errors tend to cluster in familiar places. Hardcoded numbers typed directly into formulas hide assumptions and break when inputs change. Broken links occur when a sheet points to the wrong row or an old version of a schedule. Sign errors flip the direction of cash flows, and timing mismatches place a cash item in the wrong period. Unit mismatches, such as thousands mixed with millions, can distort a whole valuation.

The bars below are illustrative. They show one hypothetical mix of errors found during a review, with hardcoded numbers ranked highest. The exact mix will differ by team and by model. The purpose is to encourage reviewers to look for each error type deliberately rather than trusting that a model is clean.

Most serious modeling errors come from a few predictable habits, so a short checklist catches many of them.

Prevention is simpler than repair. Keep inputs in one place, label units, use consistent formulas across each row, and run the checks described earlier. A reviewer who reads the model with a list of these error types will find more problems in less time than a reviewer who simply scans for obvious mistakes.

Hardcoded numbers

Broken links

Sign errors

Timing mismatch

Unit mismatch

Illustrative error mix (Illustrative)

Practice and Review

024

Closing Review Sequence

This ebook has moved from the purpose of modeling to the tools used in practice. Financial modeling turns a business story into connected forecasts, and corporate finance uses those forecasts to decide on investment, financing and payouts. The backbone is three linked statements with a schedule layer, and the quality of the result depends on clear, tested assumptions.

Before a model is released, it should pass a final review sequence. The draft is built and checked against its structure. A peer reviews the logic with fresh eyes. The model is stress tested under plausible downside cases. The final memo states the answer, its assumptions and its limits. After release, the team follows up as results arrive and updates its view.

A model earns trust through a clear structure, tested assumptions, visible checks and an honest account of its limits.

The timeline below summarizes that sequence. Each step protects the model's credibility, and each one is easier to complete when earlier steps were done carefully. A learner who can explain this sequence, and apply it on a real question, has a working grasp of corporate finance and financial modeling.

Draft model

Peer check

Stress test

Final memo

Follow up

Review cycle before release

References

025

References and Learning Sources

vaayaa References

vaayaa Editorial Team, vaayaa Sprouter discourses on Corporate Finance and Financial Modelinghttps://vaayaa.com/sprouter
vaayaa Research Desk, vaayaa News on Corporate Finance and Investment Advisoryhttps://vaayaa.com/news
vaayaa Subject Matter Review, vaayaa Sprouter discourses on Enterprise and Financial Risk Managementhttps://vaayaa.com/sprouter
vaayaa Research Team, vaayaa News on Financial Accounting and Bookkeepinghttps://vaayaa.com/news

Learning Sources

Micro Degree Corporate Finance and Financial Modelinghttps://vaayaa.com/course/corporate-finance-and-financial-modeling
Micro Degree Corporate Finance and Investment Advisoryhttps://vaayaa.com/course/corporate-finance-and-investment-advisory
Micro Degree Enterprise and Financial Risk Managementhttps://vaayaa.com/course/enterprise-and-financial-risk-management
Micro Degree Financial Accounting and Bookkeepinghttps://vaayaa.com/course/financial-accounting-and-bookkeeping
Micro Degree Financial Planning and Wealth Managementhttps://vaayaa.com/course/financial-planning-and-wealth-management

Corporate Finance and Financial Modeling Explained

What you will learn

Contents

What the Field Covers

Where Models Sit

Why Assumptions Drive Results

Who Uses Models

Three Valuation Lenses

Parts of Model Design

Where the Effort Goes

Linking Cash, Capital and Rates

Layers Beneath the Decision

The Model Improvement Loop

Building the Core Model

Connecting Debt to Cash

Driver Choices and Weight

A Valuation Work Sequence

Choosing a Forecast Approach

Checks That Catch Errors

Decisions Modeling Supports

Shared Skills Across Roles

Who Relies on the Model

Keeping a Model Current

From Model to Recommendation

Practice Review Path

Common Errors to Avoid

Closing Review Sequence

References and Learning Sources

vaayaa References

Further Reading

Learning Sources

More in Finance

Credit Analysis and Small Business Finance

Digital Banking and FinTech: A Practical Reference

Digital Payment Systems: How Money Moves Electronically

Enterprise and Financial Risk Management: A Working Guide