The moment a customer’s controller stops trusting the reports, the ERP is dead in that company, no matter what else it does well. They will keep paying for a while, out of sunk cost, and they will keep a shadow spreadsheet of everything that matters, and the shadow spreadsheet is where the business actually lives from then on. Everything I built into Agaro ERP’s finance core follows from refusing that outcome.
Double entry is the integrity contract
The non negotiable core is that every financial event is a balanced journal entry. Not a flag on a transaction, not an amount in a column. A balanced entry, where debits equal credits at the moment of writing and the database itself would refuse anything else. Every business operation that moves money, invoicing, payment, expense, inventory valuation, payroll, produces its entry from one mapping, in one place, so there is no second implementation of what an invoice means in ledger terms to drift out of agreement with the first.
This is old accounting discipline enforced with new tools, and the payoff is a property most reporting systems lack: the reports cannot disagree with each other, because they are all projections of the same entries. Balance sheet and income statement come from the same ledger, so the question “why doesn’t this match that” has an answer that is always a query, never a scandal.
Derived, cached, and never authoritative
The second discipline is that nothing derived is ever authoritative. Stock on hand, customer balance, account balance, every one of those is derived from underlying facts and may be cached for speed, but the cache knows it is a cache. When a customer asks why a number looks wrong, the system can always recompute from the entries and show the trail. A number that cannot be recomputed from primary facts is not a report, it is a rumor.
This costs almost nothing to design in and is nearly impossible to retrofit. The day you allow a report to maintain its own running total, you have created a second source of truth, and the two sources will disagree at the worst possible moment, which is in front of an auditor.
The dangerous convenience of editing
The most important refusal in the whole system is also the simplest: no human edits a posted number. Corrections happen as new entries that reference what they correct, so the history of the business reads as what actually happened, in order, including the mistakes. Companies that let users edit historical figures do not have an audit trail, they have a story that changes.
It is a fight to ship, because editing is what users ask for the first week. It is worth the fight, because the request behind the request is never “let me change the past.” It is “I need the present to be correct,” and immutable corrections deliver that without the rot.
Trust compounds
What all of this buys is not elegance. It is that the numbers become load bearing for real decisions: a controller closes the month from Agaro’s reports without reconciling by hand first, an owner sets prices off margin reports without spot checking, and eventually the AI agents in the system act on the same numbers, because they are safe to act on. Trust compounds in both directions. A system that tells the truth once, provably, gets to be believed again. A system caught lying once is a spreadsheet with a login page forever.