The ledger and what "posted" means

Snap Apps keeps a real double-entry ledger underneath the receipts, not a flat list of categorised amounts. That is what lets a BAS reconcile, and what an accountant expects to see.

Double-entry, in brief

Every transaction is made of two or more splits against different accounts, and the splits on a posted transaction always sum to exactly zero. A $110 fuel purchase including $10 GST on a credit card, for example, is one split to the fuel expense account, one to GST, and one to the credit card liability — three lines, net zero. This is enforced by the database itself, not by application code remembering to check.

Draft vs. posted

A transaction starts as a draft — proposed from a scanned document, or started by hand. Drafts can be half-built, edited, or deleted freely; they don't need to balance while you're still working on them. A transaction only becomes posted — a permanent part of your books — once it balances to zero and you've confirmed it. A draft that doesn't balance simply can't be posted; the database refuses the transition rather than accepting an unbalanced entry and hoping someone notices.

Confirming is the one action that posts

Editing a document's fields changes data. Confirming it is a separate, deliberate act that posts the balanced transaction to your ledger — the two are kept apart on purpose, so your books only ever move when you actually meant them to.

The image stays attached

A posted transaction keeps a permanent link to the original receipt image — the evidence that justifies the entry stays with it for as long as you're required to keep the record. See Data retention and deletion.

A worked example

$110.00 of fuel on a business credit card, including $10.00 GST: