After configuring or modifying a workflow, it must be explicitly activated. An inactive or draft version will not trigger. While other options could cause issues, the most common oversight for inconsistent triggering after configuration is failing to activate the new version.

The correct foundational sequence is: 1) Create Sales tax codes for each tax rate (e.g., State 6%, County 2%). 2) Create Sales tax groups that combine relevant tax codes and assign them to customers/vendors. 3) Create Item sales tax groups that combine relevant tax codes and assign them to products/services. This links the transaction (via customer and item groups) to the correct tax codes.

The Fixed assets posting profile determines which main accounts (e.g., depreciation expense, accumulated depreciation) are used when transactions like depreciation are posted. If this is misconfigured, the subledger will post to one set of accounts, but the system’s expectation for the GL will be different, causing a mismatch. This is the primary control point for FA-to-GL account mapping.

All three statements are key advantages. The Allocation function (1) preserves a link to the original transaction, (2) automates calculations to ensure the total debits/credits balance perfectly, and (3) can use allocation rules/methods (like percentages, fixed weights, or dynamic bases) that can be reused, making the process more efficient and consistent than manual line entry.

The ‘Import payments from a file’ tool in Accounts receivable is specifically designed for this purpose. It allows you to set up a processing pipeline that defines the file format (like ISO20022), imports the data, and then uses matching rules to automatically propose and apply the payments to open customer transactions, significantly reducing manual effort.

The ‘Transfer’ transaction type is used to move budget amounts between financial dimensions (like departments, cost centers, projects) or budget codes within the same budget model and fiscal year. ‘Original budget’ sets the initial budget, ‘Revision’ amends it, and ‘Carry-forward’ moves leftover budget to a new year.

For automatic intercompany sales/purchase order creation, the primary setups are: 1) Intercompany master planning groups (which define the supplier/customer relationship between the legal entities), and 2) Intercompany trade agreements (which define the price and discount terms for items sold between these entities). These together enable the system to automatically generate the corresponding document.

Financial dimension validation rules are the core configuration tool for enforcing dimension entry requirements. You can create a rule on the account structure that specifies: for a specific main account (or range, like all expense accounts), the Cost Center dimension must not be blank. This is a preventative, system-level control applied at data entry.

After defining the fiscal calendar, you must physically generate the accounting periods for the new year within the Ledger calendar module. This creates the period records (e.g., 2025-001, 2025-002) that the system references. Without these generated periods, no transactions or batch jobs can be posted to the new year, regardless of the calendar setup.

After configuring or modifying a workflow, it must be explicitly activated. An inactive or draft version will not trigger. While other options could cause issues, the most common oversight for inconsistent triggering after configuration is failing to activate the new version.0