Quick Answer — SAP Balance Not Zero Error
- Error F5 702: "Balance in transaction currency must be zero" means your FI document debits do not equal credits in the document (transaction) currency.
- Three root causes: (1) simple debit/credit amount imbalance in FB50/FB01 — fix by correcting the line item amounts; (2) document splitting fails to balance by profit centre — fix the profit centre assignment or splitting configuration; (3) foreign currency rounding — configure OBA4 tolerance and rounding difference account.
- Cause 1 is most common for manual postings. Check the Document Overview (Ctrl+F9 in FB50) — the totals bar shows debits vs credits and the unbalanced difference immediately.
- Cause 2 applies when document splitting is active and amounts appear to balance overall but fail the per-profit-centre balance check.
- This is different from "posting period not open". That error is about the posting date; this error is about document amounts.
Always check the Document Overview first. In FB50, press Ctrl+F9. The totals line shows debits and credits in the document currency. If they differ, the fix is always to adjust the line item amounts — no configuration changes needed.
Document splitting errors require configuration fixes, not amount fixes. If the document amounts balance overall but the error persists, document splitting is the cause. The fix is in the splitting configuration or profit centre derivation — not in the document amounts themselves.
This error in MIRO is a different scenario from the existing MIRO balance error page. The MIRO "balance not zero" covered elsewhere is about logistics invoice imbalance. This page covers the general FI posting context — FB50, FB01, FB60, and document splitting.
Zero-balance clearing accounts are essential when document splitting is active. Without them, any document with items across multiple profit centres will fail the splitting balance check. Configure the zero-balance account before activating document splitting in a new ledger.
Rounding difference configuration (OBA4) prevents false balance errors. Small rounding differences from currency conversion are normal. Without OBA4 configuration, these differences cause unnecessary posting failures. Set up the rounding difference account and tolerance during initial system configuration.
What "Balance in Transaction Currency Must Be Zero" Means
The error F5 702: "Balance in transaction currency must be zero" is SAP enforcing the fundamental rule of double-entry bookkeeping: every accounting document must have equal debits and credits. In SAP FI, this rule is applied at the document level in the document (transaction) currency — the currency you entered the amounts in, which may be different from the company code's local currency.
The error appears before SAP writes anything to the database. No partial posting occurs — the entire document is rejected. This is intentional: a document that does not balance would immediately produce incorrect financial statements, so SAP blocks it at source.
Transaction currency vs local currency: A Canadian company (local currency CAD) receives a USD invoice. The transaction currency is USD. SAP requires the document to balance in USD (the currency you type the amounts in). Any currency conversion to CAD happens separately. The "balance not zero" error refers specifically to the USD balance — not the CAD equivalent.
For more complex journal entries posted through batch input sessions or BAPI interfaces, the Document Overview approach does not always apply. In these cases, the balance error appears in the application log rather than on screen. Check the batch input log or the interface error log for the specific document type and amount combination that is failing. The log usually includes the line item number causing the imbalance, which points directly to the data mapping issue in the interface configuration.
Simulation before posting: In FB50 and FB01, always use the Simulate function (Document → Simulate or Ctrl+F9) before pressing the Post button for any manual journal entry. Simulation shows the full document as SAP would post it — including any automatic tax lines or document splitting lines that SAP adds. If the simulation shows a balance error, you can correct the entry before it fails on posting. Making simulation a standard step in the posting workflow eliminates virtually all manual imbalance errors.
Reading the Document Overview to Find the Imbalance
In FB50 and FB01, the Document Overview (press Ctrl+F9 or use the menu Document → Simulate) shows a full list of all entered line items with a totals row at the bottom. The totals row shows the sum of debit entries, the sum of credit entries, and the difference. The difference is exactly the amount you need to add or remove to make the document balance.
| Scenario | What Happened | Fix |
|---|---|---|
| Missing tax line | User entered the gross invoice amount as one line but did not enter the VAT/GST line item | Add the tax line manually or use the Tax tab to auto-calculate |
| Deleted counterpart | User deleted one line item but its offsetting entry was left in the document | Delete the remaining orphaned line or restore the deleted one |
| Rounding difference | Two lines were manually entered and rounded differently (e.g. 1333.33 vs 1333.34) | Correct one amount or add a rounding adjustment line |
| Wrong currency on one line | One line was entered in CAD and another in USD in a document that should be all one currency | Correct the currency field on the mismatched line |
| Forgot offsetting GL line | User entered a debit to an expense account but did not enter the corresponding credit to the bank or accrual account | Add the missing credit line to balance the document |
| Partial amount entered | User typed a partial amount on one line instead of the full amount | Correct the amount to match the intended full value |
The difference amount is your shortcut. When the Document Overview shows a difference of — for example — CAD 450.00 credit, you need exactly CAD 450.00 more on the debit side. This tells you immediately what amount is missing and which direction (debit or credit). You do not need to manually add up all lines. SAP does the arithmetic for you in the totals row.
Simple FI Document Imbalance — Most Common
This is the most common cause for manual FI postings in FB50, FB01, FB60, and FB70. The user has entered amounts but the total debits do not equal the total credits.
Common reasons for a manual imbalance: a line item was deleted without removing its counterpart; a tax line was expected but not entered; a bank posting line was accidentally omitted; amounts were rounded differently on debit and credit sides; or a foreign currency amount was typed incorrectly on one line.
A useful diagnostic approach for complex documents with many line items: in the Document Overview, sort the lines by amount (click the Amount column header). Lines that have no matching counterpart will appear as outliers — a single large debit with no corresponding large credit, or vice versa. This makes it much faster to find the missing or incorrect line in a document with 20+ entries than scrolling through each line in sequence.
Document splitting balance errors look different from simple imbalances. A simple debit/credit imbalance shows clearly in the Document Overview totals row — debits and credits are unequal. A document splitting balance error appears even when the totals row shows equal debits and credits. If the Document Overview shows balanced totals but SAP still rejects the posting with F5 702, document splitting is the cause — move on to checking profit centre assignments and zero-balance clearing account configuration rather than looking for a missing line item.
- Document Overview: debits ≠ credits
- Difference amount shows in totals row
- Occurs in FB50, FB60, FB70, FB01
- Fix: correct the line item amounts
- No configuration change needed
- Can be fixed by any FI user
- Document Overview: debits = credits (balanced)
- Error still fires on posting attempt
- Occurs when document splitting is active
- Cause: per-profit-centre balance fails
- Fix: configuration (splitting rules, zero-balance account)
- Requires SAP FICO consultant or BASIS team
Document Splitting — Balance Zero Per Profit Centre
If the document amounts balance overall (total debits equal total credits) but the error still appears, document splitting is almost certainly the cause.
When document splitting is active, SAP requires the document to balance to zero for each splitting characteristic separately — not just overall. The most common characteristic is profit centre. If your document has a cost centre posting on one line (which derives a profit centre) and a bank or vendor line on another, SAP tries to split the bank/vendor line across profit centres to match. If it cannot, the posting fails.
- Cost line: cost centre A (profit centre 1000)
- Bank line: no profit centre derivable
- SAP cannot split the bank line by profit centre
- Document does not balance per profit centre
- Result: F5 702 or splitting-specific error
- Cost line: cost centre A (profit centre 1000)
- Bank line: zero-balance account creates balancing entry
- Bank split: profit centre 1000 debit + credit zero out
- Document balances at zero for profit centre 1000
- Result: document posts successfully
Fix for document splitting balance errors: (1) Ensure every cost-relevant line item has a cost object with an assigned profit centre. (2) Configure the zero-balance clearing account in the document splitting characteristics setup (SPRO > Document Splitting > Define Zero Balance Clearing Accounts). (3) Verify the document splitting rules for the document class and item category combination include all the line item types in the failing document. In S/4HANA, use the document splitting simulation tool in the IMG to test configurations before activating in production.
Foreign Currency Rounding Differences
When clearing open items denominated in foreign currency, small rounding differences can arise from exchange rate calculations. For example, if a USD 100.00 invoice was originally posted at an exchange rate of 1.3520 (CAD 135.20) and is now being cleared at 1.3519 (CAD 135.19), there is a CAD 0.01 rounding difference. Without configuration to handle this, SAP may reject the clearing posting with a balance error.
The fix is configuration, not data entry: go to OBA4 (G/L Account Tolerances), select the company code, and configure: (1) a permitted payment difference amount (e.g. CAD 5.00), and (2) a rounding difference GL account where these small amounts are automatically posted. With this configuration, SAP posts the rounding difference automatically and the clearing succeeds.
OBA3 for customers and vendors: OBA4 covers G/L account tolerances. For customer and vendor payment differences, the equivalent configuration is OBA3. Both should be configured with appropriate rounding difference accounts and tolerance amounts as part of the initial SAP FICO system setup.
Configuring OBA4 and OBA3 to Handle Rounding Differences
Foreign currency rounding differences are not user errors — they are a normal consequence of exchange rate arithmetic. When a USD 1,250.00 invoice was originally posted at CAD 1.3250 per USD (CAD 1,656.25) and is cleared at a slightly different rate, SAP may calculate a CAD 0.01 rounding difference that technically unbalances the clearing document in one currency. Without tolerance configuration, this causes a balance error on an otherwise valid payment.
OBA4 vs OBA3 — which one applies: OBA4 covers GL account-to-GL account clearing tolerances (for example, bank clearing accounts and GR/IR clearing). OBA3 covers customer and vendor payment tolerances (for example, slight payment differences from customers who round their payments). Both should be configured as part of the initial SAP FICO system setup, but they are often missed in rapid implementations and only become apparent when the first foreign currency clearing fails.
Diagnosing and Fixing the Balance Not Zero Error
Do not attempt to force-balance a document by adding an artificial line item. Adding a dummy debit or credit line to make the amounts balance produces a document that is technically zero but financially incorrect. Every line item in an FI document must represent a real business transaction. Artificial balancing lines create reconciliation problems and audit issues. Fix the root cause instead.
SAP Balance in Transaction Currency Must Be Zero — 20 Questions Answered
This error means the FI document you are trying to post has debits that do not equal credits in the document (transaction) currency. SAP FI enforces the double-entry bookkeeping rule: every document must balance to zero. The error can appear in FB50, FB01, FB60, FB70, and during clearing transactions. It also appears in document splitting scenarios where the document must balance to zero for each splitting dimension.
The error appears in any FI posting transaction where the entered amounts do not balance: FB50 (G/L journal entry), FB01 (complex journal entry), FB60 (vendor invoice), FB70 (customer invoice), F-02 (general posting). It also appears during clearing (F-32, F-44, F-03) and in document splitting scenarios where a profit centre or segment dimension is not balanced by the split. Less commonly, it appears due to foreign currency rounding differences.
The most common message is F5 702: 'Balance in transaction currency must be zero.' You may also see F5 020 in some scenarios. In document splitting contexts, the message may reference the splitting dimension (profit centre or segment) rather than the document currency. The exact message number appears in the status bar when the posting is attempted.
In FB50, go to the Document Overview (Ctrl+F9 or the totals area at the bottom). SAP shows the total debits and total credits in the document currency. If they do not match, add, remove, or adjust line items until debits equal credits. The difference is usually a missing line item — for example, a tax line that was expected but not entered, or a bank posting line that was missed.
Document splitting is a SAP feature (New G/L and S/4HANA) that distributes accounting line items across additional dimensions — typically profit centre or segment — so that a balance sheet can be produced by segment. When document splitting is active, SAP requires that the document balance to zero not just overall but also for each splitting dimension separately. If a line item has no profit centre assigned, or if the splitting rules cannot distribute the amounts correctly, the document fails with a balance-related error.
Document splitting configuration is in the SAP IMG under Financial Accounting > General Ledger Accounting > Business Transactions > Document Splitting. Key steps: (1) activate document splitting for the ledger; (2) define document splitting characteristics (profit centre, segment, business area); (3) define splitting rules per document class and item category; (4) define zero-balance accounts for each splitting characteristic. In S/4HANA, document splitting is activated per ledger in the ledger configuration.
A zero-balance clearing account is a technical GL account used by document splitting to balance entries across splitting dimensions. When a document has line items with different profit centres, SAP cannot always directly balance the dimensions without creating additional balancing lines. The zero-balance clearing account is debited and credited in equal amounts for each dimension to make the document balance at zero for each profit centre or segment. This account should have no balance in normal reporting.
Document types in SAP have different splitting rules assigned. For example, the vendor invoice document type (KR) may have a specific splitting method that handles cost centre to profit centre derivation automatically, while a general G/L document type (SA) may not. If a document type has splitting active but the splitting rules do not cover the combination of items in the document, the balance error appears. Check the document splitting rules for the specific document class associated with the failing document type.
In FB50 the error is almost always a simple debit/credit imbalance — the amounts entered by the user do not add up to zero. In MIRO the error is more commonly related to document splitting: the system-generated document has profit centres assigned to some line items but not others, causing the document to fail the zero-balance test for the splitting dimension. The fix in FB50 is to correct the amounts; the fix in MIRO context is usually to ensure profit centre derivation is configured correctly.
Transaction currency is the currency in which a document is posted — for example USD for a US vendor invoice. Local currency (company code currency) is the currency of the company code — for example CAD for a Canadian company code. SAP stores every document amount in both currencies. The balance-not-zero error refers specifically to the transaction currency balance, meaning the document-level debits and credits in the entered currency must sum to zero, regardless of what the local currency amounts are.
Yes, though rarely. Foreign currency rounding differences can cause a document to appear balanced in the local currency but not in the transaction currency, or vice versa. This typically occurs in clearing transactions where small rounding amounts from currency conversion are not fully cleared. SAP has tolerance settings (OBA4 for G/L accounts, OBA3 for customers and vendors) that allow small rounding differences to be posted automatically to a rounding difference account rather than causing a posting failure.
A rounding difference occurs when the calculated local currency equivalent of a foreign currency amount does not result in a round number due to exchange rate precision. SAP handles most rounding differences automatically by posting the remainder to a configured rounding difference GL account. If this account is not configured, or if the tolerance is set too tight, a rounding difference can cause a balance error. Configure the rounding difference account in OBA4 (G/L tolerances) or the relevant clearing configuration.
In FB50 or FB01, use the Document Overview (Ctrl+F9) which shows total debits and credits with the difference highlighted. In the simulation view (before posting), SAP shows which dimension is unbalanced if document splitting is active. In a parked document (FBV0), the system shows the imbalance. For documents failing during a batch run, check the application log for the specific line item causing the mismatch.
A document splitting characteristic is a field (profit centre, segment, business area, or custom field) that must balance to zero in every accounting document when document splitting is active. In S/4HANA, document splitting characteristics are defined per ledger. The most common characteristic is profit centre — when active, every document must have line items that net to zero for each profit centre in the document.
The Universal Journal (ACDOCA) is the single database table in SAP S/4HANA storing all accounting postings. Document splitting in S/4HANA writes the split line items directly to ACDOCA, which is why splitting issues manifest differently than in ECC New G/L. If document splitting fails the balance check, the entire posting is rejected before writing to ACDOCA. The error must be resolved at the configuration level (splitting rules, profit centre derivation) before documents can post.
The most common splitting-related cause is a line item with no profit centre assigned when document splitting by profit centre is active. For vendor line items, the profit centre comes from the cost object assigned (cost centre, internal order, WBS element). For bank line items, the profit centre comes from the bank GL account master or a derivation rule. If any line item cannot derive a profit centre, the document cannot be split and fails the balance check.
These are completely different errors. 'Balance not zero' means the document amounts do not balance to zero — it is a mathematical validation failure. 'Posting period not open' means the date of the document falls in a period that has been closed in OB52. The first requires fixing the document amounts or splitting configuration; the second requires opening the posting period or changing the posting date.
Yes. During clearing (F-32 for customers, F-44 for vendors), if the document being cleared has a different profit centre split than the clearing document, document splitting may not be able to balance the clearing document by profit centre. This is especially common when clearing items from different periods or with different cost objects. The fix usually involves configuring the clearing posting key field status and the zero-balance clearing account correctly.
The zero-balance indicator is a setting in the document splitting characteristic configuration (SPRO > Document Splitting > Define Document Splitting Characteristics) that tells SAP to use a zero-balance clearing account to force the document to balance for that characteristic. When set, SAP automatically creates additional balancing line items using the configured zero-balance GL account whenever it cannot directly balance the splitting dimension through the document's own line items.
Yes. VoiSAP's SAP FICO training covers document posting, document splitting configuration, field status, and all common FI errors on a live SAP S/4HANA system. You post real documents, encounter and fix real errors, and understand why each error occurs — not just how to clear the message. Book a free demo to discuss your background and how the training is structured.
Book a free demo — cover FI document posting, document splitting, and how VoiSAP training prepares you for real FICO consultant roles.