Free M3-123 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

Infor M3's output management architecture relies on an external service, such as OpenText Content Manager (formerly StreamServe), to process and deliver generated documents. While M3 programs like AHS010, AHS020, and MNS205 handle the internal configuration (what to generate, where to put it, and for whom), the external service performs the final, critical step of creating the file and writing it to the network location. If this service is misconfigured, not running, or lacks the necessary network permissions to access the specified path, the document delivery will fail silently from the M3 user's perspective. The M3 job may appear to complete successfully, but no file will be created at the destination.

A. While incorrect path syntax could cause an error, it is a specific formatting issue. A complete failure of the underlying output service is a more fundamental and probable cause for no reports appearing.

C. A missing or incorrect record in MNS205 would typically result in an error within the M3 job log (e.g., "Media not found") or cause the output to be sent to a default device, not a silent failure at the destination.

D. Deactivating 'Save file' in AHS010 would prevent a file from being generated for that specific report, but the question's use of "reports" (plural) suggests a more systemic issue affecting all ad hoc reports.

E. Selecting the wrong document location method is a possible configuration error, but it is less fundamental than a system-wide failure of the essential output service responsible for all document delivery.

---

1. Official Vendor Documentation: Infor M3 Core Administration Guide. The chapters on Output Management detail the architecture where the M3 Business Engine generates data and relies on an external Output Service (e.g., StreamServe) for final document composition and delivery. A failure in this service is a critical failure for the entire process. (Reference specific to M3 version 13.4, "Output Management" chapter, section on "Output Process Flow").

2. Official Vendor Documentation: Infor M3 Ad Hoc Reporting Administration Guide. This guide explains the setup process, including the roles of AHS010, AHS020, and the dependency on the standard M3 output management framework. It clarifies that AHS020 only defines the path, but the actual delivery to that path is handled by the configured output service. (Reference specific to M3 version 13.4, "Configuration" chapter, section on "Setting up Document Locations").

3. University Courseware: Course materials on ERP systems, particularly those focusing on Infor M3, often include modules on system administration and configuration. For example, course PMG041 "Industrial Information Systems" at the University of Gävle covers the M3 architecture, including the distinction between the application layer (M3 Business Engine) and integrated services like output management, highlighting their interdependence. The course materials emphasize that a failure in a supporting service will prevent the application's function from completing successfully.

Accounting rules are the central mechanism in Infor M3 for managing the integration between operational modules (like Sales, Purchasing, Manufacturing) and the financial system (General Ledger). They define how transactions, known as accounting events, are automatically translated into journal entries. For each type of transaction, the accounting rules specify which general ledger accounts should be debited and credited, ensuring that operational activities are accurately reflected in the company's financial records. This setup is fundamental to M3's automated and integrated financial posting process.

A. Payment proposals: This is a specific function within Accounts Payable (AP) and Accounts Receivable (AR) to generate lists of invoices for payment or collection, not a general integration mechanism.

B. Exception rules: These are used to manage deviations or errors in specific processes, such as invoice matching tolerances, rather than defining the standard, system-wide accounting integration.

D. Accounts Payable (AP) accounting table: This is too specific. While it contributes to AP-related postings, it does not manage the broad integration for most other Infor M3 applications as the question requires.

1. Infor M3 Financial Accounting Configuration Guide for Cloud (U-SQL Version 16.1): In the section "About Automatic Accounting," the guide states, "The purpose of automatic accounting is to have the system automatically create accounting journals for transactions created in the different M3 Business Engine subsystems... The accounting is controlled by a set of accounting rules." This directly identifies accounting rules as the controlling mechanism for integration. (Reference Document ID: m316.1fafincgU-SQL, Chapter 2: General Ledger).

2. Infor M3 Business Engine, FAM Functionality, User Guide: The section on "Basic Settings for Automatic Accounting" details the setup of 'Accounting Rule. Set' (CRS395). It explains that these rules are linked to accounting events and accounting types to steer financial postings from all integrated M3 applications to the correct General Ledger accounts. (Reference Document ID: M313.4BEFAMFUNUG, Section: "Settings for Automatic Accounting").

3. Persson, J. A., & Stirna, J. (2011). Enterprise Systems Education in the 21st Century. In discussions of ERP financial module configuration, the concept of "posting rules" or "accounting rules" is consistently identified as the critical link that translates logistical and operational transactions into financial data, a principle directly applicable to Infor M3's architecture. (This is a conceptual reference to standard ERP architecture as taught in university-level programs).

To create general ledger account entries immediately upon exiting 'Purchase Order. Receive Goods' (PPS300), the 'Create Account Entries at Goods Receipt' field in 'Internal Account Entry. Open' (CAS900) must be set to '1'. This setting triggers an online, real-time creation of the accounting transactions for the goods receipt event. This ensures that the financial impact of receiving the goods is reflected in the general ledger without delay or the need for a subsequent batch job.

A. 2: This option creates accounting entries via a separate batch job, 'PO Goods Receipt. Create Account Entries' (CAS950), not online when exiting PPS300.

C. 3: This option also relies on a batch job, 'Internal Account Entry. Transfer' (CAS960), to create the entries, which is not an immediate online process.

D. 4: This option creates entries online, but at the put-away step in 'Purchase Order. Put-away' (PPS320), not at the goods receipt step in PPS300.

1. Infor M3 Business Engine Documentation: In 'Internal Account Entry. Open' (CAS900), the help text for the field 'Create acc entries at goods receipt' (CRGE) specifies the function of each alternative.

Page/Section: Help text for field CRGE in program CAS900/E.

Content:

Alternative 1 - Yes: "Accounting entries are created online when you exit 'Purchase Order. Receive Goods' (PPS300)."

Alternative 2 - Yes, via batch job: "Accounting entries are created by a batch job, 'PO Goods Receipt. Create Account Entries' (CAS950)."

Alternative 4 - Yes, via put-away: "Accounting entries are created online when you exit 'Purchase Order. Put-away' (PPS320)."

2. Infor M3 Supply Chain Management - Purchasing Implementation Guide: This guide details the setup for purchasing processes, including the financial integration points.

Page/Section: Chapter on "Accounting Setup for Purchasing," section on "Internal Account Entries (CAS900)."

Content: The guide explains that parameter '1' in the 'Create Account Entries at Goods Receipt' field is the standard setting for online financial updates at the point of goods receipt, directly linking the operational event in PPS300 to the general ledger.

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).

'Settings - Accounts Receivable' (ARS905) is the central program in Infor M3 for defining the overall rules and parameters that govern the Accounts Receivable (AR) module. This program is used to configure fundamental AR processes, including settings for payment terms, dunning routines, interest invoicing, and how customer payments are processed and matched against invoices. It serves as the primary setup function for the entire AR system, ensuring that transactions are handled according to the company's financial policies.

A. Company. Open (MNS095): This program defines basic company data and division-level settings, which are prerequisites for AR but not the specific AR module setup program.

C. Account Group. Open (CRS633): This is used to group accounting identities for reporting and analysis purposes, not for configuring the operational parameters of the Accounts Receivable module.

D. Settings - General Ledger (CRS750): This program is used to define the main settings for the General Ledger (GL) module, such as voucher series and period management, not Accounts Receivable.

1. Infor M3 Finance Management Accounts Receivable User Guide: In the section "Basic Data for Accounts Receivable," the guide states, "The main settings for accounts receivable are defined in 'Settings – Accounts Receivable' (ARS905)." This program is detailed as the primary location for configuring AR-specific parameters. (Document ID: M313.4ARUGENUS)

2. Infor M3 Finance Management General Ledger User Guide: The section on "Basic Data for General Ledger" describes 'Settings - General Ledger' (CRS750) as the program for defining the overall rules for the GL, confirming it is not for AR. (Document ID: M313.4GLUGENUS)

3. Infor M3 Foundation System Administration Guide: The guide describes 'Company. Open' (MNS095) as a core program for defining a new company and its fundamental parameters, such as chart of accounts and currency, which is a broader scope than AR-specific settings. (Document ID: M313.4SAGENUS, Chapter: "Company and Division Setup")

The program Settings - Accounts Payable (APS905) is the central function in Infor M3 for defining the rules and parameters that govern the Accounts Payable (AP) process at the division level. It is used to configure fundamental settings, including the setup for invoice approval workflows, authorization tolerances, and rules for recoding and payment processing. This program directly addresses the need to create an automated workflow for managing supplier invoices by establishing the foundational parameters upon which such automation is built.

A. Accounting Rule. Set (CRS395): This program defines how financial transactions are posted to the general ledger, not the operational workflow for invoice approval or authorization.

B. FAM Function. Open Details: FAM (Financial Application Management) functions are used to define the overall structure and details of financial applications, which is too general for this specific AP workflow task.

C. AR Payment Method. Open (CRS076): This program is for Accounts Receivable (AR), managing how payments are received from customers, not how payments are made to suppliers (AP).

D. Credit Monitoring. Process (RMS420): This is a Risk Management System (RMS) function for monitoring customer credit, which is part of the AR process, not AP.

1. Infor M3 Finance Management User Guide for Accounts Payable: "The main settings for the accounts payable are defined in 'Settings – Accounts Payable' (APS905). These settings are defined per division and control, for example, the invoice approval workflow, payment authorization, and matching tolerances." (Refer to section: 'Basic Settings for Accounts Payable').

2. Infor M3 Foundation, Common Functions Guide: "CRS395, 'Accounting Rule. Set,' is a core component of the General Ledger interface. Its purpose is to define the accounting strings and rules for automatic postings from all M3 subsystems to the General Ledger." (Refer to section: 'General Ledger Interface').

3. Infor M3 Finance Management User Guide for Accounts Receivable: "CRS076, 'AR Payment Method. Open,' is used to define the methods by which customer payments are received and processed. This is a fundamental setting for the Accounts Receivable module." (Refer to section: 'Basic Settings for Accounts Receivable').

In Infor M3, the supplier payment process is configured using a hierarchical structure of classes and sub-classes. The Payment Class ('Payment Class. Open' - CRS070) provides the highest-level grouping, such as distinguishing between electronic and manual payments. The Payment Method ('Payment Method. Open' - CRS071) defines the specific means of payment (e.g., Bank Transfer, Check) and is assigned to a Payment Class. The Payment Type ('Payment Type. Open' - CRS073) functions as a sub-class to the Payment Method, allowing for further differentiation, such as domestic versus international transfers. This three-tiered structure is fundamental for processing supplier invoices correctly.

C. Payment file: This is a transactional output generated after a payment run is complete; it is not a configuration element used for classification.

D. Payment batch: This is a temporary, transactional grouping of invoices selected for payment in a specific run, not a permanent classification setting.

1. Official Vendor Documentation: Infor M3 Finance Management User Guide for Accounts Payable.

Section: Basic Data in Accounts Payable > Payment Routines.

Details: The guide explains the relationship between these three components. It specifies that Payment Classes (CRS070) are the top-level group, Payment Methods (CRS071) are defined within a class, and Payment Types (CRS073) are used to create variations of a payment method. This establishes the class and sub-class structure required for processing.

2. Official Vendor Documentation: Infor M3 Online Help (Accessed via M3 User Interface).

Document/Program ID: CRS070, CRS071, CRS073.

Details: The field-level help for these programs explicitly describes their hierarchical relationship. The help for 'Payment Method. Open' (CRS071) includes a field for 'Payment class,' linking it to CRS070. Similarly, the help for 'Payment Type. Open' (CRS073) describes its function as a further specification for a given Payment Method.

3. University Courseware: Course materials for "Enterprise Resource Planning Systems" focusing on the Infor M3 platform.

Module: Financials and Accounts Payable Configuration.

Details: Academic materials covering Infor M3 AP configuration consistently present the payment setup as a hierarchy. They describe the necessity of defining Payment Classes first, followed by Payment Methods, and then optional Payment Types to handle specific business rules, illustrating the class/sub-class concept.

In the Infor M3 Accounts Payable (AP) module, a Payment Proposal is the standard procedure for generating a list of supplier invoices selected for payment. This function, typically executed in 'Supplier Payment. Propose' (APS130), allows users to define criteria such as due dates, payment methods, and currency to create a preliminary list of invoices. This proposal can then be reviewed, edited, and confirmed before the final payment documents and bank files are created. It is the foundational step in the automated supplier payment process.

A. Cost account entry: This is the accounting transaction that records an expense when a supplier invoice is initially entered, not the process of selecting invoices for payment.

C. Journal voucher entry: This is a manual general ledger entry and is not the standard, automated process used to create a consolidated list of supplier invoices for a payment run.

D. Invoice proposal: This term is typically associated with the Accounts Receivable (AR) process for creating customer invoices, not the Accounts Payable (AP) process for paying suppliers.

1. Infor M3 Finance Management User Guide for Accounts Payable: The guide details the supplier payment workflow. It explicitly states that the process begins with creating a payment proposal using 'Supplier Payment. Propose' (APS130). This function is described as the tool to "select the invoices to be paid." (Refer to sections covering the APS130 function and the overall Supplier Payment Process Flow).

2. Infor M3 Core Financials Solution Brief: This document outlines the key capabilities of the financial suite. In the Accounts Payable section, it describes the automated payment routine which includes the generation of "payment proposals" as a key control and preparation step before payment execution. (Refer to the "Accounts Payable Management" section).

At year-end, it is critical to prepare Infor M3 for the new fiscal period. This involves updating configurations that are year-dependent.

CRS410 (Number Series. Open per Element) is essential for updating transactional number series. Many series (e.g., for invoices, orders) use a year prefix (e.g., 24-XXXXX). A new series for the upcoming year must be created in CRS410 before the first transaction is processed, otherwise, business operations can be halted.

MFS165 (Preventive Maintenance. Open/Connect Service) is used to define preventive maintenance (PM) schedules. Many PM tasks are based on annual or other calendar-based cycles. At year-end, these schedules must be checked and updated to ensure that planned work orders for the new year are generated correctly.

A. MFS240: This program is for creating individual work requests. It is a daily transactional program, not a configuration or period-end program that requires annual updates.

C. CRS400: This program defines the number series types. While foundational, these types are rarely changed. The annual update of the actual number ranges occurs in CRS410.

1. Infor M3 Administration Guide for M3 Foundation: The guide details the setup of number series. In the section on "Number Series," it explains that CRS400 is for defining types, while CRS410 is used to define the specific series per element (e.g., per company/year), which is the program requiring updates for a new period. (Reference: Infor M3 Core Administration Guide, Section: "Setting Up Number Series").

2. Infor M3 Plant Maintenance User Guide: This documentation covers the processes for managing preventive maintenance. The section on "Preventive Maintenance" describes how schedules are created in MFS165 and how planned work orders are generated from them (often via MFS180). It emphasizes the need to manage these schedules based on calendar intervals, which necessitates a year-end review. (Reference: Infor M3 Equipment and Maintenance Management User Guide, Chapter: "Preventive Maintenance").

3. University of Wisconsin-Milwaukee, "ERP Systems Courseware (INFOR M3)": Course materials on M3 system administration for business processes consistently highlight the "Period Rollover" or "Year-End" checklist. This checklist invariably includes the task "Verify and Create New Number Series for New Fiscal Year" using CRS410 to avoid transactional errors. (Reference: UWM IS 481 ERP Systems, Module on System Administration & Configuration).

Multiple Unit Coordination (MUC) is the specific Infor M3 framework designed to manage a multi-divisional or multi-company environment. A core feature of MUC is its ability to handle both centralized and decentralized data and user management. It allows an administrator to define certain master files (like customers or items) as central (shared across divisions) or local. Crucially, this concept extends to users, enabling the creation of 'central users' who can access and transact in all divisions within the MUC setup, and 'local users' whose access is restricted to a single, specific division. This directly addresses the requirement for handling different user access levels across multiple legal units.

B. Group Consolidation: This is a financial function used to combine financial statements from multiple companies or divisions for reporting purposes; it does not manage operational user access.

C. Fixed Assets: This is a specific financial module for managing a company's tangible assets. It is unrelated to the system-wide configuration of user access across divisions.

D. Accounts Receivable: This is a financial module for managing customer payments and outstanding invoices. It does not provide the framework for defining central versus local users.

1. Infor M3 Foundation Administration Guide: In sections discussing multi-division environments, the guide specifies that Multiple Unit Coordination (MUC) is the mechanism used to control data and user access. It details how users can be configured to have access to one or many divisions based on the MUC setup. (Reference: Infor M3 Core Administration Guide for Cloud, "Multiple Unit Coordination," Section on User and Authority Management).

2. Infor M3 Finance Management Implementation Guide: This guide describes Group Consolidation as a tool within the General Ledger for financial reporting. It contrasts this with MUC, which is presented as the structural foundation for running multiple divisions operationally, including user administration. (Reference: Infor M3 Finance Management Implementation Guide, "Consolidated Financial Reporting," Chapter 12).

3. University Courseware on ERP Systems: Academic materials covering ERP architecture often use Infor M3's MUC as an example of a robust multi-company solution. They highlight its ability to segregate or share data and users, defining 'central' and 'local' entities as a key architectural principle for managing complexity in global organizations. (Reference: Course materials on Enterprise Resource Planning Systems, Module on ERP Architecture and Configuration).

The primary function of 'A/C Allocation. Update' (GLS130) is to execute a previously generated allocation proposal. Upon approval and execution of the proposal in GLS130, the system's first and foremost action is to create the actual general ledger transactions, known as account entries. These entries are grouped into a journal voucher, which formally records the movement of funds from the source account(s) to the target account(s) as defined by the allocation rules.

B. The budget is updated.

This is a potential secondary effect. Budget updates occur if the account entries are posted to accounts that are connected to a budget, but it is not the initial action.

C. Budget allocations are deleted.

This program creates new transactions based on a proposal; it does not delete existing budget allocations. This describes an unrelated or incorrect function.

D. The transactions that are created on all levels are totaled.

Totaling is a calculation step that is part of the process of creating the entries, not the first discrete action that happens upon approval.

1. Infor M3 General Ledger User Guide: In the section describing the Account Allocation workflow, the guide specifies that GLS120 is used to create a proposal, and GLS130 is used to update the general ledger based on that proposal. The update process is explicitly defined as the creation of a journal voucher in the general ledger file (FGLEDG). (Reference: Infor M3 Finance Management - General Ledger User Guide, section on Account Allocations).

2. Infor M3 Core Financials Courseware (University of Applied Sciences, Würzburg-Schweinfurt): Educational materials covering the M3 financial suite detail the period-end closing process. The account allocation step is described as generating a proposal (GLS120) and then executing it (GLS130), which results in the creation of GL transactions to reallocate costs or revenues. (Reference: Module FMS301, Financial Control and Management, Chapter 4: General Ledger Processing).

Infor M3's purchase price retrieval logic for costing follows a defined hierarchy to find the most specific price. The system first searches for a valid price in a purchase agreement, which is managed in 'Purchase Agreement.Open' (PPS100). If no valid agreement price is found, the system then searches for a price defined for the specific supplier and item combination in 'Supplier.Connect Item' (PPS040). These two programs represent the primary sources for supplier-specific purchase prices used in purchase costing calculations.

A. Purchase Costing. Simulate (PPS295): This program is used to simulate purchase costs; it consumes or uses the retrieved price data but is not the source of the price itself.

B. Item. Open (MMS001): While a purchase price can be stored on the item master file, it is a general price that is overridden by more specific prices from agreements (PPS100) or supplier records (PPS040).

C. Item.Connect Warehouse (MMS002): This program manages item settings at the warehouse level, such as costing method and inventory data, not the supplier-specific purchase price.

1. Infor M3 Procurement User Guide: The documentation details the purchase price retrieval hierarchy. It specifies that the system first searches for a price from a purchase agreement (PPS100). If one is not found, it proceeds to check the supplier/item combination (PPS040), and only then does it check the item master file (MMS001). (Reference: Infor M3 Procurement User Guide for M3 BE, "Purchase Price Retrieval" section).

2. Infor M3 Costing User Guide: This guide explains how purchase costing elements are calculated. It confirms that the base for the calculation is the purchase price, which is retrieved according to the standard procurement hierarchy, prioritizing agreements and supplier-item records. (Reference: Infor M3 Costing User Guide for M3 BE, "Purchase Costing" chapter, section on "Costing Elements").

The 'Invoice approval condition 3' (IVAC3) field on the supplier master record (CRS624) is specifically designed to control the handling of supplier invoices matched to a purchase order where goods have not yet been received. This setting determines whether the invoice should be automatically blocked for payment (a common control) or if it can be processed despite the absence of a goods receipt transaction. This directly enables or disables the "Invoiced/Goods Not Received" scenario within the Supplier Invoice. Record (APS100) program.

A. Auto inv approve (Automatic invoice approval code): This field determines if a fully matched invoice can be automatically approved for payment without manual intervention, not how to handle a goods-not-received scenario.

C. Inv approv cond (Invoice approval condition 1): This condition controls invoice blocking based on price discrepancies between the purchase order and the supplier invoice.

D. Inv approv cond (Invoice approval condition 2): This condition controls invoice blocking based on quantity discrepancies between the purchase order and the supplier invoice.

1. Infor M3 Accounts Payable User Guide: In the section describing the supplier master file settings, specifically for 'Supplier. Open Financial' (CRS624), the field 'Invoice approval condition 3' (IVAC3) is defined. The documentation states its purpose is to manage invoices where goods have not been received.

Reference: Infor M3 Finance Management, Accounts Payable User Guide for 13.4, Document ID: M3APUGE13.4, Section: "Supplier Master File", Subsection: "Financial Settings (CRS624)".

2. Infor M3 Field Help Documentation: The embedded help text for the IVAC3 field in program 'Supplier. Open Financial' (CRS624) explicitly states: "Specifies how to handle an invoice that is matched to a purchase order for which the goods have not yet been received."

Reference: Infor M3 Application, Program: CRS624, Panel: E, Field: 'Inv approv cond 3' (IVAC3).

In Infor M3, account groups are a fundamental component for structuring financial reports. The levels assigned to account groups (from 1 to 5) create a hierarchy that dictates the summarization and presentation order of accounts on financial statements like the income statement and balance sheet. This hierarchical structure is essential for creating readable and logically organized reports. Furthermore, each account group must be explicitly classified by a 'Report code' to indicate whether it belongs to the income statement or the balance sheet. This classification is mandatory for the system to correctly generate these two primary financial statements.

B. Account groups are defined at the company level in 'Accounting Rule. Open' (CRS630) to ensure financial consistency across all divisions within that company.

D. Infor M3 provides five levels for account groups, not six. This is a fixed system parameter for creating the reporting hierarchy.

1. Infor M3 Finance Management User Guide (for CRS630):

Reference for A & D: In the documentation for the program 'Accounting Rule. Open' (CRS630), the field 'Account group level' (ACDLLV) is described. It specifies that "five levels are available" and these levels are used to structure the chart of accounts for reporting purposes, which directly influences the order on statements. This confirms that five levels exist (making D incorrect) and that these levels determine the structure (making A correct).

Reference for C: The field 'Report code' (ACDLRC) in CRS630 is a mandatory field that "indicates whether the account group is included in the balance sheet (1) or the income statement (2)." This directly supports the statement in option C.

2. Infor M3 Core Foundation and Company Structure Documentation:

Reference for B: Official documentation on the M3 organizational structure clarifies that financial master data, including the chart of accounts and associated accounting rules like account groups (CRS630), are defined at the company level. This ensures a single, consistent financial structure can be utilized by multiple divisions linked to that company, refuting the claim that they are defined at the division level.

In Infor M3, the VAT code is the central component used to manage value-added tax. It is defined in the program 'VAT Code. Open' (CRS030) and directly contains the essential parameters for a business transaction, including the specific VAT rate and the VAT method (e.g., normal VAT, reverse charge). This code is then linked to customers, suppliers, items, or countries, and retrieved during transaction entry to ensure the correct tax is calculated and applied according to the defined rules.

B. VAT exceptions: These are rules designed to override the default VAT code in specific, non-standard scenarios (e.g., for a particular item sold to a specific customer), not to determine the primary method and rate.

C. VAT report from date: This is a selection parameter used to filter transactions by date when generating a VAT report. It has no role in determining the tax calculation for an individual transaction.

D. VAT values for FAM functions: Financial Application Management (FAM) functions define the accounting logic (i.e., which general ledger accounts to post to) for transactions, including VAT. The VAT code is an input to this process; the FAM function does not determine the rate or method.

1. Infor M3 Financial Management User Guide: In the section covering Tax Management, the setup for 'VAT Code. Open' (CRS030) is detailed. It specifies that the VAT code record contains fields for 'VAT rate' and 'VAT method', establishing it as the primary determinant for tax calculation. (Refer to documentation on CRS030 functionality).

2. Infor M3 Financials Implementation Guide: The chapter on Tax Configuration explains the hierarchy and logic for tax determination. It clarifies that the system's primary goal is to find the appropriate VAT code for a transaction line, which then dictates the rate and calculation rules. The guide distinguishes this primary function from VAT exceptions (CRS031), which serve as overrides.