Configuring Valuation Methods, Exchange Rate Types, and the Posting Flow

Explanation

Once the business purpose of foreign currency valuation is understood, the next step is understanding how the process is technically configured and executed. The core configuration object is the valuation method, which determines how the system calculates exchange rate differences for a given valuation run. A valuation method specifies the exchange rate type to use (for example, a rate type representing the average or closing spot rate), whether valuation is based on the lowest value principle (only posting a loss if the foreign currency value has decreased, common under conservative local GAAP treatments), whether it always values regardless of direction (common under IFRS-oriented approaches), and how reversal postings are handled in the following period. Exchange rate types are maintained separately from valuation methods and represent named categories of exchange rates - for instance, a company might maintain one rate type for daily transactional postings and a separate rate type specifically for period-end valuation, allowing treasury or finance to control which rate is used for statutory closing purposes without affecting day-to-day transaction posting rates. Rates for each type are loaded for specific dates, and the valuation program looks up the rate effective on or before the valuation date depending on configuration. For open items in accounts payable and accounts receivable, the valuation program (executed through the standard periodic foreign currency valuation transaction) reads each open document line still outstanding at the valuation date, compares the exchange rate used at original posting to the valuation exchange rate, and calculates the difference. If the difference is material based on the valuation method's rules, an adjustment posting is created: a debit or credit to an exchange rate difference account (often split between realized/unrealized gain and loss accounts) offset against a balance sheet adjustment account tied to the reconciliation account of the vendor or customer. This adjustment is usually posted with a specific document type and, in many configurations, is automatically reversed at the start of the next period so that when the item is eventually cleared, the realized gain or loss calculation is not distorted by prior period valuation postings. For GL account balances (such as foreign currency bank accounts), a similar principle applies but the valuation is based on the account balance in the foreign currency rather than individual open items, since GL balance valuation typically applies to accounts managed on an open-item-managed or balance basis depending on account configuration. Account determination is a critical configuration link: for each combination of chart of accounts, valuation area (if group and local currency valuations are both required), and currency type, the system needs configured GL accounts for posting the unrealized gain, unrealized loss, and balance sheet adjustment. Missing or incorrect account determination is one of the most common causes of failed valuation runs in production, typically surfacing as an error indicating no account was found for a particular posting key or account symbol combination. Running the valuation, in practice, is usually first executed in test mode to review a list of proposed postings before committing them in update mode, giving the close team a chance to catch anomalies, missing rates, or account determination gaps before financial statements are affected.

Code example

* Conceptual configuration elements (not code, illustrative structure)Valuation Method: ZUSD_LOWVAL  Exchange Rate Type: M (period-end spot rate)  Valuation Procedure: Lowest Value Principle - always valuate  Reverse Posting: Yes - reverse in following period  Document Type: SA (or configured valuation-specific type) Account Determination (simplified):  Chart of Accounts: INT  Currency Type: 10 (Company Code Currency)  Exp. Rate Diff. Key (from reconciliation account)    -> Loss Account: 000000 (Unrealized FX Loss)    -> Gain Account: 000001 (Unrealized FX Gain)    -> Balance Sheet Adjustment Account: 000002 (per recon account) * Execution sequence (conceptual)1. Maintain/verify exchange rate type M has rate for valuation date2. Run valuation program in test mode for company code + valuation date3. Review proposed list: open items, calculated differences, target accounts4. Resolve any 'no account determined' or 'no rate found' errors5. Re-run in update mode to post adjustment documents6. Confirm reversal posting scheduled for start of next period

Real project scenario

A shared services finance team supporting multiple European company codes configured two exchange rate types: one for daily AP/AR posting and one dedicated to period-end valuation, so that treasury could control the official closing rate independently from transactional rates used throughout the month. During a quarter-end close, the valuation run in test mode surfaced several vendor reconciliation accounts with no account determination configured for the unrealized loss account, which the team resolved by updating the account determination table before proceeding to update mode, avoiding a failed or incomplete valuation posting during the actual close.

Common mistakes

• Configuring only one exchange rate type and using it for both daily transactions and period-end valuation, removing the ability to control the official closing rate separately. • Skipping the test run and posting directly in update mode, which can result in unexpected large postings due to misconfigured account determination. • Forgetting to configure the reversal posting setting, causing valuation adjustments to remain in the ledger and distort the next period's realized gain/loss calculation. • Assuming account determination is automatically inherited from the reconciliation account without explicitly verifying the exchange rate difference key mapping. • Not reviewing the test run output carefully, missing open items excluded from valuation due to account flag or currency configuration issues.

Best practices

• Maintain a dedicated exchange rate type for period-end valuation separate from daily transactional rates when tighter control over closing rates is required. • Always execute the valuation program in test mode first and review the proposed posting list before running in update mode. • Document account determination mappings clearly and review them whenever new reconciliation accounts or currencies are introduced. • Confirm reversal posting settings align with the intended accounting treatment for unrealized gains and losses. • Build a checklist step in the close calendar specifically for verifying exchange rates are loaded before the valuation run is scheduled.

Interview angle

Candidates are often asked to walk through what happens end-to-end when the valuation program runs: how it selects open items, calculates the difference, determines the posting accounts, and how the reversal works. Interviewers may also probe understanding of why a dedicated valuation exchange rate type is a common design choice versus reusing the transactional rate type.