SAP Error Fix: Account Determination for Entry LNER WRX Not Possible
"Account determination for entry LNER WRX not possible" typically occurs during goods receipt (GR) or invoice receipt (IR) processes in SAP Materials Management. This error arises because the system cannot find the necessary G/L account for the specified transaction key (WRX) in the configuration. This guide covers the exact fix using FS00 and OMWB, then goes deeper into what the GR/IR clearing account actually does, how WRX relates to BSX, a real business scenario, and a full prevention checklist.
✅ Common Error Message
"Account determination for entry LNER WRX not possible" typically occurs during goods receipt (GR) or invoice receipt (IR) processes in SAP Materials Management (MM). This error arises because the system cannot find the necessary G/L account for the specified transaction key (WRX) in the configuration.
🔧 Solution 1: Check or Create the GR/IR G/L Account
Solution — Tcode: first check whether the G/L account exists — FS00.
Create G/L: GR/IR A/C — 374999.
🔧 Solution 2: OMWB — Configure the WRX Account Mapping
Solution — Tcode: OMWB
Follow path: SPRO → Materials Management → Valuation and Account Assignment → Account Determination → Account Determination Without Wizard → Configure Automatic Postings — OMWB.
Select Account Assignment.
Check the material master valuation class and related settings.
Determine which combination of chart of accounts, valuation area, and valuation class needs to be mapped for WRX in OBYC.
Example Configuration in OBYC/OMWB
- Transaction Key — WRX, Valuation Class 3000 — Raw Material
- Transaction Key — WRX, Valuation Class 3050 — Packaging
Select Chart of Account — LNER, then select WRX — GR/IR Clearing A/C.
Example: Select Valuation Class — 3000, Debit — 374999, Credit — 374999.
Example: Select Valuation Class — 3050, Debit — 374999, Credit — 374999.
Save. Post the GR/IR transaction again to verify if the issue is resolved.
🔍 What the GR/IR Clearing Account Actually Does
The GR/IR (Goods Receipt/Invoice Receipt) clearing account is a temporary holding account that bridges a timing gap built into standard purchasing: goods usually arrive before the vendor's invoice does, and the two events almost never post on exactly the same day. When a goods receipt is posted, SAP needs to record that inventory has increased in value, but it can't yet post the corresponding liability to the vendor's account, because the invoice — the actual financial claim — hasn't been received yet.
The GR/IR clearing account solves this: at goods receipt, SAP debits inventory (via BSX) and credits the GR/IR clearing account (via WRX) with the expected value. When the vendor's invoice is later posted in MIRO, SAP debits the GR/IR clearing account and credits the vendor account, effectively closing out the temporary liability and replacing it with a formal payable. If the quantities and prices match exactly, the GR/IR account nets to zero for that transaction; discrepancies (price or quantity variances) are what typically leave a residual balance that needs investigation during GR/IR account reconciliation.
📑 WRX vs BSX: Two Sides of the Same Goods Receipt
| Aspect | BSX | WRX |
|---|---|---|
| What it determines | The inventory (balance sheet) account, debited at goods receipt | The GR/IR clearing account, credited at goods receipt |
| Represents | The increase in stock value | The temporary liability for goods received but not yet invoiced |
| Cleared by | N/A — remains on the balance sheet as inventory value | The vendor invoice posting in MIRO |
| Needs general modification? | No | No — valuation class alone is generally sufficient for WRX |
Every standard goods receipt against a purchase order touches both keys simultaneously — this is precisely why a company mapping a new valuation class for the first time needs to configure both BSX and WRX (and typically GBB too, as covered in a related guide on this site) before that valuation class is ready for live purchasing transactions.
📊 GR/IR Reconciliation: Why Configuration Alone Isn't the End of the Story
Even after WRX is correctly configured, GR/IR clearing accounts require ongoing operational attention, since they're designed to be temporary but can accumulate open balances if goods receipts and invoices don't consistently match. A residual balance on a GR/IR account typically means one of three things: a goods receipt was posted but the invoice hasn't arrived yet (a normal, expected timing difference that will clear itself), a goods receipt was posted with a different quantity or price than the eventual invoice (a genuine variance needing investigation), or an invoice was posted without ever having a matching goods receipt (which may indicate a process gap).
Transaction MB5S (GR/IR account maintenance/analysis) is the standard tool for reviewing these open balances, letting AP and MM teams periodically clear or investigate items that have sat open longer than expected. Fixing the account determination error in this guide gets the posting working again, but healthy GR/IR management also depends on this ongoing reconciliation discipline, not configuration alone.
✅ Prevention Checklist for MM/FI Configuration Teams
- Whenever a new chart of accounts, valuation class, or plant goes live, map WRX (alongside BSX and GBB) for every valuation class actually in use, not just the ones tested first.
- Reuse existing GR/IR clearing accounts across related valuation classes where appropriate, rather than fragmenting reconciliation across many near-identical accounts.
- Test a full purchase-to-pay cycle (goods receipt through invoice receipt) for every valuation class during any major configuration change, not just the goods receipt side.
- Establish a regular GR/IR reconciliation review (via MB5S) as a standard AP/MM operational task, separate from account determination configuration.
- Document which G/L account serves as the GR/IR clearing account for each chart of accounts, so new configuration consistently reuses the correct one.
📱 This Error in SAP S/4HANA
Transaction key WRX, GR/IR clearing account logic, and OMWB/OBYC configuration all work identically in SAP S/4HANA as in ECC, since this is foundational Materials Management/Financial Accounting integration configuration rather than something restructured by the Universal Journal. What's improved in S/4HANA is GR/IR monitoring: the Fiori app "Manage GR/IR Clearing Account" (or similar GR/IR monitoring apps depending on your release) provides a more analytical, filterable view of open GR/IR items than the classic MB5S list, making the reconciliation discipline described above easier to maintain at scale.
💼 Real-World Scenario: A New Chart of Accounts Missing Its GR/IR Mapping
Pooja Mishra, an SAP MM consultant, was engaged after a client migrated to a new chart of accounts (LNER) as part of a broader finance restructuring project. Goods receipts for raw materials (valuation class 3000) had been tested and worked correctly under the new chart of accounts, but when the warehouse team began receiving packaging materials (valuation class 3050) for the first time under the new setup, they hit this exact error.
Investigating in OMWB, Pooja found that WRX had been correctly mapped for valuation class 3000 during the initial testing phase, but nobody had extended that mapping to valuation class 3050, since packaging materials hadn't been part of the original test scope. He added the missing WRX mapping for valuation class 3050 using the same GR/IR clearing account (374999) already in use for raw materials, and goods receipts for packaging materials began posting successfully. This illustrates a common real-world pattern with a new chart of accounts or a major configuration change: testing tends to cover the most common valuation classes first, and less frequently used ones can surface gaps only once they're actually used in production.
❗ Common Mistakes When Fixing This Error
- Fixing WRX for one valuation class without checking whether other valuation classes under the same chart of accounts will need the same mapping soon.
- Creating a brand new GR/IR clearing account rather than reusing the existing one, fragmenting GR/IR reconciliation across multiple accounts unnecessarily.
- Assuming that because BSX is correctly configured for a valuation class, WRX and GBB are automatically covered too.
- Not testing both the goods receipt and the corresponding invoice receipt (MIRO) after fixing WRX, since a WRX fix alone doesn't guarantee the invoice side will clear correctly.
- Overlooking a new chart of accounts rollout as a trigger to systematically review all transaction key mappings (BSX, WRX, GBB) across every valuation class in use.
📈 Troubleshooting Decision Tree
- Confirm the GR/IR clearing account exists in FS00 for the chart of accounts named in the error.
- If it doesn't exist, create it with finance's input on the correct account number and properties.
- Go to OMWB and select transaction key WRX, then check whether a mapping exists for the specific chart of accounts and valuation class involved.
- If missing, add the mapping, typically reusing the existing GR/IR clearing account for consistency across valuation classes.
- Retest both the goods receipt and the invoice receipt (MIRO) to confirm the full cycle works end to end.
📋 Related SAP Transactions
| Transaction | Purpose |
|---|---|
| FS00 | Create or display a G/L account, including the GR/IR clearing account. |
| OMWB | Configure automatic account determination with a guided, valuation-class-driven interface. |
| OBYC | Configure automatic account determination for all transaction keys directly. |
| MIGO | Post the goods receipt that triggers the WRX/BSX posting pair. |
| MIRO | Post the vendor invoice that clears the GR/IR liability created at goods receipt. |
| MB5S | List GR/IR account balances, useful for reconciling open GR/IR items after the fix. |
🎓 Interview-Style Questions and Answers
Q: Why does SAP need a separate GR/IR clearing account instead of posting directly between inventory and the vendor?
Because a goods receipt and its corresponding invoice rarely happen on the same day; the GR/IR clearing account temporarily holds the liability for received-but-not-yet-invoiced goods, bridging that timing gap until the invoice is posted.
Q: What does it mean if the GR/IR clearing account has a non-zero balance for a specific purchase order line?
It typically means either the goods receipt or the invoice has been posted but not the other, or there's a quantity/price mismatch between the two — both are common reasons for GR/IR reconciliation review.
Q: If BSX is correctly mapped for a valuation class but WRX is not, what happens during a goods receipt against a purchase order?
The goods receipt will fail with an account determination error specific to WRX, since the inventory debit (BSX) and GR/IR credit (WRX) are both required for the posting to balance, and both must be independently configured.
📚 Quick Glossary of Terms Used in This Guide
- WRX: The transaction/event key for GR/IR clearing, determining the account used to bridge goods receipt and invoice receipt timing.
- GR/IR clearing account: A temporary holding account for the value of goods received but not yet invoiced.
- MIRO: The transaction used to post a vendor invoice, which clears the GR/IR liability created at goods receipt.
- MIGO: The transaction used to post a goods receipt, which creates the GR/IR liability via WRX.
- OMWB: A guided SAP transaction for configuring automatic account determination, valuation-class-driven.
🎯 Conclusion
"Account determination for entry LNER WRX not possible" is SAP correctly refusing to post a goods receipt without a configured place to temporarily hold the value of goods received but not yet invoiced. By confirming the GR/IR clearing account exists and mapping it correctly per valuation class in OMWB, you can resolve this error and understand exactly why the GR/IR mechanism exists in the first place — not just clear the message and move on. Keep the WRX-vs-BSX comparison above bookmarked for the next time a new valuation class needs full account determination coverage.