Reversal Blocked by Existing Clearing
FB08 refuses the reversal because the document has an entry in the clearing document field. SAP will not reverse a cleared line without first undoing the clearing, since reversing it directly would leave the offsetting open item unmatched. The clearing must be reset with FBRA, and any downstream reconciliation on that clearing document must be undone first, before FB08 will accept the reversal.
Covers the standard FI error that stops a reversal when the target document already carries a clearing document number. Walks through the usual causes - manual clearing, automatic clearing runs, payment runs and bank statement reconciliation - and the correct unwind order using FBRA before FB08. Distinguishes genuine data fixes from the manual journal workaround that corrupts open item history.
Published 16 Sept 2026· 1,064 words
The business symptom
Accounting reports that they tried to reverse an invoice or a payment document and the system threw an error saying the document cannot be reversed because it has already been cleared. Sometimes this comes from AP wanting to cancel a vendor invoice that was paid by mistake, or from AR wanting to cancel a customer invoice that a cash application run already matched against a receipt. The user's first instinct is that FB08 is broken, because the document clearly shows as open in their mental model - they do not connect the clearing status shown on the document display screen with the block on the reversal transaction. The complaint usually arrives phrased as 'FB08 will not let me cancel this invoice, it says something about clearing' with no further detail, and the requester expects a quick unblock rather than a multi-step unwind.
The configuration behind it
- Document was cleared manually against a payment, credit memo, or another invoice using standard clearing transactions (incoming/outgoing payment, transfer posting with clearing) - by far the most common cause.
- Document was picked up by an automatic clearing program that matches open items on defined criteria, clearing it against another item without a manual posting in between.
- Document was included in an automatic payment run; the payment run generated the clearing, so the clearing document is a payment document rather than a manual entry, and the payment itself may already be reconciled against a bank statement.
- The clearing is one of several lines cleared together in a single clearing transaction - resetting it affects every item in that clearing document, not just the one line the requester cares about, which is often not understood until FBRA is run.
- The clearing document has since been reconciled with an electronic bank statement or manual bank statement posting, which locks it against reset until that reconciliation is itself reversed.
- The clearing involves a special G/L transaction, such as a down payment cleared against the final invoice, requiring the special G/L clearing to be undone in the correct sequence before the invoice reversal is possible.
- The clearing document has been archived from the database; if archiving ran before anyone attempted the reset, FBRA has nothing to reset and reversal by normal means becomes impossible.
What to check
- FB03 - display the document, check the clearing document field and the clearing date to confirm it is actually cleared and identify the clearing document number.
- FB03 on the clearing document itself - check whether that clearing document has in turn been cleared or reconciled against something else, such as a bank statement.
- FBRA - run in test/simulation first to see whether the system allows the reset and what other line items are part of the same clearing.
- FBZP or the payment run log (F110 output) - if the clearing document is a payment, confirm whether the payment run status shows it as already reconciled with a bank statement.
- FB50/FB03 posting period check - confirm the posting period for the clearing date and for today's date are both open for the company code.
- FBL1N/FBL3N/FBL5N - pull the account line item list including cleared items to see the full clearing chain across all affected accounts.
How to prove it in the data
Pull FB03 on the disputed document and note the clearing document field and clearing date are populated. Then pull the same clearing document in FB03 and check whether it is itself cleared, reconciled, or part of a payment run. A line item report from FBL1N/FBL5N filtered to 'cleared items' for the account and date range shows the full chain: original document, clearing document, and any further clearing on top of that, which is the evidence needed to justify the unwind sequence before touching anything.
Resolution path
If the clearing is a plain manual clearing and the posting period is open, run FBRA to reset the clearing (data fix, no transport). This returns both sides to open item status and FB08 then works normally on the original document. If the clearing document is a payment run item already reconciled with a bank statement, the bank statement posting must be reversed first by whoever owns bank reconciliation, then FBRA, then FB08 - still a data sequence, no config change. If the block is a closed posting period, either open the relevant special period for the correction (a controlled config/master data change via period control settings, usually needs approval and is not a transport but a configuration table update) or post the reversal in the current open period instead. If the clearing document has been archived, FBRA cannot act on it; the only path is a manually posted correcting entry with a documented reference to the original document, since a true system reversal is no longer technically possible.
The fix people try first (and why it fails)
The reflex fix is to post a manual journal entry that debits and credits the same accounts to net the effect of the original document, leaving the cleared document and its clearing untouched. This looks like it fixes the balance but it does not remove the clearing relationship, leaves the vendor or customer open item history inconsistent with the ledger, and often triggers a mismatch during the next dunning run, payment run, or reconciliation because the system still believes the original pair of documents is correctly matched.
Whose problem this is
AP or AR accounting owns the reset-and-reverse sequence for manually cleared items. Treasury or the bank reconciliation team owns any case where the clearing document is tied to a bank statement posting. FI configuration owns posting period control when a closed period is the blocker. The handover note should state the original document number, the clearing document number, whether a bank statement or payment run is involved, and the exact order of undo steps already attempted.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-functional-issues/reversal-not-possible-because-the-document-is-already-clearedERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.