Infor M3 Financials Configuration: Structure, Rules, and Close
Infor M3 financials are configured around a company and division structure, a set of accounting dimensions, and accounting rules that translate business events into ledger postings. The company holds shared master data while divisions carry their own general ledger and reporting, which is how a single M3 instance supports multiple legal entities across countries. Accounting identities define the valid values in each dimension, FAM functions control number series and posting behavior for financial transactions, and accounting rules map each event to debit and credit accounts. Get that chain right and the close becomes routine.
Company, Division, and Accounting Dimension Structure
M3 supports up to seven accounting dimensions. Dimension one is conventionally the main account, and the remaining dimensions carry cost center, cost unit, project, product group, or whatever analytical axes the business requires. Valid values are maintained as accounting identities per dimension, with rules controlling which combinations are permitted and which dimensions are mandatory for a given account. The temptation on every implementation is to add dimensions because they are available. Resist it: each additional mandatory dimension multiplies the validation burden on every transaction and every integration, and unused dimensions are far harder to remove later than to add. Four well-defined dimensions beat seven half-populated ones in every implementation we have reviewed.
- Model divisions on legal entity and statutory reporting requirements, not on management hierarchy
- Define which dimensions are mandatory per account rather than making all dimensions mandatory globally
- Keep dimension values numeric and range-structured so reporting can aggregate by range
- Document the dimension purpose in writing before go-live; ambiguity here causes years of miscoding
FAM Functions, Number Series, and Voucher Control
FAM functions govern how each class of financial transaction behaves: which voucher number series it uses, whether it posts automatically or requires approval, and which detail rules apply. Supplier invoices, customer invoices, payments, and general journal entries each map to their own function with detail records defining the specifics per division. Number series are defined separately and referenced by the function, so a division can maintain statutorily required continuous numbering. Auditors ask about this chain more often than any other configuration in M3, because it establishes that vouchers cannot be created outside a controlled, gapless sequence. Capture the mapping in a single document and keep it with your control evidence.
- Assign separate voucher number series per division and per transaction class for clean statutory reporting
- Review FAM function detail records whenever you add a division; missing details cause posting failures at go-live
- Restrict manual journal entry functions to a named approver group and log the exceptions
- Never reuse or reset number series mid-year, even in test, so environments remain comparable
Accounting Rules: Turning Operational Events into Postings
M3 posts operational activity through accounting rules that combine an accounting event with an account entry type and produce the accounts to debit and credit. A goods receipt, an inventory adjustment, an order invoice, and a work in process movement each raise an event, and the rule set decides where the value lands. This is the most powerful and most misunderstood area of M3 financials. Missing rules produce failed or suspended postings rather than wrong numbers, which is preferable but still disruptive at close. Build a complete matrix of events used by your operational configuration, walk every one through a test transaction, and keep the matrix under change control.
Period Close, Reconciliation, and Statutory Reporting
A clean M3 close depends on the operational side more than the finance side. Unreported receipts, unconfirmed picking lists, open manufacturing orders past their finish date, and unmatched supplier invoices all carry into the ledger as reconciliation work. Build a close calendar that requires operational cutoff before financial cutoff, run the inventory to general ledger reconciliation before opening the next period, and review suspended postings daily rather than monthly. Multi-country groups should also confirm currency revaluation, intercompany balances, and local statutory formats early, because a surprise in local reporting requirements is the most common cause of a delayed close. Publish the close calendar to operations, not just to finance.
How Netray AI Agents Shorten the M3 Close
Netray agents reconcile inventory subledger movement against general ledger postings continuously rather than at month end, surfacing the specific transactions behind a variance instead of a total. They also monitor for suspended postings, missing accounting rule combinations after a configuration change, and operational documents that will block cutoff, and route each to an owner with the business key attached. Finance teams using this typically compress close by two to four days in the first quarter, mainly by eliminating the investigation phase. The agents can be deployed on-premises for controlled environments where financial data cannot leave the network, and they log every recommendation for audit review.
Frequently Asked Questions
What is the difference between a company and a division in Infor M3?
The company is the top-level entity holding shared configuration and master data such as items and business partners, while divisions sit inside it and each carry their own general ledger, accounting periods, and statutory reporting. That structure lets a single M3 instance serve multiple legal entities that share operational data but must report separately. Nearly all financial tables are keyed by both company and division, so any report or extract must filter on both.
What are accounting rules in Infor M3?
Accounting rules translate operational events into ledger postings. Each event, such as a goods receipt, inventory adjustment, or customer invoice, is combined with an account entry type, and the rule determines the accounts and dimensions used for the debit and credit. If a required combination has no rule, the posting suspends rather than posts incorrectly. Building and change-controlling a complete event matrix during implementation prevents most posting failures after go-live.
How many accounting dimensions does Infor M3 support?
M3 supports seven accounting dimensions. The first is conventionally the main account and the remaining six carry analytical axes such as cost center, cost unit, project, or product group. Valid values are maintained as accounting identities per dimension, and you control which dimensions are mandatory for each account. Use only the dimensions you will genuinely report on, because every mandatory dimension adds validation load to transactions and integrations and is difficult to retire later.
Key Takeaways
- 1Company, Division, and Accounting Dimension Structure: M3 supports up to seven accounting dimensions. Dimension one is conventionally the main account, and the remaining dimensions carry cost center, cost unit, project, product group, or whatever analytical axes the business requires.
- 2FAM Functions, Number Series, and Voucher Control: FAM functions govern how each class of financial transaction behaves: which voucher number series it uses, whether it posts automatically or requires approval, and which detail rules apply. Supplier invoices, customer invoices, payments, and general journal entries each map to their own function with detail records defining the specifics per division.
- 3Accounting Rules: Turning Operational Events into Postings: M3 posts operational activity through accounting rules that combine an accounting event with an account entry type and produce the accounts to debit and credit. A goods receipt, an inventory adjustment, an order invoice, and a work in process movement each raise an event, and the rule set decides where the value lands.
Put this into numbers
Free interactive tools for exactly this problem. No signup to use them.
Financial Close Cycle Time Calculator
Quantify the labor hours and annual cost consumed by manual journal entries and reconciliations, and model a realistic automated close target.
Free ToolERP Month-End Close Checklist
A 32-point close checklist built for manufacturing ERP, covering transaction cutoff, inventory and WIP valuation, subledger reconciliation, and period lock.
Free ToolCapEx Payback and NPV Calculator
Build the payback period, net present value, and lifetime ROI numbers your capital approval request needs for equipment, automation, or ERP investments.
Terms used in this article
If your M3 close runs on spreadsheets and detective work, Netray can automate the reconciliation and exception routing that eats the first week of every month.
Related Resources
Infor M3 Technical Architecture: A Practical Guide
Infor M3 technical architecture explained: M3 Business Engine, Infor Grid, database tables, H5 client, and integration layers for on-prem and CloudSuite teams.
Infor M3Infor M3 Manufacturing Execution Setup
Infor M3 manufacturing execution setup: product structures, routings, MO statuses, operation and receipt reporting, and shop floor data capture practices.
Infor M3Infor M3 Upgrade and CloudSuite Migration
Infor M3 upgrade and CloudSuite migration guide: modification inventory, extensibility rework, data strategy, testing waves, and 9 to 18 month timelines.