How to Run Period End Close in M3
How do I run period end close in M3
Also searched as
- M3 month end close checklist
- M3 accounting period close process
- how to close an accounting period in M3
- M3 sub-ledger to GL close order
Short answer
M3 period end close is not a single button - it is a sequence: close sub-ledger activity in inventory, purchasing and sales first, reconcile and post any pending vouchers, then close the accounting period in the financials basic data so no further postings can hit it without explicit reopening. Doing the steps out of order is the most common reason a company has to reopen a period after close.
Applies to: Infor M3 Business Engine 10.x-14.x, Financials, Inventory, Purchasing and Order modules
Run a clean M3 period close
- 1Confirm all inventory transactions for the period are posted - receipts, issues, cycle count adjustments and manufacturing order reporting should be complete before you look at closing anything.
- 2Review and clear any transactions sitting in error or suspense queues (MMS statistics update, cost update jobs) so they do not post into the wrong period once it changes.
- 3Close purchasing activity for the period: match and post supplier invoices via APS100 (Supplier Invoice. Record) so accrued but unmatched receipts are identified before period close, not after.
- 4Close order/billing activity for the period: confirm customer orders that should be invoiced in this period have gone through OIS300 invoicing and posted to the ledger.
- 5Run any standard cost update or inventory valuation jobs required by your costing method so inventory value on the balance sheet reflects the period's activity.
- 6Reconcile sub-ledger totals (AP, AR, inventory) against the general ledger control accounts before touching the period status - this is the step that catches most real close problems.
- 7Post any manual GL vouchers via GLS100 needed for accruals, depreciation or adjusting entries for the period.
- 8Update the accounting period status in the Financials basic data so the period is closed to further transaction posting, and communicate the new open period to all transacting modules.
- 9Keep a rollback plan - know which period status change and which vouchers would need to be reversed if a late-arriving transaction forces you to reopen the period.
Why order matters: sub-ledgers before GL
M3, like most ERPs, posts sub-ledger activity (inventory movements, supplier invoices, customer invoices) into the general ledger through automated voucher creation. If the accounting period is closed to new postings before all sub-ledger activity for the period is finished, those late transactions either fail to post, post into the wrong (next open) period, or generate an error queue that has to be manually reconciled - all three outcomes create more work than closing in the right order the first time.
The practical discipline most M3 shops use is a hard cutoff communicated to warehouse, purchasing and order entry teams a day or two before financial close: no more receipts, invoices or shipments should be dated into the closing period after that cutoff unless finance explicitly approves a late entry.
Reconciling sub-ledger to GL before closing
The single highest-value step in the checklist is reconciling inventory value, AP and AR sub-ledger totals against their GL control accounts before changing period status. A mismatch caught here is a same-day fix; a mismatch discovered after the period is closed and the next period has started often requires either a reversing entry in the new period or reopening the closed one, both of which complicate audit trail and reporting for that quarter.
Reopening a closed period
M3 does allow a closed accounting period to be reopened for correction, but it should be treated as an exception process with controlled access, not a routine fix - reopening after downstream reports, tax filings or consolidations have already used the closed period's balances can force those to be rerun. Most finance teams restrict who can change period status and require a documented reason before a reopen happens.
Common pitfalls
- !Closing the accounting period before all supplier invoices for the period are matched and posted, leaving accrued liability misstated.
- !Closing before customer order invoicing (OIS300) for the period is finished, which understates period revenue.
- !Skipping the sub-ledger to GL reconciliation step and only discovering a mismatch during external audit review.
- !Not communicating the close cutoff to warehouse and order entry teams, who keep dating transactions into a period that finance is about to close.
- !Reopening a closed period without a controlled process, then forgetting to re-run downstream consolidation or reporting that already used the old closed balances.
- !Running standard cost updates after period close instead of before, which shifts inventory valuation into the wrong period.
How an ERP-grounded AI assistant handles this
ERPray, grounded in the company's M3 financial and sub-ledger tables, can run the reconciliation checks that normally take a controller an afternoon - comparing inventory sub-ledger totals to the GL control account, listing unmatched supplier invoices, or flagging orders that should have been invoiced in the closing period - and surface just the exceptions that need a human decision, rather than a full manual walk through every module.
Frequently asked questions
What is the right order to close an M3 period in?
Close operational sub-ledgers first - inventory, purchasing invoice matching, and order invoicing - reconcile those totals to the general ledger control accounts, post any manual adjusting vouchers, and only then change the accounting period status to closed.
Can a closed period be reopened in M3?
Yes, M3 supports reopening a closed accounting period for correction, but it should be access-controlled and treated as an exception, since anything that already consumed the closed period's balances (reports, consolidations, tax filings) may need to be rerun.
What causes the most period close delays in M3?
Unmatched supplier invoices and orders that should have been invoiced in the period but were not processed in time are the two most common delays, followed by inventory transactions still sitting in error queues from failed cost updates.
Does M3 automatically stop transactions from posting into a closed period?
Once the accounting period status is set to closed, M3 blocks new GL postings dated into that period from the standard financial programs, though sub-ledger transactions dated into a closed period can still generate errors that need manual handling rather than posting silently.
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-toHow to Create a New Item in M3 (MMS001)
A new item in M3 is created in two stages: item basic data in MMS001 (Item. Open), which defines company-wide attributes such as description, item group and unit of measure, then facility-level data in MMS002 (Item/Facility. Connect), which attaches the item to a specific warehouse or plant with purchasing, planning and costing parameters. An item is not usable for orders, purchasing or MRP until both stages are complete.
Error fixFixing SyteLine's 'transaction out of balance' GL posting error
This posting error means SyteLine tried to create a general ledger journal entry where total debits do not equal total credits, which the GL will not accept. The most frequent causes are a missing or misconfigured account in the automatic account determination setup (COA mapping), currency rounding on multi-currency transactions, or a source transaction (inventory, job cost, AP/AR) that only partially calculated its cost or tax components before posting.
Error fixFix Oracle EBS Workflow Notification Mailer Not Sending Emails
When EBS notifications stop reaching inboxes, check the mailer status in Oracle Applications Manager (OAM) Workflow Manager first - a Suspended or Error status almost always points at an SMTP or IMAP connectivity or credential problem introduced by a mail server change, not at Workflow itself. Fix the mail server configuration, restart the mailer component, and requeue the backlog.
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 ERPAI for Infor M3: A Practical Path from MI Programs to a Private Assistant
Add grounded AI to Infor M3: natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or private cloud in Europe.
Stuck on Infor M3 (M3 Business Engine)?
Talk to engineers who work inside Infor M3 (M3 Business Engine) every week, and who build private AI that answers these questions from your own ERP data.