# Infor M3 order to cash: the flow and the programs > Source: https://netray.co/erp-help/infor-m3-order-to-cash-process-programs > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer M3 order to cash runs customer order entry (OIS100), allocation, picking and delivery in warehouse management (MWS410 delivery handling), then invoicing, which transfers the invoice to Accounts Receivable and the general ledger, and finally cash application. The customer order line status shows where each line is stuck. ## Kind how-to ## System infor-m3 ## Erp Infor M3 ## Module Customer Order Management / Warehouse / Invoicing ## Query infor m3 order to cash ## Alternate Queries - m3 customer order to invoice flow - m3 order to cash programs OIS100 MWS410 - infor m3 customer order status 22 44 66 77 ## Applies To Infor M3 13.x, distribution and manufacturing configurations. Program numbers and status behaviour depend on your order type and warehouse settings. ## Steps ### The order to cash chain, step by step **Items:** - Customer order entry: OIS100 creates the order header and lines against a customer (CRS610) and items (MMS001). Price, discount and credit check run here. - Allocation: the line allocates stock from the warehouse, or triggers a purchase or manufacturing order for make-to-order items. - Picking: the pick list is released and printed or sent to the handheld. Pick confirmation reports what was actually picked. - Delivery: the delivery is created and confirmed through the delivery handling (MWS410). This is the goods issue that reduces inventory and starts the shipping document. - Invoicing: a customer invoice batch selects delivered lines, creates invoices and updates them to Accounts Receivable. Prices and tax are fixed at this step. - Accounts Receivable and GL: the invoice posts to the receivable and revenue accounts using accounting control objects. - Cash application: customer payments are matched to open invoices in AR, which closes the cycle. - Follow the order status on the line to see where it is: typically 22 for entered, 33 for allocated, 44 for picked or pick list printed, 66 for delivered, 77 for invoiced. ## Sections ### Status as a diagnostic tool **Body:** A customer order line moves through statuses as the process completes. The most useful support question is simply 'which status is the line in, and what program moves it to the next one?'. Lines at 22 are not allocated, lines at 44 are waiting for delivery, lines at 66 are delivered and waiting for invoicing. Large backlogs at 66 mean invoicing is not being run. Large backlogs at 22 point at stock, credit hold or planning problems. The exact numbers can be adjusted by status settings, so confirm them in your order type setup. ### Where orders typically stall **Body:** Credit hold or credit limit stops an order at entry or before release. Missing stock leaves lines unallocated. A wrong warehouse or facility setting on the order type blocks picking. Delivery confirmation not done at the dock leaves lines unbilled. Invoicing stalls when a line has no valid price, tax code or accounting control object, or when invoice batches are not scheduled. These need master data fixes, not workarounds. ### Make to order and special flows **Body:** Make to order lines create a manufacturing order or a purchase order and the customer line waits for that supply. Drop shipments, returns, consignment and intercompany orders use their own order types and variations of the same chain. Treat each as a separate test path in any upgrade or project, since each hits different programs and accounting. ### Revenue and reconciliation **Body:** - Because shipping and invoicing are different events, there can be delivered but not invoiced value at month end. Finance usually accrues it or reports it as a reconciliation item between the order, delivery and invoice views. - Run the delivered-not-invoiced list before closing the period and decide how to treat it. ## Pitfalls - Assuming status numbers are the same at every site; they depend on order type and warehouse settings. - Not scheduling the invoice batch and discovering a large delivered-not-invoiced balance at month end. - Entering orders for items with no price list, leaving invoicing stuck on missing price. - Skipping delivery confirmation at the dock so stock and revenue are wrong. - Treating returns and credit notes as a mirror of the sale; they run through their own order types. ## Ai Angle Order to cash questions are natural for a grounded assistant: how many lines are stuck at which status, which customers have the oldest delivered-not-invoiced lines, why a given order has not been invoiced. ERPray answers these read-only from live M3 data and shows the query. It does not release, deliver or invoice anything on its own. ## Faq ### Which M3 program enters a customer order? **Answer:** OIS100 is the customer order program for entering and maintaining the order header and lines. Related programs handle delivery (MWS410 delivery handling) and invoicing. ### What do M3 customer order line statuses mean? **Answer:** Typically 22 means entered, 33 allocated, 44 picked or pick list printed, 66 delivered and 77 invoiced. Your order type and settings can change which statuses are used, so check your own setup. ### Why is my delivered order not invoiced? **Answer:** The invoice batch has not been run for it, or the line is missing a valid price, tax code or accounting control object. Check the invoice batch log and the line setup. ### Does M3 post revenue at delivery or invoice? **Answer:** Inventory leaves at delivery, while revenue and the receivable post when the invoice is updated. The gap between them is the delivered-not-invoiced position finance needs to manage. ## Search terms infor m3 order to cash, m3 customer order process, m3 OIS100, m3 MWS410 delivery, m3 order line status, m3 invoicing batch, m3 delivered not invoiced --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json