Finance & Accountingoperational
Automatic Posting
Do the books keep up with operations without re-keying?
When a sale, purchase, standalone payment, or cash transaction is saved, continON writes the matching debit and credit rows into the general ledger — including separate VAT rows and payment-method postings. Which accounts they land on is resolved at runtime from your organization’s configured account mappings, not from hardcoded rules.
What it records
Paired rows per document
Each posting writes its debit and its credit row, with the account’s running balance carried forward on both.
VAT on its own account
The VAT portion of a sale or purchase posts as a separate row on the VAT account configured for the organization.
Payment-method postings
Payments with a payment method also post to the account mapped to that method — cash, bank, or whatever your mapping defines.
Runtime account resolution
Accounts are resolved from organization settings and lookup mappings when the document is saved, so posting rules are per-organization configuration.
Reversals reflected
Reversing an operational document writes the corresponding ledger rows rather than silently editing history.
How it works
The posting logic lives inside the operational services themselves. Saving a sale writes its revenue-side rows and a VAT row on the VAT account configured for your organization; saving a purchase does the same on the expense side; recording a payment posts its debit and credit accounts and, where a payment method is set, the payment-method account as well; cash transactions post against the debit and credit accounts chosen on the transaction. When documents are reversed, matching rows are written so the ledger reflects the reversal.
Account routing is configuration, not code. VAT accounts, payment-method accounts, and expense accounts are looked up from organization-level settings and reference data at the moment of posting, so two organizations on the same platform can run different account structures and both post correctly. Changing a mapping changes where future postings land — without a software change.
What this touches
- General ledger
Where the posted rows land and are filtered and traced. - Chart of accounts
The account structure the mappings resolve onto. - Sales management
Sale documents trigger revenue and VAT postings on save. - Purchasing & supply
Purchase documents trigger expense-side postings on save. - Cash management
Cash transactions post against their chosen debit and credit accounts.
See automatic posting running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.