Configuring Order Types, Planning, Budgeting, and Settlement Rules

Explanation

Once the business purpose of Internal Orders is clear, the next step is understanding the configuration layer that governs their behavior in a live system. This starts with the Order Type, configured in the CO area of customizing, which is the master switch controlling nearly everything about an order's lifecycle. Each order type references a Number Range (internal or external numbering), a default Status Profile (if user-status tracking beyond the standard system status is needed), a Settlement Profile, a Planning Profile (optional), and a Budget Profile (if the order type is meant to be budgeted). Order types also control the field status of the order master record, meaning which fields are required, optional, or hidden when a controller creates a new order. Settlement Profiles are one of the most important configuration objects tied to Internal Orders. A settlement profile defines the allowed settlement receiver categories: cost center, G/L account, fixed asset (via Asset Under Construction), WBS element, another order, profitability segment (CO-PA), or a sales order. It also determines whether settlement is mandatory (order cannot be closed until fully settled), the default allocation structure (which groups source cost elements into settlement cost elements), and the PA transfer structure if profitability postings are needed. Configuring this incorrectly, for example forgetting to allow settlement to Assets for an investment order type, will block period-end close because the system will reject a settlement rule assignment to an invalid receiver type. Planning on Internal Orders is typically simpler than on cost centers: primary cost element planning by order lets controllers set an expected budget for materials, labor, and overhead, which can then be compared against actual postings for variance analysis. For capital-type or high-value orders, Budgeting (a formally approved control tool, separate from soft planning) is often activated, tied to a Budget Profile that defines tolerance limits, availability control activation, and whether overruns should trigger a warning, an error (blocking further postings), or simply a log entry for review. Availability control checks are typically run in the background whenever a new commitment or actual posting is made against a budgeted order, comparing consumption against the assigned budget plus tolerance. Settlement itself is a period-end (or ad hoc) process that transfers the accumulated costs from the order to its designated receiver(s), based on the settlement rule maintained on the order master record. A settlement rule can distribute costs to a single receiver at 100 percent, or split them by percentage or fixed amount across multiple receivers. Running settlement is what actually clears the order's real cost balance and posts to the receiver's controlling object, and in parallel generates the corresponding FI/CO reconciliation postings. Under S/4HANA, this settlement run still exists exactly as before conceptually, but the resulting postings appear as fully reconciled Universal Journal line items, improving traceability to the source document. A controller must also understand order groups, which are hierarchical groupings of individual orders used for reporting and mass processing (for example, running settlement or budget checks across a whole group at once rather than order by order).

Code example

Example settlement rule maintained on an Internal Order master record (illustrative, not a literal transaction screen): Order: 500001 (Trade Fair - Berlin 2025)Settlement Rule:  Receiver Category: Cost Center  Receiver: CC-1000-MKT  Settlement %: 70  Settlement Type: PER (periodic)   Receiver Category: G/L Account  Receiver: 619000 (Statistical Marketing Analysis)  Settlement %: 30  Settlement Type: PER (periodic) During month-end settlement (executed via the standard CO settlement processing step for the order or order group), the system takes the order's real cost balance for the period and distributes it 70/30 to the cost center and the statistical G/L account respectively, then marks the settled amount against the order so it is not settled twice.

Real project scenario

An engineering firm uses Investment Orders to track costs for internal tooling upgrades before capitalizing them as fixed assets. The controlling team configures a dedicated order type with a budget profile enforcing hard availability control (errors block postings beyond budget plus 10 percent tolerance), and a settlement profile allowing settlement only to Assets Under Construction. During a project, a purchase order overrun trips the availability control, blocking further goods receipt postings until the project manager requests a budget supplement, which the controller approves and updates via a budget update transaction, unblocking the workflow.

Common mistakes

• Configuring a settlement profile that does not include the actual receiver type the business needs (e.g., missing Asset as an allowed receiver for investment orders), causing settlement failures at close. • Setting availability control tolerances too tight, generating so many warning messages that users start ignoring them entirely. • Forgetting to assign a settlement rule to individual orders, resulting in costs stuck on the order past period end with no automatic distribution. • Mixing planning values and budget values conceptually, when they serve different purposes: planning is informational, budgeting can be a hard control. • Not testing order group-based mass settlement in a sandbox before running it in production, risking unexpected postings across many orders at once.

Best practices

• Align settlement profile receiver categories precisely with the actual downstream cost objects the business uses (cost centers, assets, CO-PA). • Use budget profiles with graduated tolerance levels (warning then error) rather than a single hard cutoff, to give project owners visibility before a block occurs. • Maintain settlement rules as early as order creation, not as an afterthought at period end, to avoid last-minute closing delays. • Use order groups for recurring mass settlement and budgeting to reduce manual repetitive processing. • Regularly reconcile unsettled order balances as part of month-end close checklists to catch configuration or process gaps early.

Interview angle

Expect questions on the difference between planning and budgeting on Internal Orders, what a settlement profile controls, and how availability control tolerances affect real postings. A strong answer connects configuration choices (order type, settlement profile, budget profile) directly to a business control objective, such as preventing unapproved capital overspend.