VF05 — List of Billing Documents
VF05 is used to list billing documents by payer, sold-to, billing type, date, sales organization and other selection criteria. It is most useful when billing, finance or support teams need a worklist of invoices, credit memos or other billing documents. Start with the exact document, material, organizational scope and business date, then follow status and document flow before changing configuration or master data.
Verified practitioner reference for VF05 — List of Billing Documents. It covers purpose, practical use, key data, proof-in-data checks, S/4HANA context, common errors and related objects so the transaction can be used as part of an end-to-end SAP investigation.
Published 19 Sept 2026· 571 words
Esta página ainda não está disponível em português.
Purpose
list billing documents by payer, sold-to, billing type, date, sales organization and other selection criteria. VF05 should be understood in the surrounding business flow: source document or requirement, master data, determined status and follow-on document. Capturing that chain is more reliable than treating the transaction as an isolated screen.
When it is used
VF05 is typically used when billing, finance or support teams need a worklist of invoices, credit memos or other billing documents. It is also valuable in project testing because it provides a repeatable point in the process. In production, narrow the document/material scope first and capture the before-state before mass actions or configuration changes.
How to use it in practice
- Restrict billing date and organization before broad searches.
- Add accounting and cancellation status to the layout.
- Drill into VF03 for document details.
- Follow document flow to delivery/order and FI document.
- Use consistent selection criteria when reconciling billing totals.
Key data objects
These are the fields and objects that most often explain the result in VF05. Record them in test evidence and support handovers.
- billing document — verify the exact value, status, validity and relationship to the source or follow-on document.
- billing type/date — verify the exact value, status, validity and relationship to the source or follow-on document.
- payer/sold-to — verify the exact value, status, validity and relationship to the source or follow-on document.
- sales organization — verify the exact value, status, validity and relationship to the source or follow-on document.
- accounting and cancellation status — verify the exact value, status, validity and relationship to the source or follow-on document.
How to prove it in the data
Prove the scenario through chronology and document flow. Start with the source order, delivery, requirement or master record; capture the transaction status; then follow the resulting delivery, billing, production or procurement object. Reconcile quantities, dates and statuses using the same organizational scope. A correct diagnosis explains why SAP selected or rejected the object, not just what message appeared.
ECC vs S/4HANA
SAP Help lists VF05 as List of Billing Documents and it remains a common billing-analysis transaction in S/4HANA. For new S/4HANA designs, use current strategic applications and clean-core guidance even when a classic SAP GUI transaction remains available for support.
Common pitfalls and how to diagnose them
- Comparing two extracts with different billing-date scopes. Check the source and follow-on document statuses before applying a workaround.
- Counting cancelled billing documents as active revenue. Check the source and follow-on document statuses before applying a workaround.
- Assuming a billing document with no FI document is complete. Check the source and follow-on document statuses before applying a workaround.
Whose problem this is
Primary ownership is the SD/O2C team, with MM, warehouse, Finance or Basis involved when the document flow crosses those components. A strong escalation includes document/material, plant or sales area, date, status, expected result 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/vf05ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.