Finance Index
Remittance in Accounts Payable
Payment advice that connects vendor payments to invoices, credits, discounts, and payment details for accurate cash application and reduced vendor inquiries.
Remittance is the payment advice that communicates what a vendor payment covered by connecting payments to their invoices, credits, discounts, payment dates, methods, and reference numbers. This communication enables vendors to apply cash accurately while providing AP teams with structured payment evidence for reconciliation and vendor support. Proper remittance reduces vendor inquiries and strengthens the payment automation workflow by ensuring vendors understand payment allocations.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Primary Purpose | Explains payment allocation to vendors | Enables accurate cash application and reduces AP follow-up |
| Key Information | Invoice numbers, amounts, credits, discounts, payment references | Vendors need allocation detail beyond bank descriptors |
| Timing | Triggered by payment status and method-specific rules | Ensures vendors receive advice when they can act on it |
| Recipients | Vendor remittance contacts and payment processors | Correct routing prevents delays and duplicate inquiries |
| Documentation | Creates audit trail for payment communication | Supports reconciliation and vendor dispute resolution |
What Remittance Covers
Remittance encompasses all communication that helps vendors understand payment allocations. This includes email notifications with invoice-level detail, printed check stubs with remittance tables, electronic payment advice with batch information, and structured reports that explain combined payments, credits, and discounts.
The scope extends beyond simple payment confirmation to include method-specific context such as currency information for international payments, batch identifiers for electronic payment networks, and reference numbers that connect payments to vendor accounting systems.
Payment Advice Generation
Payment advice should be generated from the same payment and invoice data used to execute the payment. This ensures consistency between what was paid and what is communicated to vendors. The advice should include payment references, payment dates, methods, invoice numbers, paid amounts, applied credits, taken discounts, and any method-specific context that helps vendors reconcile their accounts.
Automated generation reduces manual work and eliminates discrepancies that occur when payment advice is created separately from payment execution. The system should maintain the connection between payment workflow data and vendor communication throughout the process.
Invoice-Level Detail Communication
Vendors need allocation detail that explains how payment amounts relate to specific invoices, especially for combined payments that cover multiple invoices or include credits and discounts. The remittance should clearly show which invoices were paid in full, which received partial payments, and how credits or discounts affected the final payment amount.
This level of detail becomes critical when payment amounts do not match single invoice totals, when vendors maintain their own discount terms, or when payments include adjustments that are not visible in the vendor's original billing records.
Method-Specific Remittance Requirements
Different payment methods create different remittance needs and constraints. Check payments typically include printed remittance tables with invoice details. ACH and wire transfers may rely on email notifications with structured payment data. Card payments might require different recipient contacts than standard AP communications. International payments need currency context and exchange rate information.
Electronic payment networks may group multiple vendor payments into single bank debits, requiring batch-level reporting that connects grouped transactions back to individual vendors and invoices. Each method should follow appropriate timing, content, and delivery rules.
Vendor Contact Management
Accurate remittance depends on maintaining current vendor contact information, including remittance email addresses that may differ from standard vendor contacts. Payment processors need to know who should receive payment advice, and this information should be validated regularly to prevent misdirected communications.
Contact management should account for different recipients for different payment methods, such as separate contacts for card payments versus ACH payments, and should include backup contacts when primary recipients are unavailable.
Timing and Delivery Rules
Remittance timing should align with payment status changes and vendor expectations. Vendors need payment advice when they can act on it, which may vary by payment method and processing timeline. Some payments require immediate notification, while others may be batched for efficiency.
The system should handle timing rules that prevent premature notifications, duplicate communications, and delivery to outdated contact information. Proper timing reduces vendor confusion and ensures payment advice arrives when vendors are ready to apply cash.
Batch and Combined Payment Handling
When multiple invoices are combined into single payments, or when electronic payment networks group multiple vendor payments into batch transactions, remittance should provide clear allocation detail. Vendors receiving combined payments need to see individual invoice amounts, while AP teams need batch-level reporting to explain grouped bank debits.
This becomes particularly important for high-volume vendors, electronic payment adoption, and reconciliation workflows where bank statements may show provider-level debits rather than individual vendor transactions.
Common Misconceptions
Remittance is not just payment confirmation
Payment confirmation tells vendors that money moved, but remittance explains how to apply it. Vendors need allocation detail for combined payments, credits, discounts, and method-specific references that do not appear in bank descriptors.
Bank descriptors are not sufficient payment advice
Bank descriptors have character limits and formatting constraints that prevent complete invoice allocation detail. Vendors often receive funds with generic descriptors that require additional communication to understand payment allocation.
ERP remittance does not always include payment workflow context
ERP-generated remittance may lack payment method details, provider status information, selected attachments, and workflow-specific context that affects how vendors should interpret and apply payments.
One remittance template cannot serve all payment methods
Check stubs, electronic payment emails, international wire details, and card payment notifications have different content requirements and delivery constraints that require method-specific handling.
Where This Fits in the P2P Workflow
Remittance occurs after payment execution and before vendor cash application, serving as the bridge between AP payment processing and vendor account reconciliation. Upstream, remittance depends on accurate payment creation, proper invoice coding, and current vendor contact information. Downstream, effective remittance enables accurate vendor cash application, reduces payment inquiries, and supports reconciliation processes.
The quality of remittance directly affects vendor relationships and AP efficiency. Poor remittance leads to increased vendor calls, delayed cash application, and potential payment disputes that require manual resolution.
Frequently Asked Questions
Remittance should include payment reference numbers, payment dates, payment methods, invoice numbers, paid amounts, applied credits, taken discounts, and any method-specific context such as currency information or batch identifiers. This detail enables vendors to apply cash accurately without contacting AP teams.
Remittance timing should align with payment status changes and method-specific processing timelines. Vendors should receive payment advice when they can act on it, which may be immediately for some methods or after batch processing for others.
Remittance should go to vendor contacts designated for payment communications, which may differ from general vendor contacts or invoice contacts. Payment processors also need access to remittance detail for support and reconciliation purposes.
Check payments typically include printed remittance tables, ACH payments rely on email notifications, card payments may use different recipient contacts, and international payments need currency context. Electronic payment networks may require batch-level reporting for grouped transactions.
Incorrect remittance contacts lead to misdirected communications, delayed cash application, increased vendor inquiries, and potential payment disputes. Regular validation of vendor contact information prevents these issues.
Combined payments require invoice-level allocation detail showing which invoices were paid, what amounts were applied, and how credits or discounts affected the total. Vendors need to see individual invoice breakdowns to apply cash correctly.
Remittance content may be customized within method-specific constraints, but the core requirement is accurate payment allocation detail. Customization should not compromise the essential information vendors need for cash application.
Remittance creates an audit trail of payment communications that supports reconciliation, vendor dispute resolution, and compliance documentation. This trail should be maintained as part of the payment record for future reference.