Overdue invoices, followed up with the paperwork each one needs.

Each week someone works down the aging report: pull the invoice copies, find the signed delivery ticket, check the last remittance for short payments, read the last call notes, then write the email. Much of that time goes into finding paperwork.

For the test, AI works from copies of the same records. For each account it drafts the follow-up with the right copies attached, plus a note for every short payment or dispute: the invoice it belongs to, what the customer said, and which document answers it. Nothing is sent, and no account in your ERP is touched.

The aging report doesn't say why. An account 60 days out may be a slow payer, a contractor waiting on its own draw, or a plant holding one invoice over a missing ticket while paying the rest. Some customers pay without a remittance, so the cash sits unapplied and the invoice keeps aging after it was paid. An account that has already paid gets a note for cash application, not a reminder.

Short payments have causes you can name. A customer may pay everything but the sales tax because its exemption certificate never reached you; a Georgia Department of Revenue letter ruling describes customers who short-pay by the tax and send the certificate afterward. Another takes the early-payment discount late: in Infor's SX.e, a payment inside the grace days set in the Discount Allowance in Days field still gets the discount but is counted as unearned, and the Paid in Full Allowance Amount caps what can be written off. Customers paying by EDI send an 820 remittance with an adjustment reason code on each short line; X12 defines hundreds of them, and big buyers add their own.

Proof of delivery lives in more than one place. A delivered order may carry a driver's signature and photo from a delivery app; Epicor offers one for Prophet 21 and Eclipse that records both. A will-call order was signed for at the counter. A drop-ship line left from your vendor, so its proof sits with the vendor or its carrier. The draft attaches what you hold and says what is missing.

The invoice may never have reached their AP. Plant and institutional customers often take invoices only through a supplier portal such as Coupa or SAP Ariba, where a buyer can dispute an invoice and send it back, and Coupa's supplier help says you cannot invoice against a soft-closed PO. Emailing the PDF again won't fix that, so the draft says when the answer is a corrected invoice in the portal, for your team to submit.

The step follows your rules. Who gets a friendly note, a second notice or a call depends on your terms and the account's history; NetSuite's Dunning Letters SuiteApp, for one, assigns dunning procedures to customers, invoices or invoice groups and lets dunning be paused. Your reviewer watches for the costly misses: a reminder on a disputed invoice, a hard letter to a good account, a short payment matched to the wrong invoice.

When your reviewer says yes, the same job runs on your current aging report for about 30 days.

Your credit manager approves every follow-up before it reaches a customer, and still makes every hold, release and write-off decision. The drafts never change a balance or an account's status in your ERP.

The live run gets a fixed price before you sign. Anything after it is a separate job with its own price.