Two-step payment posting
How Numezis separates the obligation from the cash movement for clean books.
Two-step payment posting is Numezis's default accounting mode for both customer invoices and supplier bills. It produces the same ledger quality as Odoo / SAP / NetSuite, and it's what your fiduciary expects when they review your books.
The problem with one-step posting
In direct mode, a paid invoice produces a single journal entry that mixes the obligation (revenue / payable) with the cash movement (bank). That's fast, but it has three drawbacks:
- The exact date and method of payment are lost.
- Partial payments can't be modeled cleanly.
- Bank reconciliation requires a separate clearing logic on top.
How two-step works
When a supplier bill is approved:
DR Purchases (e.g. 6010 - Cost of materials) +1000.00
CR Outstanding payables transit (e.g. 2099) -1000.00The supplier is owed money. The cash hasn't moved yet.
When the bill is paid (via bank feed or manual):
DR Outstanding payables transit (e.g. 2099) +1000.00
CR Bank (e.g. 1020 - Bank UBS) -1000.00The cash leaves the bank. The transit account zeroes out per bill, so your trial balance always tells you "who do I still owe?".
Sales invoices follow three moments:
On issue:
DR Accounts receivable (e.g. 1100)
CR Revenue (e.g. 3400) and VAT
On full payment, in two-step mode:
the invoice is marked paid immediately and the open balance reaches zero.
DR Outstanding receipts (e.g. 1091)
CR Accounts receivable (e.g. 1100)
When the bank movement is reconciled:
DR Bank (e.g. 1020)
CR Outstanding receipts (e.g. 1091)A partial payment leaves the invoice issued and shows the partially paid stage. The journal label uses the description you entered. It does not include the technical idempotency key. The invoice line shows the chart account name.
When to use direct mode instead
Direct mode is still available as an opt-out for two specific cases:
- Cash-only businesses (small retail, market stalls) — payment and invoice happen simultaneously, no transit window.
- Instant-payment-only flows (Twint at point-of-sale) — same story.
For these, Settings → Accounting → Payment posting → Direct removes the transit step. Note: cash payments always use direct mode regardless of this setting.
Why the transit account is configurable
Different chart-of-accounts conventions use different transit codes (2099 in CH, 2980 in some FER variants, 41100 in some custom plans). Numezis lets you map the transit account per company in Settings → Accounting → Chart of accounts → Transit accounts.
Where in the app
- Accounting → Config —
/c/companies/:companyId/accounting/config
Step-by-step
- Confirm Accounting → Config payment mode is
two_step. (Expected: setting persisted per company.) (UAT-C-ACCT-BANK-001) - Approve a supplier bill. (Expected: DR expense / CR transit payable.) (UAT-C-ACCT-BANK-001)
- Register bank payment on the bill. (Expected: DR transit / CR bank; dates preserved.) (UAT-C-ACCT-BANK-001)
- Reconcile bank statement lines to payments. (Expected: match closes open amount.) (UAT-C-ACCT-BANK-001)
- Compare with direct mode on cash-only receipts where policy allows instant bank line. (UAT-C-ACCT-BANK-001)
- If period is locked, payment registration is rejected. (UAT-C-ACCT-BANK-001)
Permissions and modules
Accounting payment posting (accounting.payment.two-step-posting); banking module for reconciliation.
Country and compliance
Outstanding transit accounts required for CH fiduciary audits.