DocsControls
Management reporting certification
All documentation pages
A group number that opens, line by line, back to the file it came from
- Domain: Finance & Accounting
- Moment: Before you sign
- Customer: A digital financial services group operating across several countries
Build a group number that can be traced to its source.
The situation
A digital financial services group operates in several countries. Each entity runs its own ledger, calendar and local obligations. Much of the operating data comes from distribution, retail, telco and processing partners, each with its own format.
Group finance assembles the management actual from country submissions and partner data, accruing for what has not settled, truing up when it does, and applying group adjustments. It happens in spreadsheets, and part of the logic exists only in people's heads.
Then the number goes to a board entitled to ask how it was built.
What breaks today
Partner files change without telling anyone. A column is renamed. A new fee type appears. A partner reports net where it reported gross. Nothing errors. The number moves, and nobody says why until someone looks.
Accruals and true-ups are tracked apart from the reporting. An accrual posted in one month is reversed in another, and matching the settlement back to it depends on memory or a cell comment. After a few periods the balance is carried because it always has been.
Adjustments have no register. A manual adjustment has a value and, if you are fortunate, a note. It rarely has an owner, an effective date, a reason, or a link to evidence. Nobody can tell next month whether it repeats an earlier one.
A restatement is indistinguishable from an error. When a prior period changes, the sheet is overwritten. Two versions of one month sit in two files with two names, and nothing records what changed, or on whose authority.
The board question cannot be answered in the room. "Why is this country down against last month, and is it the same thing that moved last quarter?" Finance comes back on it, which takes a week and three people.
What Manuel does
Registers every input, then maps it to one group model. Country submissions, partner files, and system extracts become registered sources with an owner, schedule, and expected format. Each is mapped to entity, country, product, channel, partner, currency, and period. Changes to a partner format are dated and recorded.
Calculates expected against actual. Partner revenue and cost are calculated from versioned contract rates, then compared with the partner report and settlement. Any difference receives a named cause.
Carries accruals and true-ups as tracked objects. Every accrual has an origin, a basis, an owner and an expected settlement window. When the actual lands it is matched to the accrual it settles, and the true-up posts the difference. The accrual balance becomes a list you can open.
Holds every adjustment in an approved register. Owner, effective date, reason, evidence, value before, value after, approver, version history. Adjustments are made in the register, and the register is what flows into the report. None exists as a typed-over cell.
Ties out, then publishes a certified actual. Group to the sum of entities. Management actual to each local ledger. Revenue to partner settlement and to cash. Each tie-out passes or names its difference. The published number is a version. A change to a prior period becomes a new version carrying the reason, the owner, the approval and the difference against the one it replaces. Both remain, and every action keeps its actor, timestamp and before-and-after state.
What the customer gets
The board question gets answered in the room. Any line opens to the entities beneath it, then to the partner files and ledger entries, then to the adjustments and who approved them.
The close relies less on individual memory. Mappings, accrual logic, adjustment rules, and tie-outs become versioned configuration with named owners.
There is no measured close-cycle result for this work yet. Discovery measures the time for each stage, manual and repeated adjustments, the share of the result linked to source records, and partner format changes. These measures become the baseline and acceptance criteria.
What stays with your existing systems
Manuel does not replace the accounting model. It does not set policy, own the chart of accounts, or calculate expected credit loss. Your ECL model stays where it is, owned and validated as it is today. Manuel controls the process around it: that its inputs are complete and on time, that its output reaches the management view without being retyped, and that every adjustment after it carries an owner, a reason and a version.
Each country's ledger stays the system of record. Your consolidation tool, where you have one, stays. The first deployment writes back to nothing.
What a first scope looks like
Two countries, one partner category, three historical closes. Files only, read-only.
We rebuild a management actual you have already published and defended. Every difference is either our error or a step in your process that was never written down. You see it before anything touches a live close.
Related: Settlement and fee integrity / Continuous audit / Cash-in-bank reconciliation at scale