LensReading which lens this session carries.

Reconciliation ledger

Where the platform and the systems of record disagree

Each set below compares what this platform believes against what the system of record holds. Where they disagree the difference is itemized rather than netted, aged from the day it was detected, and assigned to a named person. A break that nobody owns is the single most common audit finding in shared-service operations, so unowned breaks are counted on their own tile instead of being folded into the total.

Health

Whether the two sides agree

Reconciliation sets by state, with the breaks open against them and their materiality.

Reconciliation sets
14
5 tie exactly
Breaks open
46
of 70 ever itemized
Breaks with no owner
9
$1.09m unassigned
Open more than 90 days
20
oldest is 129 days
Value in dispute
$6.97m
sum of open break deltas
Platform against source
$3.30m
$2.03b here against $2.03b there

9 breaks worth $1.09m have no owner. Nobody has been asked to establish the root cause and no due date exists. They are shown here rather than distributed silently across the other owners' queues.Show only those.

Reconciliation sets

Platform scope against the system of record, at the stated cadence

SetSystem of recordCadenceLast runPlatformSourceDifferenceBreaksOwnerStatus
REC-01
Supplier invoices cleared against the accounts payable subledger
The load-bearing reconciliation. If this does not tie, no clearing figure the platform shows can be relied on.
Group ERP — Financials
ledger
Daily7.0 hr ago$412.88m
48,210 items
$412.65m
48,197 items
$228.6k
tolerance $25.0k
8M. Okonjo
Head of Accounts Payable
Escalated
REC-02
Purchase order commitments against materials management
Commitment drift is usually timing, but a persistent gap means the platform is releasing against orders that were changed elsewhere.
Group ERP — Materials and Inventory
supply
Daily11.0 hr ago$288.40m
21,440 items
$289.61m
21,502 items
-$1.21m
tolerance $100.0k
9K. Boateng
Director, Procurement Operations
Escalated
REC-03
Payment runs released against treasury confirmations
Zero tolerance by policy. It ties today, but it ties against treasury, not against a bank — the bank channel is not connected.
Treasury and Cash Management
banking
Daily6.0 hr ago$196.70m
3,860 items
$196.70m
3,860 items
ties
tolerance $0
0L. Duarte
Group Treasurer
Ties
REC-04
Booked orders against customer relationship management
Fifty-four orders exist in the source with no platform counterpart. Most are manual entries made outside the flow.
Customer Relationship Management
crm
Daily9.0 hr ago$604.20m
15,920 items
$606.98m
15,974 items
-$2.78m
tolerance $250.0k
9A. Whitfield
VP Revenue Operations
Escalated
REC-05
Credit memos and disputes against accounts receivable
Credits raised by agents but not yet posted show up here first. Ageing beyond a week is the signal that matters.
Group ERP — Financials
ledger
Weekly2.6 days ago$18.64m
4,120 items
$18.40m
4,088 items
$238.0k
tolerance $15.0k
8B. Sørensen
Head of Order-to-Cash
Breaks open
REC-06
Agent-posted journals against the general ledger
Ties exactly, and it must: an unmatched agent journal is a financial statement risk, not an operations nuisance.
Group ERP — Financials
ledger
Daily5.0 hr ago$74.30m
9,640 items
$74.30m
9,640 items
ties
tolerance $0
0E. Vandermeer
Group Financial Controller
Ties
REC-07
Platform roster against core human resources worker records
Twenty-five names hold platform responsibilities without a matching active worker record. That is an access finding as much as a data one.
Core HR and Payroll
hcm
Weekly3.7 days ago$0
1,486 items
$0
1,461 items
ties
tolerance $0
6S. Bergqvist
Director, People Systems
Breaks open
REC-08
Payroll-affecting change events against core human resources
Counts tie. Attribute-level agreement is checked by sampling rather than in full, and the sample is small.
Core HR and Payroll
hcm
Weekly3.8 days ago$0
2,740 items
$0
2,740 items
ties
tolerance $0
0S. Bergqvist
Director, People Systems
Ties
REC-09
Contract obligations against contract lifecycle management
One hundred and sixty-seven obligations exist in the contract system that the platform is not watching. Coverage gap, openly counted.
Contract Lifecycle Management
legal
Weekly5.4 days ago$0
6,210 items
$0
6,377 items
ties
tolerance $0
7V. Marchetti
Head of Legal Operations
Escalated
REC-10
Incident and change records against IT service management
Clean. The platform raises records in the service tool rather than keeping a private queue, which is why this one is easy.
IT Service Management
itsm
Daily4.0 hr ago$0
18,740 items
$0
18,740 items
ties
tolerance $0
0J. Petrakis
Head of IT Operations
Ties
REC-11
Inventory positions against materials management and planning
Two systems disagree with each other before the platform is involved. The reconciliation exposes that rather than picking a winner.
Supply and Demand Planning
supply
Daily13.0 hr ago$341.90m
74,200 items
$344.21m
74,810 items
-$2.31m
tolerance $500.0k
9R. Nakamura
Director, Supply Chain Systems
Escalated
REC-12
Indirect tax determinations against the tax engine
Counts tie and value is within tolerance, but a monthly cadence on a daily process is itself a weakness.
Indirect Tax Engine
tax
Monthly14.2 days ago$41.22m
39,400 items
$41.21m
39,400 items
$13.0k
tolerance $20.0k
0F. Aubert
Head of Tax Technology
Ties
REC-13
Marketing spend commitments against the ledger
The largest proportional variance in the ledger. Committed spend in the campaign tool is not the same thing as accrued spend, and the platform has been treating them as if they were.
Marketing Automation
marketing
Monthly16.8 days ago$52.40m
1,840 items
$49.88m
1,793 items
$2.52m
tolerance $250.0k
9C. Delgado
Director, Marketing Operations
Escalated
REC-14
Cost-center and hierarchy alignment against planning
Six cost centers were reorganized in the planning system and the platform has not caught up. Small count, large consequence for any benefit claim.
Planning and Consolidation
ledger
Monthly11.2 days ago$0
412 items
$0
418 items
ties
tolerance $0
5D. Halvorsen
Director, Finance Systems
Breaks open

Itemized breaks

1 of 70 shown, oldest first

BreakKindFunctionWork unitPlatformSourceDeltaAgeOwnerStatus
REC-11-BRK-08
The two sides agree the item exists and disagree on the amount. Usually rate, rounding or a partial posting.
Value variance
High
Supply ChainSC3C-1008$4.96m$5.36m$401.7k41d
due 11.0 days past
V. Marchetti
Head of Legal Operations
Investigating

Actions

What is waiting on a person

A break is a disagreement between two systems that both claim to be right. No agent on this estate is allowed to decide which one wins.

Operations

What this desk is allowed to start

A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.

Trigger and bound

This desk can start a reconciliation run: pull both sides, match on the declared key, and write every unmatched line as a break with its materiality. It cannot post an adjustment, write off a difference, or change a tolerance — all three are decisions with a financial consequence and all three sit with a person.

Live observability

What the record shows right now

Set-level status. A set is only clean when every line in it matched inside tolerance.

Current distribution

14 sets

Clean536%
Breaks open321%
Escalated643%

Is policy and strategy coming to fruition

Whether the written intent is holding here

5 of 14 reconciliation sets closed clean. 46 breaks are still live.

Not holding on the record

The policy position is that no figure leaves this platform without a reconciled source. On the record 35.7% of sets closed clean, 16 breaks have been resolved and 46 remain live, 11 of them above the set's own materiality threshold. Tolerances on this page are the ones written into each set definition; none of them has been reviewed by an external auditor.

What this ledger is, and what it is not

It is a break register. Every disagreement is a row with a kind, a value, an age from detection and either a named owner or the word Nobody. Sets that tie are shown as ties rather than being left off the page, because an empty page is not evidence of agreement.

It is not proof that the underlying figures are right. The source side of each comparison comes from a modeled feed in this build, so the arithmetic is real and the counterparty is simulated. Connect a real instance and these same sets will run unchanged — the numbers will move, and that movement is the point of running them.