Invoice configuration
The flow form has an optional Configuration block (switch it on with the toggle next to Configuration). It controls how the invoices the flow produces behave. Everything here is optional — a flow runs without it.
Invoice settings
- Invoice description template — builds each invoice's description with the templating engine.
- Sort invoice lines by — the field the invoice lines are ordered by.
- Credit invoice number template — how numbers are built for credit invoices from this flow.
- Payment in days — the payment term; sets the due date that many days after the invoice date.
- Order number template — builds an order/reference number for each invoice.
What users may do with the invoice
These switches decide what's allowed on invoices the flow creates:
- Allow edit, Allow delete, Allow cancel — permit those actions on the invoice.
- Allow delete after completion, Allow cancel after completion — permit them even once the invoice is finalized.
- Require cancelation remark — force a reason when an invoice is cancelled (this is the setting behind the mandatory reason in Cancel or delete an invoice).
Verbose logging
Verbose logging sets how much detail the flow records when it runs: None, User info, Debug info, or Redundant info. Turn it up while diagnosing a flow, and back down for normal running.
Grouping source data into invoices
Two fields on the flow control how source records become invoices:
- Group by data selector — the field used to group source records together.
- Group by template — a template that builds the group key.
Records that share the same group end up on the same invoice — for example grouping all of a month's activities for one debtor into a single invoice.
These settings change what the produced invoices look like and what can be done to them. Change them on a test flow first and confirm with a real execution.