Agents post the entries. A person reviews the record.
Bills, invoices and payroll posted by agents into books that refuse anything unbalanced. Every correction is a reversal your controller can trace back to the original.
Updated
Where agent bookkeeping goes wrong.
01
Small slips, big cleanups
A swapped digit leaves the books out of balance, and someone spends month-end finding it.
02
Fixes without a trail
A corrected figure overwrites the wrong one, so nobody can see what changed or why.
03
No record of who posted
Entries arrive from several agents, and the books don't say which change came from where.
Scenarios
Questions a controller can answer.
How OpenLedger answers
No. The server refuses an entry whose debits and credits differ, so the trial balance always nets to zero.
How OpenLedger answers
The server refused it with both totals. The agent fixed the swapped digits and posted it three minutes later.
How OpenLedger answers
The reversal carries its reason, and both entries stay on the record, dated the same day.
What changes.
- Books that always balanceUnbalanced entries never reach the ledger.
- Corrections you can traceEvery reversal points back to the entry it corrects.
- Statements on requestTrial balance, profit and loss and balance sheet, as of any date.
- No per-seat billOpen source under Apache 2.0, on a machine you run.
Controls.
Balanced on write
An entry that doesn't balance is refused, and nothing is written.
Whole cents
Every amount is an integer number of cents.
Reversals, not edits
The original stays beside a reversal and its reason.
Audit log
Every change writes an audit row in the same transaction.
Read-only SQL
run_query accepts SELECT statements only.
Self-hosted
One SQLite file on infrastructure you control.
Questions.
Does it replace our accounting system?
Not today. It's a ledger your agents write to, with no invoicing, tax, AR/AP aging or period close. Some teams run it beside their main system; Attri builds the sync in managed deployments.
Can a person approve an entry before it posts?
Not in the open-source server; the tools post directly. Attri adds approval rules, such as holding agent entries over a set amount, in managed deployments.
Does it have sign-in?
Not yet. The open-source server has no sign-in or access control, and Docker binds it to localhost. Keep it off shared networks. API keys are planned for v0.2, and Attri adds access control in managed deployments.
Let your agents keep the books. Keep the rules on the server.
Run OpenLedger on sample books in minutes, or have Attri deploy it inside your environment with access control and approval rules.