Controls and the journal
Second-person approval by default, a journal you can verify, drill-down from a statement figure to the source document, and a month close with period lock.
The approval step, on screen.
Illustrative screen with synthetic data.
Illustrative screen · synthetic data
AI prepares, a person approves
With AI turned on (it is off by default), a suggestion proposes the expense account and the VAT code. It has no posting authority. The preparer submits; by default a second person approves before the bill posts. The preparer cannot approve their own bill.
Four-eyes approval.
By default, postings and bills post only after a second person approves them. This is a company policy. Changing the policy is itself an approved change.
A maker cannot approve their own change. The database enforces this rule.
An append-only journal you can verify.
The journal, the audit log and the access log are append-only and hash-chained. A “verify ledger” check lets you verify the chain.
Drill from a figure to the source document.
Start from a figure on a statement. Open the accounts behind it, then the lines, then the entry, then the source document.
Company isolation.
Each company’s data is isolated from the others by row-level security in the database.
Foreign currency and month close.
-
Multi-currency
Foreign-currency postings are recorded with their rates.
-
FX revaluation
At month close, FX revaluation is proposed as draft entries.
-
Close runs
A month close runs with a checklist and ends with a period lock.
Statements.
-
Balance sheet and income statement
Each on its own screen, in the Swiss OR art. 959a / 959b structure.
-
Cash-flow statement
Indirect method, on its own screen.
-
Trial balance
On its own screen.
-
General ledger
Account lines, on their own screen.
See your own documents go through the journal.
Bring a QR-bill, a camt bank statement or a VAT period. We will walk through how documents are prepared, approved and posted, and how a VAT return is reviewed and exported.