Worked cases
Three reconciliation cases from one Friday, argued to a decision.
These are worked cases, not customer stories: one movement each, taken from the product’s own record and followed until somebody could say what it was. Two of them end in an entry. The third ends in a refusal, and that is the one worth reading.
What a case is
What does a reconciliation case actually contain?
Four things, and it is not finished until it has all four. Everything below this beat is one of these, filled in.
- The record it started from
- The statement line, the document, the reference the bank actually wrote. Kept verbatim and never rewritten into something tidier, because the untidy version is the one an auditor asks to see.
- Every explanation that was weighed
- Including the ones that lost. A verdict carrying only the winner is an assertion; a verdict carrying the alternatives and what separated them is something a person can argue with.
- The decision, and whose it is
- Attributed, posted or unresolved — and where a person has to make the call, their name and the moment they made it. We compute and show the working; your team decides what goes into your books.
- The trail
- The evidence, the rejected alternatives and the order in which the answer changed. It survives a re-run, and it exports.
All three cases below are read on Aug 14, 2026, on the same group and the same 47 bank accounts. A site showing one group on two different days is a site whose figures were assembled rather than computed.
That shared day is why the three can be read together. They are cuts of one Friday rather than three separate demonstrations.
Case one
What happens when one company has posted and the other has not?
Nothing, and that is the finding. A rebilling one company has issued and the counterpart has not yet posted is a timing difference, and a timing difference closes itself — as long as somebody can say which movement it is.
The two ledgers were compared movement by movement rather than balance against balance, and that is the whole difference between a case and a number. A balance comparison tells you the two companies are apart by an amount. A movement comparison hands you the document that explains it, with the day it was posted on the side that has it.
Until the second entry exists, this one document is the entire gap between the two companies. It sits on the pending list with its own reason written on it, and it leaves that list when the counterpart posts in the ordinary course — not because anybody chased it.
The useful part is what did not happen. Nobody posted anything to make the two sides agree, nobody adjusted a balance, and nobody spent a morning proving that a difference was allowed to be there.
Difference
EUR 132,600
Rebilled shared costs
Both legs, as each ledger holds them
- Corporation Servicios Has issued it
- EUR 6,845,000
- Corporation España Has not posted it
- EUR 6,712,400
The document on the side that has it
4400012884 · Aug 12Closes itself
Case two
How do you know which of two identical entries is the real one?
Not from the entries. Two vendor payment documents for the same amount, a day apart, are indistinguishable inside the ledger. What separates them sits outside it: one is cleared by a line on the bank statement and the other clears nothing, because the money left the account once.
What left the account
EUR 2,760.00
One payment, one bank line
Two documents, one payment
- 1500042318 · KZ · Aug 12EUR 2,760.00Cleared by a bank line
- 1500042407 · KZ · Aug 13EUR 2,760.00Clears nothing
Proposed correction
Reverse document 1500042407Awaiting approval
The bank statement is the arbiter here, and it is why a reconciliation that stops at the balance never finds this one: both documents are inside the ledger balance and only one of them is inside the bank’s. The pair is found at the line, on the day, with the payment that actually happened sitting beside them.
The correction is drafted and it is not posted. It names the document to reverse, the reason, and the approval it is waiting for. If your controller reads the evidence the other way round, the other document reverses instead, and the record keeps both readings and the choice between them.
This is the ending where a system has to stop. It can say which document the bank supports and show exactly what it read. Whether the reversal goes into your books is your team’s call, and it is stored as theirs.
Case three
What does a receipt nobody can attribute do to the rest of the day?
It counts as cash and as nothing else. The money is in the account, so it is in the position. The customer it belongs to is undecided, so it is in nobody’s receivable. Both are true at the same time, and a system forced to pick one of them picks the wrong one.
The reference on the line matches an open document in two companies of the same group, and nothing else in it separates them. Three of the four lanes found no record at all, which is part of the answer rather than a hole in it: it is how the reader knows the question was asked.
So the line stays where a person can see it, with both candidate documents on it. The position is complete, because the cash is real. The receivable is not closed, because closing the wrong one moves a debt from one company to another and comes back two months later as a collection call.
A wrong counterparty is worse than an empty one. It is the harder answer to give, and it is the only one that never has to be undone.
Receipt
EUR +12,940
RCPT 20260814-0517 · Aug 14
What the bank wrote
TRANSF SEPA //FRA 26-0517
What each lane returned
- Intercompany entityNothing found
- Identifier on the movementNothing found
- Account already on fileNothing found
- What the movement settlesArdenta Retail1400071842
- What the movement settlesArdenta Servicios1400071903
VerdictUnresolved
Movements the evidence could not decide9
The third ending
Why is the case that does not resolve the important one?
Because everything in this market can show you the first two. What separates one system from another is what it does with the case it cannot finish.
- A match rate cannot describe it
- A rate says how much matched. It says nothing about what the rest was, and the rest is the only part anybody has to work on. Three cases like these summarize a day more honestly than any percentage of it.
- A refusal has a name, a reason and a queue
- Not an empty cell and not a zero. Unresolved is a state that can be counted, sorted and reported on, with the records that produced it attached to every row of it.
- The alternatives keep their scores
- The explanations that lost stay on the case with what separated them. A person overruling a verdict is arguing with something specific rather than with a closed box.
- The answer changes when the evidence does
- A document arriving late re-decides the case, and both decisions survive with the order they happened in. A trail holding only the current answer cannot explain a change of mind.
One of the three cases above closes without anybody touching it. One waits for a controller to approve an entry. One waits for a person to decide something the evidence cannot. On every one of them, the record says which.
Where these live
Where does each of these cases live in the product?
Each case is one screen deep inside a different module, and each module page carries the rest of what that screen does.
The modules these cases came out of
Before the first session
What buyers ask about a worked case
- 01Can we see one of these run on our own figures?
- Yes, and it is the whole of the first session. One month of statements for one account and the ledger extract that should agree with them is enough to produce your own version of all three endings.
- 02What happens to a case nobody can decide?
- It stays unresolved, in a queue, with the records that produced it. It is never guessed at to clear the list and it never drops out of the count. A movement that stops being visible is the failure this whole page is about.
- 03Who posts the correction?
- Your team. The correction is drafted with the evidence behind it and the document it affects named, and it waits for the approval your own controls require. Nothing reaches your books that somebody on your side has not approved.
- 04Does a decision survive new evidence?
- It is re-decided rather than overwritten. The late document, the new verdict and the previous one all stay, in the order they arrived, so a change of mind can be explained instead of only observed.
- 05Can an auditor follow one of these from a report back to the file?
- Yes. Every figure on a report traces to the movement, the movement to the record it was read from, and the record to the file it arrived in. The trail exports, so those questions get answered without anybody rebuilding the answer in a spreadsheet.
Bring one month, and we will work your own cases.
One month of statements for one account and the ledger extract that should agree with them. What comes out is your own three endings, on your own figures, with the records behind each one.
Every case arrives with what produced it, and nothing is posted anywhere without your approval.