Platform Concepts

Most of what you learn in BigLedger is not really about the screen you learned it on.

A sales order, a cash bill, a sales return and a purchase invoice are the same record in the same table, told apart by one column. So the way a document is numbered, the way it decides whether it adds to stock or takes away, what happens the moment you press Finalise, and which branch and profit centre it lands in are one explanation, not sixty. Learn it once on the till and you already know it on the purchase invoice.

These pages hold those shared explanations. An applet page tells you what its screen does with a thing; this section tells you what the thing is. Where the two disagree, the applet page is about a screen that may have changed, and this section is about a model that rarely does — so check both and tell us.

The generic document

One table behind every sales order, cash bill, sales return and purchase invoice — and the ten columns that number it, five BigLedger assigns and five your other system fills in

Where the rest of the shared explanations live today

Not everything cross-cutting has moved here yet. These are the ones already written, in the module they grew up in:

Where this number came from — why two screens show two different figures, and which of them you should believe for what
Document numbering — the single counter table behind every running number, the pool that keeps two tills from waiting on each other, and what you can and cannot change