All posts

Working a receivables ledger down: a redesigned collections process

Late payment is a working-capital cost most operators carry without measuring it. We walk one redesigned collections workflow and the mechanism by which it closes the gap between what is invoiced and what is collected on time.

Javier Leguina

Javier Leguina

Co-founder & CTO of flowscope, previously a founding engineer at ModelML (YC W24).

· Automation in practice

Late payment is a working-capital cost that most operators carry on the balance sheet without measuring it precisely. The headline number is visible enough. Allianz Trade found that global average days sales outstanding rose three days to 59 in 2023, the largest jump since 2008. What sits underneath that number is harder to read off the cash-flow statement. Every additional day a receivable stays open is a day the business has financed a customer's purchasing rather than its own, and the days accumulate not because customers are unwilling to pay but because the work of getting paid is done by hand, late, and inconsistently. A redesigned collections process is worth walking step by step because the gap between what a company invoices and what it collects on time is mostly mechanical, and mechanical gaps close.

What the receivables ledger actually contains

The starting point is the aging report, the schedule that buckets open invoices by how long they have been outstanding: current, one to thirty days past due, thirty-one to sixty, sixty-one to ninety, and beyond. If you sit behind a credit-and-collections clerk, the daily work is to read that report, decide which accounts to chase, find a phone number or an email contact, look up the order so the conversation can be specific, and record what the customer said. Atradius, in its 2025 Payment Practices Barometer for North America, found that forty-three percent of credit-based B2B sales in the US were overdue, with bad debts affecting five percent of long-overdue invoices. That forty-three percent is the queue the clerk works against, and almost none of the time spent on it goes to the judgment the role exists to apply.

Where the days actually go

If you watch a full collections cycle, the time piles into three activities, none of which is negotiation. The first is prioritization done from memory or a spreadsheet, deciding which of several hundred open invoices to call today, usually the largest or the oldest rather than the riskiest. The second is contact assembly, finding the right person, attaching the invoice, and writing the message, repeated for each account. The third is dispute handling, where a customer says the price is wrong or the shipment was short, and the clerk has to leave the ledger, find the order and the delivery record, and reconcile the two before the conversation can continue. The Hackett Group, in its 2025 Working Capital Survey, reported that days sales outstanding degraded for a second straight year, which is consistent with a process that scales by adding people to a manual queue rather than by removing the manual steps.

The mechanism that adds the days

The link worth being precise about is the one between invoice accuracy and days outstanding. An invoice with an error, a wrong price, a missing purchase-order number, a quantity that does not match the delivery, does not get paid late at random. It gets disputed, and a disputed invoice stops aging on the customer's schedule until the dispute is resolved. The seller's clock keeps running while the buyer treats the balance as suspended. Every percentage point of invoice error converts into a measurable population of disputes, and every dispute converts into added days outstanding while it waits in someone's inbox for the order and delivery context to be assembled. This is why the redesign targets disputes specifically. The days they add are not a cost of doing business with slow payers, they are a cost of unresolved exceptions, and exceptions are the part of the process where a human is genuinely needed but is currently starved of the information to act quickly.

What the redesigned workflow does

The agent begins by capturing the receivables ledger and the aging directly from the accounting system, the same way it would read a trial balance during a month-end close. It ranks open accounts by a combination of amount and risk rather than by age alone, so a large balance from a customer who has started paying late surfaces ahead of a small one that is merely a few days out. It generates dunning contact at fixed intervals relative to the due date: a reminder before the date, a firmer notice at the first past-due bucket, an escalation at the next, with the invoice and the account history attached so each message is specific. When a customer raises a dispute, the agent does not attempt to settle it. It routes the dispute to a person with the order, the pricing, and the delivery record already assembled, the same reconciliation logic that sits behind a three-way match, so the clerk opens a complete file instead of starting a search. Where the accounting system has no usable interface for posting notes or status, the agent writes back through the same screens a person would use.

What stays with a person

The negotiation stays with a person, and so does the credit decision. When a customer asks for a payment plan, when a long-standing account needs its credit limit reconsidered, when the choice is between pressing for payment and keeping a relationship, a human makes the call and remains accountable for it. The Federal Reserve Banks' Small Business Credit Survey and the JPMorgan Chase Institute's cash-flow research both describe how thin the cash buffers are at smaller firms, which is the reason these judgments cannot be automated away. The cost of pressing the wrong customer too hard, or extending credit to one who will not pay, falls directly on a balance sheet with little room to absorb it. The agent's contribution is to ensure that when the person makes the call, every account in front of them is prioritized correctly, every routine reminder has already gone out on schedule, and every dispute arrives with its context attached. That is the shape of an aligned engagement, where the agent does the mechanical ninety-something percent and the human does the part that requires judgment, with better information than before.

A reasonable counter

A reasonable counter is that days sales outstanding is driven by customer behavior and macroeconomic conditions, not by the seller's process, and that no amount of workflow redesign moves a number set by how fast customers choose to pay. There is real truth in that. Some of the three-day rise Allianz Trade measured reflects tighter credit and slower buyers across the economy, and a better dunning cadence will not change a customer's decision to stretch a payable as a financing tactic. But the days the redesign reclaims are not those days. They are the days added by disputes that sat unresolved because no one had assembled the order and delivery context, and the days added by reminders that went out late or not at all because the queue was worked by hand. Those exist regardless of the macro picture, and they are the days a process can actually take back.

Common questions

Why do invoices get paid late, and what part of that can a process actually fix?
Days pile up less because customers refuse to pay and more because the work of getting paid is done by hand, late, and inconsistently. The largest mechanical source is disputes: an invoice with a wrong price, a missing purchase-order number, or a quantity that does not match the delivery gets disputed, and a disputed invoice stops aging on the buyer's schedule while the seller's clock keeps running. A redesigned process takes back the days added by unresolved disputes and by reminders that went out late or not at all, since those exist regardless of macroeconomic conditions. It does not change a customer's decision to stretch a payable as a financing tactic.
What does the collections agent automate, and what decisions stay with a person?
The agent captures the receivables ledger and aging from the accounting system, ranks open accounts by a combination of amount and risk rather than age alone, and sends dunning reminders at fixed intervals relative to the due date with the invoice and account history attached. When a customer raises a dispute, it does not settle it; it routes the dispute to a person with the order, pricing, and delivery record already assembled. Negotiation and the credit decision stay with a person, including payment plans, credit-limit reconsideration, and choosing between pressing for payment and keeping a relationship. The human makes those calls and remains accountable for them, with better information than before.
How does invoice accuracy connect to days sales outstanding?
Every percentage point of invoice error converts into a measurable population of disputes, and each dispute adds days outstanding while it waits in someone's inbox for the order and delivery context to be assembled. A disputed invoice is treated by the buyer as suspended, so it stops aging on their schedule even as the seller's clock keeps running. This is why the redesign targets disputes specifically rather than treating late payment as an unavoidable cost of slow payers. The days disputes add are a cost of unresolved exceptions, which is the part of the process where a human is genuinely needed but is currently starved of the information to act quickly.