Does it post journal entries?

It prepares them. Posting is a permission your team can grant and most choose not to, at least at first — the value is in arriving at the close with the reconciliation done, the evidence attached and the accruals listed, which does not require the ability to write to the ledger.

How is this different from reconciliation software?

Reconciliation tools match what you tell them to match, on rules you maintain. The work that actually consumes the close is the retrieval around the break — the statement, the invoice, the approval, the person who knows why. That is the part this owns, and it is the part no matching rule addresses.

Can it work if half our evidence lives in email?

That is the normal case. It reads the mailbox, the shared drive and the finance folder alongside the ledger, because in most companies the explanation for a break is in a reply somebody sent three weeks ago rather than in any system of record.

What about the breaks it cannot explain?

They stay on the list, with an age against them and whatever evidence was found. A break that is six days old and visible is a different problem from one discovered on day three of the close, and making the age visible is most of the fix.

Will it change how our close is structured?

Not unless you want it to. It works to your checklist, your definitions and your pack format. The change teams usually notice is that the checklist starts the month already partly complete, rather than the structure itself changing.

Month-end close

The close starts before the month ends.

It reconciles as the month runs rather than after it, pulls the statements, explains what moved with the underlying records attached, and has the accrual list and the close pack assembled before day one. Running in your own cloud, against your own ledger.

Get a demo

A close is mostly not accounting. It is retrieval — finding the statement, the invoice, the approval and the explanation, five days after the person who could have told you in a sentence stopped thinking about it.

How a close actually assembles

Four stages, spread across the month instead of stacked on day three.

Reconciled through the month, not after it

The reconciliation that takes three days on day two takes ten minutes a day through the month, because the difference is found while somebody still remembers what caused it.

Matches the ledger against the bank, the processor and the sub-ledger daily
Surfaces the break the day it appears rather than three weeks later
Keeps the running list of what is unexplained, with its age

ReconciledBank, processor and ledger agree to the day.

BreakOne item, £2,140, since Tuesday. Unexplained.

Day one of the close

What was already done before anyone opened the checklist — in your own audit trail.

See what gets logged →

Month-end closeyour audit trail

REC

Bank and ledger reconciledDaily through the month, nothing carried forward

clean

BRK

1 break unexplained — 6 daysStatement line and invoice attached

held

VAR

Cloud spend up 18%Three transactions account for the movement

explained

ACC

Accrual list assembledFrom goods received, not invoiced

review

Who this actually changes the week for

Three people whose first five days of the month currently look nothing like the other fifteen.

MAThe management accountantWhich of these breaks are timing and which are real?Where is the statement that explains this one?Do I have to ask three people what this cost centre did?

FCThe financial controllerAre we going to close on day five again this month?What is unexplained, and how old is it?Is the pack in the shape the reviewer wants?

COThe cost centre ownerWhy am I being asked about a number from five weeks ago?What actually drove the movement?Can somebody show me the transactions?

What it does across the month

Each of these is a task the finance coworker already owns. The flow is what they look like joined up.

Reconcile the accountPull the statementMatch the settlementAge the breakAttach the evidenceSeparate timingExplain the varianceCompare the periodChase the ownerPrepare the accrualAssemble the close packFile the documentLog what it didAsk when unsure

Questions controllers ask first

The ones that come up before anyone lets software near the close.

: It prepares them. Posting is a permission your team can grant and most choose not to, at least at first — the value is in arriving at the close with the reconciliation done, the evidence attached and the accruals listed, which does not require the ability to write to the ledger.
: Reconciliation tools match what you tell them to match, on rules you maintain. The work that actually consumes the close is the retrieval around the break — the statement, the invoice, the approval, the person who knows why. That is the part this owns, and it is the part no matching rule addresses.
: That is the normal case. It reads the mailbox, the shared drive and the finance folder alongside the ledger, because in most companies the explanation for a break is in a reply somebody sent three weeks ago rather than in any system of record.
: They stay on the list, with an age against them and whatever evidence was found. A break that is six days old and visible is a different problem from one discovered on day three of the close, and making the age visible is most of the fix.
: Not unless you want it to. It works to your checklist, your definitions and your pack format. The change teams usually notice is that the checklist starts the month already partly complete, rather than the structure itself changing.

“The close does not take five days because the accounting is hard. It takes five days because nobody can find anything.”
— Why retrieval is the real work

Month-endto: AI coworker

Where are we before day one?

reconciled to yesterday✓ 1 break, 6 days old

Put an AI coworker
inside your own cloud.

Bring last month's close, including the part that overran. We will show you where it would have stood on day one.