Twelve kinds of paper, what each one does to the ledger, and the handful of rules the system will not let you break. This is the same manual the AI works from — so if you and it ever disagree, this page is where to settle it.
Every paper walks the same steps, only ever forwards — and who may change it narrows at each one.
The figure, the date, the party, the lines, the account it went to, the bank or cash it went through — all of it is corrected by the assistant, and it is one walk every time:
An invoice keyed at 2,810 that the paper says is 2,180, already paid 2,180 from the bank. Corrected to 2,180: its entry becomes 2,180, the receipt stays knocked against it, and the bank line stays posted. Nothing else moves.
Corrected below what was received, the knock-off has to move first, and the assistant says where the rest of that money belongs — another invoice of the same customer, or a balance left on them. The receipt's entry is written again with it.
Voiding is for a paper that should not be in the books at all — entered twice, or not this company's. You can do it yourself. What decides whether it is allowed is one question: has money already moved against it?
Void it. A reversal entry is written automatically and the original stays beside it — net zero, both visible.
Refused. Voiding would reverse this document and leave the receipt standing, so debtors would go negative by what was paid, with nothing to explain it.
If the paper was read wrong, it is not a void at all — ask the assistant to correct it. If the payment was the mistake, void the payment first. Only a sale or purchase really taken back after it was paid is a credit note.
Worth holding in your head, because it decides who gets to choose what.
The expense, revenue or asset account. This is where capital-versus-expense is decided, and where the house posting preferences earn their keep.
Bank or till, and only on papers where money actually moved. The paper says which; you are reading it, not deciding it.
Bil Tunai with no English on it anywhere
is still cash. Putting it in the bank is a mistake that stays invisible until the month
will not reconcile.Click any one for the steps. Six of them reach the ledger; six never do, by design.
Five of these the database enforces — it will simply refuse you. The last one nothing can enforce, and that is the point of it.
Not a document — the external check on everything above. It is the one figure in the books the company did not write itself, which is why it comes last.
The papers are in and the statement ties out. What is left is reading the result, handing it over, and making sure it stays what was handed over.
Open it from the speech-bubble button at the top right. It works on the page you are looking at — "this should be 500-001" means this document — and every change it makes goes into its log with an undo.
Where to find things, and the shortcuts that save the most clicks.
The steps above are the safe operations: they validate their inputs, enforce evidence and the status graph, refuse what should be refused, and each one is recorded and undoable. That makes them exactly the right tools for an agent — so the agent is given the same operations you have, and no others.
It cannot reach into the tables, cannot skip a step you could not skip, and cannot produce a state you could not have produced by hand. When it is unsure it stops and asks rather than guessing, and every move it makes can be undone one at a time.