What Is a Document Flow in SAP and Why Does It Matter?
Every posting in SAP creates a document, and documents belonging to the same transaction are automatically linked. Understanding this principle helps you answer questions like "Why can't I reverse this document?" or "Where is the payment?" independently. This article explains the document flow concept, walks through two practical examples, and clarifies what changed in S/4HANA.
Anyone working in SAP with incoming invoices, payments, or credit memos is always moving through a document flow, even if that term rarely comes up in day-to-day work. Understanding what lies behind it helps you use SAP more purposefully, categorise errors more quickly, and explain connections that might otherwise seem puzzling.
In brief: A document flow describes the link between all SAP documents that belong to the same business transaction, for example an invoice, a payment, and the clearing entry. It allows a transaction to be traced completely from start to finish.
What is a document in SAP?
In SAP, every posting is saved as a document. A document is the digital record of a transaction. It contains information such as the posting date, company code, accounts involved, amounts, and tax codes. Each document receives a unique document number. The original posting is retained for audit purposes. Changes are documented, and significant corrections are typically made using a reversal document.
Documents are not only created by manual postings. Automatic processes such as payment runs, dunning, depreciation, and foreign currency revaluations also generate documents. The system thereby maintains a complete record of what was posted, when, and why.
What is a document flow?
A document flow arises when multiple documents are linked to one another because they represent the same business transaction. The classic example is an incoming invoice:
- An incoming invoice is entered. The invoice document is created.
- The invoice is paid. The payment document is created.
- The payment document clears the open item. Both documents are now linked to one another.
SAP links these documents automatically through document relationships and clearing information. These links are created at the time of posting and do not normally need to be maintained manually. Together they form the document flow for this business transaction.
A note on terminology:
"Document flow" is widely used in SAP training and day-to-day work. Depending on the process, SAP also uses terms such as clearing chain, follow-on documents, or document relationships. You will not find a system object called "document flow" as such in FI — but the concept is visible wherever linked documents and open item clearing are involved.
Two examples from day-to-day work
The principle applies equally to vendors and customers. Here are two typical sequences:
Vendor (Accounts Payable)
Invoice entry via transaction FB60 (GUI) or the Fiori app "Create Supplier Invoice" (F0859). Invoice document is created. Open item: €5,000 on the vendor account.
Payment via the Fiori app "Manage Automatic Payments" (F0770). Payment document is created and clears the open item.
Document flow closed. Both documents are linked, the open item is cleared, balance is zero.
Customer (Accounts Receivable)
Outgoing invoice issued to the customer. Customer document is created. Open item: €3,500 on the customer account.
Customer payment received and posted in SAP. Payment document is created.
Document flow closed. The payment clears the open item and the documents are linked.
Why does this matter in day-to-day work?
The document flow concept explains a number of situations that users encounter regularly:
| Situation | Explanation through the document flow |
|---|---|
| "I cannot reverse this document." | The document has already been cleared. A follow-on document such as a payment exists. The document flow must first be unwound. |
| "Why is the invoice still showing as open?" | No payment document exists. The document flow is not yet closed and the open item remains. |
| "The credit memo and the invoice cancel each other out. Why is there still an open item?" | The credit memo and invoice have not yet been offset against each other. They are not yet linked. |
| "Where can I find out who paid this invoice?" | In the document flow. The payment document is linked to the invoice document and contains all relevant information. |
The document environment and follow-on documents in the document display (FB03) allow you to trace which documents are connected to one another.
Document flow in S/4HANA: what has changed
The principle of the document flow is the same in S/4HANA as in ECC. The linking of documents to a business transaction is a fundamental principle of SAP accounting and continues to work through the established document relationships and clearing information.
What S/4HANA improves is the transparency of financial data and reporting: the Universal Journal (ACDOCA) brings financial accounting and controlling together in a shared data structure, making cross-area analyses and reports easier to produce.
Fiori tip:
In SAP Fiori, the app "Create Supplier Invoice" (F0859) is available for invoice entry, and "Manage Automatic Payments" (F0770) handles the payment run. Both apps offer a more direct view of linked documents than the classic GUI transactions.
What stays with you
The document flow is not an abstract concept. It is the explanation for why SAP works the way it does. Every posting creates a document, every document belongs to a transaction, and SAP links these transactions automatically. Once you understand this, you can answer questions like "Why can't I reverse this?" or "Where is the payment?" on your own, without having to ask your key user every time.
Understanding SAP in the context of your own work
If you want to understand these connections not just in theory, but directly in your own processes and with your own postings, get in touch. I offer training for end users and key users that starts exactly where the questions arise in day-to-day work.
Find out more about SAP FI training