Invoicing strategies
An invoicing strategy decides whether an order gets its own invoice, or is combined with others into one.
The two strategies
An invoice per order. Every order produces its own. Straightforward to trace: one order, one document, and a customer querying an invoice is querying one order.
Aggregated daily. Eligible orders from a day are combined into a single invoice. Fewer documents, which matters for a trade customer placing several orders a week — they get one invoice rather than fifteen.
How the strategy is chosen
Four things are consulted, in this order, and the first that applies wins.
1. Mixed payment methods. An order paid by more than one method always gets its own invoice, whatever anything else says. It cannot be bundled with others, because the payments would no longer line up with the document.
2. The customer account's override. This is the strongest ordinary setting. An account set to a daily summary gets one, regardless of which channel its orders arrive through.
3. The channel's default — with one exception. If the channel aggregates daily but the order was paid by a method that invoices per order or defers, that order opts out and keeps its own invoice, so the payment and the document settle together.
The opt-out only works one way. A method that could be aggregated never pulls an order into aggregation on a channel set to invoice per order.
4. The payment method's own posting behaviour, when nothing above decided.
The account beats the channel
Worth stating plainly, because the intuition often runs the other way: the customer account overrides the channel, not the other way round.
The channel setting is a default for orders arriving through it; the account setting is a decision about how that customer is billed. A trade customer wanting one invoice a day gets one whether they order through the trade portal or the public storefront.
If an account's strategy appears to be ignored, the cause is almost never the channel — check for mixed payment methods on the order, which override everything.
Choosing between them
Per order suits consumer sales, where each order is a separate transaction and the customer expects a document matching what they bought.
Aggregated daily suits trade customers ordering repeatedly, where a single daily invoice is easier for both sides to handle and reconcile.
The distinction is really about how the customer wants to be billed rather than anything technical, which is why the setting lives on the channel and the customer account rather than somewhere central.
What it does not change
What is posted — the same revenue, the same tax, the same accounts. Only how it is grouped into documents.
When it is recognised — aggregating does not defer anything into another period.
Credit notes — value going back to the customer produces a credit note either way.
Order edits
An edit to an order already covered by an invoice does not rewrite that invoice, whichever strategy produced it. It produces a supplementary document. See editing an order after posting.