Design how invoices move from import through review, approval, export, treasury payment, and synced completion. Workflows are built in the visual editor under Settings → Workflow.
1. Open the workflow editor
Settings → Workflow opens the canvas for the active tenant. Nodes represent steps; edges show allowed transitions when a step completes or is approved.
Publish changes when ready. In-flight invoices keep their current step unless you run a reset.
Common node types: Review, Approval, Export to accounting, Set status, Set invoice date, Assign invoice tags, Treasury, Conditions.
Set invoice date
Add Set invoice date to assign, copy, or clear invoice date, posting date / month, due date, or (when DATEV RW Leistungsdatum is enabled) delivery date. Use Assign custom with service-period expressions to derive dates from line accruals.
Dedicated guide: Set invoice date (workflow). Delivery field: Delivery date (Leistungsdatum).
2. Conditions on transitions
Condition nodes branch the flow based on invoice data, for example extracted vs calculated total, payment status, cost centre present, document type, or invoice tags.
False branches should land on a human review step, not a dead end.
3. Treasury branch
When treasury is enabled, add nodes such as ready for payment, submit payment batch, and awaiting payment confirmation. Amount on the payment batch should match invoice detail totals.
Related: Embat treasury and SEPA vs international payment batches.
4. Next
Configure an approval matrix when amount tiers or cost centers drive who must sign off.
Quick reference
| Task | Where |
|---|---|
| Edit flow | Settings → Workflow |
| Set dates | Palette → Set invoice date |
| Totals branch | Condition: extracted vs calculated |
| Treasury path | Treasury nodes after approval |
| Approvals | Approval matrix |