Smart tools should be able to show their work. Here is everything under the hood — the logic, the rules, the safeguards, and the audit trail. No black boxes. No hand-waving.
TRiON ships with proven accounting rules already in place — Dutch double-entry, VAT regime routing, GRNI matching. Day one is already correct. What happens after that is not blind automation. Every supplier invoice is verified against the original purchase order on every run — quantities, prices, what was actually received. A deviation stops the flow. Nothing incorrect continues unnoticed.
Before your first transaction, TRiON already knows: NL domestic VAT is 21% to account 4110. EU B2B is 0% reverse charge, box 3a. Goods receipts go through GRNI. Every journal entry must balance. These are not settings you configure — they are the foundation, built in and verified. You are not starting from zero. You are starting from correct.
Every supplier invoice is checked against three sources simultaneously: the original purchase order, the quantities actually received, and what is being invoiced. Lines are flagged green (exact match — auto-accepted), amber (favorable deviation — still requires an explicit decision), or red (overcharge or quantity discrepancy — the flow stops entirely, a human must act before anything posts). A wrong entry from a bookkeeper does not continue. It surfaces on that invoice, before anything reaches the ledger.
Every journal entry in TRiON has an origin — either a human approval or a locked logic rule that traces back to one. You can show an auditor the exact moment a rule was established, who approved it, and every subsequent transaction that executed under it. Nothing in the ledger is unexplained.
TRiON uses a single atomic posting function. If the debit total does not equal the credit total, the transaction is rejected in its entirety — nothing is written to the database. This is not a validation warning. It is a hard block.
All journal posting goes through a single atomic function. This function validates Dr = Cr before writing a single row. There is no path in the system that allows two-step, partial, or conditional posting. Every entry either posts completely and balanced — or does not post at all.
The most common source of VAT errors in small business accounting is manual mis-selection of the rate. TRiON determines the VAT regime automatically from the customer's country and VAT number — and locks the invoice accordingly.
Invoicing EU consumers (B2C without a VAT number) requires OSS registration. TRiON blocks the invoice from saving if this combination is detected, displays a hard error, and prevents any posting. This is not a warning — it is a compliance gate. EU B2C cannot go through until OSS is registered and activated.
When goods arrive, inventory increases. But the supplier invoice arrives separately — sometimes days later. TRiON implements the GRNI two-step, the same principle your auditor expects from any properly run operation.
* GRNI = Goods Received Not Invoiced — standard accrual accounting practice
The GRNI account tells you immediately what stock you hold for which no invoice has been received. This accrual is essential for correct year-end balance sheets and prevents the most common small-business inventory error: stock on the shelf that isn't reflected in the accounts payable.
The journal is immutable. Entries cannot be edited after posting — only reversed via credit note, which itself creates a new auditable entry. Here is what the live ledger looks like.
An external accountant or auditor can verify the ledger directly — every entry, every balance, every audit trail. The expected result: zero unbalanced entries, zero orphaned journal headers. We are not asking you to take our word for it.
These are not features. They are design constraints that cannot be worked around — by users, or by us.
We want to be completely clear on this, because it matters more in financial software than in any other category.
TRiON is a tool that automates the execution of accounting rules you define and approve. It does not file VAT returns on your behalf. It does not replace your accountant's advisory role. It does not take legal responsibility for your filings.
What it does: it ensures that the data going into those filings is complete, balanced, correctly classified by regime, and traceable to its source. It removes the human error in execution — not the human judgment in oversight.
This is what's under the hood. If something is missing or you want to go deeper on any part of the architecture, we'd rather have that conversation directly than leave a gap.