Vendor correspondence is the controlled exchange of supplier-account information between Accounts Payable and an external business partner. A balance confirmation asks the supplier to agree or challenge a stated balance; a balance notification requests a response only where the supplier disagrees; a balance request asks the supplier to report the balance in its own ledger. Each method needs a clear cutoff date, follow-up ownership and a documented treatment of discrepancies.
Why correspondence is part of reconciliation, not just a letter
Internal supplier open-item reports are necessary, but they prove what the company believes it owes—not independently what the supplier believes it is due. During a financial close or audit, an AP team may seek external confirmation to identify disputed invoices, missing credits, unallocated payments and timing differences. The purpose is to strengthen evidence around liabilities and make unexplained differences actionable.
Choose the correspondence type for the required assurance
SAP documents distinct balance-confirmation, balance-notification and balance-request methods. A positive balance confirmation requests an answer whether figures agree or not. A notification emphasizes exceptions, so silence is not an explicit agreement. A balance request asks for the counterparty's own recorded number instead of supplying one for acceptance. These are not interchangeable: the evidence strength, workload and follow-up risk differ.
Prepare a statement that the supplier can actually reconcile
Before contacting the supplier, the AP analyst should confirm the legal entity and supplier account, reporting cutoff, currency and open-item basis. Invoices, credits, advances and payments may appear differently depending on timing and selection rules. A clear reply channel and reference make it easier to distinguish a genuine accounting difference from a misunderstanding about the period being compared.
Illustration: why equal totals are not always enough
Assume AP records three unpaid invoices totaling ₹480,000, while the supplier reports ₹430,000. One ₹50,000 credit note may explain the difference—or an unallocated payment, timing cutoff or missing document may be involved. AP must check supporting transactions and the supplier's detail. A verbal assurance or a net-zero adjustment without evidence does not establish that the individual items are correct.
Who owns each step?
Accounts Payable prepares and validates the underlying records. An independent finance or audit reviewer may approve the population and monitor responses. The supplier confirms its position. When an external auditor manages confirmations, reply routing should preserve independence rather than passing through the person responsible for the recorded balance. Disputes should have owners, due dates and evidence of resolution.
What the SAP functionality supports—and what it does not decide
SAP S/4HANA documentation describes supplier balance-confirmation output, configurable selections and reply tracking in supported deployments. It also documents correspondence creation and scheduled open-item lists. Actual application availability, outputs and forms depend on edition, release and configuration. The software can prepare a controlled communication; it does not replace judgement about disputed liabilities or the appropriateness of the evidence.
Consultant thinking: design the exception process first
For implementation workshops, ask which counterparties need positive confirmation, how special G/L items are treated, whether currencies and cutoff dates are clear, who chases non-responses, and what happens when the supplier contests a figure. Design a traceable exception log and approval path before optimizing form layout. A beautiful letter without follow-up discipline is weak control evidence.
Related concepts include Accounts Payable Month-End Closing, Vendor Account Clearing, Supplier Master Data Controls, Duplicate Invoice Checks, and the SAP FI / FICO hub.