From Zero to Collected

Designing a cash collection function for B2B tech companies, one relationship at a time

When a B2B finance team starts getting serious about cash collection, the first instinct is usually to fix the reminders. Send them earlier, send more of them, follow up harder when they go unanswered. The logic feels sound. If invoices are going unpaid, more pressure should help.

It usually does not, because the invoice is rarely where the problem started.

Walk back through a sample of your overdue accounts and a pattern shows up. Sales closed a deal on net-45 terms and the invoice went out on net-15, so the customer was technically late from day one without knowing it. An annual auto-renewal went out at last year’s rate because nobody updated the billing system after a mid-cycle downgrade. The reminder landed with someone who left the company three months ago. The customer cannot approve the invoice because the pricing has three components they cannot reconcile against what they remember signing.

None of these are collection problems. They are upstream failures that look like collection problems by the time they appear in the aging report. Sending more reminders does not fix them.

This is where most guides on cash collection go wrong. They start at the invoice and work forward. The real work starts earlier.

Why B2B is different

In a transactional business, a late payment is an isolated event. You collect it or you write it off, and the relationship is largely unaffected. In B2B tech, the customer you are chasing this month is the one someone else in your company is trying to renew in six. The relationship does not pause while the invoice is unresolved. It keeps running, and how finance handles the collection becomes part of how the customer experiences the company.

That changes what good collection looks like. Not faster chasing, but smarter positioning. An AR team that knows what CS has flagged on an account before reaching out. A reminder that goes to the person who actually handles vendor payments, not the main contact on the CRM record. A payment experience that lets the customer clear an invoice, raise a question, or set a payment date without starting an email chain.

These are not small refinements. Research across thousands of B2B tech finance teams shows the median company collects in 52 days. The top quartile gets there in 33. The difference between them is not payment terms. Both groups set broadly similar terms. The difference is process maturity, and 19 days of DSO is a meaningful number when multiplied across a year of invoices.

The collection gap

One number makes this concrete. Best Possible DSO is what your DSO would be if every customer paid exactly on their due date. The gap between that number and your actual DSO is pure collection friction, process inefficiency after payment terms are accounted for. For the median B2B tech company, that gap is 29 days. The best performers have brought it below 24. The bottom quartile runs at 35 days or more.

Those 29 days do not close by chasing harder. They close by understanding what is creating them.

The five most common causes, in the order they tend to appear in the invoice lifecycle, are payment terms set without finance in the room, a sales-to-finance handoff where deal details never make it into the billing system, an onboarding process that activates the customer but misses the financial setup, pricing complexity the customer’s AP team cannot approve without querying it, and invoicing errors that surface as disputes weeks after the contract was clean. Each has a fix. None of the fixes sit in the collection function itself.

Where does your AR stand right now

Before building anything, the book asks one question: can you actually trust what you are looking at?

Most teams cannot. Their billing tool, ERP, and payment processor each hold a different version of the same data, and the picture they are working from is already wrong before the first reminder goes out.

Five questions tell you where you stand.

Do you have a single place where every open invoice lives, updated in real time? If the answer is no, your data is fragmented, and every decision you make about which accounts to chase is built on an incomplete picture.

Can you pull your DSO, aging balance, and Collection Effectiveness Index without a manual exercise? If not, you are measuring the function after the fact rather than managing it in real time.

Do you know, for every overdue account, whether the invoice reached the right person? A surprising share of overdue invoices are simply unseen ones.

Does your billing system reflect the exact terms agreed in the last deal you closed? If sales and finance are working from different versions of the same contract, disputes are already in the pipeline.

When a payment lands, does it match automatically to the right invoice? If someone on your team is reconciling payments by hand, your cash application process is creating an AR picture you cannot trust.

If you answered no to more than two of these, the collection process is not your most urgent problem. The foundation it needs to run on is.

What the collection process actually looks like when it works

Once the upstream work is done, some invoices still go overdue. That is where the collection process takes over, and most teams build it wrong for the same reason they chase too hard: they treat every account the same.

A customer who has paid on time for two years and misses once is not the same account as one that has been drifting later every month for a quarter. Sending them the same automated sequence tells both of them that nobody was paying attention. The accounts that matter most, the ones with large balances, renewal conversations in motion, or payment behaviour that has started to shift, need a different approach from the long tail.

Segmentation is how you build that in from the start. Not a complex system. Two or three buckets based on value and payment behaviour is enough to begin. The long tail runs on automation. Strategic accounts get personal attention at the right moments. And the criteria that decide which is which get reviewed as accounts move, because an account that was low-risk last quarter is not necessarily low-risk today.

From there, the collection sequence has five stages: confirmation before the due date, a reminder just before it, resolution when something is blocking payment, escalation when it has gone past what finance can move on its own, and enforcement when nothing else has worked. Each stage has a different purpose, a different channel, and a different set of people involved. Getting the timing and the tone right at each one is what separates a collection function that collects from one that just sends reminders.

The book goes deeper from here: the exact timeline benchmarks drawn from research across thousands of B2B finance teams, how to read an account before reaching out, which channel to use at each stage, how to handle disputes before they age, where agents now carry the mechanical work so your team can focus on the accounts that need them, and the metrics that tell you whether the whole function is working.

Everything above covers the first two chapters of nine. The diagnostic above is one of eight frameworks in the book.

Get access to the full book below: