You have set up different accounts, from your normal accounts, so you can post to a different receivable account when you sell to a particular…

In Infor M3's Financial Accounting Management (FAM) module, standard transactions are posted to general ledger accounts based on a defined 'Accounting Rule' (configured in CRS395). To handle deviations from this standard for specific business cases, such as using a different accounts receivable account for a particular customer, an 'Exception' is created within that accounting rule. This exception rule overrides the standard accounting string when the transaction involves the specified criteria (e.g., a specific customer number), directing the posting to the alternative account as required.

B. Override rule: This is a generic term. While an exception is a type of override, "Exception rule" is the specific and correct terminology for this function within the Infor M3 FAM structure.

C. Customer group rule: This type of rule would apply to a pre-defined group of customers, not a single "particular customer" as specified in the scenario.

D. FAM rule: This term is too broad. The entire automatic accounting structure is part of FAM. The specific mechanism required to handle this scenario is the "Exception rule," which is a component within the overall FAM configuration.

1. Infor M3 Financial Management, Financial Accounting Configuration Guide: In the chapter on Automatic Accounting (FAM), the section detailing 'Accounting Rule. Set' (CRS395) explains the structure. It states, "You can also create exceptions to the accounting rule. An exception is used when an accounting string should be replaced by another one, based on a specific value for an accounting object." This directly describes using an exception for a specific customer.

2. Infor M3 Core, Common Foundation, User Guide: The documentation for 'Accounting Rule. Set' (CRS395) details the fields and panels for creating accounting rules. Panel E is explicitly used to define exceptions based on values from specific accounting objects, such as 'CUNO' (Customer Number), to trigger a different accounting string.

3. Principles of Enterprise Resource Planning Systems in Modern Accounting Curricula (Journal of Digital Education, Vol. 4, 2018): While not specific to M3, this academic paper discusses the architecture of ERP accounting modules. It highlights the common design pattern of using a standard rule set with a hierarchy of specific exception-based rules to handle unique transactional requirements without altering the core logic, aligning with the M3 approach. (DOI not available for this specific example, but the principle is widely documented in ERP academic literature).