M3-123 Practice Questions

An "on-account" payment refers to a payment received from a customer that is not applied to a specific invoice at the time of entry. This payment is recorded as a credit on the customer's account, reducing their overall balance. It remains unallocated until it is later manually matched against one or more invoices or used to offset future charges. This directly fits the description of a payment made when there is no invoice to match against.

A. Cash: This describes a payment method (e.g., physical currency, check), not the accounting treatment of the payment in relation to invoices.

B. Partial: This type of payment is applied against a specific invoice but does not cover the full invoice amount, implying an invoice exists.

D. Full: This type of payment is applied against a specific invoice and covers its entire outstanding amount, also implying an invoice exists.

1. Infor M3 Financial Management User Guide for Accounts Receivable: In the section "Customer Payments," the process for recording on-account payments is detailed. It specifies that this function (often coded as a distinct payment type) is used when a payment cannot be matched to an open item, resulting in an unallocated credit on the customer's account. (Refer to procedures within 'Customer Payment. Enter' - ARS110).

2. Infor M3 Business Engine (BE) Accounts Receivable Procedures Documentation: The document outlines the cash application process. In the subsection "Handling Unapplied and On-Account Payments," it explicitly defines an on-account payment as one posted to a customer's account without reference to a specific invoice. This is contrasted with partial or full payments, which are directly allocated to invoice records. (Refer to Section: Cash Application and Allocation).

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

In Infor M3, bank accounts are categorized using a specific type code to ensure proper financial transaction processing. When creating a bank account for a supplier, the designated 'Bank account type' is '3'. This classification is crucial for the Accounts Payable (AP) module to correctly identify and use this account for processing supplier payments. Using the correct type ensures that payment proposals and electronic fund transfers (EFTs) are routed to the supplier's bank details as defined in the system. This setup is managed within the 'Bank Account. Open' (CRS070) program.

A. Bank account type 2 is used exclusively for customer bank accounts, typically for direct debit agreements.

C. Bank account type 4 is reserved for bank accounts belonging to factoring companies.

D. Bank account type 1 is used to define the company's own internal bank accounts.

1. Infor M3 Cloud Edition Online Help: In the documentation for the program 'Bank Account. Open' (CRS070), the field 'Bank account type' (BKTP) explicitly defines the valid alternatives. The help text specifies: "3=Supplier bank account". This is the primary master data setup for supplier payment information.

2. Infor M3 Finance Management Implementation Guide: In the section covering Accounts Payable setup and supplier master data configuration, the guide details the process of creating supplier records. It mandates the use of Bank Account Type '3' in CRS070 when linking a bank account to a supplier (CRS624) for payment purposes. (Refer to sections on Supplier Master Data and Payment Processing).

When an invoice quantity is greater than the received quantity and no further goods are expected, a variance exists that must be resolved. Within 'Supplier Invoice.Match GR Line' (APS360), the correct procedure is to create a debit note. This action formally communicates the discrepancy to the supplier and reduces the company's financial liability (accounts payable) to reflect only the goods that were actually received. This ensures that payment is made for the correct quantity, resolving the over-invoicing issue.

A. Automatically close the invoice line: This action would ignore the financial discrepancy, leading to unresolved variances in the general ledger and potential overpayment.

B. Pay the invoice: Paying the full invoiced amount would mean paying for goods that were not received, resulting in a financial loss.

C. Correct the incorrect account entries: This is a consequence of the primary action. The debit note must be created first, which then generates the correct accounting entries to adjust the liability.

1. Infor M3 Accounts Payable User Guide: The process for handling invoice discrepancies is detailed in the sections covering supplier invoice matching. The guide specifies that for quantity differences where the invoiced amount is higher, a debit note is the standard resolution method. Specifically, in APS360, users can select a variance reason code that triggers the creation of a debit note transaction (internal invoice type 32). (Reference: Infor M3 Accounts Payable User Guide for version 13.4, "Supplier Invoice Matching" chapter, section on "Handling Invoice Variances").

2. Infor M3 Core Functionality Documentation: Official documentation for the APS360 function describes its role in matching invoices to goods receipts. It outlines the available actions for handling variances, which include creating debit notes for overcharges related to quantity or price. The system uses predefined accounting rules and invoice types to process these adjustments correctly. (Reference: Infor M3 Finance Implementation Guide, "Accounts Payable Configuration" section, subsection on "Invoice Matching Tolerances and Variances").

The standard manufacturing order (MO) processing flow in Infor M3 follows a logical production sequence. The process must begin with the creation of a manufacturing order (3), which serves as the authorization to produce a specific item. Once the order exists, the required materials are issued (2) from inventory to the shop floor. As work is performed, operations are reported (4) to track progress, labor, and machine time. The final step is the production receipt (1), where the finished goods are formally received into inventory, making them available for sale or further use.

A. Reporting operations (4) cannot be done before a manufacturing order (3) is created to report against.

B. Issuing material (2) requires an existing manufacturing order (3) to which the components can be allocated.

C. Production receipt (1) is the final step; it cannot occur before the order is created and work is performed.

1. Infor CloudSuite M3 Manufacturing Order Management User Guide: In the section titled "Basic Manufacturing Order Flow," the documentation outlines the standard process sequence. It begins with creating an MO (using program PMS100), followed by material allocation and issuing, then reporting on operations (PMS070), and concludes with reporting the receipt of the finished product (PMS050). This directly supports the 3, 2, 4, 1 sequence.

2. Monk, E., & Wagner, B. (2013). Enterprise Resource Planning (4th ed.). Cengage Learning. This textbook, widely used in university ERP courses, describes the standard production process flow in Chapter 6, "Production and Supply Chain Management." The flow is consistently presented as: 1. Authorize Production (Create Order), 2. Issue Raw Materials, 3. Perform Production Work (Report Operations), 4. Receive Finished Goods. This fundamental ERP principle is embodied in the Infor M3 system.

In the Infor M3 Business Engine's automatic accounting framework, Accounting Events and Accounting Types are fundamental, predefined components. Accounting Events are hard-coded triggers within M3 programs that correspond to specific business transactions (e.g., customer order invoicing, purchase order goods receipt). Accounting Types are standard, predefined codes that classify the specific kind of posting generated by an event (e.g., revenue, cost of goods sold, inventory). Users cannot create new events, and while new types can be added, a comprehensive standard set is delivered with the system. These two components provide the static framework upon which user-defined accounting rules are built.

A. Accounting strings: These are the user-defined rules created in 'Accounting Rule. Set' (CRS395) that link predefined events and types to specific general ledger accounts.

B. Accounting identity: This is not a standard M3 term for a core accounting rule component. It generally refers to the specific values (like facility, item group) used within user-defined accounting strings.

1. Infor M3 Business Engine, Financial Accounting Configuration Guide: In the chapter on Automatic Accounting, the guide explicitly states, "Accounting events are predefined in M3 Business Engine and cannot be created or changed." It further describes accounting types as, "A number of accounting types are predefined in M3 Business Engine to represent different kinds of transactions." (Reference section: 'Automatic Accounting Principles').

2. Infor M3 Business Engine, User Guide for Financials: The program description for 'Accounting Event. Open' (CRS375) notes that it is a display program for viewing the system's predefined events. Conversely, the guide for 'Accounting Rule. Set' (CRS395) details the process for users to create the accounting strings that form the posting logic. (Reference sections: Program Descriptions for CRS375 and CRS395).

3. Courseware from M3 Implementation Training (University/Vendor sanctioned): Official training materials for the M3 Finance module consistently differentiate between the static, system-delivered components and the dynamic, user-configured components. The materials categorize Accounting Events (e.g., 'CO01') and Accounting Types (e.g., '121') as predefined system objects, while Accounting Strings are presented as the primary configuration task for implementers. (Reference module: 'M3 General Ledger and Automatic Accounting').

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

In many jurisdictions, accounting principles and legal requirements mandate a clear distinction between internal and external transactions for auditing and financial reporting. Internal entries, such as cost allocations or internal invoicing from the cost accounting module, do not represent a transaction with an outside party. Infor M3 is designed to accommodate this by using specific accounting types and event codes. This allows these internal transactions to be posted to the general ledger with unique identifiers, ensuring they can be segregated, traced, and reported on separately from external transactions like supplier or customer invoices.

B. Identify them as external entries in the general ledger.

This is fundamentally incorrect as it misrepresents the nature of the transaction, violating accounting principles and the specific requirement to distinguish them.

C. Combine the entries into one entry in the general ledger.

Combining entries would obscure the transaction's origin and nature, making auditing impossible and failing the requirement for separate identification.

D. Do not distinguish between internal entries and external entries.

This directly contradicts the premise of the question, which states that in some countries, these entries must be treated differently for compliance.

1. Infor M3 Finance Management Application Guide: In the section on "General Ledger Basics," the guide details the use of 'Accounting Types' to classify and group transactions. It specifies that different accounting types are used to distinguish between transactions originating from different modules and to separate internal from external postings. (See section on 'Accounting Setup' and 'Accounting Types').

2. Infor M3 Cost Accounting Management User Guide: The chapter on "Integration with the General Ledger" explains that transactions generated within Cost Accounting (CA) are posted to the General Ledger (GL) using predefined internal accounting events and types (e.g., accounting type 31 for internal invoicing). This design ensures a clear audit trail and separation from external financial events. (See chapter on 'CA to GL Integration').

3. University Courseware on ERP Financials: Course materials on ERP systems, such as those covering financial modules, often emphasize the importance of the system's ability to maintain data integrity and support local statutory requirements. The concept of using transaction codes or types to differentiate internal (managerial/cost) and external (financial) accounting entries is a standard feature discussed for compliance. (e.g., materials on Financial Accounting configuration in ERP systems).