Lesson

Control ratio inputs before dividing

Turn a stack of statement amounts into an auditable comparison packet by aligning scope, time, definitions, units, basis, and stock versus flow denominators.

Updated Aug 7, 2026 Review due Nov 7, 2026
On this page
  1. What you will be able to do
  2. Give each input an identity
  3. Match time shapes
  4. Use articulation as an error detector
  5. Separate repairable differences from missing evidence
  6. Work the Beacon example
  7. Practice
  8. Exit check
About this lesson

Lesson details

Estimated study time
75 min
Learning objectives (6)

You receive a spreadsheet with Beacon's Year 5 net income, Harbor's ending assets, a column labeled “000s,” and no statement-version field. The formulas calculate. Should you use them?

No. The first analytical task is to establish what each number represents.

What you will be able to do

By the end of the lesson, you can build a source-to-ratio workpaper, diagnose entity, time, scale, definition, basis, and version mismatches, compute a beginning-ending average, and state when that approximation should be replaced or qualified.

The payoff arrives immediately in Beacon's denominator. Dividing $24,000 Year 5 income by $220,000 December 31 assets gives about 10.91%. Dividing by the declared $200,000 beginning-ending average gives 12%. Both divide correctly; only the second answers this module's period-return question. The input controls below explain which question a spreadsheet has actually computed.

Give each input an identity

Create one row per input before one column per ratio:

Field Required label
Amount Source value before display rounding
Entity Reporting entity and consolidation boundary
Time Period for flows; date for stocks
Units Currency, scale, sign convention
Definition Exact line, subtotal, or analyst-defined measure
Basis Accounting framework, policy, classification, and relevant scope
Version Original, amended, or restated statement
Locator Statement, note, schedule, dataset field, or stipulated fact

Accounting students may recognize this as a documentation control. Finance students may recognize it as data lineage. It is the same discipline: keep a claim connected to the evidence that produced it.

Match time shapes

An income statement covers a period. A balance sheet reports a date. Beacon's $24,000 net income spans Year 5; its $220,000 assets exist at December 31. This module pairs the flow with a beginning-ending average:

($180,000 opening assets + $220,000 ending assets) ÷ 2
= $200,000 average assets

The average is a convention, not a discovered fact about every day. It works as a bounded approximation because the packet excludes major midyear structural events. If an acquisition closed late in the year, monthly or transaction- weighted data might better answer the question. Obtain those observations and state the new convention; do not switch denominators silently.

An ending-balance denominator is not an arithmetic mistake. It is a different convention with a different time meaning. The defect arises when the analyst presents it as though it were the declared average-period measure or never states the choice.

Use articulation as an error detector

Both endpoint positions must satisfy the accounting equation. Equity should also reconcile:

$90,000 opening equity + $24,000 net income − $4,000 distributions
= $110,000 ending equity

The locator is not implicit: Beacon's equity_activity object in the Year 5 JSON packet supplies $24,000 net income, no owner contribution, and the $4,000 distribution. The opening and ending positions supply the two equity balances. Net income increases the accumulated performance component of equity; an owner distribution reduces equity outside net income. That is why both amounts belong in the bridge from opening to ending equity even though only one appears in the income statement.

A failed tie may reveal a missing owner contribution, translation adjustment, restatement, scope mismatch, or simple data error. It does not tell you which. Stop the affected conclusion until the difference is explained.

Separate repairable differences from missing evidence

You can convert thousands to whole dollars when the scale is documented. You can calculate adjacent averages when both endpoints are available. You cannot repair an unknown consolidation scope or an unidentified restatement version by assuming it matches.

Use three dispositions:

  • aligned: proceed under the declared convention;
  • adjusted with evidence: retain the transformation and original value;
  • not comparable: narrow or stop the claim and request the missing evidence.

“Not comparable yet” is a competent conclusion.

Work the Beacon example

Follow Align a period flow with average statement balances. The example computes $200,000 average assets, $100,000 average equity, 12% ROA, and 24% ROE. It also shows why ending-only alternatives answer a different measurement question.

Practice

Use Identify the controlled ratio input packet to select a ready source packet. Then solve Compute ROA from aligned average assets, which changes the company and amounts so the answer cannot be recalled from Beacon.

Exit check

A company reports annual net income in millions, beginning assets in whole USD from an originally filed statement, and ending assets in millions from a later restatement. Write the minimum repair plan before computing ROA. Name which facts can be transformed mechanically, which source version must be resolved, and one event that could make a two-point average unrepresentative.