# How AR automation works, from invoice acceptance to applied cash

> Trace each customer invoice from submission to applied cash, route rejections, disputes, and receipts to the right owner, and measure an AR pilot honestly.

- Canonical page: https://procindex.com/blog/ar-automation-guide
- Author: ProcIndex
- Published: 2025-11-18
- Updated: 2026-11-10
- Topics: accounts-receivable, ar-automation, collections, cash-application

A reminder is queued for an invoice that shows 12 days past due. The customer disputed one line yesterday, their transfer for the rest landed this morning, and billing still thinks the PDF was accepted because the email didn't bounce. Three teams are looking at the same invoice and each has a different, partly correct story.

Accounts receivable automation earns its keep when it moves the right facts between those teams before someone acts on stale ones. This guide walks the invoice from submission to applied cash, shows who should own each state, and explains how to measure whether a change actually helped.

## Track the last confirmed step, not the last action

Most AR systems record what *you* did: invoice created, email sent, reminder sent. What the next owner needs is the last thing that was *confirmed* by someone outside your team. A sent email does not tell you the customer accepted the invoice. A bank deposit does not tell you which invoice it pays.

| Last confirmed step | What it proves | Who acts next | What they need |
| --- | --- | --- | --- |
| Invoice submitted | It left your system | Billing | Whether it reached the right contact or portal |
| Invoice rejected | The customer will not process it as sent | Billing and the account owner | The rejection reason: missing PO, wrong legal entity, price mismatch |
| Invoice accepted, not yet due | It is in the customer's payable queue | Nobody, until the due date | The due date calculated from the agreed terms |
| Accepted and past due | The customer owes it and is late | Collections | Open balance, last contact, any payment promise |
| Receipt in the bank | Money arrived | Cash application | Payer, amount, currency, remittance |
| Receipt partly applied | Some invoices are settled | AR | The remaining amount and whether it is a claim or an unresolved allocation |

Keep each status tied to the record that proves it: the portal reference, the bank line, the customer's email. When new evidence arrives, let the next owner see it before they act.

## Invoice acceptance is the step most teams don't track

Your ledger says the invoice went out on the 3rd. The customer's procurement portal says it is under review. Collections wants a payment date. Before anyone sends a second copy, give the collector the portal status and the name of the person who can check it.

Record the invoice number, submission date, customer account, and the reference returned by the portal or billing channel. Store the last confirmed status and when you checked it. Portals use their own vocabulary. Coupa's supplier portal, for example, distinguishes an invoice that is under review from one that is approved and accepted for payment. Learn what each status means in that customer's process, and calculate the due date from the agreed terms rather than from the date you pressed send. [Coupa's guide to viewing and managing invoices](https://docs.coupa.com/en/supplier-documentation/coupa-for-suppliers/the-coupa-supplier-portal-or-csp/features-and-processes-in-the-coupa-supplier-portal/invoices/view-and-manage-invoices).

| What the customer reports | Who acts next |
| --- | --- |
| Submission received, review pending | Billing asks when review will finish |
| PO or legal entity mismatch | Billing and the account owner confirm the correct order and buyer |
| A charge is disputed | The owner of the contract or billing line reviews the evidence |
| Approved and past due | Collections confirms the payment run and records the promise |
| Customer says payment was sent | AR checks the bank and remittance before anyone asks again |

### Keep the original and corrected invoices connected

If the customer rejects a bill because it used the wrong PO, save the rejection against the original invoice. Find out whether they want a corrected resubmission or a credit memo and a replacement invoice. After the fix, confirm which document is now collectible and whether the corrected one was accepted. If both versions stay open in your system, both will enter the reminder queue, and the customer will get a dunning letter for an invoice they were told to ignore. The [guide to customer invoice requirements](https://procindex.com/blog/customer-invoice-requirements) covers POs, portals, registration, and tax certificates in detail.

## Decide the collections action before drafting the email

An AI tool can summarize a customer's reply and draft a polite follow-up in seconds. Deciding whether a message should go out at all, and for which invoices, needs the ledger and the dispute history in front of whoever approves it.

| What the records show | What collections should do |
| --- | --- |
| Accepted invoice, due date missed, no dispute | Confirm the open balance and ask for a payment date |
| Receipt confirmed but not yet applied | Ask AR which invoices it covers; pause follow-up on those items |
| One line disputed | Send billing the line and the customer's reason; follow your policy on the undisputed balance |
| Portal rejected the invoice | Billing fixes and resubmits; collections waits for acceptance |
| Payment promise still current | Record the date and check whether cash arrives before reminding again |

Pull the amount and status from the ledger, not from the email thread. Verify any payment promise against the customer's actual words. If the evidence is incomplete or contradictory, show the collector what needs checking instead of sending a draft.

### Make every pause specific

A pause needs a reason, an owner, and a review date. On an account with several open invoices, decide which invoices the pause covers. NetSuite, for example, documents pausing dunning for a customer, a single invoice, or an invoice group while a query or dispute is resolved. [Oracle's guide to pausing and resuming dunning](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4035800285.html).

When the dispute closes or the cash is applied, reopen the ledger before resuming outreach. A credit may have reduced the balance or removed the invoice entirely. Keep a record of the balance and status the system used to make the send decision, plus the message that actually went out. When a customer complains about a reminder, that record is the first thing you will want.

## Apply cash from three records, not one

Cash application starts with the bank line (what arrived), the remittance (what the payer meant to settle), and the open items (what is owed). A customer may send one payment for six invoices and deduct a freight charge on one of them. Apply the amounts the remittance supports. Leave the uncertain remainder in a visible unapplied queue with an owner. Give the disputed amount a separate claim record.

Then check the result against the remittance invoice by invoice. A deposit can reconcile to the penny at the bank and still be applied to the wrong invoices, which sends collectors after a customer who already paid. The [cash application guide](https://procindex.com/blog/cash-application-automation) covers matching rules and ERP-specific behavior, and the [guide to unapplied cash](https://procindex.com/blog/unapplied-cash-remittances) covers parent-company and consolidated remittances.

Deductions deserve their own workflow. Applying $900 against a $1,000 invoice is a cash application task. Deciding whether the customer was entitled to withhold $100 is a claim decision that belongs to shipping, pricing, or sales. Mixing the two is how short pays end up written off by default. See [customer deductions and short pays](https://procindex.com/blog/customer-deductions-short-pays).

## Where automation helps and where a person decides

| Task | What software can reasonably do | What a person should decide |
| --- | --- | --- |
| Portal status checks | Read and record the status and reference | Whether a rejection needs a credit or a resubmission |
| Remittance intake | Pull remittance from email or files and attach it to the bank line | Allocation when two invoices could match |
| Cash matching | Propose allocations and flag remainders | Approving uncertain matches; accepting a deduction |
| Collections drafts | Prepare a message from ledger data and customer history | Whether to send, and what to ask for |
| Dispute routing | Route the claim with the invoice line and evidence | Approving, denying, or splitting the claim |

## Measure the clock you changed

AR has at least four separate clocks. Measure each one on its own:

1. **Submission to acceptance.** Driven by invoice quality and portal handling.
2. **Acceptance to payment.** Driven by customer behavior and collections.
3. **Bank receipt to application.** Driven by remittance intake and matching.
4. **Claim received to decision.** Driven by evidence gathering and internal owners.

Faster cash application clears aging sooner, but it does not change the day cash reached the bank. If you count it as faster collection, the business case will overstate the cash benefit.

For an aggregate view, a period-end days sales outstanding (DSO) estimate is ending trade receivables divided by net credit sales for the period, multiplied by the number of days. Illustrative example: ending receivables of $1,080,000 against $675,000 of net credit sales in a 30-day month gives $1,080,000 ÷ $675,000 × 30 = 48 days. Use the same entities, currency, and customer population every month. A change in sales volume or terms moves DSO without any change in how customers pay, so open the invoices behind the number before crediting or blaming collections. [Oracle's days sales outstanding documentation](https://docs.oracle.com/en/cloud/saas/financials/26a/faofc/days-sales-outstanding.html). The [DSO and cash forecasting guide](https://procindex.com/blog/dso-cash-forecasting) works through that diagnosis.

## Run a pilot with cases that cross teams

Vendor demos use clean invoices and a single bank feed. Your backlog does not look like that. Build the pilot from three real, redacted cases:

- **A rejected invoice.** Does the tool record the rejection reason, route it to billing, and keep collections away until the corrected invoice is accepted?
- **A short payment.** Does it apply the supported amount, leave the difference visible, and send the claim to someone who can decide it?
- **A bundled deposit.** Does it allocate across invoices, show the remainder, and tie the total back to the bank line?

Give the vendor the same records your team had at the time. Ask which queue each item enters, who can resolve it, and what appears in the ledger afterward. Then interrupt a posting in a sandbox and retry it. You should end up with one payment record, not two.

Run collections messages in draft mode first. Include a payment confirmed an hour before a reminder was scheduled, and check that the workflow rechecks the balance at send time. Measure how often reviewers change the proposed action and how long they spend checking it. Compare handling time and correction counts with a baseline sample from before the pilot. The [AR pricing and ROI guide](https://procindex.com/blog/ar-automation-pricing-roi) shows how to carry that evidence into a quote comparison.

## What goes wrong

- **Sent treated as accepted.** The due date starts from the send date, and collections chases invoices still under review.
- **Original and replacement both open.** The customer receives reminders for an invoice they were told to discard.
- **Pauses with no expiry.** A dispute closes, nobody restarts follow-up, and the balance ages quietly.
- **Deductions absorbed in cash application.** The analyst clears the short pay to a write-off account to finish the batch.
- **Match rate as the headline metric.** Automatic matches rise while corrections rise faster.

## First pass on your past-due list

- [ ] Pull 20 invoices that are more than 15 days past due and record the last *confirmed* step for each.
- [ ] Count how many were never accepted, how many have unapplied cash against them, and how many are disputed.
- [ ] Give each of those groups a named owner and a review date.
- [ ] Add portal reference and acceptance date fields to your invoice tracking if they don't exist.
- [ ] Require a reason, owner, and review date on every collections pause.
- [ ] Start timing receipt-to-application and claim-to-decision separately from DSO.

## Sources

- https://docs.coupa.com/en/supplier-documentation/coupa-for-suppliers/the-coupa-supplier-portal-or-csp/features-and-processes-in-the-coupa-supplier-portal/invoices/view-and-manage-invoices
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4035800285.html
- https://docs.oracle.com/en/cloud/saas/financials/26a/faofc/days-sales-outstanding.html

---

Published by ProcIndex, which builds AI accounting agents for construction and manufacturing finance teams. ProcIndex currently connects to NetSuite, Sage Intacct, and QuickBooks. Worked examples in this guide are illustrative, not customer results.
