Comparison
How to automate your accounts receivable process
Let billing issue invoices and a schedule chase them. Automate cash application proposals, and keep a person on anything short-paid or disputed.
By the Foxnut team · Updated
How do you automate the accounts receivable process?
To automate the accounts receivable process, let the billing system issue invoices, let a dunning schedule chase them, and put the work into cash application: deciding which open invoices a payment that has already landed actually pays. Automate the identification and the proposal there. Keep a named person on the settlement of anything short-paid, disputed or unreferenced.
We are Foxnut AI. We build AI and growth systems with senior people only, from Bengaluru and Paris, and hand them over running. There’s a link to talk to us at the end of this guide. Let’s work out which part of your receivables is worth automating first.
Confusion to avoid: “automate accounts receivable” names three different jobs, and two of them are mostly solved. The billing system issues invoices the moment the order or the contract exists. Chasing them is a schedule of reminders that any dunning feature can run, and whether to hand the stubborn ones to a collections process is its own decision with its own page in this library.
The job that resists is the one in the middle of the money’s arrival: cash application. It is the least visible of the three and the one where automation projects in this process stand or fall. That is why the handover this studio structures a receivables build around treats the matching layer, not the invoicing layer, as the thing the owner has to be able to run without its builder.
The reason cash application is hard is structural, not technical. On the payables side of the same transaction, the payer holds everything: which invoices are being paid, what was deducted and why. On the receivables side, that information belongs to somebody else, and you get exactly as much of it as the payer’s systems and habits choose to send.
A receivables process can be tidy to the last invoice and still drown in unmatched cash, because the mess is made upstream, in other companies’ payment runs.
Why is accounts receivable cash application so hard?
Cash application is hard because payment formats separate the money from its explanation. In the ACH network’s own corporate transaction types, a CCD entry, the ordinary corporate credit or debit, can carry a single addenda record of payment-related information. A CTX entry supports up to 9,999 addenda records, enough for a full ANSI ASC X12 remittance message to travel with the payment.
The payer chooses the format, in the payer’s own treasury setup. A customer who pays forty invoices with one CCD transfer has sent a sum of money whose explanation physically cannot ride along with it. The detail arrives separately, as an emailed PDF, a portal posting, a spreadsheet, or not at all. Wires and cheques have the same problem: the money is one number and the reasoning is somewhere else.
Then there is the money that arrives already disagreeing. A payment that covers a batch of invoices minus a promotional allowance, a damaged-goods deduction and a disputed price difference is not an unmatched payment in the timing sense. It is a commercial position expressed as arithmetic.
No matching rule can resolve it, because there is nothing to match. The customer has deliberately paid an amount that corresponds to no invoice on file. Cash application is where that position first becomes visible, and what the process does with it decides whether the disagreement gets resolved or silently absorbed.
This matters because of what reads the output. The result of cash application is the aged trial balance, meaning which invoices are outstanding and how old they are, and that schedule is more than a working paper. Under the credit-losses standard, an aging schedule is one of the named methods for estimating the allowance for expected credit losses.
The standard’s own worked example prices its illustrative entity’s buckets from historical loss rates of 0.3% on current receivables through 8%, 26% and 58% to 82% on anything more than 90 days past due. A payment applied to the wrong invoice moves balances between those buckets. The books still balance, the cash is still in the bank, and an input to the financial statements has quietly changed.
What are the ways to apply a payment to an invoice?
There are four ways: a person applies it, rules settle it end to end, rules post it and a person settles it, or rules propose it and a person approves it. At least one major ERP documents those three automated behaviours for applying customer cash from an imported bank statement, and the differences between them are exactly where the control decisions sit.
| A person applies it | Rules settle it end to end | Rules post it, a person settles it | Rules propose it, a person approves it | |
|---|---|---|---|---|
| What decides the match | Whoever reads the statement line, the remittance email and the open-invoice list, and picks | Matching criteria against open invoices in the legal entity; on success the payment journal posts and the invoice is settled in one pass | The customer is identified - by invoice match or by the payer's bank account against the customer record - and the payment posts on account, with settlement left open | The same matching rules run, but results land on a review tab as drafts, to be approved or rejected before anything posts |
| What arrives in the ledger | Whatever the person decided, at the person's pace | A settled invoice with no human touch between statement and ledger | Cash recognised promptly, application deferred - the aging shows the money but the invoice still looks open | Nothing, until a named person has looked |
| Where the errors go | Into whatever the person misread, at the speed of one line at a time | Into the settled history, discoverable only by someone who later questions a closed item | Into a visible on-account balance that sits on the customer until someone finishes the job | Into a rejected draft, at the cost of reviewing everything, including the obvious matches |
| What it assumes | Patience and low volume | That the statement line carries enough reference to be trusted alone | That identifying the payer is automatable even when the allocation is not | That review capacity exists and reviewers do not rubber-stamp |
The middle two columns matter most, because they split a decision most projects treat as one decision. Recognising the cash and applying it are different acts with different errors. Posting the payment on account is close to riskless, because the money did arrive from that customer. Settling it against specific invoices is where a wrong guess changes what the aging says.
A design that automates the first act aggressively and the second act selectively has kept the risk where it can see it.
What decides whether accounts receivable is worth automating?
Six structural dimensions decide whether a process is worth automating. Accounts receivable reads unusually on them because your customers create the exceptions, and because the output feeds a financial-statement estimate and not an operational queue.
| Dimension | What it reads on accounts receivable | Source |
|---|---|---|
| Exception variance | Set by the payer, not the process. Whether a payment arrives with its remittance detail is decided by the payer's choice of format: in the ACH network's corporate entry types, a CCD entry can carry a single addenda record of payment-related information while a CTX entry supports up to 9,999, enough for a full X12 remittance message. The receiver controls neither the choice nor the discipline of what the addenda cite, so the unmatched residue - payments without references, batch payments, short payments expressing deductions - varies payer by payer and cannot be engineered away on the receiving side alone. | Nacha, ACH Guide for Developers, 'How ACH Works' |
| Volume | Not the invoice count and not revenue. A shipped matching engine organises its own setup around statement lines, matching rules and the payer's identifying details, scoped to open invoices in the current legal entity - so what grows the manual workload is the number of distinct payers, payment formats, currencies and remittance channels the process has to absorb, with entity structure multiplying all of it. No verified public figure ties a payment count or dollar volume to when automation pays back, so none is quoted here; the honest form of the threshold is the count of payers whose payments arrive without a usable reference. | Microsoft, Dynamics 365 Finance, 'Cash application in advanced bank reconciliation' |
| Cost of an error | Priced by the aging bucket the error moves. A misapplied payment leaves one invoice looking paid and another looking overdue, and the schedule that absorbs the mistake is a named input to the financial statements: under Topic 326, an aging schedule is one of the permitted methods for estimating expected credit losses, and the standard's own worked example carries historical loss rates that climb from 0.3% on current receivables to 8%, 26%, 58% and 82% as the buckets age. The same corrupted schedule is what credit-limit decisions and escalation-to-collections decisions read, so one wrong application can trigger actions against a customer whose only fault was paying in a format the process could not parse. | FASB, ASU 2016-13, paragraphs 326-20-30-3 and 326-20-55-37 to 55-40 |
| Reversibility | High in the ledger, low in what read it. The application itself is reversible as documented product behaviour: cancelling an incorrectly posted payment journal unsettles the invoice it settled, and a payment posted on account can be settled later once the allocation is known. What does not reverse is everything that consumed the wrong picture in the interval - a reminder or a stop sent to a customer who had paid, a credit decision taken on a wrong aging, a dispute conceded because the disputed line appeared settled. The window between a wrong application and its correction is where the process's real damage accrues. | Microsoft, Dynamics 365 Finance, 'Cash application in advanced bank reconciliation' |
| Regulatory exposure | The receivable balance is checked against the world outside the company. The auditing standard effective for fiscal years ending on or after 15 June 2025 directs the auditor, for accounts receivable arising from goods or services, to perform confirmation procedures or obtain evidence by directly accessing information maintained by a knowledgeable external source, with subsequent cash receipts among the indirect fallbacks - and requires the audit committee to be told when neither was done for a significant risk. The standard's defined unit of trouble, the confirmation exception, is information from the customer that differs from the company's records: exactly the artefact a misapplied payment produces, one customer statement at a time. | PCAOB AS 2310.24, .25, .28, .A2 |
| Vendor market maturity | Settled for statement-driven matching, silent on the disagreements. Statement import, configurable settle-customer-invoice rules, payer identification from the bank account on the statement line, automatic cash discount application, a preview-and-approve queue and payment cancellation that unsettles what it posted are all shipped, documented ERP functionality rather than a build. The same documentation records its own limits: matching runs against open invoices in the current legal entity, and only journal names without approval workflow are supported. What no matching feature adjudicates is a short payment expressing a deduction - the documentation has nothing to say about who owns a disagreement, because that was never a configuration question. | Microsoft, Dynamics 365 Finance, 'Cash application in advanced bank reconciliation' |
The exception row and the maturity row point in the same direction from opposite sides. The shipped tooling is good at exactly the payments whose references arrive intact, and the ones that arrive broken are broken for reasons no receiving-side software controls.
The regulatory and error-cost rows then say why you cannot simply force the broken ones through. Their output is read by the loss estimate, the credit decision and, once a year, an auditor asking the customer directly.
Has Foxnut AI built accounts receivable automation?
Yes, as part of a client’s accounting and finance automation, and two claims here need more careful reading than the rest of this page. Both trace to one source only, our founder’s own account of the studio’s engagement history. That is an operating record, not a cited market statistic.
Named directly
We have built accounting and finance automation for a client, and the engagement's own account of what it touched names accounts receivable directly, alongside daily reconciliation, paying suppliers, bank reconciliation, invoice reconciliation and tax reconciliation
Not in isolation
Our founder's stated view, given as the studio's position and not as a finding: finance automation is very hard to build one process at a time, because it touches all the different parameters and subsystems that make up a company's finance function
| Number | What it measures | Period | Source |
|---|---|---|---|
| Named directly | We have built accounting and finance automation for a client, and the engagement's own account of what it touched names accounts receivable directly, alongside daily reconciliation, paying suppliers, bank reconciliation, invoice reconciliation and tax reconciliation | As of August 2026 | Foxnut AI engagement records (not externally retrievable) |
| Not in isolation | Our founder's stated view, given as the studio's position and not as a finding: finance automation is very hard to build one process at a time, because it touches all the different parameters and subsystems that make up a company's finance function | As of August 2026 | Foxnut AI engagement records (not externally retrievable) |
The “Named directly” record states which processes the engagement reached, nothing more. It does not say how it went, how well it worked, or what it cost. The “Not in isolation” record is a view, not a finding, taken from that same operating record.
Everything else, including exception counts, build time, cost, who ran it and which client, stays unstated, because our founder did not supply it and this page does not infer it.
What do accounts receivable automation projects get wrong?
The first error is scoping. Projects automate the parts of the receivables process the business already controls, invoice generation and reminder schedules, and report the process automated while the cash still lands in a spreadsheet every morning. The test of an accounts receivable automation is not whether invoices go out without touch. It is what happens in the hour after the bank statement arrives.
The second error is measuring the match rate and not the residue. A system that auto-applies most of the payments has automated the payments that were never the problem, because the judgment work was always in the remainder. The number that describes the process’s health is the age and size of the unapplied and on-account balances, and how long a payment waits between arriving and meaning something.
The third error is treating unapplied cash as harmless because the total is right. The money is in the bank either way, so applying it can feel like bookkeeping hygiene. The aging schedule says otherwise. It is an estimation input under the credit-losses standard and the trigger for reminders, credit holds and escalations, so a wrong or stale application is bad data flowing into decisions that act on customers by name.
The fourth error is letting a tolerance parameter make pricing decisions. Auto-clearing small residuals looks like sensible noise reduction, and it quietly forgives every short payment below the threshold without anyone deciding to. A deduction is a customer’s opening position in a negotiation. A write-off rule that clears it unread accepts the position, permanently, at machine speed.
Can AI do accounts receivable?
A system can do the identification and the proposal, and it should. Keep a named person on the settlement of anything short-paid, disputed or unreferenced, and treat the write-off tolerance as a pricing decision owned by a person, not a matching parameter.
The first half follows from the maturity and exception rows together. Statement-driven matching is shipped, documented functionality, and the payments it handles well are the ones whose references arrive intact. No judgment is displaced when a rule settles a clean, fully referenced payment. Posting unidentified cash on account promptly is the same logic one step earlier: recognising that money arrived is separate from deciding what it means, and the first act is safe to automate even where the second is not.
The second half follows from the three risk rows. The error-cost row says a wrong application changes an input to the financial statements and to customer-facing decisions. The reversibility row says the ledger fix is easy but the downstream reads are not recalled. The regulatory row says the balance a misapplication distorts is the one an auditor is directed to verify against the customer’s own records.
So a payment that does not match cleanly is not a low-stakes item to force through a rule. It is either missing information, which a person can go and get, or a live commercial disagreement, which a person must own. A system that proposes an application and holds it for review fits that shape. A system that clears residuals silently does not.
How can you check your own accounts receivable in an afternoon?
Pull the unapplied and on-account balances and age them. Then take one month of incoming payments and count how many arrived with no reference a rule could act on, and which payers sent them.
If the unreferenced share traces to a handful of large payers, the highest-return move in the whole process is not software. It is asking those payers to cite invoice numbers in a format their own payment run already supports. The matching engine works better the day the inputs improve, and that conversation costs nothing to try.
Most receivables projects automate what the business already controls and leave the morning spreadsheet where it was. We start from what happens after the bank statement arrives, and we have built finance automation that reached accounts receivable directly. The people who sign our proposal do the work. There is one tier, we made and launched our own products first, and your finance team owns the system when we leave.
The first step is a free expert audit: a senior practitioner reviews your setup, with no RFP and no pitch deck. You can read about the consulting side of Foxnut AI first. Or tell us what your unapplied-cash number looks like and we will say honestly whether this is a software problem or a payer-conversation problem.
The part most pages leave out
When not to choose Foxnut AI
Situations where another option is the better call, and where we say so in the first conversation rather than the fourth.
- The accounting or ERP system you already run ships its own statement-driven customer payment matching, with statement import, configurable settle-customer-invoice rules, automatic cash discount handling and a review queue, and nobody has switched it on. That feature, configured and not replaced. At least one major ERP's documentation lists rule-based matching of bank statement lines to open customer invoices, automatic settlement, discount application and a preview-and-approve mode as shipped functionality. Our honest recommendation is to configure what is already licensed before you commission a new system to do the same matching.
- Most of what arrives is not a clean payment against a clean invoice. The trading relationship runs on deductions, promotional allowances and short payments, so the typical receipt covers a batch of invoices minus amounts the customer has decided to dispute. A redesigned process, not an automated matcher. When the exception is the relationship's normal case, the work is not matching at all. It is resolving commercial disagreements, and that needs a dispute and deduction process with named owners, agreed references and response times. Automating the matching layer above an unresolved dispute pattern just files the disagreements faster.
- The design lets the system clear residual balances (short payments, small differences, payments that almost cover an invoice) by writing the remainder off automatically below a tolerance, because the amounts are individually small. A human control point placed before the write-off, not after it. A residual written off unread is a dispute priced at zero by a parameter. Nobody decided to forgive that specific amount, and once it has been cleared it stops appearing anywhere a person would think to look. The tolerance is a pricing decision about disputed money, and it belongs to a named person, not to a matching engine's configuration.
- The information a match would run on does not exist in usable form. Remittance advice arrives as emailed PDFs and portal downloads nobody captures, the bank delivers no structured statement feed, or the open-invoice records carry inconsistent references. Your organisation, doing the documentation first. A matching engine assumes a structured statement on one side and clean open invoices with stable references on the other. Arranging the bank feed, settling the reference discipline and agreeing with your largest payers what their payments will cite are prerequisites a build cannot replace.
- The volume is a handful of customer payments a month, most arrive referencing a single invoice, and the person who applies them also reviews the aging before anything escalates. The person already doing it, unchanged. The condition worth watching is not a fixed payment count. It is the number of distinct payers, payment formats and remittance channels the process has to absorb, because that is what multiplies the unmatched residue, not the size of the business measured any other way.
Sources
- Public Company Accounting Oversight Board, AS 2310 'The Auditor's Use of Confirmation' (effective for audits of fiscal years ending on or after 15 June 2025) - paragraph .24's direction that for accounts receivable arising from the transfer of goods or services the auditor should perform confirmation procedures or otherwise obtain evidence by directly accessing information maintained by a knowledgeable external source; paragraph .25's fallback to other substantive procedures, with the note listing subsequent cash receipts among the indirect evidence; paragraph .28's requirement to communicate to the audit committee when neither was done for a significant risk; and Appendix A's definition of a confirmation exception as information in a confirmation response that differs from the information the auditor obtained from the companyRetrieved
- Financial Accounting Standards Board, Accounting Standards Update No. 2016-13 'Financial Instruments - Credit Losses (Topic 326)', June 2016 - paragraph 326-20-30-3 naming methods built on an aging schedule among the permitted ways to determine the allowance for credit losses, and Example 5 (paragraphs 326-20-55-37 through 55-40), which estimates expected credit losses for trade receivables from an aging schedule using the illustrative entity's historical loss rates of 0.3% for current receivables, 8% at 1 to 30 days past due, 26% at 31 to 60 days, 58% at 61 to 90 days and 82% beyond 90 days. Read as text extracted from the FASB's own PDFRetrieved
- Nacha, 'How ACH Works', ACH Guide for Developers - the corporate transaction types: a CCD (Corporate Credit or Debit) entry 'can contain a single addenda record to relay payment-related information', while a CTX (Corporate Trade Exchange) entry 'supports up to 9,999 addenda records' and is used in trading partner relationships 'because a full ANSI ASC X12 message or payment-related UN/EDIFACT information can be sent with the CTX entry'Retrieved
- Microsoft, 'Cash application in advanced bank reconciliation', Dynamics 365 Finance product documentation - the Settle customer invoice matching rules that match imported bank statement lines to open customer invoices in the current legal entity and post and settle a customer payment journal on success; the Generate customer payment action that posts a payment without settling it; automatic customer account identification by matching the statement line's related bank account to the customer's IBAN or account number; automatic application of cash discounts during rule-based settlement; the Require review before posting parameter that holds matching-rule results on a Pending review tab for approval or rejection; the payment-cancellation feature whose note states that a settled invoice is unsettled when the payment journal is cancelled; and the stated limit that only journal names without approval workflow are supportedRetrieved
Foxnut AI takes on work like this from Bengaluru and Paris. If you want to see how we do it before you talk to anyone, here is what an AI engagement covers and what you keep.