Skip to main content

Voucher lifecycle

Voucher writes are exposed through the generated ledger, accounting-entry, and staged-operation API references. This guide explains the state model at a high level.

States​

  • draft: editable accounting work that is not posted.
  • posted: ledger work that has been recorded.
  • reversed: a posted voucher has been reversed by a correction workflow.

Suggestions and imported review items are not posted vouchers. They must become reviewed draft or posted ledger work through the documented endpoint flow.

Safe writes​

Use the generated endpoint page for the exact request body, response body, status codes, and idempotency requirements. For write operations:

  • include the required company scope
  • preserve X-Request-Id for diagnostics
  • use documented idempotency keys when the endpoint requires them
  • treat 409 responses as state conflicts that need a fresh read
  • use correction or reversal workflows instead of editing posted accounting history directly

Provider handoff​

Accounting-system exports, including Fortnox source-control flows, add provider review states on top of the voucher lifecycle. Use the Integration APIs and ledger reference pages for provider-specific pull, review, post, and export operations.