SAP VF04 Billing Due List Is Empty: Why Documents Do Not Appear
SAP VF04 billing due list empty no billing documents found
Also searched as
- VF04 no data selected billing due list
- delivery not showing in VF04
- SAP sales order not appearing in billing due list
- why is VF04 empty after goods issue
Short answer
VF04 only lists documents that are billing relevant, not yet fully billed, not blocked, complete, and inside the selection dates you entered. When a delivery or order is missing, the cause is almost always one of: goods issue not posted, a billing block, an incompletion, wrong billing relevance on the item category, or a billing date outside the selection range.
Applies to: SAP ECC 6.0 and S/4HANA on-premise SD billing (VF04, VF01, V.23, V.21); behaviour of the billing due list is the same in both
How to find why a document is missing from VF04
- 1Run VA03 or VL03N on the document and open Document Flow. Confirm whether it is order related or delivery related billing and, for delivery based billing, that goods issue (PGI) status is complete.
- 2In VA03 open the item and check the Billing tab. The Billing Relevance field must not be blank. If it is blank, billing relevance comes from item category configuration (VOV7) and the schedule line or delivery copy.
- 3Check blocks. Header billing block in VBAK, item billing block, and a delivery billing block on the delivery header all remove the document from the due list. Release order blocks with V.23.
- 4Check incompletion with Edit, Incompletion Log in VA02 or VL02N. An incomplete billing relevant item does not appear in VF04 until the missing field is filled.
- 5Check the billing status. If the document was already billed in full, the billing status is C and VF04 will not offer it. Look in the Document Flow for an existing invoice, and cancelled invoices (VF11) which reopen the item.
- 6In VF04 widen the selection. Set Billing Date From and To to cover the planned billing date, clear Sold-to or Ship-to filters, and select the right Billing Type (F2 for invoice, or delivery related type for the delivery).
- 7Use the Log of Incomplete Billing Documents (V.21) or the Billing Due List Log button after a run to see why selected documents did not produce an invoice.
- 8If the document is a pro forma or intercompany flow, confirm the correct billing type and organisational data in copy control (VTFL for delivery to billing, VTFA for order to billing).
How VF04 decides what to show
The billing due list is a selection program over SD documents with an open billing requirement. For order related billing it reads sales document items whose billing relevance is set. For delivery related billing it reads deliveries, and a delivery only becomes billing relevant once goods issue is posted when the item category requires it. That is why a delivery that has been picked and packed but not goods issued never shows up.
Each document carries a billing status. In ECC the status lived in the header and item status tables (VBUK and VBUP). In S/4HANA the status fields moved into the document tables themselves, so selections that read VBUK or VBUP directly in custom reports may break after migration. The user-facing logic in VF04 is unchanged.
Blocks, incompletion and credit
A billing block is a two character reason code configured in OVV3 and assigned in the order header or item, or inherited from the delivery. Blocks are common for returns, free of charge deliveries and special pricing approvals. They sit quietly in the document, and VF04 simply omits the item. Check the field in VA03 on the Billing Document tab and in VL03N on the Billing tab.
Incompletion is the other silent cause. The incompletion procedure assigned to the item category marks required fields. If a billing relevant field such as payment terms or pricing date is empty, the item status becomes incomplete and billing is blocked until it is repaired. Run V.21 or the incompletion log to see the exact field. Credit blocks do not usually stop billing, but a credit block on the delivery can stop goods issue, which then stops billing.
Selection dates, billing type and copy control
The default billing date in VF04 is today. Documents whose billing date is in the future are not selected until that date is inside the range. The billing date is proposed from the delivery date or goods issue date per copy control, and a pricing date set in the past or future can differ from it. Always widen both From and To dates when testing.
If the billing type you chose has no copy control entry for the source document type, the document is not eligible even when everything else is correct. In SPRO, Sales and Distribution, Billing, Billing Documents, Maintain Copying Control for Billing Documents, confirm an entry exists for the source type to the target billing type. A missing item category entry hides specific items only.
VF04 Maintain Billing Due List V.23 Release sales orders for billing V.21 Log of incomplete billing documents VFX3 Billing documents blocked for accounting VOV7 Item category (billing relevance) VTFL Copy control delivery to billing VTFA Copy control order to billing
Common pitfalls
- !Assuming PGI is complete because the delivery is picked. Only a posted goods issue status C makes a delivery based document billing relevant.
- !Setting the billing date range to today only and missing documents with a billing date from the past or the end of month.
- !Clearing a billing block on the order but forgetting the separate block on the delivery header.
- !Running custom reports against VBUK and VBUP after an S/4HANA conversion and getting empty results.
- !Cancelling an invoice with VF11 and then wondering why the delivery reappears. That is correct, the item is open for billing again.
How an ERP-grounded AI assistant handles this
A grounded assistant like ERPray can take a delivery or order number and walk the same checks read-only: goods issue status, billing relevance, billing blocks on header, item and delivery, incompletion log, billing status and the billing date, then return the first blocking reason along with the transaction to fix it. It shows the query it used and respects SAP authorisations, so it lists only documents the user may see. It does not release blocks or create invoices.
Frequently asked questions
Why does VF04 show nothing even though goods issue is posted?
Check the billing block on the order item and the delivery, the incompletion log, and the billing date range. A posted goods issue only satisfies one requirement. The document must also be complete, unblocked, billing relevant and not already fully billed before VF04 will list it.
What is the difference between V.23 and VF04?
V.23 releases sales orders that carry a billing block so they can be billed. VF04 is the work list that actually creates invoices for documents that are due. Typically you release with V.23 first, then run VF04 to produce the billing documents.
Why did a delivery reappear in VF04 after invoice cancellation?
Cancelling an invoice with VF11 reverses the billing status of the referenced items, which reopens them as billing due. This is expected. Create a new invoice or block the delivery if the document should not be billed again.
Can I see why a mass billing run skipped documents?
Yes. After a VF04 run use the Log button, or run V.21 for incomplete documents. The log lists each skipped document with the reason, such as pricing error, missing account determination or incomplete data, so you can correct and rerun.
Related
SAP VL150: Collective Processing of Documents Due for Delivery
VL150 (and its more commonly used successor VL10) mass-creates outbound deliveries for sales orders that are due by a selected date, based on shipping point, route, and delivery-relevant item category. Orders that do not appear are usually held back by a delivery block, an incomplete order, a failed availability check, or a delivery date outside the selection window.
How-toSAP Sales Order Incompletion Log in VA01/VA02: Fix and Configure
An SAP sales order is incomplete when a field marked as required by its incompletion procedure is empty. Open the order in VA02, choose Edit, Incompletion Log, fill the listed fields, and save. If you need to change which fields are required, you maintain incompletion groups and procedures in SD customizing, not in the order itself.
Error fixSAP Pricing Error: Condition Record Missing for PR00 in a Sales Order
The error means the pricing procedure expected a price condition such as PR00, found no valid record for the key, and the condition was flagged mandatory. Use the pricing analysis in the order item to see which access failed, then create the record with VK11, or fix the pricing procedure determination if the wrong procedure was selected.
How-toSAP SE16N vs SQVI: Table Browser vs Ad Hoc Query
SE16N is a single-table browser: fast filtering, formatted display, and export from one table at a time, with an optional edit function for authorized users. SQVI (Quick Viewer) builds ad hoc queries that join multiple tables without writing ABAP, and can be saved as a reusable report. Use SE16N for a quick look at one table; use SQVI when you need data joined across two or more tables.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPAI for SAP S/4HANA Sales and Distribution (SD) That Explains Orders, Pricing and Blocks
AI for SAP S/4HANA SD: order status, delivery and billing blocks, pricing explanations and credit holds in plain English. Read-only, on-prem option.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.