Six levels. One standard. The playbook for CFOs who want control. Not just reports.
Peter Engel · Founder & CEO, Actuals
I have one belief about finance that I keep coming back to, regardless of company, industry, or ERP system.
Accounting systems assume truth. They do not create it.
Financial truth has an origin. It lives upstream of your ERP, upstream of your close, upstream of your audit. In the gap between what your order system says happened, what your PSP processed, and what your bank actually settled.
In fifteen years, first as an auditor and then building Actuals, I have seen six places where financial truth is either established or lost. Not one of them is the ERP. They are all upstream.
This playbook walks through all six. For each one I describe what breaks when it is missing, what most finance teams try, and what financial truth on that level actually looks like.
Written for CFOs of digital businesses processing tens of thousands to millions of transactions per day. Marketplaces, food delivery, parking, subscriptions, SaaS.
These are the patterns I see in high-volume digital finance teams every week.
The team works nights and weekends. Every month. The sprint never shortens despite hiring. That is not a people problem.
Not errors in judgment. Positions with no clear origin. The trail from transaction to journal entry breaks somewhere in the middle.
Growth adds complexity faster than the finance function can absorb it. What should be a configuration change becomes a project.
The tool is not the problem. The data the tool receives is. A model built on unreconciled exports does not become reliable because the interface is better.
You know they are probably right. But if a specific figure were challenged, you could not follow the path in real time. You would need to reconstruct it.
Every one is a symptom of the same gap. Financial truth is not being established upstream. The six levels in this playbook are the six places where that changes.
Want to know your score before finishing the playbook?
Take the scan →Each level is where financial truth is either established or lost. Each depends on the one before it.
Financial truth begins before data enters the ERP. If it is not validated upstream, the ERP records a version of events. Not the truth.
Every transaction must be followable from source to journal. When identifiers shift across systems, the chain breaks silently.
Monthly visibility means monthly blindness. Financial truth is not a month-end event. Control requires a daily pulse on what has reconciled and what has not.
Knowing that a difference exists is not enough. Without automated root cause, the same errors return every cycle. Because no one fixed the source.
Financial truth must be provable at any moment. Audit anxiety is a symptom of truth that was never maintained.
When the first five levels are in place, growth stops being a threat. Finance accelerates the business instead of becoming its bottleneck.
Each chapter covers one level. CFO sections are strategic. "In practice" blocks are for controllers and finance managers. Forward this to your team.
The ERP is not the origin of financial truth. It is the destination. Everything depends on what you send it. Most high-volume finance functions send it data they have not verified.
This chapter covers where truth is established, why the ERP implementation does not fix it, and what pre-ERP validation actually looks like.
In a high-volume digital business, financial reality is created across multiple disconnected systems. The order management system records what should happen. The PSP records what the customer paid. The bank records what you actually received. The ERP records what you told it.
None of these agree by default. Without pre-ERP validation, every journal entry rests on an assumption.
Can you prove that the order in your OMS matches the payment in your PSP and the settlement in your bank, for any transaction, today, without preparation? If this requires pulling three exports manually, SOURCE is missing.
NetSuite, SAP, Dynamics. Real improvements in structure and reporting. But the ERP only receives data. It does not validate it. Six months after go-live, the reconciliation problem is still there. It just has a better interface.
A layer between your operational systems and the ERP that continuously matches orders, payments, and settlements before they become journal entries. The ERP receives what has been verified. Not what came through the pipe.
Macy’s disclosed $151 million in erroneous bookkeeping entries accumulating since Q4 2021. A single employee had concealed a mistake for nearly three years. Internal controls did not catch it. SOURCE was missing.
CFO Dive · Macy’s regulatory filing · Nov–Dec 2024
SOURCE establishes that truth exists. TRACE ensures it can be followed. A transaction that cannot be traced is a number you cannot explain. A number you cannot explain is a liability, not an asset.
This chapter covers where the trail breaks, what custom builds miss, and what end-to-end traceability actually requires.
Traceability breaks where identifiers change between systems. An order ID in your OMS becomes a payment reference in your PSP, becomes a batch settlement in your bank file. Each translation is a potential break. At high volume, those breaks accumulate silently.
The close still happens. The reports still print. But when someone asks you to explain a specific number, you cannot follow the path. You reconstruct it. That is not traceability. That is archaeology.
A custom integration layer. Works until a PSP is added, volume spikes, or the engineer who built it leaves. It becomes a dependency no one wants to own or change.
Every order, payment, refund, settlement, and chargeback has a traceable path from origin to journal entry. That path does not break when a new PSP is added or a market is entered.
Symbotic, an AI-powered warehouse automation company processing millions of inventory transactions for Walmart, announced in November 2024 it could not file its annual report due to accounting errors. Material weaknesses in internal controls. Stock dropped 32% in a single day.
MarketWatch · Symbotic regulatory filing · November 2024
SOURCE and TRACE establish that truth exists and can be followed. PULSE is about when you look at it. A finance function that checks its position once a month is flying blind for 29 days out of 30.
This chapter covers the close problem, AI in finance, and what continuous control actually requires.
APQC benchmarked 2,300 organisations. Median close: 6.4 calendar days. Bottom quarter: 10 or more. In a high-volume digital business, those days are spent finding out what happened. Not confirming what is already known.
Manual workarounds start breaking well before 100,000 transactions per month. By the time you reach that volume, the cracks are already structural. Adding people does not fix a data sequencing problem.
Mismatches between PSPs, order system, bank, and ERP are identified and resolved as they happen. By month-end, nothing is outstanding. The close is a confirmation, not an investigation.
Median month-end close across 2,300 organisations. Top 25% close in 4.8 days. The difference is not the size of the team.
APQC Open Standards Benchmarking · General Accounting
Almost every finance team is experimenting with AI right now. The experiments mostly work in isolation, on a clean file. The problem comes when teams try to move from experimenting to relying on it. AI does not say it is not sure. It gives you a complete, plausible answer. If PULSE is missing, the AI fills gaps with something that looks right but is not.
Gartner predicts that through 2026, organisations will abandon 60% of AI projects unsupported by AI-ready data. 63% either do not have, or are not sure they have, the right data management practices for AI.
Gartner · Lack of AI-Ready Data Puts AI Projects at Risk · February 2025 · gartner.com/newsroom
McKinsey’s 2025 survey found that nearly two-thirds of organisations have not begun scaling AI across the enterprise. Teams must rewire core processes, talent, and technology. Not just add new tools on top of old ways of working.
McKinsey · How Finance Teams Are Putting AI to Work Today · 2025 · mckinsey.com
The 60% abandonment rate is not a failure of ambition. It is a failure of sequence. SOURCE, TRACE, and PULSE must be in place before the AI tool is opened.
PULSE tells you that a difference exists. ROOT tells you why. Without it, finance teams spend every cycle resolving the same discrepancies. The symptom is treated. The source is not.
This chapter covers the loop that keeps finance in firefighting mode and what breaks it.
A settlement does not match. Is it a timing difference? A currency conversion error? A fee structure that changed? A duplicate entry? Without automated root cause, finding out requires a person every time. The consequence: a team that is permanently reactive. Every close, the same investigation.
More controllers. A dedicated reconciliation team. This resolves the discrepancy but not the source. Next month, the same discrepancy reappears, resolved again by the same people using the same effort.
When a difference is flagged, the system identifies its cause. The team does not investigate the discrepancy. They decide what to do about its cause. Once. Not every month.
"Teams must rewire core processes, talent, and technology. Not just add new tools on top of old ways of working."
McKinsey · The State of AI in 2025 · November 2025
The first four levels establish financial truth. PROOF makes it provable at any moment. Not just once a year under pressure. Audit anxiety is a symptom of truth that was never maintained continuously.
Most finance teams experience audit as an event. A period of intense preparation and hoping the auditor asks about something that can be explained. That experience is a direct consequence of SOURCE through ROOT not being maintained year-round.
Weeks of evidence assembly. Pulling exports. Reconciling differences that were not resolved during the year. Hoping the auditor does not ask about the suspense account accumulating since March.
Every transaction has a traceable path. Every reconciliation is current. Every difference is resolved or documented. The audit is not a test. It is a confirmation that the numbers always were right.
"We now track all transactions from initiation to our general ledger. A paradigm shift to be in control."
CFO · Recharge.com
The first five levels establish financial truth. SCALE is what happens when that truth holds as the business grows, without the finance team growing proportionally to hold it together.
This is the level where finance stops being the bottleneck and starts being the accelerant.
Without the first five levels, every increase in transaction volume creates more manual work, more risk, and more pressure. The business scales. Finance struggles to keep up. "We will hire more finance staff" becomes the default answer to a structural problem.
With all six levels in place, volume growth is absorbed by infrastructure. A new PSP, a new market, a doubling of transaction volume: these become configuration changes, not crises.
Reconciliation is continuous. Evidence is maintained. The close is a confirmation of what is already known.
Every number has a traceable path. Audit is a retrieval exercise. The team answers from evidence. Not from memory.
SOURCE, TRACE, and PULSE give AI a live, reconciled dataset. The output becomes something you can act on.
"Financial truth is not a destination. It is the standard you maintain every day."
Peter Engel · Founder & CEO, Actuals
One question per level. Answer honestly. Not aspirationally. The score tells you exactly which levels are in place and which are missing.
Click to mark what you can genuinely confirm right now. Not what you are working toward.
The diagnostic gives you a directional answer. The free scan goes deeper. It benchmarks each level against other high-volume digital finance teams and shows you precisely where to focus first.
15 minutes. Instant results. No sales call.
Take the free scan →I started this playbook with a belief. Accounting systems assume truth. They do not create it.
If you have read this far, you now know where truth is created. In six places, upstream of everything you report. SOURCE, TRACE, PULSE, ROOT, PROOF, SCALE.
The diagnostic tells you which of those six your finance function has built. The missing ones are not failures. They are the work. Clear, specific, sequenced work that every high-volume CFO can prioritise.
Financial truth is not a destination. It is the standard you maintain every day.
The free scan at highvolumeaccounting.actuals.io benchmarks your six levels against other high-volume finance teams. 15 minutes. No sales call.
The free scan benchmarks your six levels against other high-volume digital finance teams. Instant results. No sales call.