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 four steps, and only ever forwards.
A posted document can be voided — a real invoice does get cancelled. 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.
The document keeps its number, lines and attachment, marked
void. Three months later the books can still answer what happened to it —
a deleted document leaves only a gap in the numbering.
Refused — and this is the important one. Voiding reverses this document and deliberately leaves the receipt standing, because the money genuinely arrived. Both halves are right; together they leave debtors negative by what was paid, with cash in the bank and nothing to explain it.
Raise a credit note instead. It reverses what the invoice put in the ledger and leaves the payment as a balance on the customer — to refund, or to set against their next invoice. Net revenue back to zero, every paper still readable, and the money accounted for rather than orphaned.
The document is sealed — not just the total, but the party, the number, even the date. It will not save. What is not sealed is the entry behind it, and that is the only door in. Walking through it is deliberately a three-step walk, because every step is on the record.
need_to_verify. It also unlocks.
done together.
The walk goes through. An invoice mis-keyed at 1,000 that should have been 600 ends up at 600 on both sides, with no reversal entry and no second document — because nothing was ever wrong except the keying.
Use this only when the paper was right and the entry was wrong, or the figure was simply typed wrong. If the paper itself is wrong, the customer holds a copy saying 1,000 — that needs a note, not an edit.
Step 3 is refused when the corrected figure is lower than what has already been received. Otherwise the invoice drops to 600 while 1,000 sits against it, and the difference has nowhere to live.
Put the journal back to what it was — the document returns to
posted by itself — then raise a credit note for the difference.
It stands open as the customer's 400, to refund or set against their next invoice.
Same answer as voiding, for the same reason.
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.
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.