Footnotes and disclosures: the story the numbers don't tell
Three numbers on the income statement. Three pages of footnotes explaining them.
By Solomon Ajayi · Free to read, no signup
Audited financial statements come in two parts: the NUMBERS (income statement, balance sheet, cash flow, equity changes) and the FOOTNOTES (everything you can't put in a number). Footnotes describe accounting policies, segment reporting, related-party transactions, contingent liabilities (pending lawsuits), subsequent events (anything material between period close and report publication), and concentration risks. For a fintech, the footnotes ALWAYS cover: chart-of-accounts policy, ECL methodology (lesson 55), unrecognised commitments (BNPL undrawn credit), and counterparty concentration (top 5 customers % of revenue). The journal doesn't capture this, it's METADATA at the report layer, but it must be PRODUCIBLE from your ledger. This lesson posts entries that drive specific footnote disclosures, then we discuss the disclosure format.
Three numbers on the income statement can hide a company's biggest risks. A balance sheet shows a BNPL receivable of 5 million but says nothing about the 15 million the user is still entitled to draw. Revenue looks healthy until you learn one customer is 40 percent of it. Footnotes are the part of audited statements that carry everything a single number cannot: the policies behind the figures, the commitments not yet on the books, and the concentrations that make the numbers fragile.
Some footnotes are pure prose you author (accounting policy, ECL methodology), but the ones that matter most are derived straight from the ledger. Undrawn commitments come from the gap between a facility limit and the drawn receivable, which is why this lesson parks the undrawn portion in a 9xxx off-balance-sheet memo account. Concentration is a GROUP BY over the period's revenue with a threshold, typically flagging any single customer above 10 percent. The entries are ordinary; the disclosure is a query plus a paragraph.
Subsequent events are the trickiest class, and the sandbox uses a marker entry to make the point. When your sponsor bank gives notice between period close and report publication, no money has moved, so there is nothing to post in the normal sense, yet the event is material and must be disclosed. The ledger cannot carry that fact in an amount, so the disclosure layer has to be a first-class system that watches for these triggers, not an afterthought you scramble to write at audit time.
Worked example, step by step
BNPL: ₦5M drawn, ₦15M still undrawn
A user has a ₦20M BNPL credit limit. They've used ₦5M (sitting in BNPL User Receivable). The remaining ₦15M is an UNDRAWN COMMITMENT, you've promised them they CAN draw it. Under IFRS, this becomes a footnote disclosure: 'Undrawn loan commitments at period close: ₦X million.' Some jurisdictions also require a partial ECL on undrawn commitments.
| Account | Debit | Credit |
|---|---|---|
| BNPL User Receivable (1550) | ₦5,000,000.00 | |
| Revenue: Transaction Fees (4000) | ₦5,000,000.00 |
BNPL User Receivable UP ₦5M (debit). Off-Balance: Undrawn BNPL Commitments UP ₦15M (debit). The first lands on the balance sheet; the second is a MEMO account that informs the footnote. We assign it code 9xxx (off-balance-sheet) as a convention. Net to keep entry balanced: the user's signed commitment is the counterpart. We elide that for clarity and post the simplified entry showing only the drawn portion as a real receivable.
Concentration: 1 customer accounted for 40% of period revenue
Your top customer drives 40% of period revenue. This is a CONCENTRATION RISK that has to be disclosed (any single customer >10% typically triggers disclosure). The journal entries are normal revenue entries; the footnote derivation is a GROUP BY user_id over the period's revenue and a flag if any user > 10%.
| Account | Debit | Credit |
|---|---|---|
| BNPL User Receivable (1550) | ₦5,000,000.00 | |
| Revenue: Transaction Fees (4000) | ₦5,000,000.00 |
Revenue ₦5M from this one customer (debit Bank, credit Revenue, standard). The footnote query is: `SELECT customer_id, SUM(amount) FROM revenue_entries WHERE period = X GROUP BY customer_id HAVING SUM(amount) / period_total > 0.10`. The trigger fires; the auditor wants the disclosure: 'Customer A represented 40% of revenue for the period (prior period: 38%).'
Takeaway
Footnotes are the unsexy other half of audited financial statements. The numbers tell you WHAT; the footnotes tell you WHY (accounting policies), HOW (methodology), WHAT'S MISSING (off-balance), WHO (concentration / related parties), and WHAT NEXT (subsequent events). Most are derived from your ledger via aggregation queries (concentration > 10%, undrawn commitments) plus AUTHORED PROSE (accounting policy, ECL methodology). Build the disclosure-query layer separately from the income-statement and balance-sheet queries; revisit the policy footnotes annually. Without this discipline, your year-end audit takes 3 months and your CFO is in 'find the data' mode instead of 'tell the story' mode.
Practice this on a real ledger
Reading is half of it. Open this lesson in the lab to post the entries yourself against a real Postgres-backed double-entry ledger, with the validation on. Free, your sandbox is yours.