Books that never fall behind.
The production work runs every night against a ledger the engine has learned, so the close starts from books that are already current.
The month does not pile up.
Coding runs every night rather than in a week-long scramble after period end, which is what makes a two-to-three-day close arithmetic rather than heroics.
- Every transaction coded the night it posts
- Each client’s ledger learned over time, so recurring items code themselves
- Anything ambiguous flagged for a decision, never guessed
What a coded transaction carries
A category with no account behind it is not treated as resolved. Coverage is reported, not assumed.
How a transaction gets coded.
Four steps, in this order, every night.
Ingest
New transactions sync from the connection into the open close. The write is idempotent, so a repeated sync cannot duplicate a row.
Rules
The client’s learned rules run in priority order. A match codes the transaction outright, at high confidence.
Judgment
What the rules do not match is categorized against that client’s own history and chart of accounts. Low confidence is a flag, not an answer.
Correction
When a human changes a category, the change is recorded and a rule is written, so the same pattern codes correctly next month.
Most bookkeeping software learns nothing. You correct the same vendor every month for a year and it never notices.
A correction is worth more than a category.
Changing one transaction should change next month, not just this one. When a reviewer recodes a row, Bursar derives the pattern behind it and writes a rule for that client.
- The learned rule outranks the rule that got it wrong, so the same mistake cannot win again next month
- Patterns are derived precision-first - a narrow rule that fires rarely beats a broad one that fires wrongly
- Rules are per client. Nothing learned on one client’s ledger is applied to another’s
What a correction changes
The mechanism differs by provider, and we would rather say so.
Xero exposes bank transactions directly, so coding happens as they arrive. QuickBooks Online does not expose the bank feed’s “For Review” queue to any application, so on QBO Bursar reads accepted transactions and corrects the coding nightly. The result is the same current ledger; the route to it is not identical, and onboarding accounts for it.
- On Xero: transactions are coded as they land
- On QuickBooks Online: accepted transactions are recoded nightly, and setup covers how the client’s bank rules accept them
- Either way, nothing is coded without a rule or a reviewable confidence score behind it
Coding, by provider
Onboarding covers how a client’s bank rules accept transactions, because on QBO that is what determines how quickly Bursar can add value.
Give us your five most annoying clients.
First month free. A finished close in two to three days, or you pay nothing for it.