How do I handle partial payments and split invoices in cash application?

Apply a partial payment against the specific invoice the customer intended, leaving the remainder open rather than closing the invoice or creating an unexplained credit. When one payment is meant to cover multiple invoices (a split payment), allocate it line by line using the remittance detail; if no allocation is specified, apply oldest-invoice-first is the most common default rule.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 10, 2026Last reviewed September 10, 2026Editorial policy

Part of the payment reconciliation and cash application guide.

Partial payment rule	Apply to the specific invoice; leave remainder open, don't force-close
Split payment default	Oldest invoice first, absent explicit remittance instructions
Where this usually breaks	No remittance detail specifying which invoices a payment covers
Stripe's handling	Unmatched amounts remain in a Source object pending manual application

Partial payments: leave the balance open

A payment that's less than the full invoice amount should reduce that invoice's open balance by exactly the amount received, leaving the remainder outstanding and still visible on the aging report. The two mistakes to avoid: closing the invoice anyway (which understates AR and loses track of money still owed) and posting the shortfall as an unexplained write-off before confirming with the customer whether more payment is coming, a dispute exists, or it was simply an underpayment in error.

Split payments across multiple invoices

When a single payment is meant to settle several invoices — common with customers who batch their AP runs — the remittance advice accompanying the payment should specify exactly which invoices and amounts it covers. Applying it correctly means allocating line by line according to that remittance detail, not just applying the total against the oldest open balance and hoping it works out. When no remittance detail exists at all, oldest-invoice-first is the standard default, on the reasoning that a customer paying down a balance is most likely settling their oldest obligations first — but this default should be confirmed with the customer whenever the amount doesn't split evenly across the open invoices.

Overpayments

The reverse case — a payment larger than any single open invoice — should close that invoice and hold the excess as a credit on the customer's account (applied to a future invoice) or refunded, rather than applied against an unrelated invoice without the customer's knowledge.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Worked example

One payment, two invoices, no remittance advice

A customer has two open invoices: Invoice #1042 for $2,000 (due 45 days ago) and Invoice #1078 for $3,000 (due 10 days ago). A $3,000 payment arrives with no remittance detail. Applying the oldest-invoice-first default: $2,000 closes Invoice #1042 in full, and the remaining $1,000 applies as a partial payment against Invoice #1078, leaving $2,000 still open on that invoice. The customer should be contacted to confirm this allocation matches their intent, particularly because the payment amount happens to equal Invoice #1078's total exactly, which is a reasonable signal they may have intended to pay that invoice specifically instead.

Frequently Asked Questions

Apply the oldest-invoice-first default and document that the allocation was made without confirmation, so it can be corrected later if the customer eventually clarifies their original intent.

No — the remaining open balance keeps the original invoice's due date and continues aging from that date, not from the date of the partial payment.

As a customer credit balance until the refund is processed, not as revenue or as an adjustment to an unrelated invoice.

Sources

Topic

Payment Reconciliation & Cash Application

Payment reconciliation is the process of proving that every dollar that hit your bank account is accounted for somewhere in your books — matched to a deposit, a payout, an invoice, or an explained var…

Definition

What is an AR aging report and how do I read it?

An AR aging report lists every open invoice grouped by how long it's been outstanding — current, 1-30, 31-60, 61-90, and 90+ days past due. Read it by tracking the bucket distribution over time, not just the total; a shrinking current bucket and growing 90+ bucket signal a collections problem before it shows up in a blended DSO figure.

How-to

How does automated cash application work?

Automated cash application matches incoming payments to open invoices using deterministic rules first (exact amount plus invoice number or customer ID), then fuzzy or confidence-scored matching for near-misses, routing anything unresolved to an exception queue for a person to confirm. The result is applied straight to the AR subledger without manual lookup for the majority of payments.