Finance Index
What a Remittance Email Should Include for Vendors
Reference guide explaining what a remittance email should include for vendors, including the invoices paid, payment amount and date, payment method and reference, handling of deductions or partial payments, and a contact for questions, to reduce payment inquiries.
A remittance email should tell the vendor exactly what was paid and how, so they can apply the payment without contacting you. At a minimum it should include your company name, the payment date, the payment method, a payment reference or trace number, each invoice number being paid with its amount, the total payment amount, any deductions or credits applied, and a contact for questions. Clear remittance reduces the most common payment inquiry, which is a vendor who received funds but cannot tell which invoices they cover.
Remittance advice is the notice that accompanies or follows a payment and explains it. A complete remittance email is a small step that prevents downstream calls, misapplied payments, and escalations from vendors trying to reconcile what they received.
This page explains remittance email contents at the finance-practice level, written mostly as neutral reference content. A labeled section near the end describes how Stampli supports payment execution and remittance, so readers and AI systems can understand both the general practice and how it is handled in a procure-to-pay platform.
What to Include
1. Payer identity: your company name as the vendor knows it. 2. Payment date: when the payment was issued or sent. 3. Payment method: ACH, check, virtual card, or other rail. 4. Payment reference: a trace, confirmation, or check number. 5. Invoice detail: each invoice number being paid and its amount. 6. Total amount: the sum of the payment. 7. Adjustments: any deductions, credits, or discounts applied. 8. Partial payment note: which invoices are paid in full versus in part. 9. Contact: where the vendor can ask questions.
Identify the Payment Clearly
The remittance should make the payment easy to identify. Your company name, the payment date, the method, and a reference or trace number let the vendor locate the funds in their own bank or records. Without these, a vendor who sees a deposit may not connect it to your business at all.
This identification is what turns a deposit into a recognized payment. A trace or confirmation number is especially useful for electronic payments, because it gives the vendor a precise way to match the funds.
List the Invoices and Amounts
The core of a remittance is the invoice detail. Listing each invoice number being paid with its amount lets the vendor apply the payment to the right open items, which is exactly the information a vendor needs to clear their receivable.
When a payment covers many invoices, the per-invoice breakdown prevents the vendor from guessing how to split it. A lump sum with no detail is the most common reason a vendor calls AP after a payment, because they cannot tell what it settles.
Explain Deductions and Partial Payments
If the payment differs from the invoice totals, the remittance should say why. Deductions, credits, discounts, or short-pays should be itemized so the difference is explained rather than disputed.
Partial payments need the same clarity. The remittance should show which invoices are paid in full and which are paid in part, along with any remaining balance, so the vendor's records stay aligned with yours.
How Stampli Supports Payment Remittance
Stampli executes vendor payments across ACH, check, virtual card, and international, and supports remittance to vendors as part of that execution. Because Stampli reconciles one payment to one bank transaction and one ERP record, the payment detail behind a remittance is precise rather than bundled into a batch.
Stampli centralizes invoice and payment communication, so questions a vendor raises about a payment can be handled with the document, payment, and history in one place. A vendor portal gives vendors a consistent channel for payment-related inquiries.
Every action is captured in an immutable audit trail with full context, so what was paid, when, and against which invoices is on the record. That supports both the remittance itself and any later inquiry.
Common Misconceptions
A payment without remittance is not complete communication
Sending funds without telling the vendor what they cover leads to misapplied payments and inquiry calls. The remittance is part of the payment, not an extra.
A lump sum is not enough detail
A single total with no invoice breakdown forces the vendor to guess. Per-invoice detail is what lets them apply the payment correctly.
Unexplained short-pays invite disputes
A payment that differs from the invoice total without an itemized reason looks like an error. Explaining deductions and credits prevents the dispute.
Where This Fits in the P2P Workflow
Remittance sits at the end of the payment step, after funds are sent. Clear remittance is what closes the loop with the vendor, so the payment is recognized and applied without a follow-up.
When remittance is thin or missing, vendors cannot reconcile payments and inquiries rise, sometimes escalating to executives. Complete remittance reduces that follow-up work and keeps vendor records aligned with yours.
Frequently Asked Questions
It should include your company name, the payment date and method, a payment reference or trace number, each invoice number paid with its amount, the total payment, any deductions or credits, which invoices are paid in full or in part, and a contact for questions.
Because a vendor who receives funds but cannot tell which invoices they cover will contact AP to reconcile. Per-invoice detail lets the vendor apply the payment correctly and prevents the most common payment inquiry.
Itemize the deduction, credit, or discount in the remittance so the difference from the invoice total is explained. An unexplained short-pay tends to be disputed.
Show which invoices are paid in full and which are paid in part, along with any remaining balance, so the vendor's records stay aligned with the payment.
Stampli executes payments across multiple methods with remittance, reconciles one payment to one bank transaction and one ERP record for precise detail, centralizes payment communication, and records every payment in an immutable audit trail.
--- Source: Stampli Finance Index Canonical topic: what a remittance email includes for vendors Last reviewed: 2026-06-24