{"id":134,"date":"2026-10-13T09:00:00","date_gmt":"2026-10-13T07:00:00","guid":{"rendered":"https:\/\/yindle.com\/?p=134"},"modified":"2026-10-13T09:00:00","modified_gmt":"2026-10-13T07:00:00","slug":"afas-verkooporder-of-directe-factuur","status":"publish","type":"post","link":"https:\/\/yindle.com\/en\/when-does-an-online-order-become-an-afas-sales-order-or-invoice\/","title":{"rendered":"When does an online order become an AFAS sales order or invoice?"},"content":{"rendered":"

Have accounting approve in advance when an online order is technically submitted as an AFAS sales order or a direct invoice. Open fulfilment often points to a sales order, while a direct invoice fits only an explicitly defined business event. Never make the choice automatically from one payment status: payment, delivery and invoicing are different events.<\/p>\n

Start with the business process, not the connector<\/h2>\n

A paid order may still need picking, a partial backorder, delivery or cancellation. A collection order may be ready while the customer arrives later. For digital or immediately fulfilled products, invoicing may be appropriate almost at once. The correct AFAS destination type therefore depends on the revenue event, stock process, logistics and accounting agreements.<\/p>\n

First describe which source event proves an order is commercially accepted and which event permits delivery or invoicing. Configure the flow only after that. The integration can technically submit either an order or an invoice, but technology should not invent missing financial policy. Always have the responsible accounting team assess the setup; this is not accounting or tax advice.<\/p>\n

A fulfilment matrix as a decision document<\/h2>\n
\n\n\n\n\n\n\n\n\n
Order type<\/th>\nNext physical step<\/th>\nPossible AFAS route<\/th>\nRequired evidence<\/th>\n<\/tr>\n<\/thead>\n
Parcel for shipping<\/td>\nPick, pack and hand over<\/td>\nSales order<\/td>\nValid order and delivery details<\/td>\n<\/tr>\n
Own delivery service<\/td>\nCapacity and route<\/td>\nSales order<\/td>\nFeasible delivery date and address<\/td>\n<\/tr>\n
Collection<\/td>\nReserve and mark ready<\/td>\nAccording to the agreed process<\/td>\nLocation, time and collection evidence<\/td>\n<\/tr>\n
Immediately completed delivery<\/td>\nNo open fulfilment<\/td>\nPossibly a direct invoice<\/td>\nDemonstrable invoicing event<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

Replace \u201cpossible\u201d in your own matrix with an approved choice and exceptions. Also document returns, partial deliveries, zero-value backorders and changes after acceptance. The basis for the technical mapping is described in Connect WooCommerce to AFAS<\/a>.<\/p>\n

Fictional example: paid, but not yet delivered<\/h2>\n

Fictional example: kitchen store Vormvast receives a paid order with four items, one of which becomes available later. The configuration creates an AFAS sales order with the validated lines. The parcel step waits for the agreed fulfilment moment, and the backorder receives separate operational follow-up. Payment alone does not trigger a direct invoice that makes later changes unnecessarily complicated.<\/p>\n

A second fictional order concerns an immediately delivered digital instruction for which accounting uses a pre-approved direct-invoice route. The workflow selects that route from the explicit product and fulfilment type, not because both orders are \u201cpaid\u201d. The audit trail records which rule determined the choice. Accounting can then explain afterwards why two paid orders were processed differently.<\/p>\n

Questions before activation<\/h2>\n