VF11 — Cancel a Billing Document

VF11 reverses a billing document by creating a second billing document of a cancellation type, with quantities and values mirrored to net the original to zero. It does not delete VBRK/VBRP records or undo the accounting posting directly; it books an offsetting accounting document against the same G/L accounts, customer, and cost objects. The structural fact that causes most confusion: once a billing document has accounting relevance, its financial fields are locked, so any correction has to go through this reversal path rather than a change transaction. The original and its cancellation both persist, connected in the document flow, so the audit trail always shows both the wrong invoice and its reversal, never a silent edit.

Reached for whenever a released billing document turns out to be wrong after posting to FI: wrong customer, wrong pricing condition applied, wrong quantity billed, duplicate invoice run, or a billing document created against the wrong sales order or contract. Used before the invoice is paid or heavily referenced downstream, since cancellation gets progressively harder once dunning, correspondence, or intercompany settlement has picked up the document. Not used for correcting a document that has not yet been released to accounting, where VF02 or simply deleting the billing due list entry is enough. On S/4HANA the equivalent action is also available from a Fiori billing document app, but VF11 remains the direct route for anyone working from a list of document numbers.

In SE16 on VBRK, filter the original billing document number and check FKSTO; a populated cancellation flag confirms it was reversed and SFAKN carries the cancellation document number. Look up that cancellation number in VBRK again to see its own FKSTO and creation date. Cross-check VBFA with the original document as the preceding document; a successor entry with a cancellation document category confirms the link. Pull BKPF/BSEG for both accounting document numbers referenced from VBRK to confirm the postings actually net to zero on the customer and revenue accounts.

VF11 functions the same way on ECC and S/4HANA; the underlying tables and the cancellation-by-reversal logic are unchanged. S/4HANA adds a Fiori app for managing and cancelling billing documents from a worklist, useful when cancelling in bulk or working from a status-filtered list rather than known document numbers, but it drives the same copy control and accounting logic underneath.

Functional SD owns the decision to cancel and the choice of cancellation billing type. FI has to confirm the accounting period is open and the customer line is not cleared before the cancellation is attempted. A clean handover includes the original billing document number, the reason for cancellation, confirmation of clearing status, and confirmation that no downstream document (dunning, intercompany, revenue recognition) references it yet.

VF03 is the natural first stop to confirm the status and accounting relevance of the document before attempting a cancellation. VOV8 configuration explains why a particular billing type behaves the way it does during copy control. VKOA is relevant when the reversal posts to an unexpected G/L account, since account determination runs again for the cancellation document exactly as it did for the original. VA13 or VA23 help trace back to the sales order or contract that originated the billing, useful when the cancellation is prompted by an upstream order error rather than a billing mistake itself.