Posting Exclusions
Keep selected orders out of web-fulfillment accounting postings with exclusion rules that filter by market, store, order type, order status, payment method, and sales or return side.
Posting exclusions are rules that keep matching orders out of web-fulfillment postings. Use them when some orders are booked another way — for example marketplace orders settled through the marketplace's own accounting, or B2B orders invoiced from an ERP — so the same revenue and payments are not booked twice.
Rules are managed under Configuration → Settings → Advanced → Accounting settings, in the Posting exclusions card. Select Add exclusion rule to add one, and the delete icon to remove it.
Exclusions apply only to web-fulfillment postings. POS postings built from Z-reports and the Export bookkeeping file under Reports → Payments are never affected. Rules have no effect unless Web fulfillment posting enabled is on, or postings are generated manually from Reports → Accounting.
Rule fields
| Field | Description |
|---|---|
| Name | Label describing the rule's purpose. Not used for matching. |
| Active | Only active rules are evaluated. |
| Markets | The order's market. |
| Market groups | The market group of the order's market. An order whose market has no market group never matches this filter. |
| Stores | The order's store, or the store the posting is booked at when the order has no store. |
| Store Groups | The store group of that store. |
| Order types | The order's order type. |
| Order statuses | The order's status. |
| Payment methods | Matches when any real-money payment on the order (captured, sold, invoiced, or credited) uses one of the listed payment method names. |
| Transaction types | Which side of a matching order to exclude: Sales, Return, or both. Empty excludes both. |
Order type and order status are evaluated when the posting is generated, not when the order was placed. An order that changes status between runs can match on one run and not on the next.
How rules are evaluated
- Within a rule, every filter you fill in must match (AND). An empty filter matches every order. Matching is case-insensitive.
- Across rules, one matching active rule is enough (OR). When several rules match, their transaction types add up.
Salesremoves the sale side of the order from the posting: its product lines, shipping, captured payments, and deposits taken.Returnremoves the refund side: refunds, returned lines, and deposit refunds.- Each side is removed together with its payments, so the remaining posting still balances.
Transactions that a rule excludes are not recorded as posted. If you later remove or narrow a rule, generate web-fulfillment postings for the affected days under Reports → Accounting to book them.
To stop using a rule, remove it. Turning Active off is currently not kept when the settings are saved — the rule is read back as active.
Examples
| Goal | Filters | Transaction types |
|---|---|---|
| Leave marketplace orders out entirely | Order types: Marketplace | Empty (both) |
| Book B2B sales from the ERP, but keep returns in Omnium | Market groups: B2B | Sales |
| Leave out orders paid by invoice in one market | Markets: NO; Payment methods: invoice | Empty (both) |
Validation
The Validation tab reports exclusion problems — see Configuration:
- active rules exist while Web fulfillment posting enabled is off (info);
- an active rule has no filters, so it matches every order — and with both transaction types it turns web-fulfillment postings off entirely (warning);
- a rule references an unknown market, market group, store group, order type, order status, or payment method (warning);
- a rule has an unknown transaction type (error).
Related pages
- Postings & Ledger Lines — what the sales and return sides of a web-fulfillment posting contain.
- Configuration — web-fulfillment posting settings.
- Postings in the UI — re-run web fulfillment for a date range.