Infor M3 order to cash: the flow and the programs
infor m3 order to cash
Also searched as
- m3 customer order to invoice flow
- m3 order to cash programs OIS100 MWS410
- infor m3 customer order status 22 44 66 77
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.
Applies to: Infor M3 13.x, distribution and manufacturing configurations. Program numbers and status behaviour depend on your order type and warehouse settings.
The order to cash chain, step by step
- 1Customer order entry: OIS100 creates the order header and lines against a customer (CRS610) and items (MMS001). Price, discount and credit check run here.
- 2Allocation: the line allocates stock from the warehouse, or triggers a purchase or manufacturing order for make-to-order items.
- 3Picking: the pick list is released and printed or sent to the handheld. Pick confirmation reports what was actually picked.
- 4Delivery: the delivery is created and confirmed through the delivery handling (MWS410). This is the goods issue that reduces inventory and starts the shipping document.
- 5Invoicing: a customer invoice batch selects delivered lines, creates invoices and updates them to Accounts Receivable. Prices and tax are fixed at this step.
- 6Accounts Receivable and GL: the invoice posts to the receivable and revenue accounts using accounting control objects.
- 7Cash application: customer payments are matched to open invoices in AR, which closes the cycle.
- 8Follow 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.
Status as a diagnostic tool
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
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
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
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.
Try it here, free
Infor M3 Customer Order Status Tracking Worksheet
Document what each customer order status means in your M3 setup, stage by stage, and share it with the order desk.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
Which M3 program enters a customer order?
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?
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?
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?
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.
Related
How to Enter a Customer Order in M3 (OIS100)
OIS100 (Customer Order. Open) is the primary M3 program for entering and maintaining customer orders, built as a header-then-line workflow: you first create the order header with customer, order type and delivery terms, then add order lines that each carry their own item, quantity, price and delivery date defaulted from customer and item agreements.
How-toSyteLine Customer Order to Invoice: Step by Step
A SyteLine customer order flows from Order Entry through pick, pack, and Customer Shipment, then to invoicing, either through the Auto Invoice batch utility or manual Invoice Entry, posting revenue and relieving inventory once the shipment is confirmed.
How-toHow to record an expense in the general ledger in Infor M3
In M3 an expense reaches the general ledger as a voucher: either a supplier invoice entered in Accounts Payable (the APS450 family) that debits an expense account and credits the AP control account, or a manual journal voucher entered in General Ledger (GLS040 in most installations). Either way the voucher needs a valid accounting string, a balanced total, and must be updated to the ledger.
How-toPick Line vs Wave Line in Infor M3
A pick line is the instruction to pick a quantity of an item from a location for one order line. A wave groups many such lines so the warehouse releases and works them together by time, route, carrier or zone. Terminology and screens depend on your M3 release and warehouse setup, so confirm against your own configuration.
Error fixM3 API Error: Record already exist
Record already exist means the MI Add transaction you called is trying to insert a key that is already present in the target M3 table, most often because a prior call succeeded and was retried, or because the key fields you built do not match what you think they match. Read the errorField and errorFieldGroup attributes on the response to see exactly which key field M3 flagged, then either switch to the matching Chg (change) transaction or fix the key construction in the caller.
AdvancedPaging M3 API MI List Transactions Past the Default Record Limit
M3 List transactions (the read/browse transaction most MI programs expose, such as CRS610MI.LstByNumber or OIS100MI.LstOrderHead) cap the rows returned per call using the MaxReturnedRecords input field, and by default many clients leave it low or unset, which looks like the API silently truncating results. Set MaxReturnedRecords explicitly, then loop the call using the last key values from the previous page as the starting position until fewer rows than the limit come back.
AI for ERPInfor M3 AI: A Practical Path from MI Programs to a Private Assistant
Infor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
Stuck on Infor M3?
Talk to engineers who work inside Infor M3 every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor M3 Customer Order Status Tracking WorksheetDocument what each customer order status means in your M3 setup, stage by stage, and share it with the order desk.
- Infor M3 Program Reference (MMS001, OIS100, PMS100)Searchable lookup of frequently used Infor M3 programs by code, area and purpose, so you stop hunting through menus.
- Infor M3 User Acceptance Test Script TemplateFill-in UAT script with scenario, preconditions, step table, results and sign-off for M3 end to end process testing.
ERP fixes and how-tos
- How to Enter a Customer Order in M3 (OIS100)Practical walkthrough of entering a customer order in Infor M3 OIS100: header setup, order type, line entry, pricing, availability check and confirmation.
- Pick Line vs Wave Line in Infor M3Pick line versus wave line in Infor M3: what each represents in warehouse picking, how waves group work, and how to decide which applies in your setup.
- Private AI Layer for Infor M3 On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to Infor M3 on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
Runs with your ERP
- Infor M3 Scheduling Workbench and M3: finite scheduling explainedHow Infor M3 Scheduling Workbench schedules against capacity and materials and writes orders back to M3 via PSMI, with setup, pitfalls and AI help.
- Infor Factory Track and Infor M3: handheld scanning transactionsHow Infor Factory Track gives M3 handheld scanning for receive, putaway, move, count, pick, pack and shipment loading, with setup steps, pitfalls and AI uses.
- Infor EDI Managed Service and Infor M3 over IONHow Infor's EDI managed service connects to Infor M3 through ION with pre-built trading partner links: data flows, setup steps, pitfalls and a private AI layer.
Guides
- Infor M3 Customer Order Management: OIS100 Configuration, Pricing, and ATPMaster Infor M3 customer order management. Configure OIS100 order entry, pricing, ATP checks, credit management, and delivery scheduling in M3 13.4+.
- Infor M3 Distribution Management and Order Fulfillment SetupConfigure Infor M3 distribution management with order processing, warehouse allocation, shipping integration, and customer delivery scheduling best practices.
- Infor M3 Warehouse Management: Setup and Daily FlowHow the Infor M3 warehouse management system works: warehouses, locations, balance IDs, picking, replenishment and cycle counts. A practical setup guide.
AI on your ERP
- Infor M3 Customer Order Management With AI for Status, Allocation and Promise DatesAI for Infor M3 customer order management: answer order status, allocation and delivery date questions from OOHEAD and OOLINE data without exposing it publicly.
- Infor M3 AI: A Practical Path from MI Programs to a Private AssistantInfor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
Integrations
- How to add WhatsApp to Infor M3How to connect WhatsApp Business to Infor M3: M3 API (MI programs), ION events, template messages, opt-in rules and two-way replies, including on-prem M3 setups.
- How to add AI agents to Infor M3How to add AI agents to Infor M3: a tool layer over MI programs and ION, read-first workflows for POs, MO and CO exceptions, and human approval on writes.