VF04 — Billing Due List
VF04 is used to select sales orders and deliveries due for billing and create billing documents individually or collectively. It is most useful when billing teams need a worklist of documents that meet billing-date, status and copy-control prerequisites. Start from the exact business object, organizational scope and status, then prove the result through document flow, logs or master data before applying a corrective action.
This ERPClimb practitioner page covers VF04 — Billing Due List. It focuses on the transaction's real operational role, the parameters that matter, the evidence needed to diagnose problems, S/4HANA context, and the mistakes that cause most support rework.
Published 19 Sept 2026· 653 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
select sales orders and deliveries due for billing and create billing documents individually or collectively. VF04 is most useful when treated as part of an end-to-end process rather than a shortcut. The object status you see here is usually influenced by upstream master data, configuration, planning or document history, so capture those inputs before changing anything.
When it is used
VF04 is typically used when billing teams need a worklist of documents that meet billing-date, status and copy-control prerequisites. It is also valuable during project testing because it exposes a repeatable state that can be compared before and after configuration or master-data changes. In production, narrow the population first and distinguish display/analysis from actions that post, approve, replicate or change status.
How to use it in practice
- Enter a narrow billing-date and organizational selection first.
- Review why expected documents are absent before creating any billing.
- Check billing blocks, goods-issue status and copy-control prerequisites.
- Create a small controlled set and inspect the processing log.
- Reconcile generated billing documents and accounting status.
Key data objects
These are the most useful anchors when working in VF04. Capture them in screenshots, test evidence and incident handovers so another consultant can reproduce the same result and identify whether the issue is data, configuration, status or integration.
- billing date — verify the exact value, validity/date context and relationship to the affected process.
- billing type — verify the exact value, validity/date context and relationship to the affected process.
- reference document — verify the exact value, validity/date context and relationship to the affected process.
- customer/sales organization — verify the exact value, validity/date context and relationship to the affected process.
- billing block and due status — verify the exact value, validity/date context and relationship to the affected process.
How to prove it in the data
Build an evidence chain rather than relying on one message: identify the source requirement or master record, show the transaction status or worklist entry, then show the resulting document, posting, warehouse object, planning element or replication log. Use the same date and organizational scope throughout. That makes the diagnosis repeatable and separates a true fix from a coincidental retry.
ECC vs S/4HANA
SAP still supports VF04 in the S/4HANA backend and also provides the Create Billing Documents app as a modern processing surface. Where a Fiori app or cloud service becomes the strategic user experience, the SAP GUI transaction can still remain valuable for support, migration and deep technical analysis, but it should not be used to justify a legacy design for new work.
Common pitfalls and how to diagnose them
- Assuming an order should appear before its billing relevance/prerequisite is satisfied. Return to the exact object status and chronology before applying a workaround.
- Running a broad collective billing job without reviewing split criteria. Return to the exact object status and chronology before applying a workaround.
- Treating a missing item as a VF04 defect when a billing block or PGI status excludes it. Return to the exact object status and chronology before applying a workaround.
Whose problem this is
Primary ownership is the SD O2C team, with adjacent functional, Basis, Security or integration teams joining when the evidence crosses system boundaries. Escalate with the object/document number, organization, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/vf04ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.