Orientation — how the system thinks
The mental model before you touch a form: cycles, double-entry books, the ledger boundary, and the one order that matters.
Money moves in cycles
Every money event in the platform is a cycle: a set of business forms you fill in order. Each form does two jobs — it stores the business record (an invoice, a payment, an expense) and it posts a balanced double-entry journal to the General Ledger.
You never type debit and credit lines for routine work. You fill a business form; the books update. Manual journals exist, but they are the exception: opening balances, adjustments, and reclassifications.
Rule
The rule that never changes
Every journal entry has equal total debits and credits. The system enforces this and rejects anything that does not balance.
The five account types
| Type | Meaning | Normal balance |
|---|---|---|
| ASSET | Things you own — cash, receivables, inventory, prepaid, fixed assets | Debit |
| LIABILITY | Things you owe — payables, tax, accruals | Credit |
| EQUITY | Owners' stake — retained earnings | Credit |
| REVENUE | Income | Credit |
| EXPENSE | Costs | Debit |
Process rules baked into the system
- A posting must fall inside an OPEN accounting period that covers the entry date. If not, the system refuses to post.
- Every posting is idempotent — re-running the same business event does not create a duplicate journal.
- Posted entries are never edited or deleted. To undo, you post a reversing entry. The system does this automatically for voids, cancellations and deletions.
- Reports are the book of record; they read only POSTED journals.
- Foreign amounts convert to your base currency using a stored rate. A missing rate is an error, never a silent 1.0.
The ledger boundary — what posts and what does not
This is the most important shared fact in the entire manual. Operational records and financial postings are not the same thing. Knowing which is which prevents almost every reconciliation problem.
| Action | Moves stock? | Posts a journal? |
|---|---|---|
| Purchase order — receive goods | Yes (RECEIPT) | Yes — Dr 1300 Inventory / Cr 2050 GRNI |
| Purchase invoice recorded | No | Yes — Dr 2050 GRNI + 2310 Input VAT / Cr 2000 AP |
| Supplier payment | No | Yes — Dr 2000 AP / Cr Cash or Bank |
| Sales invoice issued | No | Yes — Dr 1200 AR / Cr 4000 Revenue + 2300 Tax |
| Sales receipt | No | Yes — Dr Cash or Bank / Cr 1200 AR |
| Sales order approve / fulfil | Yes (allocated, then ISSUE) | No |
| Stock adjustment / transfer / return | Yes | No |
| Port container register / advance status | Yes (gate events only) | No |
| Port documents issue / sign / deliver | No | No |
| Demurrage invoice issued | No | Yes — Dr 1200 AR / Cr 4100 Demurrage Income |
Watch
The consequence to remember
Inventory is valued in the books only when goods are received on a purchase order. Selling or issuing stock reduces quantity on hand but does not post Cost of Goods Sold. Treat stock quantity reports and the Inventory GL account as two different views of the world.
Seven rules that never change
- Stock is tracked at the variant, not the product.
- Available = On hand − Allocated; allocation happens at sales-order approval.
- Purchase-order approval posts nothing; goods receipt posts Inventory / GRNI.
- Only ISSUED sales invoices post revenue; only ISSUED demurrage invoices post demurrage income.
- Containers move one step at a time in a fixed order; the demurrage clock starts at registration.
- Documents go DRAFT → ISSUED → SIGNED → DELIVERED; VOID is the exit.
- Every posted entry is reversed, never edited.
Modules outside the automated ledger
These exist in the app but are not sources of journal entries. Treat them as operational tools, not accounting events.
- Inventory quantity movements (adjust, transfer, fulfil, warehouse bridge) — stock only.
- Port documents (waybill, gate pass, loading request, delivery order, customs register) — records only.
- The sales-order step — reserves and issues stock; revenue posts at the invoice.
- AI assistant and insights — read-only analysis; proposals require human approval and never auto-post.
- Payroll and platform billing — record payroll through a manual journal or an operating expense if you need it in the books. Platform billing is your software subscription, not company accounting.
Note
If you need more automation
If an operational action should post to the ledger — automatic COGS or shrinkage, for example — raise it as a change request so it is added deliberately with its own posting rules, rather than assumed.
How to use this manual
The chapters are numbered in operating order, not by menu order. Read them in sequence for a clean setup, or jump straight to the chapter for the module you run.
| Order | Chapters | Why this order |
|---|---|---|
| Set up | CH 01 → CH 03 | Access, then the finance foundation, then master data — nothing works before these |
| Core goods flow | CH 04 → CH 07 | Inventory exists, is bought, is sold, then moves by container |
| Supporting modules | CH 08 → CH 13 | Fleet, cashbook, approvals, reporting, admin, Telegram |
| Run the month | CH 14 → CH 15 | Close the period, then keep the reference pages open |
Rule
One prerequisite
Nothing posts until your Chart of Accounts is active and an open accounting period covers the date. Finish CH 02 before you attempt any operational posting.