Why a Vendor Payment is Not a Double Expense and How to Trace It in SAP S/4HANA
In SAP S/4HANA, a payment to a vendor settles an existing liability from a posted invoice; it is not a new expense. Tracing the payment back to the original invoice is done using clearing documents, assignment fields, and line item displays.
On this page
The short answer
For an ordinary payment of a previously posted supplier invoice, the payment settles a liability; it does not post the original purchase again. The invoice may debit an expense, inventory, an asset or a clearing account depending on the process. Trace the vendor items through their clearing document, company code and fiscal year. Partial payments, discounts, exchange differences and bank clearing require separate interpretation.
The Accounting Mental Model: Expense vs. Settlement
In the simplified consulting example, the invoice debits an expense and credits the vendor; the full payment debits the vendor and credits the bank or bank clearing account. This is not the universal entry for every purchase. Goods receipts, capital purchases, taxes and accruals can change when and where costs are recognized. The example excludes those cases, payment differences and fees.
A Worked Example: Invoice to Payment
Consider a user who receives an invoice for consulting services for 1,000 EUR. They post it via transaction FB60 or a relevant Fiori app, referencing a cost center. The system creates a financial document (e.g., document number 5100000011) with this entry:
Debit: Consulting Expense (G/L account) 1,000 EUR
Credit: Vendor Liability (vendor sub-ledger) 1,000 EUR.
This invoice is now an 'open item' in the vendor's account. A week later, the user executes the payment run or posts a manual outgoing payment via the 'Post Outgoing Payments' Fiori app. The payment run selects this open invoice, creates a payment document (e.g., document number 5200000055), and clears the item. The accounting entry for the payment is:
Debit: Vendor Liability 1,000 EUR
Credit: Bank Account 1,000 EUR.
The expense account balance from the original invoice remains 1,000 EUR. The vendor account balance is now zero for these items.
// Illustrative accounting entries, not executable code
// Document 5100000011 (Invoice Posting):
// Debit G/L 600000 (Consulting Expense) 1,000 EUR
// Credit Vendor 471100 (Liability) 1,000 EUR
//
// Document 5200000055 (Payment):
// Debit Vendor 471100 (Liability) 1,000 EUR
// Credit G/L 113100 (Bank Account) 1,000 EURExpected Result: A Cleared Open Item
After full clearing, the invoice retains its original amount in the line item display. Clearing does not turn that amount into zero: the selected debit and credit items balance to zero together. Inspect cleared status, clearing document, clearing date and the related items. One clearing event can settle several invoices, so a payment document number is not necessarily a one-to-one invoice reference.
Diagnosis: How to Trace Payment to Invoice
Use the clearing information and the company code and fiscal year to display the related items. Assignment and reference can help search, but their contents depend on master data, posting and process configuration. Do not assume that invoice and payment always share a purchase-order value; assignment alone is not proof that a particular payment settled an invoice.
Common Mistakes and Misinterpretations
A partial payment normally leaves the original invoice open and creates a separate open payment item. A residual-item payment clears the original invoice and creates a new open item for the remainder. Cash discounts, exchange differences or tolerances may add other postings. Do not treat these cases as identical to a full payment of the exact invoice amount.
Decision Criteria: Is This a Clearing Transaction?
Compare the complete accounting entry and cleared/open status rather than classifying by one account. An ordinary settlement need not repeat the original expense, but a valid payment can include profit-and-loss postings for differences or discounts. Use the clearing document to identify the actual items and distinguish full, partial and residual-item processing.
Scope and System Limits
The example covers a standard full payment without taxes, discounts, exchange differences or fees. Special G/L transactions and other settlement processes can require additional steps. Availability of GUI transactions, Fiori apps and displayed fields depends on the S/4HANA edition, configuration and authorizations; use the tools available in your system.
Prerequisites and Environment
To perform the actions described, you need access to an SAP S/4HANA system (any recent version where the FI-AP module is active) with the necessary authorizations for accounts payable transactions (e.g., for FB60, F-53, FBL1N) and display. A foundational understanding of double-entry accounting is required to interpret the entries. Knowledge of vendor master data and the business partner concept is essential, as 'the master data of vendors is administered by the business partner in SAP S/4HANA.' The examples and navigation may vary slightly between the classic SAP GUI and the SAP Fiori interface, but the underlying accounting and clearing logic remains consistent.
Things to check
- Identify invoice and payment items with company code and fiscal year.
- Inspect cleared status, clearing document and date; do not expect the original invoice amount to become zero.
- Distinguish full, partial and residual-item payment.
- Inspect discounts, differences and bank clearing separately.
Where this applies
This guide covers standard invoice and payment clearing. It does not cover down payments, bills of exchange, withholding tax items, or netting, which have distinct clearing rules and document flows.