Bank reconciliation an auditor can sign.
Luxeron reconciles a bank statement against a cashbook month by month. Every figure on the statement it produces traces back to a line in your files, and every explanation is checked against those files before it is shown to you.
Three steps.
No new habits and no new file formats. You bring the two documents you already have.
Drop the files
The bank statement as a PDF, the cashbook as Excel or CSV. Add any supporting schedules you keep. Nothing is parsed until you ask for a plan, so dropping files costs nothing.
Approve the plan
You read what the run intends to do before it does it. Nothing reconciles until you approve — an unreviewed plan produces a statement nobody can review.
Read the statement
A month-by-month reconciliation with schedules, a worklist for what is still open, and an Excel workbook you can hand to an auditor.
Built for the moment a number has to be defended.
Every figure traces to a line
Open any unreconciled amount and you get the statement row behind it — the page, the date, the narration as it was read — and the cashbook entry it should have matched.
The AI proposes, a person disposes
Explanations are drafted by an AI that works your actual files with tools, then accepted or rejected by a named reviewer. The rejection goes back on the worklist with the reason attached.
Money is never a floating-point number
Every amount is exact decimal arithmetic from the moment it is read to the moment it is printed. Rounding happens once, deliberately, at two decimal places.
What it refuses to do.
The list below is the reason to trust the rest. A reconciliation tool that hides its own limits is not one you can sign behind.
It will not fill a gap to make the page balance
If the listed items do not add up to the whole difference, the shortfall is printed as an unaccounted plug and labelled as a fault in the software — not folded quietly into an adjustment.
It will not present an unverified figure as fact
When the AI produces a number it could not tie back to your files, that number is marked unverified on screen. The same goes for a finding it could not ground in a line.
It will not sign for you
The certification block prints blank rules for the names and dates. An unnamed signature block is a form; a pre-filled one is a forgery.
It will not ship a control that does nothing
Features without a working backend are listed as not built, in the settings screen, by name. A switch that silently has no effect is worse than an absent one.
Being straight about the state of it
Luxeron is in active development. These are the limits as they stand today, so nothing here comes as a surprise after you sign up:
- One organisation per deployment. The bank details, currency and organisation name come from the server's configuration, not from a form — so a browser can never change what a statement claims about who it is for.
- The first account is the administrator. Sign-up is refused on a deployment with no accounts yet, because the first one has to be created deliberately.
- Email addresses are collected but not yet verified, and there is no self-service password reset — an administrator resets a password.
- A full run takes minutes to about an hour, depending on how much the AI has to investigate. It runs in the background; you can close the tab.
Try it on the next month you reconcile.
Bring one statement and one cashbook. You will see the plan before anything runs, and the statement before anything is signed.