FINANCE ACADEMY · INTERNAL TRAINING MANUAL

The Finance Controllership

& Record-to-Report
Handbook

How multinational companies actually execute R2R, Financial Reporting,

Controls, Month-End & Year-End Close, Balance Sheet Governance and
Finance Transformation.
A practical field manual for Financial Controllers, R2R Managers,
Corporate Accountants and Finance Transformation leaders.

Prepared for CA Kirankumar M · Financial Reporting · Financial Controls · IFRS · R2R

Table of Contents
How to Use This Handbook 2

PART I — FOUNDATIONS OF RECORD-TO-REPORT AND CONTROLLERSHIP 4

Chapter 1 — The Finance Function and the Record-to-Report Value Chain 5
Chapter 2 — The Chart of Accounts and General Ledger Architecture 10
Chapter 3 — Journal Entries and the Journal Lifecycle 14
Chapter 4 — Subledger-to-GL Reconciliation 19
Chapter 5 — Trial Balance Review and General Ledger Scrutiny 24

PART II — THE CLOSE 28

Chapter 6 — The Month-End Close 29
Chapter 7 — The Year-End Close 33
Chapter 8 — Consolidation 37
Chapter 9 — Financial Statement Preparation and Presentation 41

How to Use This Handbook

This is not an accounting textbook. There are already hundreds of good textbooks that will teach you what a
debit is, how to derive a deferred tax asset, or how to word an IFRS 15 disclosure. This handbook assumes
you already passed those exams. What it teaches is the thing no exam tests and no textbook explains properly:
how the finance machinery of a large multinational company actually runs, day after day, close after
close, and where a Controller has to place their hands to keep it running.

I have written it the way I would mentor a newly qualified Chartered Accountant who has just joined my
team. When you sit next to a good Controller for two years, you slowly absorb a set of instincts — why we
accrue this way and not that way, why the intercompany desk panics on Day 2, why the auditors always ask
for the same three reconciliations, why a “small” unreconciled balance is never small. This handbook tries to
transfer those instincts directly, in plain professional English, without hiding behind jargon.

Every chapter follows the same six-part rhythm so you always know where you are:

1. Introduction explains the concept from first principles — why the process exists at all, where it sits inside
Record-to-Report, and how it feeds the financial statements.

2. Detailed End-to-End Process walks the activity from the very first source transaction to final closure,
naming every team that touches it — Procurement, Sales, Treasury, Tax, Payroll, Fixed Assets, Product
Control, Business Finance, FP&A, Risk, Internal Audit, External Audit and Corporate Finance.

3. Practical Corporate Example drops you into a realistic multinational situation across different industries
and shows how an experienced Controller thinks it through.
4. Accounting Treatment gives you the journal entries, the debit/credit logic and the flow through the general
ledger, trial balance, balance sheet, P&L and cash flow — with IFRS, IAS, US GAAP, ASC and Ind AS
woven in where they change the answer, never taught as separate theory.

5. Practical Insights is the part you will re-read before an audit or a promotion: common mistakes, the
judgements management actually makes, control weaknesses, audit observations, root-cause analysis,
automation and AI use-cases, and the best practices I have seen work inside Fortune 500 finance teams.

6. Interview Preparation closes every chapter with graded questions — basic, intermediate, advanced,
scenario, behavioural, managerial, leadership and case-study — with model answers, what the interviewer is
really testing, and the mistakes candidates make.

Read it in order the first time. After that, keep it on your desk and jump to the chapter you need. The goal is
simple: by the end you should be able to walk into any large finance organisation, understand the close within
a week, and hold your own in front of the auditors, the CFO and an interview panel.

Let’s begin.

3
 The Finance Controllership & Record-to-Report Handbook

PART I — FOUNDATIONS OF RECORD-TO-REPORT

AND CONTROLLERSHIP

4
 The Finance Controllership & Record-to-Report Handbook

Chapter 1 — The Finance Function and the Record-to-Report

Value Chain

1. Introduction
Every company, whether it sells software in California or cement in Gujarat, has to answer one deceptively
simple question at the end of every month: how much did we earn, what do we own, what do we owe, and can
we prove it? Record-to-Report — almost always shortened to R2R — is the end-to-end business process that
produces that answer and stands behind it. When people outside finance hear “accounting,” they usually
picture someone typing journal entries. R2R is much larger than that. It is the entire chain that starts the
moment a business event occurs and ends when a complete, reconciled, reviewed and signed-off set of
financial statements is delivered to management, the board, auditors and regulators.

To understand where R2R fits, it helps to see the three great transactional cycles that feed every finance
organisation. The first is Order-to-Cash (O2C) — everything from a customer placing an order, to invoicing
them, to collecting the cash and recognising the revenue. The second is Procure-to-Pay (P2P) — everything
from raising a purchase order, to receiving goods or services, to booking the supplier invoice and paying it.
The third is Hire-to-Retire (H2R) — the payroll and people-cost cycle. These three cycles generate the raw
transactions. R2R is the cycle that sits downstream of all of them: it takes the millions of transactions those
cycles produce, makes sure they landed in the accounting records correctly, adds the entries that no transaction
system produces on its own (accruals, provisions, depreciation, revaluations, allocations, eliminations, tax),
reconciles everything, and turns it into financial statements. If O2C, P2P and H2R are the rivers, R2R is the
reservoir and the treatment plant that makes the water fit to drink.

Why does this process need to exist as a distinct, controlled discipline rather than just “adding up the ledger”?
Because the numbers a large company reports are relied upon by people who can never see the underlying
transactions — investors deciding whether to buy the stock, banks deciding whether to lend, tax authorities
assessing what is owed, employees whose bonuses depend on results, and a board that is legally accountable
for the accuracy of what is published. The entire edifice of capital markets rests on the assumption that
reported numbers are complete, accurate, valid and produced consistently period after period. R2R is the
machinery that earns that trust. When it fails — think of the great accounting scandals — it is almost never
because someone couldn’t do arithmetic; it is because the process of recording, reconciling, reviewing and
controlling broke down.

Within R2R sits the role this handbook is really about: the Financial Controller. If R2R is the machine, the
Controller is the chief engineer. The Controller owns the integrity of the general ledger, the discipline of the
close, the substantiation of the balance sheet, the design and operation of financial controls, and the quality of
what is reported. The Controller is not primarily forward-looking — that is FP&A’s world of budgets and
forecasts. The Controller is the guardian of what actually happened: the historical record, told accurately and
defensibly. A good CFO can raise capital and set strategy, but they can only do so standing on a foundation the
Controller has made solid.

2. Detailed End-to-End Process

Let me walk you through the full R2R chain the way it actually flows in a large multinational, because seeing
the sequence end-to-end is the single most useful mental model you can build early in your career.

5
 The Finance Controllership & Record-to-Report Handbook

It starts with a source transaction driven by a business event. Somebody sold something, bought something,
paid someone, received cash, consumed inventory, or signed a contract. That event is captured first in an
operational or subledger system — the billing system raises a customer invoice, the procurement system
records a goods receipt, the payroll engine calculates salaries, the fixed-asset register capitalises a new
machine. Each of these subledgers holds the transaction-level detail: which customer, which invoice number,
which cost centre, which asset. Supporting documents live here too — the signed contract, the delivery note,
the supplier invoice PDF, the bank statement. These documents are the evidence, and the entire control
philosophy of finance rests on the idea that every number in the ledger can be traced back to a document that
proves it.

From the subledgers, transactions flow — usually automatically through an interface, sometimes through a
batch upload — into the General Ledger (GL), which is the central accounting brain of the company, almost
always inside an ERP such as SAP, Oracle or PeopleSoft. The GL summarises everything into accounts
defined by the Chart of Accounts. At this point the company has a rough picture of its position, but it is not
yet a reliable one, because the subledgers only capture things that were physically transacted. They do not
know that a month’s rent has been consumed but not yet invoiced, that a factory machine lost a month of its
useful life, that a customer probably won’t pay 3% of the outstanding receivables, or that a court case might
cost money next year. These are the entries the R2R team must add during the close.

The close is the heartbeat of R2R. On a defined calendar — I will teach you to think in “workdays,” where
Workday 1 (WD1) is the first business day after month-end — the team performs a tightly sequenced set of
activities. Sub-ledgers are cut off and closed so no new transactions leak into the wrong period. Accruals are
booked for costs incurred but not yet invoiced. Prepayments are released as the periods they cover elapse.
Depreciation and amortisation are run. Provisions are assessed and adjusted. Foreign currency balances
are revalued to closing rates. Intercompany balances are matched and any mismatches chased down.
Allocations push shared costs out to the businesses that consumed them. Then every material balance sheet
account is reconciled — the GL balance is compared to independent supporting evidence and any difference
explained. The trial balance is reviewed for anything that looks wrong. Only then is the entity’s ledger
considered “closed.”

For a group with many legal entities, there is a further step: consolidation. Each entity’s closed trial balance is
translated into the group reporting currency, intercompany transactions between entities are eliminated so the
group doesn’t appear to trade with itself, minority interests are calculated, and the whole is rolled up into a
single set of consolidated financial statements — the income statement, balance sheet, cash flow statement,
statement of changes in equity and the notes. These are then subjected to review by senior finance, analytical
review to explain movements, and eventually external audit. Throughout, the process is wrapped in controls
— approvals, segregation of duties, reconciliations, review sign-offs — and evidence of those controls is
retained because auditors and, for listed companies, SOX will test them.

Notice how many teams touch this chain. Procurement and Accounts Payable feed P2P transactions and
accruals for goods received not invoiced. Sales and Accounts Receivable feed O2C and the provision for
doubtful debts. Treasury provides cash positions, FX rates, debt and interest data. Tax provides current and
deferred tax entries. Payroll feeds compensation costs. Fixed Assets teams run depreciation and
capitalisation. Product Control (in banks) validates daily P&L before it ever reaches the monthly ledger.
Business Finance and FP&A consume the results, explain variances and challenge the numbers. Risk and
Internal Audit test that controls worked. External Audit independently verifies the output. Corporate
Finance / Group owns consolidation and external reporting. The Controller sits at the centre of this web,

6
 The Finance Controllership & Record-to-Report Handbook

orchestrating the sequence, arbitrating disputes, and taking ultimate responsibility for the number that goes
out.

3. Practical Corporate Example

Consider a global consumer-goods company — call it NovaBrands — that sells across sixty countries,
manufactures in twelve, and runs its finance close out of a Global Capability Centre in Bangalore with local
Controllers in each region. In a single month, NovaBrands processes several million invoices, tens of
thousands of purchase orders, dozens of factory inventory movements per site, and payroll for forty thousand
people. No human being can look at all of that. The R2R process is precisely what makes it governable.

On WD1, the GCC team confirms that all subledgers have cut off cleanly — that the last of the month’s
shipments were invoiced in the right period and not spilled into the next. On WD2, the accruals team books an
estimate for the advertising campaign that ran in the last week of the month but for which the agency invoice
won’t arrive until the 15th of next month; without that accrual, the month would look artificially profitable
and the next month artificially poor. On WD3, depreciation runs across the fixed-asset registers of all twelve
factories. On WD4, the intercompany team matches the sale of finished goods from the Polish factory to the
German sales company and finds a €400,000 mismatch — Poland booked the sale but Germany hasn’t yet
booked the purchase because the goods are still in transit. They resolve it with an in-transit entry rather than
letting it distort the consolidation. By WD5 the balance sheet reconciliations are being reviewed by the local
Controller, and by WD6 the consolidated pack is with the Group CFO. Every one of those steps exists because
a specific thing would otherwise go wrong. That is the mindset I want you to build: for every activity in the
close, be able to say what breaks if it isn’t done.

4. Accounting Treatment
At this foundational level the “accounting treatment” is the architecture itself. Every transaction in R2R obeys
double-entry: total debits equal total credits, always, without exception, and the trial balance is simply the
proof of that equality — a listing of every account with its debit or credit balance, which must sum to zero (or,
presented differently, where total debits equal total credits). The GL feeds two primary statements. Balances in
asset, liability and equity accounts carry forward period to period and form the balance sheet. Balances in
income and expense accounts are closed out to retained earnings at year-end and, during the year, form the
profit and loss account. The cash flow statement is derived — under the indirect method — by starting from
profit and adjusting for non-cash items (depreciation, provisions) and movements in working capital, all of
which come from comparing this period’s balance sheet to last period’s.

The chain of impacts is worth memorising as a reflex. A single accrual for unbilled advertising, say
$1,000,000, is booked as Debit Advertising Expense (P&L) $1,000,000 / Credit Accrued Liabilities
(Balance Sheet) $1,000,000. The P&L takes the cost in the correct period (matching principle). The balance
sheet shows the obligation. The cash flow statement, indirect method, adds the accrual back as a non-cash
working-capital movement because no cash has yet left. When the invoice arrives next month and is paid, the
accrual reverses and cash falls. This single example contains the whole logic of accrual accounting, and every
close is thousands of variations on it. The relevant standards — IAS 1 for the presentation of the statements,
the accrual and going-concern assumptions embedded in the IFRS Conceptual Framework, and their US
GAAP equivalents — are not abstractions; they are the rules that decide when and how much of each of these
entries you book.

7
 The Finance Controllership & Record-to-Report Handbook

5. Practical Insights
The most common conceptual mistake I see in new joiners is treating the close as a data-entry exercise rather
than an assertion exercise. When you sign off an account, you are asserting that it is complete (nothing
missing), accurate (correctly valued), valid (nothing that shouldn’t be there), and properly cut off (in the right
period). Interviewers and auditors both love these financial-statement assertions — completeness, existence,
accuracy, valuation, rights and obligations, cut-off, presentation — because they are the language in which
control failures are diagnosed. Learn them early.

The second insight is about standardisation. In a multinational running its close from a shared-service centre,
the single biggest driver of quality is not clever people; it is consistent process. If forty entities each close their
own way, the group can never trust the aggregate. Fortune 500 finance functions therefore invest enormously
in a global close calendar, standard journal templates, a harmonised chart of accounts, and a single
reconciliation platform such as BlackLine. When I have led transformations, the biggest gains never came
from technology alone; they came from first standardising the process so the technology had something clean
to automate. Automate a mess and you get an automated mess, faster.

The third insight is where automation and AI genuinely help. Modern close platforms auto-certify low-risk
reconciliations (zero-balance or fully-matched accounts), use rules and increasingly machine learning to flag
anomalous journals, and provide real-time close dashboards so the Controller can see on WD3 which of forty
entities are behind. AI is now being used to draft variance commentary, to match intercompany transactions
probabilistically, and to read supplier invoices for accrual estimation. But — and I will repeat this throughout
the book — none of it removes the Controller’s judgement or accountability. The machine proposes; the
Controller disposes.

6. Interview Preparation
Basic — “What is Record-to-Report?” A strong answer defines R2R as the end-to-end process of capturing
financial transactions, processing them through the general ledger, closing the books, reconciling accounts and
producing reported financial statements, and crucially positions it downstream of the O2C, P2P and H2R
transactional cycles. Weak candidates describe only journal entries; the interviewer is testing whether you see
the whole value chain.

Intermediate — “Walk me through what happens between a business event and a number appearing in
the financial statements.” Trace it: source transaction in a subledger with supporting documents → interface
to the GL under the chart of accounts → period-end adjustments (accruals, depreciation, provisions, FX,
allocations) → reconciliation and trial-balance review → consolidation and elimination → statements and
disclosure → review and audit. The interviewer wants to hear the sequence and the controls along the way.

Advanced — “Where in the R2R chain is financial-statement risk highest, and why?” A mature answer
points to the manual, judgemental steps — top-side adjustments, provisions and estimates, intercompany, and
cut-off — because these are where management judgement enters and where controls are hardest to automate,
and links this to the assertions (completeness and valuation especially) and to where auditors focus.

Scenario — “You join a group where forty entities each close differently and the consolidation takes
fifteen workdays. What do you do first?” Don’t jump to technology. Say you would first map the current
close, standardise the calendar and chart of accounts, harmonise reconciliation and journal standards, then
layer automation — and you’d sequence entities by materiality and risk. This shows you understand that
process precedes tooling.

8
 The Finance Controllership & Record-to-Report Handbook

Behavioural (STAR) — “Tell me about a time you improved a close.” Situation: the close ran to WD8 with
frequent restatements. Task: I was asked to bring it to WD5 without adding headcount. Action: I mapped every
task to a workday, moved reconciliations to a continuous “hard-close-light” model, automated the low-risk
certifications in BlackLine, and instituted a daily stand-up during close. Result: we hit WD5 within two
quarters, cut post-close adjustments by 60%, and freed the team for analysis. Keep it specific and quantified.

Managerial / Leadership — “How do you ensure quality across a close run by a shared-service centre in
one country and Controllers in another?” Talk about clear RACI and hand-offs, a single close calendar
with owners and deadlines, standard templates, exception-based review, escalation paths, and a culture where
the SSC is treated as a partner accountable for quality, not a low-cost typing pool. The interviewer is testing
whether you can run a distributed operation, which is the reality of every large finance function today.

Case study — “Design the target-state close for a newly merged group of two companies on different
ERPs.” Structure your answer around people, process, technology and data: a unified close calendar and
policy, a mapped/harmonised chart of accounts, an interim consolidation tool while the ERPs are rationalised,
standardised reconciliations, and a phased migration plan with UAT. What impresses is not a perfect answer
but a structured, sequenced, risk-aware one.

9
 The Finance Controllership & Record-to-Report Handbook

Chapter 2 — The Chart of Accounts and General Ledger

Architecture

1. Introduction
If Record-to-Report is the machine, the Chart of Accounts (COA) is the blueprint that determines what the
machine can and cannot do. The COA is the structured list of every account into which the company records
its transactions — every asset, liability, equity, income and expense line. It sounds like a boring housekeeping
list, and new joiners often treat it that way, but I want you to understand something that took me years to fully
appreciate: almost every reporting limitation, every painful manual workaround at close, and every “we can’t
get that number out of the system” complaint traces back to a chart of accounts that was designed badly or
has been allowed to decay. The COA is the foundation. Get it right and reporting becomes almost effortless;
get it wrong and you will spend the rest of the entity’s life patching around it in spreadsheets.

The General Ledger is the master accounting record that uses the COA. Every subledger transaction, every
manual journal, every automated posting eventually lands in the GL, summarised into COA accounts and
tagged with a set of dimensions that tell you not just what the amount is but where it belongs — which legal
entity, which cost centre, which profit centre, which geography, which product. In a modern ERP the GL is not
a single flat list; it is a multi-dimensional structure often called an account coding block or chart of accounts
string. Understanding that structure is understanding how a large company can slice its results forty different
ways from the same underlying data.

Where does this fit in R2R? The COA and GL are the substrate on which everything else runs. The close posts
into it, reconciliations reconcile it, the trial balance is extracted from it, consolidation rolls it up, and financial
and management reporting are just different views of it. When I interview candidates for controllership roles,
one of my favourite tests is to ask them to design a chart of accounts for a simple business, because it instantly
reveals whether they understand how reporting really works or whether they only know how to pass exam
entries.

2. Detailed End-to-End Process

Let me explain the anatomy of a modern chart of accounts, because this is where the real learning is. A well-
designed COA in a large ERP is not one dimension (the “natural account”) but several segments or
dimensions, each answering a different question about a transaction. The natural account answers what — is
this revenue, salaries, trade receivables, accrued liabilities? The cost centre answers who is responsible — the
department or team that owns the cost. The profit centre or business unit answers which part of the business
earned or spent it. The legal entity / company code answers which statutory entity the transaction belongs to,
which matters enormously because each legal entity files its own statutory accounts and tax returns. Further
segments often capture geography/region, product or service line, project or WBS element, intercompany
trading partner, and future/spare segments held in reserve. In SAP you will hear this as the interplay of
company code, GL account, cost centre, profit centre and the controlling area; in Oracle as the accounting
flexfield with its segments; in PeopleSoft as ChartFields. The vocabulary differs but the concept is identical: a
transaction is coded to a combination of dimensions, and reporting is the act of aggregating along whichever
dimension you care about.

Now, how does the COA get built and maintained end to end? At design time — typically during an ERP
implementation or a transformation — the finance team defines the segment structure, the length and
numbering logic of each segment, and the validation rules that decide which combinations are allowed (you

10
 The Finance Controllership & Record-to-Report Handbook

don’t want someone posting depreciation to a revenue account). Numbering is deliberate: assets might be
1xxxxx, liabilities 2xxxxx, equity 3xxxxx, revenue 4xxxxx, cost of sales 5xxxxx, operating expenses 6xxxxx,
and so on, so that a human or a report can group by the first digit. Ranges are left as gaps for future accounts.
This is boring and it is critical.

Once live, the COA becomes a governed master-data object. New accounts are not created casually. A
request goes through a master-data management process — usually a form, an owner (often a COA
governance team or the Controller’s office), a review of whether an existing account already covers the need,
and an approval. Uncontrolled COA growth is one of the quiet killers of finance quality: I have inherited
charts with eight different “miscellaneous expense” accounts created by eight different people, none of which
anyone can explain, all of which the auditors flag. Governance also covers mapping: the local statutory COA
of each entity must map to the group COA used for consolidation, and often to a tax chart and a regulatory
chart as well. A single transaction in Germany might roll up one way for German statutory accounts (HGB),
another way for group IFRS reporting, and yet another for the tax return. The mapping tables that connect
these are among the most important — and most fragile — pieces of finance infrastructure.

Every day, transactions post into the GL from three sources: automated subledger interfaces (AP, AR, fixed
assets, payroll, inventory), recurring/automated journals (depreciation, standard accruals, allocations), and
manual journals posted by accountants. Each posting is validated against the COA rules — is this a valid
account? a valid combination? within an open period? properly balanced? The GL then maintains, for every
account-dimension combination, an opening balance, period movements and a closing balance. At period
end these balances are frozen, the period is closed in the ERP so nothing further can post to it, and the trial
balance — the complete list of closing balances — is extracted for reconciliation, review and consolidation.

Which teams touch this? Master-data / COA governance owns account creation and mapping. The
Controller’s office owns the design and the policy. IT / ERP teams implement segment structures and
validations. Every transactional team codes their transactions to the COA. Consolidation / Group owns the
group COA and the mapping. Tax owns the tax chart mapping. And auditors test whether the COA is
controlled and whether mappings are complete and accurate.

3. Practical Corporate Example

I once took over as Controller of a technology group that had grown by acquisition. It had bought six
companies in five years and, to “move fast,” had simply bolted each one’s chart of accounts onto the
consolidation with a hand-built mapping spreadsheet. The result was predictable. The group had over 4,000
active GL accounts, of which perhaps 1,500 were genuinely needed. Three different acquired entities each had
their own “consulting revenue” account with different numbers, so pulling total consulting revenue for the
group meant manually summing three accounts and hoping no one had posted to a fourth. The monthly
mapping spreadsheet had grown to 12,000 rows and was maintained by one analyst; when she went on leave,
the consolidation broke.

The fix was a chart-of-accounts rationalisation, and it is a good illustration of how a Controller thinks. We did
not start by deleting accounts — that would have destroyed comparability and broken interfaces. We started
by defining a clean target group COA with a disciplined segment structure, then built a many-to-one
mapping from every legacy account into it, reviewing each mapping with the local Controllers so nothing was
silently misclassified. We froze the creation of new accounts under a tightened governance process. We moved
the mapping out of the fragile spreadsheet into the consolidation tool’s managed mapping tables with version
control and audit trail. Over two quarters, group accounts fell to around 1,800, the consolidation time dropped

11
 The Finance Controllership & Record-to-Report Handbook

by three days, and — the part the CFO cared about — we could finally answer “what did we spend on X
across the group?” in one query instead of a two-day reconciliation. Nothing about that project was
glamorous. All of it was foundational.

4. Accounting Treatment
The COA doesn’t itself generate journal entries, but it governs every journal entry, and understanding its
impact on the statements is essential. The first digit or range of the natural account determines which primary
statement the balance flows to: asset, liability and equity accounts (typically ranges 1–3) accumulate on the
balance sheet and carry forward each year; income and expense accounts (ranges 4 and above) accumulate in
the P&L and are closed to retained earnings at year-end through the closing process. The dimensions
determine the reporting cuts: aggregating by cost centre gives you departmental cost reports, by profit centre
gives you business-unit P&Ls, by legal entity gives you the statutory trial balances that feed each entity’s
financial statements, and by group account gives you the consolidated numbers.

A concrete illustration of why coding discipline matters: suppose an accountant posts a marketing agency
accrual of $200,000 but codes it to the wrong cost centre — say, the finance department’s rather than
marketing’s. The company-level P&L and balance sheet are perfectly correct; total expense and total accrued
liability are right, and the auditor sees nothing wrong at the statutory level. But the marketing director’s
management report is understated by $200,000 and the finance director’s is overstated, variance analysis
throws a false flag, and someone spends half a day chasing a “cost overrun” that is really a miscoding. This is
the essence of why the COA matters: the statutory numbers can be right while the management numbers
are wrong, and the difference is entirely a function of coding discipline. Standards such as IAS 1 govern how
the aggregated statements are presented (current vs non-current, nature vs function of expense), but the COA
is what makes that presentation mechanically possible — you present expenses “by function” only if your
COA lets you separate cost of sales from distribution from administration.

5. Practical Insights
The classic mistakes are worth naming. Overloading the natural account with dimension information —
creating separate accounts like “Salaries – London” and “Salaries – Mumbai” instead of one salaries account
with a geography dimension — bloats the COA and makes it rigid. Location belongs in a segment, not in the
account name. Uncontrolled account proliferation, where anyone can create an account, produces the
duplicate-and-orphan mess I described. Weak mapping governance between local and group charts causes
consolidation errors that are extremely hard to find because each individual entity looks fine. “Dump”
accounts — miscellaneous, suspense, clearing accounts left uncleared — are where errors hide; auditors go
straight to them, and a well-run shop keeps suspense and clearing accounts at or near zero at every close.

Management judgement enters mostly at design: how granular should the chart be? Too coarse and you can’t
analyse; too fine and you drown in accounts nobody maintains. The art is to push detail into dimensions
(which are flexible and reportable) and keep the natural account list lean and stable. Control weaknesses that
auditors and SOX testers look for include the ability to post to both sides of a clearing account without review,
unrestricted account combinations, and mappings that aren’t independently reviewed. Automation and AI now
help by detecting likely-miscoded transactions (a machine-learning model can learn that “agency” invoices
usually hit marketing, not finance, and flag exceptions), by auto-suggesting the correct account during invoice
coding, and by continuously monitoring for new or dormant accounts. The best-practice Fortune 500 pattern is
a single global COA with strong central governance, local statutory extensions mapped centrally, and
clearing/suspense accounts monitored at every close.

12
 The Finance Controllership & Record-to-Report Handbook

6. Interview Preparation
Basic — “What is a chart of accounts and why does it matter?” Define it as the structured list of accounts
used to record and organise all financial transactions, and stress that its design determines what the company
can report and how easily. Mention the account categories and the balance-sheet-versus-P&L split.

Intermediate — “What are the segments or dimensions of a modern chart of accounts, and what does
each do?” Natural account (what), cost centre (who is responsible), profit centre/business unit (which part of
the business), legal entity (which statutory reporter), plus geography, product, project and intercompany
partner. Show you understand that reporting is aggregation along a dimension.

Advanced — “How do local statutory, group, and tax charts of accounts relate, and where does risk
arise?” Explain the mapping from local statutory COAs to a group COA for consolidation and to a tax chart
for returns, and locate the risk in incomplete or inaccurate mappings that leave each entity looking correct
while the consolidation is wrong — a completeness and classification risk that is hard to detect.

Scenario — “You inherit a group with 4,000 accounts and a 12,000-row mapping spreadsheet
maintained by one person. What do you do?” Walk through the rationalisation approach from the example:
define a clean target COA, build and review mappings rather than deleting, tighten governance, move
mapping into a controlled tool, and sequence by materiality — never a big-bang deletion that breaks
comparability and interfaces.

Behavioural (STAR) — “Tell me about a time poor master data caused a reporting problem.” Use the
acquisition example or your own: describe the symptom (couldn’t get a clean group number), the root cause
(duplicate accounts, fragile mapping), your action (rationalisation and governance), and the result (fewer
accounts, faster close, reliable reporting).

Managerial — “How would you govern the chart of accounts across thirty countries?” Central
ownership of the global COA, a formal master-data request-and-approval process, local statutory extensions
mapped centrally, periodic reviews for dormant and duplicate accounts, and clear policy on suspense/clearing
accounts. The interviewer wants evidence you can impose discipline across a federated organisation.

Case study — “Design a chart of accounts for a company that manufactures in three countries and sells
through both retail and e-commerce.” Show the segment thinking: natural account, legal entity per country,
cost centre for departments, profit centre or channel (retail vs e-commerce), product line, and geography —
with intercompany partner to handle inter-factory trade. Explain how each management and statutory report
falls out of aggregating those dimensions. What impresses is that you separate account from dimension
cleanly.

13
 The Finance Controllership & Record-to-Report Handbook

Chapter 3 — Journal Entries and the Journal Lifecycle

1. Introduction
The journal entry is the atom of accounting. Everything a company reports is ultimately built from journal
entries, and yet the journal entry is also where most of the real risk in financial reporting lives. That sounds
contradictory until you understand the distinction between two kinds of journals. The vast majority of entries
in a large company are system-generated — the billing system posts revenue and receivables automatically,
the AP system posts expenses and payables, payroll posts salaries. These flow through validated interfaces, in
high volume, and while they can be wrong, they are wrong in systematic ways that controls over the source
systems catch. The dangerous journals are the manual journals — the ones a human being types directly into
the general ledger to record something no system knows about, or to correct something a system got wrong.
When you read about accounting frauds and restatements, the instrument of the crime is almost always a
manual top-side journal, posted late in the close, to an account that isn’t reconciled, with a vague description.
This is why external auditors, under standards like ISA 240, are required to test manual journals for signs of
management override. As a Controller, you must treat every manual journal as a small assertion you are
personally standing behind.

Where does this fit in R2R? Journals are the mechanism of the entire close. The accruals, provisions,
depreciation, revaluations, allocations, reclassifications and corrections I described in Chapter 1 are all journal
entries. Learning to prepare, support, review and control journals well is, in a very real sense, learning
controllership. Your resume, Kiran, lists posting journals for “revenue, costs, accruals, provisions, and
reclassifications” — that single line describes the core daily work of a close accountant, and this chapter
unpacks everything a Controller needs to know behind it.

2. Detailed End-to-End Process

Let me walk the full lifecycle of a manual journal in a large company, because the discipline around it is a
microcosm of good controllership.

It begins with a trigger — a business reason for the entry. Perhaps the utilities invoice for the last month
hasn’t arrived (accrual), perhaps an annual insurance premium was paid upfront and must be spread
(prepayment), perhaps a cost was booked to the wrong cost centre (reclassification), perhaps a legal claim now
needs providing for (provision). The accountant preparing the journal first establishes the basis and support:
what is the amount, how was it calculated, and what evidence supports it? For an accrual it might be a
supplier’s rate card and the known consumption; for a provision, a legal opinion and a management estimate;
for a reclassification, the original miscoded transaction. This supporting documentation is not optional
paperwork — it is the journal. A number without support is not an accounting entry; it is a guess, and an
auditor will treat it as one.

The accountant then prepares the journal on a standard template — increasingly within a workflow tool such
as BlackLine Journals, SAP’s journal workflow, or Oracle’s — specifying the accounts to debit and credit,
the amounts, the entity, the period, a clear narrative description (a good description says what, why and the
basis, e.g. “Accrual for March electricity — Plant 12, based on Feb actuals of $48k pro-rated for meter
reading period, invoice expected 15 Apr”), and whether the entry is a one-time posting or a reversing accrual
that will automatically reverse next period. The choice of reversing versus non-reversing matters enormously:
accruals for costs that will be invoiced next month should auto-reverse so the invoice, when it lands, doesn’t
double-count; a genuine one-off correction should not reverse.

14
 The Finance Controllership & Record-to-Report Handbook

The journal then goes for review and approval. This is the beating heart of journal control: the person who
prepares a journal must not be the person who approves it. This segregation of duties — maker versus
checker — is a foundational control, tested under SOX and by every internal audit. The reviewer’s job is not
to rubber-stamp; it is to challenge the basis, confirm the support is adequate, check the accounts and period are
correct, and satisfy themselves the entry is complete and accurate. Approval limits are usually tiered by
amount — a $5,000 accrual might need a team-lead’s approval, a $5,000,000 provision the Controller’s or
CFO’s. Only after approval does the journal post to the GL, at which point it updates account balances, feeds
the trial balance, and becomes part of the permanent record with an audit trail showing who prepared, who
approved, and when.

After posting comes review in context: the entry’s effect shows up in the trial-balance review and, if it hit a
balance sheet account, in that account’s reconciliation, where it must be explained. This closes the loop — a
journal is not truly “done” until the balance it created or moved has been substantiated. Exception handling
covers rejected journals (sent back to the preparer with comments), late journals (posted after the initial close
and requiring re-run of dependent reports), and error corrections. At period end, the population of manual
journals is itself reviewed — how many, by whom, to which accounts, how many were late, how many
reversed — because the pattern of journals is a powerful control indicator.

The teams involved span the whole finance organisation. Close accountants / R2R prepare the bulk of
manual journals. Team leads and Controllers review and approve. Business Finance and FP&A often
request reclassifications and challenge accruals. Tax posts tax journals. Treasury provides data for interest
and FX journals. Internal Audit samples journals to test controls, and External Audit independently selects
journals — especially large, round-number, period-end, or unusual-account entries — to test for override and
error.

3. Practical Corporate Example

In a global bank’s product-control environment — precisely the world you have worked in — journals take on
an added dimension because they often adjust trading P&L and balance sheet positions that move daily.
Imagine the Daily P&L validation flags that a trading desk’s reported income is €2.1m higher than the
independent price-tested valuation supports, because a trade was booked at an off-market rate. Product
Control raises a P&L adjustment journal to bring the reported figure in line with fair value, debiting trading
income and crediting a valuation-adjustment liability, with the trade reference, the independent price source
and the variance calculation as support. That journal is reviewed by a senior in Product Control, approved, and
posted. It will then appear in the month-end Subledger-to-GL reconciliation and in the balance sheet
substantiation of the valuation-adjustment account.

Now contrast that disciplined entry with the classic failure. In many restatement cases, a manual journal was
posted late in the close, to a rarely-reviewed suspense or “other” account, with a description like “adjustment
per management,” no independent support, and prepared and approved by the same senior person because
“there wasn’t time for review.” Every one of those attributes — late, unreconciled account, vague narrative, no
support, no segregation — is a red flag, and an experienced Controller learns to smell them. The lesson I drill
into every team: the quality of your journals is the quality of your ledger. A clean journal population with
good support, real segregation, and few late entries is the single best sign of a healthy close.

15
 The Finance Controllership & Record-to-Report Handbook

4. Accounting Treatment
Journals are where debit/credit logic becomes concrete, so let me anchor the reflexes. The immovable rule: for
every journal, total debits equal total credits. Beyond that, the direction depends on the account type. Debits
increase assets and expenses and decrease liabilities, equity and income; credits do the reverse. A few of the
most common close journals, with their statement impact:

An accrual for services received not yet invoiced: Dr Expense (P&L) / Cr Accrued Liabilities (Balance
Sheet). It increases cost and recognises an obligation, and typically auto-reverses next period when the invoice
posts.

A prepayment at payment, then its release: at payment, Dr Prepaid Asset (BS) / Cr Cash (BS); each month,
Dr Expense (P&L) / Cr Prepaid Asset (BS) to consume the portion used. The P&L takes the cost evenly over
the benefit period rather than all at once.

A provision under IAS 37: Dr Expense (P&L) / Cr Provision liability (BS) when a present obligation of
uncertain timing or amount arises from a past event and an outflow is probable and estimable. Utilisation later
is Dr Provision / Cr Cash with no further P&L hit.

A reclassification moves an amount without touching profit if within the same statement, e.g. Dr Distribution
costs / Cr Administrative expenses to correct a miscoding — total P&L unchanged, presentation corrected.

A depreciation journal: Dr Depreciation expense (P&L) / Cr Accumulated depreciation (BS, contra-asset).

The cash flow impact of most accrual-type journals is nil at posting (they are non-cash) — under the indirect
method they appear as working-capital or add-back adjustments and only affect cash when they later settle.
The relevant standards decide whether and how much: IAS 37 governs provisions and stops companies
smoothing profits with excessive “big bath” provisions; the accrual and matching concepts in the Conceptual
Framework govern accruals and prepayments; IAS 8 governs how you correct a prior-period error
(retrospective restatement) versus a current-period estimate change (prospective) — a distinction interviewers
love to probe.

5. Practical Insights
The most common practical mistakes: entries with weak or no support (“I’ll attach it later” — later never
comes); poor narratives that a reviewer or auditor six months on cannot decode; accruals that don’t reverse
(causing double-count when the invoice lands) or that reverse when they shouldn’t; round-number “plug”
journals that force a balance to agree without understanding why it didn’t; and posting to suspense or
clearing accounts and never clearing them. Each of these is both an error risk and an audit finding.

The judgement in journals is mostly estimation — how much to accrue, how large a provision, whether a
receivable is impaired. Good Controllers document the basis of every estimate so that next period they can
true it up and explain the movement; the discipline of estimate-then-true-up, with the variance analysed, is
what separates a controlled close from a hopeful one. Control weaknesses auditors look for: self-approval
(maker=checker), approval limits not enforced by the system, manual journals to automated/subledger-
controlled accounts (a journal straight into receivables, bypassing the AR subledger, is almost always
wrong), and high volumes of late or post-close journals, which signal an out-of-control process.

This is one of the richest areas for automation and AI. Recurring journals (standard accruals, allocations,
depreciation) should be automated so humans only touch exceptions. Journal workflow tools enforce
segregation, approval limits, mandatory support attachment and reversal logic automatically. AI is

16
 The Finance Controllership & Record-to-Report Handbook

increasingly used to score journals for risk — flagging unusual accounts, round numbers, weekend or after-
hours postings, entries just under approval thresholds, or preparers acting outside their normal pattern —
which is exactly how a modern internal audit function focuses its testing. The best-practice Fortune 500 target
is that manual journals are a small, well-supported, fully-segregated minority of all postings, every one
traceable to evidence, with the recurring bulk automated and the exceptions scored by machine and reviewed
by humans.

6. Interview Preparation
Basic — “What makes a good journal entry?” Correct accounts and amounts, balanced debits and credits,
correct entity and period, a clear narrative stating what/why/basis, adequate supporting documentation, correct
reversing/non-reversing treatment, and proper preparer-and-independent-approver segregation.

Intermediate — “Walk me through the difference between an accrual and a provision, with entries.” An
accrual is for a known cost of goods/services received but not yet invoiced, fairly certain in amount (Dr
Expense / Cr Accruals, usually reversing). A provision (IAS 37) is a liability of uncertain timing or amount
arising from a present obligation from a past event, probable and estimable (Dr Expense / Cr Provision).
Interviewers test whether you grasp the certainty spectrum and the standard.

Advanced — “Why do external auditors specifically test manual journal entries, and what attributes
make a journal high-risk?” Because management override of controls is a primary fraud risk (ISA 240), and
manual journals are its main instrument. High-risk attributes: posted late in or after the close, to suspense/
other/unreconciled accounts, round numbers, weak or missing support, vague narratives, preparer=approver,
amounts just below approval thresholds, unusual timing. Naming these shows real control literacy.

Scenario — “During close you find a $3m journal posted to ‘other liabilities’ with the description ‘per
management’ and no attachment, prepared and approved by the same manager. What do you do?”
Don’t accuse — investigate. Obtain the basis and support, understand the business rationale, confirm whether
it’s a valid estimate or an error/override, check the account is reconciled, and escalate through the proper
channel if support can’t be produced. Emphasise segregation must be restored. This tests judgement and
integrity together.

Behavioural (STAR) — “Tell me about a time you improved journal quality or timeliness.” Kiran, your
own history fits perfectly: Situation — journals were being finalised at M+4, delaying reporting. Task —
accelerate to M+1/M+2 without losing control. Action — standardised templates, automated recurring
accruals, tightened support and reversal discipline, and sequenced preparation earlier in the close. Result —
journal prep moved to M+1/M+2, faster management reporting, no increase in errors.

Managerial — “How do you control journals across a shared-service centre posting for many entities?”
Standard templates, a workflow tool enforcing segregation and approval limits, mandatory support, a policy
on reversing entries, and monthly metrics on journal volumes, late journals, rejections and self-approvals —
reviewed and acted upon. Show you manage by exception and by data.

Leadership — “How do you build a culture where people don’t cut corners on journal support under
close pressure?” Set the tone that an unsupported number is not acceptable regardless of deadline, make good
support faster than bad support through templates and automation, recognise clean journal populations in
reviews, and never personally approve a journal you can’t explain — because the team copies the leader’s
standard, not the policy document.

17
 The Finance Controllership & Record-to-Report Handbook

Case study — “Design the journal-entry control framework for a new finance shared-service centre.”
Cover: standard chart of journal types, template and support standards, a workflow tool with enforced maker-
checker and tiered approval limits, automation of recurring journals, a policy distinguishing reversing from
non-reversing, restrictions on manual postings to subledger-controlled accounts, retention of audit trail, and a
monthly journal-analytics pack (volumes, timeliness, self-approvals, risky attributes) feeding continuous
improvement.

18
 The Finance Controllership & Record-to-Report Handbook

Chapter 4 — Subledger-to-GL Reconciliation

1. Introduction
If there is one control that defines whether a large finance organisation is genuinely in control of its numbers,
it is the subledger-to-general-ledger reconciliation. Kiran, this is the control at the centre of your career —
reducing “reconciliation breaks by 70%” is the headline of your resume — so I am going to treat it in depth,
because if you can explain this process with authority you can hold any controllership interview.

Let me start from first principles. A subledger is a detailed record of a particular category of transactions: the
accounts receivable subledger lists every open customer invoice; the accounts payable subledger every open
supplier invoice; the fixed-asset subledger every asset and its depreciation; and, in a bank, a product
processor or risk/analytics hub (in Standard Chartered’s world, the “RAH”) holds every trade, position and
its valuation. The general ledger holds only the summarised balance for each account — total receivables,
total payables, total trading assets. In a well-functioning system, the subledger and the GL should agree: the
sum of all the detailed items in the subledger should exactly equal the single control-account balance in the
GL. The subledger-to-GL reconciliation is the control that proves they agree, and investigates every difference
— every “break” — when they don’t.

Why does this matter so much? Because the subledger is where the detail and the business meaning live, and
the GL is where the reported number lives. If they diverge, one of two things is true: either the reported
number is wrong (a financial-statement error), or the detail is wrong (an operational problem that will
eventually become a reported error). Either way, an unreconciled difference between subledger and GL means
you cannot trust the number you are reporting, because you can’t substantiate it from the detail beneath it.
This is why every audit, every SOX programme, and every regulator treats subledger-to-GL reconciliation as a
key control. It sits right in the middle of R2R: downstream of the transactional cycles that feed the subledgers,
and upstream of the trial balance, balance sheet substantiation and consolidation that depend on the numbers
being real.

2. Detailed End-to-End Process

Here is how the reconciliation actually runs end to end in a large organisation, and where breaks come from.

The process starts by extracting two independent balances as at the same cut-off: the subledger balance
(the sum of detailed items — open invoices, positions, assets) and the GL control-account balance, for the
same account, entity and date. These must be pulled from their respective systems of record, ideally by
someone who cannot manipulate either. The two figures are then compared. If they match to zero, the account
is reconciled and the accountant certifies it with evidence. If they don’t, the difference is the break, and the
real work begins: investigating, categorising and resolving each break.

Breaks arise from a surprisingly small number of root causes, and learning to recognise them is the craft.
Timing differences are the most common and the most benign — a transaction hit the subledger but the
interface to the GL hasn’t run yet, or vice versa; a trade settled in the subledger on the last day but the GL
posting falls the next day. These self-correct and simply need to be identified and monitored. Interface or
mapping errors are more serious — a transaction type in the subledger is mapped to the wrong GL account,
or an interface silently drops a batch of records, so a whole category is misstated. Manual journals posted
directly to a subledger-controlled GL account create permanent breaks, because the GL now contains
something the subledger doesn’t know about (this is exactly why Chapter 3 warned against manual journals to

19
 The Finance Controllership & Record-to-Report Handbook

subledger-controlled accounts). Unposted or rejected items — transactions that errored out of the interface
and sit in a suspense queue — cause the subledger and GL to disagree until someone clears them. FX and
revaluation differences arise when the subledger and GL revalue foreign-currency balances at slightly
different rates or times, which is why your resume’s “FX impact adjustment journals” exist — to align
subledger and GL after revaluation. And genuine errors — a duplicated posting, a wrong amount — are the
breaks that actually matter most because they represent real misstatement.

Each break is categorised (timing, mapping, manual, unposted, FX, error), quantified, aged (how long has it
existed — a two-day timing break is fine, a two-month unexplained break is a red flag), and assigned an
owner and an action. Timing differences are documented and expected to clear. Real errors are corrected
with a properly supported journal. Mapping errors are escalated to fix the interface so the break doesn’t recur
— and this is the crucial controllership instinct: treat the root cause, not just the symptom. Correcting the
same mapping break with a manual journal every month is not control; it is a treadmill. Fixing the mapping
once is control. This distinction — reconciling versus solving — is precisely what drove your 70% break
reduction and is the single most important point in this chapter.

The reconciliation is then reviewed and certified: an independent reviewer checks that the reconciliation is
complete, that breaks are properly categorised and supported, that aged items are being actioned, and signs
off. In a mature shop this runs on a platform such as BlackLine or Cadency, which pulls balances
automatically, auto-certifies zero-break accounts, enforces preparer/reviewer segregation, tracks break aging,
and escalates overdue items — turning a manual spreadsheet chase into a governed, monitored control. The
output feeds the balance sheet substantiation pack and provides the audit trail SOX and the auditors require.

The teams: R2R / reconciliation teams (often in a GCC) prepare and resolve. Controllers review, certify and
own the control. IT / interface teams fix mapping and interface root causes. Front office / operations (in
banking) explain trade-level breaks. Treasury and Product Control are involved for FX and valuation
breaks. Internal Audit and SOX test the control; External Audit relies on it to gain comfort over the
reported balances.

3. Practical Corporate Example

Let me make this concrete with the situation your resume describes, generalised so it’s usable in any
interview. A global bank runs its trading-book accounting through a product processor (the subledger) that
holds every derivative, bond and FX position with its daily valuation, and this feeds the general ledger. Across
ten global regions, the daily and month-end reconciliation of the product-processor balances to the GL was
throwing a large and growing population of breaks — thousands of items, many aged, investigated manually
in disconnected spreadsheets by each region in its own way. Because everyone reconciled differently and
nobody attacked root causes, the same breaks recurred every month and the true financial-reporting risk was
buried under noise.

The way an experienced Controller fixes this is a three-part move. First, standardise: define one set of break
categories, one master-data repository mapping every product and transaction type to the correct GL account,
and one commentary standard, so a break in Singapore is classified the same way as a break in London.
Second, find and kill root causes: run root-cause analysis across the break population, discover that a large
share come from a handful of mapping errors and a couple of broken interface feeds, and fix those at source
rather than journalling around them each month — which permanently removes them. Third, automate: use
Power Query to pull and match the two data sets, VBA to categorise and track breaks, and Power BI to give
management a live dashboard of break volumes, aging and trends by region. The result is the 70% reduction

20
 The Finance Controllership & Record-to-Report Handbook

— not because people worked harder, but because the recurring breaks were engineered out and the residual
ones were surfaced and managed. In an interview, telling it in exactly this sequence — standardise, root-
cause, automate — signals that you understand reconciliation as control design, not clerical matching.

4. Accounting Treatment
Reconciliation itself doesn’t post entries, but its resolutions do, and the treatment depends on the break type. A
timing difference needs no entry — it self-corrects when the interface runs; you simply document it. An FX/
revaluation break is cleared with an alignment journal, e.g. Dr/Cr FX revaluation (P&L or a designated
reserve) / Cr/Dr the control account, to bring the GL onto the same basis as the subledger (this is your “FX
impact adjustment journal”). A genuine error — say the GL is overstated because a posting was duplicated —
is corrected by reversing the erroneous entry: Dr Control account / Cr the account originally credited in error,
with full support. An unposted/rejected item is cleared by properly posting it once the underlying data is
fixed. A mapping error is ideally fixed in the interface, but any residual GL misstatement it caused is
corrected by a reclassification journal moving the amount to the right account.

The statement impact flows from there: because the reconciliation substantiates a balance sheet control
account (receivables, payables, trading assets, ECL provision), getting it right ensures the balance sheet is
stated at the amount the detailed records support. Where a break turns out to be a real error, its correction may
hit the P&L (an overstated asset written down is an expense) or be a pure balance-sheet reclassification. In
your world specifically, reconciling the IFRS 9 ECL subledger to the GL ensures the impairment allowance
reported on the balance sheet equals the modelled allowance in the risk system — a difference there means
either the reported impairment or the modelled impairment is wrong, both of which matter to regulators. The
governing logic is that reported balances must be substantiated by independent detail; IFRS 9 (for ECL and
financial-instrument balances), IAS 21 (for the FX revaluation differences) and IAS 1 (which requires faithful,
complete presentation) all sit behind why these reconciliations are mandatory rather than optional.

5. Practical Insights
The mistakes I see most: treating reconciliation as matching rather than controlling — clearing breaks
with monthly plug journals instead of fixing root causes, so the population never shrinks; letting breaks age
without ownership until a small timing item has become a large unexplained one; inconsistent categorisation
across teams so management can’t see the true risk profile; “netting” breaks so a positive and a negative
offset to a small net figure that hides two large gross errors; and auto-certifying accounts that shouldn’t be
— a zero balance can still hide compensating errors.

The key judgement is materiality and risk-based effort: not every break deserves equal attention. A mature
Controller focuses investigation on large, aged and error-category breaks, while monitoring (not obsessing
over) small timing items. Auditors’ classic observations here are aged unreconciled items, breaks with no
commentary, reconciliations prepared and reviewed by the same person, and reconciliations that are “green”
on the dashboard but whose supporting detail doesn’t actually tie out — so never let the platform’s status
colour substitute for real substantiation.

This is the richest automation domain in all of R2R, and it is exactly what your resume showcases. Automated
matching (Power Query, BlackLine’s transaction matching, Alteryx) handles the high-volume tie-out so
humans only see exceptions. A centralised master-data repository ensures consistent mapping and
categorisation. Break-tracking and aging dashboards (Power BI) turn a hidden risk into a managed metric.
Emerging AI approaches cluster breaks by likely root cause and predict which breaks will self-clear versus

21
 The Finance Controllership & Record-to-Report Handbook

which need intervention, letting the team pre-empt problems. The Fortune 500 target state: automated daily
matching, root causes engineered out, a small managed residual of exceptions, full segregation and aging
control on a platform, and a KPI dashboard the Controller reviews — precisely the model you built.

6. Interview Preparation
Basic — “What is a subledger-to-GL reconciliation and why is it done?” It proves that the summarised
control-account balance in the GL equals the sum of the detailed items in the subledger, so the reported
balance can be substantiated from the underlying detail; a difference (break) means the number can’t be
trusted until explained.

Intermediate — “What are the common causes of reconciliation breaks?” Timing (interface lag),
mapping/interface errors, manual journals posted directly to subledger-controlled accounts, unposted/rejected
items in suspense, FX/revaluation differences, and genuine errors. Being able to categorise breaks is the core
skill.

Advanced — “How do you permanently reduce a large, recurring break population rather than just
clearing it each month?” Standardise categorisation and mapping via a master-data repository; run root-
cause analysis; fix mapping and interface issues at source rather than journalling around them; automate
matching and aging; and manage the residual by materiality. This is the 70%-reduction story — tell it as
standardise → root-cause → automate.

Scenario — “A control account shows a €5m break that’s been aging for three months with no
commentary. Walk me through your response.” Quantify and age it, pull the detail from both sides,
categorise it, determine whether it’s timing (unlikely after three months), a mapping/interface issue, or a real
error; assess the P&L/balance-sheet impact and materiality; correct with a supported journal and/or fix the
interface; escalate if material; and put a control in place so a break can’t age unactioned again.

Behavioural (STAR) — “Tell me about your biggest reconciliation improvement.” Your flagship:
Situation — thousands of recurring subledger-to-GL breaks across 10 regions, reconciled inconsistently and
manually. Task — strengthen control and cut breaks. Action — standardised categories and mapping in a
master repository, root-caused the population, fixed mapping/interface issues, automated matching and
reporting with Power Query/VBA/Power BI. Result — 70% fewer breaks, faster close, stronger SOX
evidence, live KPI visibility.

Managerial — “How do you govern reconciliations across ten regions in a shared-service model?” One
global standard (categories, mapping, commentary), a single platform enforcing segregation and aging
escalation, materiality-based review, and a monthly KPI pack (break volumes, aging, root-cause mix, self-
certifications) with accountability by region. Emphasise consistency as the enabler of trust.

Leadership — “How do you shift a team from firefighting breaks to preventing them?” Reframe the goal
from “clear breaks” to “eliminate root causes,” measure and celebrate break reduction rather than break
clearance, invest in fixing interfaces even when a manual workaround is faster short-term, and give the team
the analytics to see where breaks originate. Culture change, not just process change.

Case study — “Design a target-state subledger-to-GL reconciliation control for a global bank’s trading
book.” People/process/technology/data: standardised categories and a master mapping repository; automated
daily and month-end matching (Power Query/Alteryx/BlackLine); enforced maker-checker and aging
escalation on a platform; root-cause governance that routes recurring breaks to interface fixes; a Power BI KPI

22
 The Finance Controllership & Record-to-Report Handbook

dashboard; and clear linkage into balance-sheet substantiation and SOX evidence. Tie it explicitly to
substantiating IFRS 9 financial-instrument and ECL balances.

23
 The Finance Controllership & Record-to-Report Handbook

Chapter 5 — Trial Balance Review and General Ledger Scrutiny

1. Introduction
The trial balance is the single most important report an accountant looks at, and paradoxically the one most
often glanced past. At its simplest, the trial balance is the complete list of every account in the general ledger
with its closing balance — every asset, liability, equity, income and expense account, for a given entity and
period. Its first, mechanical purpose is to prove the books balance: total debits equal total credits. But its real
purpose, the one that separates a Controller from a bookkeeper, is as an analytical lens. A skilled reviewer
looks at a trial balance the way a doctor reads an X-ray — not just checking it “adds up,” but scanning for
anything abnormal: a balance that shouldn’t exist, a sign that’s wrong, a number that moved when it shouldn’t
have or didn’t move when it should. Your resume calls this “Trial Balance review and General Ledger
scrutiny,” and it is one of the most powerful detective controls in the entire close.

Where does it fit in R2R? The trial-balance review is the point where the close comes together and gets its
first holistic quality check. It sits after the journals, accruals, depreciation, revaluations and reconciliations
have been booked, and before the numbers are locked, consolidated and reported. It is the last broad sweep to
catch errors while they are still cheap to fix — before they harden into a reported number, a consolidation, an
external filing. Skip it or do it superficially, and errors that a two-minute scan would have caught become
restatements. Do it well, and you catch the miscoded provision, the missing accrual, the reversed sign and the
dormant balance before anyone outside finance ever sees the numbers.

2. Detailed End-to-End Process

Let me teach you how an experienced reviewer actually reads a trial balance, because this is a learnable
discipline, not a mysterious talent.

The review begins once the entity’s close activities are substantially complete. The reviewer extracts the trial
balance — ideally in a format that shows, for every account, the current balance, the prior-period balance,
and the movement (both absolute and percentage), because movement analysis is where most errors reveal
themselves. The first pass is a sign and existence check: does every account carry the balance it should?
Assets should be debit balances, liabilities credit balances, revenue credit, expenses debit. A credit balance in
a receivables account, a debit balance in a payables account, a negative cash balance, or a negative
inventory immediately signals something wrong — a misposting, a duplicate, an unapplied receipt, or a cut-
off error. These “abnormal balances” are the fastest hits in any review.

The second pass is movement and trend analysis. The reviewer compares each account to the prior month
(and often to the same month last year and to budget) and asks: does this movement make sense given what I
know happened in the business? Rent should be roughly flat month to month — a big jump means a double-
posting or a missing prior accrual. Revenue up 40% with no known reason means a cut-off error or a
duplicate. An expense account that is exactly flat when it should vary may mean an accrual didn’t reverse or
an interface failed. Depreciation that didn’t change when a big asset was capitalised means the depreciation
run missed it. This is analytical review, and it is the same technique auditors use — the reviewer builds an
expectation from business knowledge and investigates every deviation.

The third pass targets specific high-risk accounts: suspense and clearing accounts (which should be at or
near zero — any balance is unactioned work or error), intercompany accounts (which must match the
counterparty), accrual and provision accounts (are they supported and reasonable?), rounding and FX

24
 The Finance Controllership & Record-to-Report Handbook

accounts, and any “other” or “miscellaneous” accounts (favourite hiding places for errors). The reviewer
also scans for dormant accounts that suddenly have a balance and accounts that should have a balance but
are zero. Every anomaly is queried, investigated, and either explained or corrected with a supported journal,
then the trial balance is re-reviewed. Only when the reviewer is satisfied that every balance is explainable does
the entity’s ledger get signed off and passed to consolidation. Throughout, the reviewer documents the review
— the questions raised, the explanations obtained, the corrections made — because this documentation is the
evidence that a review control operated, which SOX and auditors will want to see.

The teams: close accountants produce the trial balance and answer queries. Controllers / senior reviewers
perform the scrutiny and sign off. Business Finance and FP&A help explain business-driven movements and
often perform their own P&L review in parallel. Tax reviews tax-sensitive accounts. Group / consolidation
relies on the signed-off trial balance. Internal and external audit re-perform elements of this analytical
review and test that the entity’s own review control operated.

3. Practical Corporate Example

Picture a manufacturing subsidiary’s month-end trial balance landing on the Controller’s desk. Within minutes
of scanning the movement column, three things jump out. First, the finished-goods inventory account has
fallen 15% while sales were flat and production was normal — that shouldn’t happen, and investigation
reveals a factory did its physical stock count and wrote off obsolete stock without anyone booking the
corresponding entry correctly, so the write-off hit the wrong account. Second, a prepaid insurance balance is
exactly the same as last month, when it should have amortised down by one-twelfth — the monthly release
journal didn’t run, understating expense. Third, the intercompany payable to a sister company jumped by an
amount that doesn’t match anything the counterparty booked — a mismatch to chase before consolidation.
None of these would have failed the “debits equal credits” test; the trial balance “balanced” perfectly. They
surfaced only because someone read the movements against business expectation. That is the difference
between a trial balance that is arithmetically correct and one that is actually correct, and catching all three
before close is a good day’s controllership.

In a trading environment like yours, the same discipline applies to the GL scrutiny that supports IFRS
reporting: reviewing the trading-asset, valuation-adjustment and ECL accounts for movements that don’t
reconcile to the desk’s activity, spotting a fair-value-hierarchy account where a large Level 3 position suddenly
appears, or catching an FX revaluation that didn’t run across all currencies. The instinct is identical — build
an expectation, investigate the deviation.

4. Accounting Treatment
The trial-balance review doesn’t itself generate a signature journal type — its output is corrections, and each
correction is a normal supported journal of the kind covered in Chapter 3. What the chapter really teaches is
how the trial balance is the bridge between the ledger and the financial statements. Grouping the trial-balance
accounts by their statement mapping produces the primary statements directly: aggregate the asset, liability
and equity accounts and you have the balance sheet; aggregate the income and expense accounts and you
have the P&L; the change in balance-sheet accounts between periods, reorganised, yields the cash flow
statement. This is why a clean, reviewed trial balance is the prerequisite for reliable reporting — every
statement is just a view of it. Standards shape the review in the sense that IAS 1 dictates how the trial-balance
accounts must be grouped and presented (current/non-current, the minimum line items, offsetting rules), and
IAS 8 governs whether a discovered error is a current-period correction (just book it now) or a prior-period

25
 The Finance Controllership & Record-to-Report Handbook

error material enough to require retrospective restatement of the comparatives — a judgement the reviewer
must make when the error relates to a period already reported.

A practical treatment point worth internalising: abnormal balances often indicate a specific error type, and
learning the mapping speeds diagnosis. A credit balance in AR usually means an overpayment, a duplicate
receipt, or a credit note not applied. A debit balance in AP usually means a prepayment to a supplier, a
duplicate payment, or a debit note. A suspense balance means an item that couldn’t be automatically posted.
Negative inventory means goods issued that were never received into stock — a cut-off or sequencing error.
Being able to look at an abnormal balance and immediately hypothesise the cause is a skill interviewers probe
and a skill that makes you fast at close.

5. Practical Insights
The dominant mistake is reviewing the trial balance as a formality — confirming it balances and moving on
— rather than as analytical scrutiny. A trial balance always balances if double-entry is enforced; balancing
proves nothing about correctness. The value is entirely in the movement and abnormal-balance analysis. A
second mistake is reviewing only the P&L (because that’s what management asks about) and neglecting the
balance sheet, which is where errors accumulate and hide. A third is no documentation — doing a good
review mentally but leaving no evidence, so from a controls standpoint the review “didn’t happen.”

The judgement lies in setting review thresholds: on a trial balance with hundreds of accounts you cannot
investigate every €100 movement, so you set materiality-based thresholds (investigate movements over X or
Y%) while always scrutinising high-risk accounts regardless of size (suspense, intercompany, provisions,
related-party). Auditors’ common findings: review evidence not retained, abnormal balances left unexplained,
suspense/clearing accounts carrying balances, and review sign-off happening before all journals were posted
(so the reviewed trial balance wasn’t the final one). The best defence is a documented review with a threshold
policy and a mandatory zero-tolerance scan of the high-risk accounts.

Automation and AI are transforming this from a manual scan into an intelligence layer. Rules can auto-flag
every abnormal-sign balance, every movement over threshold, every non-zero suspense account, every
dormant account that woke up — so the reviewer’s eyes go straight to exceptions. Analytics tools (Power BI,
SAC) visualise trends and highlight outliers across many entities at once. AI/anomaly-detection models learn
each account’s normal behaviour and flag statistically unusual movements the human eye would miss, and
increasingly draft first-pass variance commentary for the reviewer to validate. The Fortune 500 target: an
automated exception engine that surfaces the 5% of accounts needing human judgement, freeing the
Controller from scanning the 95% that are normal — but with the Controller still owning the final sign-off,
because analytical review is ultimately an act of business judgement, not pattern-matching.

6. Interview Preparation
Basic — “What is a trial balance and what does it tell you?” The list of all GL accounts with their closing
balances, proving debits equal credits, and — more importantly — serving as the analytical basis for
reviewing the ledger and building the financial statements. Stress that balancing proves arithmetic, not
correctness.

Intermediate — “How do you review a trial balance?” Sign/abnormal-balance check, movement analysis
versus prior period/year/budget, targeted scrutiny of high-risk accounts (suspense, intercompany, provisions,
other), investigation of every anomaly, correction, and documented sign-off. Show you review movements
against expectation, not just totals.

26
 The Finance Controllership & Record-to-Report Handbook

Advanced — “What does an abnormal balance tell you, and how do you diagnose it?” Walk the
mapping: credit AR (overpayment/duplicate/unapplied credit), debit AP (prepayment/duplicate/debit note),
suspense balance (unposted item), negative inventory (goods issued not received). Demonstrating instant
hypothesis-from-symptom marks you as experienced.

Scenario — “On review you find revenue is up 30% with no known business reason and the accrued-
expense account is flat when it should have grown. What do you do?” Treat both as expectation-
deviations: for revenue, check for cut-off errors, duplicates or a mis-timed large contract; for the flat accrual,
check whether the accrual journal ran and reversed correctly or whether a cost was missed. Quantify, correct
with support, and confirm the corrected trial balance before sign-off.

Behavioural (STAR) — “Tell me about a time trial-balance review caught a significant error.” Use a
movement-analysis catch: Situation — routine month-end review; Task — sign off the entity; Action —
spotted an inventory or prepaid movement that didn’t fit business activity, investigated, found a missing/
miscoded entry; Result — corrected before close, avoiding a misstatement that would otherwise have
consolidated and possibly been restated.

Managerial — “How do you make trial-balance review effective across many entities in a shared-service
centre?” Standard review templates with prior-period and movement columns, a materiality-threshold policy,
mandatory high-risk-account scans, exception dashboards to focus reviewer time, documented sign-off, and
metrics on errors caught pre- vs post-close. Manage by exception, evidence the control.

Leadership — “How do you stop trial-balance review from becoming a rubber-stamp under time
pressure?” Make exceptions easy to see (automation surfaces the anomalies), hold reviewers accountable for
post-close errors that a proper review would have caught, treat “it balanced” as an unacceptable sign-off
rationale, and model the behaviour by asking the hard “why did this move?” questions in review meetings so
the standard is visible.

Case study — “Design an analytical trial-balance review process for a group closing forty entities in five
days.” Automated extraction with movement/prior-period comparatives; a rules engine flagging abnormal
balances, over-threshold movements, non-zero suspense and awakened dormant accounts; a Power BI/SAC
exception dashboard across all entities; a materiality-threshold and high-risk-account policy; documented,
segregated sign-off feeding consolidation; and metrics tracking errors caught. The mark of a strong answer is
focusing human judgement on exceptions while retaining Controller accountability for sign-off.

27
 The Finance Controllership & Record-to-Report Handbook

PART II — THE CLOSE

28
 The Finance Controllership & Record-to-Report Handbook

Chapter 6 — The Month-End Close

1. Introduction
The month-end close is the recurring heartbeat of every finance organisation, the process by which a company
stops the clock at the last day of the month and produces a complete, reliable picture of its performance and
position. If you understand nothing else about controllership, understand the close, because it is where almost
everything in this handbook comes together and where a Controller earns their reputation. Every month, a
large multinational takes millions of raw transactions and — within a handful of business days — converts
them into financial statements that management will act on, that feed the group consolidation, and that must
survive audit. The close is simultaneously a production process (it has to be delivered on a deadline, every
month, without fail) and a control process (the numbers have to be right, not just fast). Balancing those two
demands — speed and accuracy — is the essential tension of the Controller’s job.

Why does the close exist at all, rather than just reporting continuously? Because accrual accounting requires a
cut-off: to say “this is what we earned and spent in March,” you must draw a firm line at 31 March, ensure
everything belonging to March is captured in March (and nothing from April leaks in), add the many
adjustments that no transaction system produces on its own, and then freeze the result so it can be relied upon.
The close is that disciplined act of drawing the line, completing the picture, and freezing it. It sits at the core
of R2R — downstream of all the transactional cycles, upstream of consolidation and reporting — and every
other chapter in this book is, in a sense, a component of it.

2. Detailed End-to-End Process

The close is best understood as a sequenced calendar of activities measured in workdays, where Workday 1
(WD1) is the first business day after month-end. Let me walk the typical sequence, because the order matters
— many activities depend on earlier ones being finished.

Pre-close (the last few days of the month) is where good closes are won. Experienced teams don’t wait for
month-end; they do everything that can be done early — reconciling accounts that no longer move, chasing
known accrual data, confirming intercompany balances, running “hard-close-light” dry runs. The best
Controllers push as much work as possible before WD1 so the post-month-end window is calmer.

WD0/WD1 — Subledger cut-off and close. The transactional subledgers (AR, AP, inventory, fixed assets,
payroll) are cut off so no new transactions post to the closing month, and their final balances are locked and
interfaced to the GL. This is the moment cut-off errors are prevented — ensuring the last shipments, receipts
and invoices land in the correct period. Bank statements are reconciled and cash confirmed.

WD1–WD2 — Accruals and adjustments. The team books accruals for goods and services received but not
invoiced, releases prepayments for the period consumed, posts payroll and bonus accruals, and records any
revenue adjustments. In parallel, recurring journals run: depreciation and amortisation, standard
allocations, lease interest and so on.

WD2–WD3 — Provisions, revaluations and specialist entries. Provisions (IAS 37) are reviewed and
adjusted, the doubtful-debt / ECL allowance is updated, foreign-currency balances are revalued at closing
rates (IAS 21), and tax provisions are estimated. In a trading business, Product Control finalises valuation
adjustments and the daily P&L is squared to the ledger.

29
 The Finance Controllership & Record-to-Report Handbook

WD3–WD4 — Intercompany and allocations. Intercompany balances are matched with counterparties and
mismatches resolved (in-transit, timing, disputes), and cost allocations push shared services and overheads out
to the businesses that consumed them.

WD4–WD5 — Reconciliation, trial-balance review and sign-off. Balance-sheet accounts are reconciled and
substantiated, the trial balance is analytically reviewed (Chapter 5), variances are explained, and the entity
Controller signs off. The signed trial balance is then submitted to Group.

WD5 onward — Consolidation and reporting. Group consolidates the entities, eliminates intercompany,
translates currencies, and produces the consolidated statements and management pack, followed by review,
commentary and distribution.

Running through all of this is a close governance layer: a close calendar assigning every task an owner, a
dependency and a deadline; a close checklist / cockpit (often in a tool like BlackLine Task Management,
Trintech Cadency or FloQast) tracking real-time status; and daily close stand-up meetings where the
Controller sees what’s on track, what’s blocked, and what needs escalation. The teams involved are the full
cast: R2R/GL accountants do the bulk of the entries and reconciliations; AP, AR, fixed assets, payroll,
inventory teams close their subledgers; Treasury confirms cash, debt and FX; Tax provides tax entries;
Product Control (banking) finalises trading P&L; Business Finance/FP&A explain variances and challenge;
Controllers review and sign off; Group/Consolidation rolls up; and Internal/External Audit rely on and
test the whole.

3. Practical Corporate Example

Consider a retail group closing across thirty countries out of a shared-service centre. The pain point when I
have walked into such environments is almost always the same: the close runs to WD8 or WD9, management
gets numbers too late to act on them, and the last three days are pure firefighting because everything was left
to the end. The fix is rarely more people; it is sequencing and pre-close discipline. We map every task to a
workday and an owner, identify the critical path (the longest dependent chain — often intercompany →
reconciliation → sign-off → consolidation), and attack it. We move every reconciliation that can be done pre-
month-end to before WD1. We automate recurring journals so WD1–2 isn’t consumed by manual typing. We
introduce a daily close stand-up so blockers surface at 9am instead of at WD7. We move to a virtual/
continuous close mindset where the ledger is kept close to reportable all month. Within a couple of quarters
the close comes in at WD5, management gets earlier numbers, and — counter-intuitively — accuracy
improves, because a calm, sequenced close makes fewer errors than a panicked one. This is exactly the kind of
acceleration your resume describes when you moved journal preparation from M+4 to M+1/M+2: pulling
work earlier in the cycle is the single highest-leverage close improvement there is.

4. Accounting Treatment
The close is not one journal but the orchestration of all of them, so the “treatment” here is the pattern of
period-end entries and their combined effect on the statements. The recurring close entries — accruals (Dr
Expense / Cr Accruals), prepayment releases (Dr Expense / Cr Prepaid), depreciation (Dr Depreciation / Cr
Accumulated depreciation), provisions (Dr Expense / Cr Provision), FX revaluation (Dr/Cr FX / Cr/Dr the
monetary balance), allocations (moving cost between cost centres/entities), and tax (Dr Tax expense / Cr Tax
payable) — together transform the raw, transaction-only ledger into a full accrual-basis picture. Their
combined effect is to make the P&L reflect all income earned and costs incurred in the period regardless of
cash timing, and the balance sheet reflect all assets and obligations existing at period end. The cash flow

30
 The Finance Controllership & Record-to-Report Handbook

statement then reconciles that accrual profit back to actual cash by stripping out the non-cash close entries
and working-capital movements. The governing framework is the accrual and matching basis (IFRS
Conceptual Framework), IAS 1’s presentation and going-concern requirements, IAS 10’s treatment of events
after the reporting period (adjusting events — conditions existing at period end — versus non-adjusting
events, a distinction that matters when something significant happens between the cut-off and sign-off), and
the individual standards behind each entry type covered in Part IV.

5. Practical Insights
The mistakes that plague closes: leaving everything to the last days rather than pre-closing; weak cut-off so
transactions land in the wrong period; manual, un-templated journals that are slow and error-prone; no
critical-path management, so the team optimises tasks that aren’t actually holding up the close; “just book a
round number” accruals that never get trued up; and treating speed and accuracy as a trade-off rather
than recognising that a well-controlled close is both faster and more accurate. A subtle but important insight:
the goal is not the fastest possible close but the right close for the business — a faster close has real value
(earlier decisions, freed-up team capacity for analysis) but only if control is maintained; a fast close that
produces wrong numbers is worse than useless.

The judgement areas are estimates (accruals and provisions), cut-off decisions near the line, and materiality
(what’s worth chasing in the final hours). Auditors’ common close findings: late journals after sign-off,
reconciliations completed after the trial balance was “closed,” accruals without support, and inadequate cut-off
testing. The best-practice pattern in Fortune 500 finance is the continuous / virtual close — keeping the
ledger near-reportable all month through daily reconciliation and automation so month-end is an event, not a
scramble — supported by a close-management cockpit, automated recurring journals, auto-certified low-risk
reconciliations, and a real-time close dashboard. AI is now used to predict close bottlenecks, auto-draft flux
commentary, and flag anomalous close journals in real time. The north star: shorten the close and deepen
control simultaneously, freeing the team to spend the back half of the month on analysis rather than
production.

6. Interview Preparation
Basic — “Walk me through a typical month-end close.” Give the workday sequence: pre-close prep →
subledger cut-off (WD1) → accruals/prepayments/depreciation → provisions/revaluation/FX → intercompany
and allocations → reconciliation and trial-balance review → entity sign-off → consolidation and reporting, all
governed by a close calendar and checklist. Structure signals experience.

Intermediate — “What is the critical path in a close and why does it matter?” The longest chain of
dependent tasks that determines the earliest possible completion — typically subledger close → intercompany
→ reconciliation → sign-off → consolidation. It matters because accelerating non-critical tasks doesn’t speed
the close; only shortening the critical path does. This is a favourite differentiator question.

Advanced — “How would you take a close from WD8 to WD5 without adding headcount or losing
control?” Pre-close everything that can move earlier, automate recurring journals and low-risk
reconciliations, manage the critical path, introduce daily stand-ups, adopt a continuous-close mindset, and
sequence by materiality and risk — while keeping segregation and review intact. Tie it to your own
M+4→M+1/M+2 achievement.

Scenario — “It’s WD4 and a major entity can’t close because intercompany won’t balance by €10m.
The consolidation is due WD6. What do you do?” Triage: is it timing (in-transit, a counterparty not yet

31
 The Finance Controllership & Record-to-Report Handbook

posted — bookable with an in-transit entry) or a real dispute/error? Get both sides’ detail fast, quantify the
P&L vs balance-sheet impact, book a supported in-transit or accrual entry to a designated account if timing,
escalate the dispute to the counterparty Controller if real, and protect the consolidation deadline while flagging
the item transparently. Never plug it silently.

Behavioural (STAR) — “Tell me about a time you accelerated or improved a close.” Your M+4→M+1/
M+2 story: Situation — journal prep and reporting were slow; Task — accelerate without losing control;
Action — pulled preparation earlier, standardised and automated recurring journals, tightened the calendar;
Result — journals ready at M+1/M+2, faster management reporting, maintained accuracy.

Managerial — “How do you run a close across a shared-service centre and local Controllers in different
time zones?” A single global close calendar with clear RACI and hand-offs, a close cockpit giving real-time
status, daily stand-ups timed for overlap, escalation paths, and metrics on timeliness and post-close
adjustments — treating the SSC as an accountable partner. Show you can run a distributed production process.

Leadership — “How do you keep a close team from burning out during the monthly crunch while still
hitting deadlines?” Reduce the crunch structurally through pre-close and automation rather than heroics,
distribute the load across the month, recognise that a calmer close is a more accurate close, rotate high-
pressure tasks, and protect the team from last-minute scope creep — leading through process design, not
exhortation to work harder.

Case study — “Design a target-state month-end close for a global group currently closing in nine days.”
Cover people/process/technology: mapped close calendar and critical path, pre-close and continuous-close
adoption, automated recurring journals and reconciliations, a close-management cockpit, standardised entity
sign-off feeding consolidation, real-time dashboards, and a metrics/continuous-improvement loop —
sequenced by materiality and risk, phased rather than big-bang.

32
 The Finance Controllership & Record-to-Report Handbook

Chapter 7 — The Year-End Close

1. Introduction
The year-end close is the month-end close’s larger, more consequential sibling. Everything you learned in
Chapter 6 still applies, but year-end adds a set of activities that only happen once a year, carries far higher
stakes because the numbers become the audited statutory financial statements filed with regulators and tax
authorities, and involves judgements — on estimates, going concern, tax, and disclosures — that management
and the board will personally sign. New joiners often think year-end is “just a bigger month-end.” It is not. It
is the moment the whole year’s accounting is finalised, frozen, restated into a defensible statutory form,
subjected to full external audit, and published to the outside world. A mistake at month-end is corrected next
month; a mistake at year-end can become a restatement, a qualified audit opinion, a regulatory sanction, or a
hit to the share price.

Year-end sits at the apex of R2R. It consumes the whole year’s transactions and monthly closes, applies the
annual truing-up and finalisation entries, and produces the annual report — the primary statements, the notes
and disclosures, and the directors’ and auditors’ reports. It is where financial reporting, tax, treasury, legal and
the board all converge, and where the Controller’s technical accounting knowledge is most heavily tested.

2. Detailed End-to-End Process

The year-end process runs in overlapping phases that begin well before the year actually ends. Pre-year-end
planning starts months ahead: agreeing the audit timetable and scope with the external auditors, identifying
the significant judgements and estimates that will need documentation, planning the physical inventory counts
and asset verifications, and preparing the disclosure requirements. Hard-close activities in the final months
include stepping up the rigour of reconciliations, clearing aged items, and performing “dry-run” or early
hard-close procedures so that surprises are found in Q3, not on the last day.

At the year-end date itself, in addition to the normal month-end cut-off, several once-a-year events occur.
Physical inventory counts are performed and reconciled to the books, with auditors often attending. Fixed-
asset verifications confirm assets physically exist. Confirmations are sent to banks, customers, suppliers and
lawyers to independently verify balances and obligations. Impairment testing (IAS 36) is performed on
goodwill, intangibles and other assets — an annual requirement for goodwill regardless of indicators.
Provisions are comprehensively reassessed. Estimates are trued up: the year’s accruals are compared to
actuals, the doubtful-debt/ECL allowance is finalised, warranty and rebate estimates are settled.

Then come the annual finalisation entries: the current and deferred tax computation is finalised (this is a
major year-end workstream — the book-to-tax reconciliation, deferred tax on temporary differences, tax
losses, uncertain tax positions), dividends are recorded, transfers to/from reserves are made, and any prior-
period error corrections (IAS 8) are booked. In a group, consolidation is performed with full rigour
including the annual eliminations and the statement of changes in equity. Crucially, the income and expense
accounts are closed off to retained earnings — the “closing the books” step that resets the P&L to zero for
the new year while carrying the balance-sheet accounts forward as opening balances.

Finally, the statutory financial statements and disclosures are drafted — not just the four primary
statements but the extensive notes: accounting policies, significant judgements and estimates, segment
reporting, financial-instruments and risk disclosures (IFRS 7), related parties, commitments and
contingencies, subsequent events. These go through the external audit (Chapter 25), management

33
 The Finance Controllership & Record-to-Report Handbook

representation letters, the audit committee and board review and approval, and finally filing with regulators
and tax authorities. Throughout, Tax, Treasury, Legal, Company Secretarial, Group Reporting and the
external auditors are deeply involved alongside the core R2R and controllership teams.

3. Practical Corporate Example

Take a listed manufacturing group at 31 December. Three things make its year-end materially harder than any
month-end. First, goodwill impairment testing: it carries goodwill from past acquisitions, and IAS 36
requires an annual test — building value-in-use models with cash-flow projections, discount rates and
terminal growth assumptions, all of which the auditors will challenge hard and which management must
document defensibly. A softening market this year means the headroom has narrowed, and the Controller must
decide whether an impairment is needed — a judgement worth potentially hundreds of millions. Second, tax
finalisation: the book-to-tax reconciliation across twenty jurisdictions, deferred tax on accelerated
depreciation and losses, and an uncertain tax position on a transfer-pricing matter all have to be resolved with
the tax team and disclosed. Third, inventory: physical counts at a dozen sites must reconcile to the ledger,
obsolete stock must be written down to net realisable value (IAS 2), and the auditors attend the counts. An
experienced Controller runs these as planned workstreams months in advance, not last-minute scrambles —
the impairment model is built in Q4, the tax reconciliation is drafted early, the count instructions go out weeks
ahead — because at year-end the one thing you cannot buy is time, and the auditors are watching every
judgement.

4. Accounting Treatment
The signature year-end entry is closing the books: the balances on all income and expense accounts are
transferred to the P&L summary and thence to retained earnings, so Dr all income accounts / Cr all expense
accounts / with the net to Retained earnings — leaving every P&L account at zero to start the new year while
balance-sheet accounts carry their closing balances forward as opening balances. The tax entries are material:
Dr Current tax expense / Cr Current tax payable for the year’s liability, and Dr/Cr Deferred tax expense / Cr/
Dr Deferred tax asset or liability for the movement in temporary differences (IAS 12). Impairment, if
required: Dr Impairment loss (P&L) / Cr the asset or goodwill (BS) (IAS 36), which is not reversible for
goodwill even if conditions improve. Inventory write-downs to net realisable value: Dr Cost of sales / Cr
Inventory (IAS 2). Dividends declared: Dr Retained earnings / Cr Dividend payable. A prior-period error
material enough under IAS 8 is corrected retrospectively — restating the opening retained earnings and the
comparative figures rather than running it through the current-year P&L, with disclosure of the nature and
effect. The combined result is a set of statements where the P&L shows the full year’s audited result, the
balance sheet the year-end position, the statement of changes in equity every movement in reserves, and the
cash flow the year’s cash generation — all tying together and all disclosed to standard.

5. Practical Insights
The classic year-end failures: leaving impairment and tax to the last minute, when both need weeks of
modelling and auditor dialogue; weak estimate documentation, so a defensible number looks arbitrary to the
auditors because the basis wasn’t written down; poor cut-off on the once-a-year items (a December
shipment counted but not de-recognised from inventory); surprises in confirmations (a bank balance or a
legal claim the books didn’t reflect); and underestimating the disclosure effort — the notes often take as
long as the numbers. A subtle governance point: the auditors’ assessment of management’s control
environment and the quality of its judgements is shaped enormously by how prepared and organised the year-
end is; a smooth, well-documented year-end buys credibility that pays off in every subsequent interaction.

34
 The Finance Controllership & Record-to-Report Handbook

The judgement density is highest here — impairment assumptions, provision estimates, going-concern
assessment, uncertain tax positions, useful-life and residual-value reviews — and the discipline that protects
you is contemporaneous documentation of the basis of every judgement, because a judgement you can
explain and support is defensible even if the auditor would have chosen differently, while a judgement with no
documented basis is indefensible even if it happens to be right. Best practice in Fortune 500 finance is to run
year-end as a project with a detailed plan, an early hard-close, pre-agreed auditor deliverables (the “prepared-
by-client” list) delivered on time, a disclosure checklist to ensure completeness, and a judgements-and-
estimates paper for each significant area prepared before the auditors ask. Automation helps with disclosure
checklists, tax computations, consolidation and reconciliation, and increasingly AI assists in drafting
disclosures and benchmarking assumptions — but the judgements remain the Controller’s and the board’s.

6. Interview Preparation
Basic — “How does year-end close differ from month-end?” Same core process plus once-a-year activities
(physical counts, confirmations, impairment testing, tax finalisation, closing the books, statutory statements
and full disclosures) and far higher stakes because the output is audited and filed. Show you know it’s not
“just a bigger month-end.”

Intermediate — “What are the key once-a-year activities at year-end?” Physical inventory and asset
verification, external confirmations, annual impairment testing (IAS 36), comprehensive provision and
estimate true-up, current and deferred tax finalisation, closing the books to retained earnings, statement of
changes in equity, and full note disclosures — then external audit and board approval.

Advanced — “Walk me through goodwill impairment testing and where the judgement lies.” Annual test
under IAS 36 regardless of indicators: identify cash-generating units, determine recoverable amount (higher of
fair value less costs of disposal and value in use), compare to carrying amount including allocated goodwill,
and impair the excess. Judgement lives in the cash-flow projections, discount rate and terminal growth — the
assumptions auditors challenge hardest — and note goodwill impairment is never reversed.

Scenario — “In November you realise the goodwill headroom has narrowed sharply and an impairment
may be needed at 31 December. What do you do?” Start the modelling now, not in January: refresh the
value-in-use model with realistic assumptions, sensitivity-test the key drivers, engage valuation specialists and
the auditors early, document the basis thoroughly, and prepare the disclosure and the board briefing — so the
judgement is defensible and there are no year-end surprises.

Behavioural (STAR) — “Tell me about a challenging year-end you delivered.” Your resume’s “Global FX
GL Selldown & Carry-Forward” and year-end initiatives fit: Situation — complex year-end finalisation across
entities; Task — deliver accurate statutory close and specific year-end processes on deadline; Action —
planned the workstreams early, coordinated Treasury/Product Control, ran the FX selldown and carry-forward
and treasury remittance cleanly; Result — timely, accurate year-end with no escalations.

Managerial — “How do you plan and run a group year-end?” As a project: early timetable agreed with
auditors, an early hard-close, a PBC list delivered on time, judgements-and-estimates papers prepared in
advance, a disclosure checklist, clear workstream owners (tax, treasury, impairment, inventory, disclosures),
and board/audit-committee milestones. Emphasise front-loading to remove last-minute risk.

Leadership — “How do you handle a significant judgement where you and the auditors initially
disagree?” Ground the discussion in evidence and the standard, present your documented basis and
assumptions, understand their concern, be willing to move if their point is valid, escalate constructively

35
 The Finance Controllership & Record-to-Report Handbook

through the proper channels if not, and protect both the integrity of the numbers and the relationship. Show
you can defend a position without becoming adversarial.

Case study — “Design the year-end plan for a listed group with goodwill, multi-jurisdiction tax and
inventory at twenty sites.” A phased project plan: pre-year-end scoping with auditors; early hard-close;
impairment modelling and tax computation started in Q4; count instructions and confirmation processes;
judgements-and-estimates documentation per area; consolidation and disclosure preparation with a checklist;
audit, representation letters, and board approval milestones — all owned, dated and front-loaded.

36
 The Finance Controllership & Record-to-Report Handbook

Chapter 8 — Consolidation

1. Introduction
A large multinational is not one company; it is a group of many legal entities — parent, subsidiaries,
sometimes joint ventures and associates — often dozens or hundreds, spread across countries and currencies.
Each of those entities keeps its own books and closes its own trial balance. But investors, regulators and
management don’t want to see forty separate sets of accounts; they want to see the group as if it were a single
economic entity. Consolidation is the process that combines the individual entities’ financial statements into
one set of consolidated financial statements for the whole group. It is one of the defining activities of
corporate accounting and group reporting, and understanding it well is essential for any controllership role
above entity level.

The core idea rests on the concept of control (IFRS 10): a group consolidates every entity it controls — where
it has power over the entity, exposure to variable returns, and the ability to use its power to affect those returns
(usually, but not always, signalled by owning more than half the voting rights). Entities it merely influences
(associates, typically 20–50%) are not consolidated line-by-line but brought in via the equity method (IAS
28), and joint arrangements (IFRS 11) are treated as joint operations or joint ventures accordingly.
Consolidation sits at the top of R2R — it takes the signed-off trial balances from every entity’s close and turns
them into the number the market sees. Your resume’s work on “global intercompany accounting and
reconciliation for consolidated reporting” is precisely a feeder into this process, because intercompany
elimination is consolidation’s central mechanic.

2. Detailed End-to-End Process

Consolidation proceeds through a well-defined sequence. It begins with collecting the data: each entity
submits its closed, reviewed trial balance — usually mapped to the group chart of accounts — into a
consolidation system (SAP Group Reporting/BPC, Oracle HFM/FCCS, OneStream, Tagetik). Data quality
here is everything; a group can only consolidate what the entities give it, which is why entity-level sign-off
(Chapter 5) is the foundation.

Next comes currency translation (IAS 21). Entities reporting in different functional currencies must be
translated into the group’s presentation currency. The rules matter: assets and liabilities are translated at the
closing rate, income and expenses at the rate at the dates of transactions (in practice usually an average rate),
and the resulting difference — because the balance sheet uses closing rates and the P&L uses average rates —
is taken to a separate component of equity, the foreign currency translation reserve (FCTR/CTA), not the
P&L. Getting translation right is a common exam and interview trap, and errors here distort equity.

Then the two great elimination steps. Intercompany elimination removes all transactions and balances
between group entities, because a group cannot trade with, owe, or profit from itself. If the Polish subsidiary
sold goods to the German subsidiary, the intercompany revenue and cost, and the intercompany receivable and
payable, are eliminated so the consolidated accounts show only transactions with the outside world.
Unrealised profit in inventory is also eliminated: if Poland sold goods to Germany at a profit and Germany
still holds them in stock at year-end, that profit isn’t real from the group’s perspective (the group hasn’t sold to
an external customer yet), so it is eliminated until the stock is sold on. The second elimination is the
investment-in-subsidiary / equity elimination: the parent’s carrying value of its investment is eliminated
against the subsidiary’s equity at acquisition, with any excess recognised as goodwill and the post-acquisition
change in the subsidiary’s equity flowing into group reserves.

37
 The Finance Controllership & Record-to-Report Handbook

Where the parent owns less than 100% of a subsidiary, non-controlling interests (NCI) are calculated — the
share of the subsidiary’s net assets and profit attributable to the outside minority shareholders — and
presented within equity and profit separately. Finally, the consolidation system produces the consolidated
primary statements (income statement, balance sheet, cash flow, statement of changes in equity) and the data
for the notes, which are then reviewed, analytically checked (does consolidated profit reconcile to the sum of
entity profits adjusted for eliminations?), and reported. The teams: entity Controllers submit data; the Group
Consolidation / Corporate Finance team runs the consolidation, eliminations and translation; Tax handles
group tax and deferred tax on consolidation adjustments; Treasury provides rates; and External Audit tests
the consolidation, eliminations and goodwill.

3. Practical Corporate Example

Imagine a group where a UK parent owns 100% of a US subsidiary and 80% of an Indian subsidiary. At
consolidation, the US entity’s USD trial balance is translated into GBP — balance sheet at the year-end rate,
P&L at the average rate, with the gap landing in the translation reserve; if the dollar weakened over the year,
that reserve takes a hit that has nothing to do with operating performance, and management reporting must
separate this translation effect from real business movement (a distinction FP&A and the Controller must
explain every year). The Indian entity, 80%-owned, has its full results consolidated line-by-line, but 20% of its
net assets and profit are stripped out as non-controlling interest and shown separately. During the year the US
subsidiary sold components to the Indian one at a mark-up, and some remain in Indian inventory at year-end
— the group eliminates that intercompany revenue/cost, the intercompany receivable/payable, and the
unrealised profit sitting in Indian stock. An experienced group accountant runs all of this through the
consolidation system’s rules, but reviews the eliminations manually for the tricky items — in-transit
intercompany, unrealised profit, and translation — because those are where consolidation errors hide and
where auditors focus.

4. Accounting Treatment
The key consolidation entries are elimination and translation entries made at the group level (they don’t touch
the entities’ own books). Intercompany trading elimination: Dr Intercompany revenue / Cr Intercompany
cost of sales (removing the internal sale) and Dr Intercompany payable / Cr Intercompany receivable
(removing the internal balance). Unrealised profit in inventory: Dr Cost of sales (group) / Cr Inventory to
strip out profit on goods still held within the group. Investment elimination at acquisition: Dr Subsidiary
share capital and reserves at acquisition, Dr Goodwill / Cr Investment in subsidiary, Cr NCI (for the
minority’s share). Translation: the balancing difference from using closing vs average rates is Dr/Cr other
comprehensive income — translation reserve. NCI in profit: a portion of consolidated profit is attributed to
NCI in the statement of changes in equity and presented separately on the face of the income statement. The
statement impacts: the consolidated balance sheet shows group assets/liabilities net of intragroup balances,
goodwill, and NCI within equity; the consolidated P&L shows only external revenue and costs, with profit
split between owners of the parent and NCI; OCI/equity carries the translation reserve; and the consolidated
cash flow shows only external cash flows. IFRS 10 (control/consolidation), IFRS 3 (business combinations/
goodwill), IAS 21 (translation), IAS 28 (associates — equity method) and IFRS 11 (joint arrangements) are
the governing standards, and under US GAAP the concepts are broadly similar with differences in, for
example, goodwill measurement and NCI presentation.

38
 The Finance Controllership & Record-to-Report Handbook

5. Practical Insights
The recurring problems: intercompany not matching (the single biggest consolidation headache — one side
booked, the other didn’t, or at different amounts or in different periods), which is why disciplined
intercompany reconciliation before consolidation is so valuable; translation errors (using the wrong rate for
the wrong line, or mishandling the reserve); forgetting to eliminate unrealised profit; goodwill and NCI
miscalculations on acquisitions; and inconsistent accounting policies or group-COA mapping across
entities, so like items are combined unlike. A practical insight worth carrying: consolidation quality is made at
the entities — a group consolidation team can only be as good as the trial balances and intercompany
discipline feeding it, so investment in entity-level close quality and intercompany matching pays off directly
in a faster, cleaner consolidation.

Auditors focus heavily on eliminations, goodwill, NCI, translation and the consolidation system’s controls (are
the elimination rules complete and correctly configured? are manual top-side consolidation entries
controlled?). Best practice: a robust consolidation system with configured, tested elimination rules; pre-
consolidation intercompany matching (often via an intercompany hub or netting process); a harmonised group
COA and accounting-policy manual so entities submit consistent data; controlled and reviewed top-side
journals; and an analytical review that proves consolidated results tie back to entity results plus known
adjustments. Automation now extends to auto-matching intercompany, system-driven translation and
elimination, and AI-assisted anomaly detection on submissions; but the judgemental consolidation items (in-
transit, unrealised profit, goodwill, control assessments) remain manual and reviewed.

6. Interview Preparation
Basic — “What is consolidation and which entities get consolidated?” Combining the individual
statements of a group into one set for the group as a single economic entity; you consolidate entities you
control (IFRS 10 — power, variable returns, ability to affect returns, usually >50% voting), equity-account
associates (significant influence, ~20–50%), and treat joint arrangements per IFRS 11.

Intermediate — “Walk me through the consolidation steps.” Collect entity trial balances mapped to the
group COA → translate foreign currencies (closing rate for balance sheet, average for P&L, difference to
translation reserve) → eliminate intercompany transactions, balances and unrealised profit → eliminate the
investment against subsidiary equity, recognising goodwill and NCI → produce and analytically review the
consolidated statements.

Advanced — “Explain currency translation under IAS 21 and where the translation reserve comes
from.” A foreign operation’s assets/liabilities are translated at the closing rate and its income/expenses at
transaction (average) rates; because the two use different rates, a difference arises that is recognised in OCI
and accumulated in the foreign-currency translation reserve, and recycled to P&L on disposal of the operation.
Contrast with transaction FX (IAS 21) which goes to P&L — a classic trap.

Scenario — “At consolidation, intercompany is out by €10m and NCI on an 80%-owned sub looks
wrong. How do you approach it?” For intercompany: pull both sides, identify timing/in-transit vs real
mismatch, book an in-transit or correcting entry, and escalate genuine disputes — never plug. For NCI:
recompute the minority’s share of net assets and profit, check the ownership percentage and the elimination
entries, and confirm NCI is presented separately in equity and profit.

Behavioural (STAR) — “Tell me about resolving intercompany issues for consolidation.” Your resume’s
intercompany work: Situation — recurring intercompany mismatches delaying consolidated reporting; Task —

39
 The Finance Controllership & Record-to-Report Handbook

resolve and strengthen; Action — root-caused the mismatches, drove matching with counterparties,
standardised the process; Result — cleaner intercompany, faster consolidation, stronger balance-sheet
integrity.

Managerial — “How do you improve consolidation quality and speed across many entities?” Harmonise
the group COA and accounting policies, drive pre-consolidation intercompany matching, ensure entity-level
sign-off quality, configure and test elimination rules, control top-side journals, and use analytical review to
validate — improving the inputs, since consolidation quality is made at the entities.

Leadership — “How do you align 40 entity teams to submit consistent, high-quality consolidation
data?” A clear group reporting policy and calendar, training and a policy manual, a validated submission
process with data-quality checks, feedback and metrics on submission quality, and treating entity teams as
accountable partners — governance and enablement, not just central control.

Case study — “Design the group consolidation process for a newly formed multinational with entities
on three ERPs and four currencies.” A consolidation system with a harmonised group COA and mapping;
configured translation and elimination rules; a pre-consolidation intercompany matching hub; entity-level
sign-off feeding submissions; controlled top-side journals; goodwill/NCI handling for acquisitions; and
analytical review — phased, with strong data governance at the entity level.

40
 The Finance Controllership & Record-to-Report Handbook

Chapter 9 — Financial Statement Preparation and Presentation

1. Introduction
Everything the R2R machine does — every transaction, journal, reconciliation, close and consolidation —
exists to produce one output: a set of financial statements that faithfully represents the company’s
performance, position and cash flows. This chapter is about that final act of assembly and presentation: how
the four primary statements are built, how they interlock, and how the presentation and disclosure standards
(IAS 1, IAS 7, IAS 8 and their US GAAP equivalents) shape what the reader actually sees. Preparing financial
statements is not mechanical formatting; it is a discipline of faithful representation — completeness, accuracy,
classification, comparability and adequate disclosure — that turns a correct trial balance into a document
outsiders can rely on.

A complete set of financial statements under IFRS comprises five elements: a statement of financial position
(balance sheet), a statement of profit or loss and other comprehensive income, a statement of changes in
equity, a statement of cash flows, and the notes (accounting policies and supporting disclosures), plus
comparative figures. Each tells part of the story: the balance sheet is a snapshot of what the company owns
and owes at a point in time; the P&L is a movie of performance over the period; the cash-flow statement
reconciles accrual profit to actual cash; and the statement of changes in equity tracks every movement in
owners’ capital and reserves. Understanding how they fit together — how a single transaction ripples through
all four — is the hallmark of a strong Controller and a favourite interview theme.

2. Detailed End-to-End Process

Preparation begins with the consolidated (or entity) trial balance, reviewed and signed off. The first task is
mapping and classification: every trial-balance account is mapped to a financial-statement line item and
classified correctly — current versus non-current (IAS 1 requires this split based on the twelve-month/
operating-cycle test), asset versus liability, operating versus financing, and by nature or by function for
expenses. Misclassification here is the most common statement error: a long-term loan shown as current, a
provision netted against an asset, income offset against expense in breach of IAS 1’s no-offsetting rule.

The balance sheet is assembled by grouping the asset, liability and equity accounts into the standard line
items (property plant and equipment, intangibles, inventories, receivables, cash, payables, borrowings,
provisions, equity), respecting the current/non-current split and minimum line-item requirements. The
statement of profit or loss is assembled from the income and expense accounts, presented either by nature
(raw materials, staff costs, depreciation) or by function (cost of sales, distribution, administration) — a policy
choice with disclosure consequences — with other comprehensive income (items not routed through profit,
such as the translation reserve, certain financial-instrument gains, and remeasurements) shown separately.

The statement of cash flows (IAS 7) is then derived, almost always by the indirect method: start from profit
before tax, add back non-cash items (depreciation, amortisation, impairment, provisions, share-based
payments), adjust for movements in working capital (receivables, payables, inventory), and separate the result
into operating, investing and financing activities. This statement is derived, not posted — it is built by
analysing the movements between this period’s and last period’s balance sheet, which is why a clean, well-
reconciled balance sheet is a prerequisite for a correct cash flow. The statement of changes in equity
reconciles opening to closing equity for every component (share capital, retained earnings, translation reserve,
other reserves), capturing profit, OCI, dividends, share issues and NCI movements.

41
 The Finance Controllership & Record-to-Report Handbook

Finally, the notes are prepared: the accounting-policies note, the significant-judgements-and-estimates note,
and the detailed supporting notes for each material line (PP&E movements, financial instruments and risk
under IFRS 7, provisions, related parties, commitments and contingencies, segment reporting under IFRS 8,
subsequent events under IAS 10, tax under IAS 12). A disclosure checklist ensures completeness. The draft
statements go through internal review, tie-out (agreeing every number to the trial balance and cross-casting the
statements to each other), external audit, and board approval. Teams: Group/Financial Reporting owns
preparation and disclosures; Tax, Treasury, Legal, Company Secretarial feed specific notes; External
Audit verifies; the Audit Committee and Board approve.

3. Practical Corporate Example

A useful exercise I set every trainee is to trace one transaction through all four statements, because it cements
how they interlock. Take a company that buys a €1.2m machine for cash and depreciates it over ten years. In
year one, the balance sheet shows PP&E of €1.08m (cost less €120k depreciation) and cash €1.2m lower; the
P&L shows €120k depreciation expense reducing profit; the cash-flow statement shows the full €1.2m as an
investing outflow but adds back the €120k depreciation in operating activities (because it reduced profit but
used no cash that year); and the statement of changes in equity shows retained earnings €120k lower via
reduced profit. One transaction, four statements, all tying together. When a candidate can walk this cleanly —
especially the way depreciation is a non-cash add-back in the cash flow while the original purchase is an
investing outflow — I know they truly understand financial statements rather than having memorised formats.
The same logic scales to every item: a provision reduces profit and creates a liability but is a non-cash add-
back until paid; a rights issue increases cash and equity but never touches the P&L; an inventory build reduces
operating cash flow while sitting as a current asset.

4. Accounting Treatment
Statement preparation is about presentation rather than new journals, so the “treatment” is the set of rules that
govern classification and the articulation between statements. IAS 1 mandates: the current/non-current
distinction, the minimum line items on each statement, the prohibition on offsetting assets against liabilities
or income against expenses unless a standard requires it, the requirement to present comparatives, the going-
concern basis (and disclosure of material uncertainties), consistency of presentation period to period, and
materiality and aggregation (immaterial items can be aggregated, material ones must be shown separately).
IAS 7 governs the cash-flow classification into operating/investing/financing and permits the direct or (near-
universal) indirect method. IAS 8 governs accounting policies (selection and consistent application), changes
in estimates (applied prospectively) versus changes in policy and prior-period errors (applied
retrospectively, restating comparatives) — the retrospective-versus-prospective distinction being one of the
most tested points in reporting. The articulation is the non-negotiable internal check: profit from the P&L
must flow into retained earnings in the statement of changes in equity and into the top of the cash-flow
statement; closing cash in the cash-flow statement must equal cash on the balance sheet; and every statement
must tie to the trial balance. Under US GAAP the statements are similar but with differences in, for example,
balance-sheet ordering (often most-liquid-first), classification options in the cash-flow statement, and OCI
composition — differences a group reporting under both frameworks must bridge.

5. Practical Insights
The common mistakes: misclassification (current/non-current, operating/financing), improper offsetting,
cash-flow statement errors (the hardest statement to get right, because it’s derived — non-cash items missed,
working-capital movements miscalculated, or a financing/investing item wrongly in operating), statements

42
 The Finance Controllership & Record-to-Report Handbook

that don’t articulate (profit not tying across the P&L, equity and cash flow), and incomplete disclosures
(the notes are where completeness most often fails, and where auditors and regulators find issues). A practical
discipline: always cross-cast and tie-out — agree every face number to the trial balance and prove the four
statements articulate to each other — before anyone else sees the draft, because a statement that doesn’t
internally reconcile destroys credibility instantly.

The judgement areas are classification decisions, materiality and aggregation (how much to disaggregate), the
significant-judgements disclosure (telling readers where management judgement most affected the numbers),
and going-concern. Regulators (and audit inspectors) increasingly focus on the quality and specificity of
disclosures — boilerplate is criticised; entity-specific, decision-useful disclosure is rewarded. Best practice: a
controlled disclosure checklist and a statutory-accounts template/tool (e.g. disclosure-management
software) that links the statements to the source data so a change flows through automatically and tie-out is
enforced; a house style for notes; and early drafting of the judgemental disclosures. Automation and
disclosure-management platforms now handle tie-out, tagging (XBRL for regulatory filing), and version
control, and AI is beginning to draft and benchmark disclosures — but classification and disclosure judgement
remain the reporting Controller’s responsibility.

6. Interview Preparation
Basic — “What are the components of a complete set of financial statements?” Statement of financial
position, statement of profit or loss and OCI, statement of changes in equity, statement of cash flows, and the
notes (policies and disclosures), with comparatives — under IAS 1.

Intermediate — “How do the four primary statements link together?” Profit from the P&L flows to
retained earnings in the statement of changes in equity and to the start of the cash-flow statement; closing cash
in the cash flow equals balance-sheet cash; the balance sheet is the cumulative position while the P&L is the
period’s performance. Demonstrate articulation, ideally with the one-transaction walk-through.

Advanced — “Walk me through preparing a cash-flow statement by the indirect method and the errors
people make.” Start from profit before tax, add back non-cash items (depreciation, impairment, provisions),
adjust for working-capital movements, then classify into operating/investing/financing. Common errors:
missing non-cash add-backs, wrong sign on working-capital movements, and misclassifying items (e.g.
interest, a financing/investing item wrongly in operating). Note it’s derived from balance-sheet movements.

Scenario — “You spot that a long-term loan is classified as current and income is being offset against a
related expense. What’s the impact and fix?” Current/non-current misclassification distorts liquidity ratios
and covenant metrics; offsetting breaches IAS 1 and understates both gross income and gross expense.
Reclassify the loan to non-current per the settlement terms, gross up the offset items, and check for covenant/
ratio implications and any disclosure impact.

Behavioural (STAR) — “Tell me about a time you improved reporting quality or timeliness.” Your
resume’s trial-balance review and reporting-efficiency work: Situation — reporting was slow/quality-
inconsistent; Task — improve accuracy and speed; Action — strengthened TB review and GL scrutiny,
standardised outputs, automated with Power BI/SAC; Result — faster, more reliable management reporting
and audit-ready statements.

Managerial — “How do you ensure disclosure completeness across a group’s statutory accounts?” A
disclosure checklist tied to the applicable framework, a statutory-accounts template/tool with enforced tie-out,

43
 The Finance Controllership & Record-to-Report Handbook

a house style, early drafting of judgemental disclosures, and review against regulator focus areas — treating
notes with the same rigour as the face numbers.

Leadership — “Regulators criticise boilerplate disclosure. How do you drive decision-useful

reporting?” Push for entity-specific, judgement-revealing disclosure over templated text, invest in the
significant-judgements and estimates note, benchmark against peers and regulator themes, and set the
expectation that disclosures explain why the numbers are what they are — raising the standard of the whole
team’s writing.

Case study — “Design the financial-statement preparation and disclosure process for a listed group.” A
controlled flow from signed consolidated trial balance → mapping and classification → the four statements
with enforced articulation and tie-out → notes via a disclosure checklist and disclosure-management tool →
internal review, audit, and board approval → XBRL tagging and filing — with automation for tie-out and
versioning and human ownership of classification and disclosure judgement.

44