What is cash application?

Cash application is the process of matching an incoming customer payment to the specific open invoices it is meant to pay. When a customer sends money, the AR team has to decide which receivables that money clears, then post the result to the ledger. Until that happens, the invoices still show as open, the aging report is wrong, and DSO is overstated. Cash application is the step that turns a deposit in the bank into a closed receivable.

How the matching process works

Every payment carries two parts: the funds and the remittance, which is the detail explaining what the funds are for. Matching is the work of lining them up against open invoices.

The clean case is simple. A customer pays one invoice in full, references the invoice number, and the amount matches exactly. The system finds the open invoice, marks it paid, and posts the cash. Nothing else is needed.

Most payments are messier than that. A single check or ACH often covers a dozen invoices at once. The remittance might list invoice numbers, or it might list the customer's own purchase order numbers, or it might list nothing at all. The matching engine works through identifiers first, then amounts, then customer history, narrowing a payment down to the set of invoices it most likely clears.

The hard cases

The difficulty in cash application is concentrated in a few recurring patterns.

• Short pays. The customer pays less than the invoice total. The system has to decide whether this is a partial payment against the full balance, an approved discount, or an unexplained gap that needs a person to chase.
• Deductions. The customer subtracts an amount for a reason: a pricing dispute, a damaged shipment, a promotional allowance. The deduction has to be coded to the right reason and often routed to a different owner to resolve.
• Remittance that arrives separately from the funds. The money lands in the bank on Monday and the email listing what it covers arrives on Thursday, or never. Without the remittance, the payment sits unapplied as cash on account until someone reconstructs the intent.
• Lump-sum payments. One payment covers many invoices but the total does not tie out cleanly, usually because of a short pay or deduction buried inside the batch. The system has to split the payment across invoices and account for the difference.

These cases are why cash application stays manual at most companies. The clean payments apply themselves; the exceptions consume the team's hours.

What straight-through processing means

Straight-through processing is a payment that is matched and posted with no human involvement. The measure of a cash application process is its straight-through rate, also called the auto-match or auto-application rate: the share of payments that clear without anyone touching them.

A high rate frees the team to work only the exceptions. Pushing the rate up means handling the hard cases automatically, not just the clean ones. That requires reading remittance from any format, pairing late remittance with the funds it explains, and coding deductions to the right reason without a person doing it by hand.

This is where agentic automation changes the work. A system like Rex can read a remittance email, match it to a batch payment that arrived days earlier, split the payment across invoices, code the deduction, and post the result, surfacing only the cases where the intent is genuinely unclear. The operator stops keying in matches and starts resolving the handful of payments the system cannot.

Why cash application matters

Cash application sits at the end of the order-to-cash cycle, and errors there ripple backward. Unapplied cash makes the aging report unreliable. Misapplied payments trigger dunning emails to customers who already paid, which damages relationships and generates disputes. A slow or inaccurate cash application process inflates DSO even when collections are working, because the cash is in the bank but the ledger does not show it yet. Getting it right is what keeps the receivables picture honest.