Reconciliation

Expected against actual, and the gap, owned

Expected against actual, matched — and every difference explained.

/dashboard/reconciliationDemo environment
Movements this period59 compared
Matched
51
Partially matched
4
Conflicting
2
Unmatched
2
Expected against actual
ReferenceEntityExpectedObservedVarianceState
REC-61002Acme US$100K$100K—MATCHED
REC-61004Acme DE€215K€217K€2,577.60CONFLICTING
REC-61014Acme UK£182K£182K—MATCHED
REC-61018Acme US Ops$94.2K$94.2K—MATCHED
REC-61020Acme US Ops$188K$188K—MATCHED
REC-61021Acme Ireland€125K€125K—MATCHED
REC-61022Acme DE€49.3K€49.3K—MATCHED
What was instructed, what the bank reported, and the difference between them. Illustrative demonstration data.

A variance beyond tolerance is escalated. It is never absorbed.

An auto-matcher that quietly widens its own tolerance to clear a queue is how a break disappears from a report and stays in the accounts. Matching happens inside a stated tolerance; anything outside it becomes an investigation with an owner, a classification and the records that disagree sitting next to each other.

Two sources disagreeing is evidence that one of them is wrong — a worse state than an absence, and drawn accordingly.

/dashboard/reconciliation/investigationDemo environment
Unresolved movementREC-61004
CONFLICTING
Entity
Acme DE
Expected
€214,800.00
Observed
€217,377.60
Variance
€2,577.60
Match attempted
Matched on the reference the provider returned
Open for
300 hours
Invoices involved
1 document
Why the two do not agreeProvider applied a spot rate that differs from the instructed rate.
What happens to the accounts meanwhileNothing is posted against an unresolved break. The Sub-ledger carries what was established, not what the matcher hoped for.
One break, with the strategy that was tried and the variance it produced. Illustrative demonstration data.

Where the system checks its own work.

Reconciliation reads what Execute instructed and what the provider reported, and hands Ledger a result it can post. An unresolved break stays visible rather than being absorbed into a figure.

Matching

Expected and actual lines matched on amount, date, counterparty and reference.

Discrepancy detection

Differences classified by kind rather than reported as one undifferentiated number.

Exception handling

A break becomes a case with an owner and a resolution, connected to the records it concerns.

Resolution record

What was decided about a break, by whom, and what it did to the ledger.

Get started

Bring your financial operations into one intelligent system.

Connect the ERPs, banks and providers you already run, establish one view of financial reality across them, and govern, reconcile and prove the work on top.

Explore VadoRail OS

Onboarding is sales-led with company verification — there is no anonymous signup.

Thanks — we'll reach out within one business day.
Couldn't send that just now — please try again in a moment.