Every time a customer pays an invoice, they usually send along some information about what they’re paying for. That information, the remittance, is what your accounts receivable (AR) team uses to match the payment to the right open invoice and close it out. Simple in theory. Brutal in practice.
The reality for most finance teams is that remittance data arrives in dozens of formats, through multiple channels, often incomplete, sometimes with no reference numbers at all. For companies processing hundreds or thousands of payments a month, aggregating all of that data and matching it accurately is one of the most time-consuming and error-prone processes in the entire AR function.
This guide breaks down what remittance processing actually involves, where the biggest pain points are, and how modern finance teams are solving the problem at scale.
What is remittance processing?
Remittance processing is the workflow that captures, interprets, and applies payment information to the correct open receivables in your financial system. When a customer makes a payment, they typically include a remittance advice, a document (or data file, or email) that tells you which invoices the payment covers, and in what amounts.
Your AR team uses that remittance advice to complete the cash application process: matching incoming payments to the invoices they settle, then posting those payments to your general ledger. Done well, it keeps your books accurate, your days sales outstanding (DSO) low, and your customer relationships clean. Done badly, it creates a backlog of unmatched payments, a growing pile of unapplied cash, and constant back-and-forth with customers to figure out what they actually paid.
Remittance processing sits at the intersection of two processes that have historically been highly manual: remittance aggregation (collecting and organizing remittance data from all the places it arrives) and cash matching (applying that data to the right invoices in your ERP or AR system).
Why remittance processing is so hard to scale
The core problem is fragmentation. Customers don’t send remittance in a standard format. They use whatever works for them: a PDF attached to an email, a portal upload, an EDI file, a check stub, a spreadsheet, sometimes a phone call. Each format requires a different approach to extract the underlying data.
At low volumes, your team can handle this manually. But as your business grows, the math starts working against you. More customers means more payment formats. More invoices means more potential for mismatches. More markets means more currencies, more regional payment conventions, more complexity.
Here are the most common pain points finance teams report:
Inconsistent remittance formats. A single large customer might pay by wire one month and ACH the next, with remittance sent via email one time and an EDI 820 the next. Your team has to handle both, and everything in between.
Missing or incomplete remittance data. Many payments arrive with no remittance at all, or with partial information. Someone sends a round-number wire with no invoice references. Your team has to go back to the customer to find out what was paid. That adds days to the process and ties up skilled people in administrative work.
Short payments and deductions. Customers often pay less than the invoiced amount, whether because of a pricing dispute, a promotional deduction, or a straightforward error. Handling these exceptions manually is slow, and they pile up fast. The revenue impact is also larger than most teams realize — invalid deductions alone can account for 1–3% of annual revenue in organizations without a structured process to catch and recover them.
Delays between payment receipt and remittance delivery. Sometimes the money arrives days before the remittance does. That cash sits unmatched, inflating your unapplied cash balance and making it harder to get an accurate picture of what you’re actually owed.
ERP limitations. Most ERP systems are not designed for high-volume, multi-format remittance processing. They rely on human input to extract data from non-standard formats and manually key it in, which is where errors accumulate.
How remittance aggregation works (and where it breaks down)
Remittance aggregation is the first stage of the process: pulling remittance data together from every channel and format into a single, usable source of truth.
For most AR teams today, aggregation is a patchwork. Someone monitors a shared inbox for emailed remittances. Another process pulls EDI files from a trading partner portal. Check stubs come in with physical mail. Customer portal downloads happen manually. Everything gets consolidated in a spreadsheet, or worse, handled separately by different people with no unified view.
The problem with that approach isn’t just inefficiency. It’s that every hand-off is a potential gap. Remittances get missed. Data gets entered wrong. The volume that can reasonably be processed per day is capped by how many people you have doing it, not by how many payments are coming in.
What effective aggregation looks like at scale is a centralized intake process that captures remittance data from all channels automatically, normalizes it into a consistent structure, and routes it into the matching workflow without human intervention at the collection stage. That means connecting to email, EDI, customer portals, lockbox files, and bank statements through a single layer, rather than managing each source as a separate manual process.
How cash matching works: straight-through vs. exception-based
Once remittance data has been aggregated and normalized, the matching process begins. The goal is to link each payment to the specific invoice or invoices it settles, then post it to your AR ledger.
At its most basic, matching is a lookup: does the invoice number in the remittance exist in your system, and does the amount match? If yes, auto-post and move on. If no, route to a human for investigation.
But the real world is messier than that. Invoice numbers get transposed. Customers pay against a purchase order rather than an invoice number. One payment covers 47 invoices across three subsidiaries. A customer underpays by 3% and you need to figure out whether it’s a legitimate deduction or an error.
High-performing AR operations handle this through a tiered matching approach:
Tier 1: Straight-through processing. Payments with complete, accurate remittance that match exactly to one or more open invoices are auto-matched and posted without anyone touching them. The goal is to push as high a percentage of payments as possible into this tier.
Tier 2: Fuzzy matching. Payments where the remittance data is close but not exact, perhaps the invoice number has a typo, or the amount is slightly off, are flagged and run through rules-based logic to find the most likely match. If confidence is high enough, they’re auto-matched and queued for review rather than blocked entirely.
Tier 3: Exception handling. Payments that can’t be matched automatically are routed to AR analysts for investigation. These include unidentified payments with no remittance, short pays, duplicate payments, and anything else the system can’t resolve on its own. Short pays in particular require careful handling, since they often reflect underlying disputes or deductions that need a resolution workflow separate from cash matching.
The measure of a good remittance processing setup is not how well it handles exceptions. It’s how few exceptions there are.
The role of AI in remittance processing at scale
This is where the biggest shifts are happening in AR right now. Traditional rules-based matching can handle clean, predictable remittance data well. But it struggles with the long tail of edge cases that make up a significant share of real-world payment volume.
AI-powered cash application tools approach the problem differently. Rather than matching only against explicit rules, they learn from historical matching patterns to recognize payment behavior at the customer level. They can read unstructured remittance documents, extract relevant data regardless of format, and identify likely matches even when the remittance is incomplete or inconsistent.
The practical result is a higher straight-through processing rate. Instead of automatically processing 40 or 50% of payments and routing the rest to analysts, AI-driven systems can push that number to 80, 90% or higher, depending on data quality and payment complexity.
Serrala’s AR automation solutions use AI to handle multi-format remittance ingestion and matching at enterprise scale, including complex scenarios like deductions management, multi-currency matching, and payments that span multiple business units or ERP systems.
What does remittance processing look like across different payment types?
The right approach to remittance aggregation and matching depends partly on the payment methods your customers use. Different payment types come with different remittance conventions and different levels of data richness.
ACH payments
ACH transfers can carry remittance data in the addenda record that travels with the payment. When customers include it, this is some of the richest machine-readable remittance available. When they don’t, you get a payment with no reference information at all.
Wire transfers
Wire remittance is typically sent separately, often via email. The payment and the remittance often arrive at different times, creating a temporary mismatch that has to be resolved manually or through a holding process.
Check payments
Check stubs are physically attached to the payment, but extracting the data from them requires either manual keying or optical character recognition (OCR) technology. For companies still receiving significant check volume, this is often the most labor-intensive part of the remittance process. Many of those companies route check payments through a bank lockbox service, which handles physical collection but still leaves the remittance extraction problem unsolved. How lockbox processing works and where automation fits in is worth understanding if check volume is a meaningful part of your payment mix.
EDI 820 transactions
EDI remittance is structured and machine-readable by design. For companies with large trading partners who use EDI, this represents the closest thing to ideal remittance data. The challenge is mapping the data to your internal invoice numbering conventions.
Virtual cards
Growing in use, particularly in B2B payments, virtual card remittance is often sent alongside the card payment details. Processing it requires specific integrations with card networks or payment processors.
Customer portals
Many large buyers require suppliers to accept payment through their procurement portals. Remittance is available within the portal, but extracting it requires either manual download or portal-specific API connections.
The more payment types you accept from more customers in more markets, the more complex your aggregation and matching problem becomes. Building a system that can handle all of them consistently, rather than stitching together point solutions for each, is one of the core challenges of remittance processing at scale.
Key metrics for measuring remittance processing performance
If you want to understand how well your current remittance process is performing, a few metrics tell most of the story. For a broader view of how these fit into the full AR picture, the AR KPIs and benchmarks guide covers industry benchmarks in more detail.
Straight-through processing (STP) rate
The percentage of payments that are automatically matched and posted without human intervention. Higher is better. Best-in-class operations typically run above 80%.
Unapplied cash as a percentage of total cash
How much of the money you’ve received is sitting unmatched? High unapplied cash is a direct sign of remittance aggregation and matching problems.
Time to post
How long does it take from payment receipt to posted cash application? Delays here affect your AR aging reports and can distort your view of what customers actually owe.
Exception rate
The percentage of payments that require manual investigation. Tracking this over time tells you whether your matching logic is improving or degrading.
Days sales outstanding (DSO)
While DSO is influenced by many factors, persistent matching problems and unapplied cash directly inflate it. If your DSO is higher than it should be given your payment terms, remittance processing inefficiency may be part of the reason.
How to improve remittance processing: practical steps
Most finance teams don’t need to overhaul everything at once. The biggest gains usually come from addressing the most common failure points first.
Centralize remittance intake. If your team is monitoring multiple email inboxes, downloading files from separate portals, and handling check stubs through a different process, the first improvement is bringing all of those channels into a single aggregation point. This alone reduces the risk of missed remittances and gives you a complete picture of what’s in the queue.
Standardize what you can. Work with high-volume customers to encourage EDI remittance or structured email formats where possible. You won’t get all of them, but moving even a portion of your payment volume to more structured remittance can meaningfully improve your STP rate.
Invest in OCR and data extraction. For remittance that arrives as PDFs, check stubs, or scanned documents, good OCR technology eliminates the manual keying step and makes data available for automated matching. The accuracy of modern OCR tools, especially those tuned for financial documents, has improved substantially.
Build your matching rules around exceptions, not the rule. Most matching logic development focuses on building rules for common cases. Flip that approach: make sure straight-through processing handles the majority automatically, and build specific workflows for your most common exception types rather than treating all exceptions as one undifferentiated queue.
Use AI to close the gap. For companies with significant remittance complexity, rule-based matching alone won’t get you to high STP rates. AI-driven matching, trained on your historical payment data, can handle the ambiguous cases that rules struggle with. Serrala’s AI-powered AR automation is designed specifically for this kind of complex, high-volume environment. If you want a practical walkthrough of how automation projects actually get implemented, this guide to automating your cash application process covers the sequencing in detail.
Remittance processing and working capital visibility
There’s a broader reason to care about remittance processing beyond operational efficiency. Unmatched payments and unapplied cash create blind spots in your working capital picture.
If you can’t accurately see what’s been paid, you can’t accurately see what’s outstanding. That affects your cash flow forecasting, your collections prioritization, and the decisions your CFO is making about liquidity and investment. Finance teams that advance the office of the CFO don’t just process payments efficiently. They give leadership the real-time visibility needed to act on that data. For a deeper look at how AR efficiency connects to working capital management more broadly, this guide to working capital excellence is worth reading.
Serrala’s accounts receivable automation is part of a broader platform that connects AR, AP, payments, and treasury, so that accurate, matched cash data flows through the entire financial picture rather than stopping at the AR ledger.
Key takeaways
- Remittance processing is not just an operational problem. It’s a working capital visibility problem — unmatched payments and unapplied cash create blind spots that affect forecasting, collections, and CFO decision-making.
- The core challenge is fragmentation: remittance arrives in dozens of formats across dozens of channels, and most ERP systems aren’t built to handle that volume without significant manual input upstream.
- Effective remittance processing depends on two things working together: centralized aggregation that captures data from every channel automatically, and intelligent matching that maximizes straight-through processing.
- Your straight-through processing (STP) rate is the single most telling metric. Best-in-class operations using AI-driven matching typically exceed 80–90%. If yours is below 50%, remittance aggregation and matching are likely your biggest bottleneck.
- Short payments and deductions are not just a matching problem — they require a separate dispute resolution workflow to recover revenue and keep DSO in check.
- AI improves remittance matching by learning customer payment patterns, reading unstructured documents, and handling edge cases that rules-based systems route to exceptions.
- For teams managing significant payment volume across multiple customers, markets, and payment types, purpose-built AR automation is the most reliable path to scale.
Frequently asked questions
What is the difference between remittance processing and cash application?
Cash application is the broader process of matching incoming payments to open receivables and posting them to the ledger. Remittance processing is specifically the stage that handles the remittance data: collecting, interpreting, and structuring the payment information that makes cash application possible. You can’t do cash application accurately without effective remittance processing. For a full breakdown of what cash application involves, the complete guide to cash application covers the end-to-end process in detail.
What is an EDI 820 transaction?
An EDI 820 is a standardized electronic data interchange document used to transmit payment order and remittance advice information between trading partners. It’s one of the most structured and machine-readable forms of remittance data available, and it’s commonly used in large-scale B2B payment environments.
What is unapplied cash?
Unapplied cash refers to payments that have been received but not yet matched to a specific invoice or receivable. It sits in a suspense or holding account until it’s matched and posted. High levels of unapplied cash typically indicate remittance processing problems and can distort your view of outstanding receivables.
Why do companies still struggle with remittance matching despite having an ERP?
Most ERP systems were designed to manage financial records, not to ingest multi-format remittance data at scale. They typically require clean, structured input, which means remittance extraction and normalization still happens manually upstream of the ERP. Dedicated AR automation tools address this gap by handling the messy intake work before data enters the ERP.
What is a good straight-through processing rate for cash application?
It depends on payment complexity, customer mix, and remittance quality, but most finance teams should aim for at least 70 to 80% straight-through processing. Best-in-class operations using AI-driven matching often exceed 90%. If your STP rate is below 50%, remittance aggregation and matching are likely significant pain points worth addressing.
How does AI improve remittance matching?
AI improves remittance matching by learning from historical payment patterns at the customer level, reading unstructured documents to extract remittance data, and identifying likely invoice matches even when remittance information is incomplete or inconsistent. This allows it to handle edge cases that rules-based systems route to exceptions, increasing the percentage of payments that are automatically matched.
What is remittance aggregation?
Remittance aggregation is the process of collecting remittance data from all the channels through which it arrives: email, EDI, customer portals, check stubs, lockbox files, and more, and consolidating it into a single structured format ready for matching. It’s the first stage of remittance processing, and fragmented or manual aggregation is one of the most common reasons AR teams struggle to scale.
