Name the person who pays your biggest invoice
Collections is said to begin when an invoice goes overdue. It begins earlier, on a vendor-setup form filled in long before anyone chases anything. Five blanks to look for, and a ten-minute test for your top 50 accounts.
Picture an invoice that does everything right. The amount matches the contract. The purchase order number is on it. It leaves your system on the day the goods arrive, and the delivery report says sent.
Then nothing happens. The due date passes. A reminder goes out, then another, each one a little firmer than the last. Weeks later someone on your side picks up the phone and learns that the invoice was never seen by a human being at all. It went to a shared inbox that nobody has opened since a reorganisation. The address was copied, faithfully, from a form.
(This is an illustrative scene, not a real client. Every collections team has lived some version of it.)
Nothing in that story was a collections failure. The reminders were well worded and well timed. The failure was older. It happened on the day the customer was set up, when a field was left empty, or filled with whatever was at hand.
The first collections call is made on day one
We tend to say that collections begins when an invoice goes past due. It is a tidy definition and it puts the start of the work at the moment the money is already late.
A better place to start is the vendor-setup form: the page, or the series of pages, that records how a new customer will receive invoices and pay them. Who receives the invoice. Where it is delivered. Whether it needs a purchase order. Whether it must be loaded to a supplier portal. How the money will arrive, and how you will be told what it is for.
Each answer is a small prediction about how your invoices will travel through someone else’s company. A correct answer clears the road for every invoice that follows. A blank, or a guess, quietly lays down an obstacle that will be found one invoice at a time, usually by a collector, usually after the due date.
That is why the form deserves the same attention as the first conversation with a customer who has promised to pay. It is that conversation, held in advance, in writing, with nobody on the other side.
Five blanks to look for
Five fields do most of the work. Each can be checked in minutes, and each fails in its own way.
1. No named person in accounts payable
The record says Accounts Payable, or a team name, or a department mailbox. It does not say who.
A team cannot be called. When an invoice stalls, a collector needs a person who can open the customer’s system, find the document and say what is wrong with it. A team name leads to a queue, and a queue leads to a ticket, and the ticket restarts the clock.
A named contact also needs a second name. People move, take leave and change roles. One name is a single point of failure. Two is a process.
2. An invoice inbox that nobody owns
Many customers publish a generic address for supplier invoices. Many of those addresses are watched carefully, by teams who scan, route and log everything that arrives. Some are not.
The trouble is that your system cannot tell the difference. A message delivered to a dead mailbox looks identical, in your logs, to a message delivered to a busy one. Sent is not received, and received is not read.
The useful question is not “what is the address?” but “who watches it, and how would we know if they stopped?”
3. A purchase-order rule nobody wrote down
Some customers will not pay an invoice that does not carry a valid purchase order number. Others will, if the invoice quotes a contract. Others accept either but route the ones without a number to a slower path.
The rule exists somewhere on the customer’s side, usually as a control that their auditors care about. When it is not captured at setup, it is discovered the hard way: an invoice is rejected at intake, and the rejection notice, if there is one, goes to the same inbox from the second blank.
4. A portal registration that was never completed
Large buyers often require suppliers to submit invoices through a portal. Registration is a project in its own right, with tax forms, bank details, approvals and a verification step. It is also easy to leave half-finished, because nothing breaks on the day you stop: the invoices simply go out by email, as they always have.
From then on, an invoice that has not entered the customer’s system does not exist for the purposes of payment. It cannot be approved, matched or scheduled. Your ledger says it is open. Their ledger has never heard of it.
5. No agreed way to say what a payment is for
The last blank is on the other side of the ledger. When the money arrives, how will you learn which invoices it settles?
A payment that comes with a remittance advice in a known format can be applied in seconds. A payment that arrives as a single amount, with no explanation, becomes a puzzle for someone in cash application. Until it is solved, the customer’s balance looks unpaid, and the next reminder is chasing money you already hold.
Why nobody sees it
Here is the uncomfortable part. These five blanks are known on day one, and they are invisible by day sixty.
The reason is where they show up. The cause sits in onboarding, in a form that belongs to sales operations or customer master data. The symptom lands in collections, as a late payment. By the time the symptom appears, the form is two systems and one team reshuffle away, and the collector has only the customer to look at.
So the customer is labelled slow. The label is plausible, it is easy to apply, and it is hard to disprove. A reminder cadence does exactly what it is built to do: it increases pressure on the account. The pressure falls on a customer who may have done nothing wrong, and does nothing for an invoice that was never in front of anyone.
This is how a missing field turns into a story about a person.
What we do not know
It is tempting to attach a number here: that a certain share of late payments trace back to onboarding data. We are not aware of a public benchmark that supports a figure, and we are not going to invent one.
That is the point of the test below. The share that applies to your business is a fact in your own records, and finding it takes less time than reading this article.
A ten-minute test
Take your top 50 customer accounts, by open balance or by revenue, whichever your team already uses. For each one, answer five questions with yes or no. A yes needs evidence: a name in the system, a confirmed address, a note from a real conversation. “I think so” is a no.
| Question | Yes means |
|---|---|
| Named AP contact | A person, not a team, and a backup |
| Monitored invoice address | Someone confirmed that it is read, and by whom |
| PO rule known | Required, optional or not used, and written down |
| Portal status known | Not required, or registered and verified |
| Remittance channel known | A format that cash application can read |
Count the blanks. There are 250 cells, so the maximum is 250, but the number matters less than its shape.
Read it three ways. Count blanks by column to see which field your process fails most often. Count by row to find the accounts with the most exposure, and start there. And compare the blanks with your own list of accounts that pay late. If the two lists overlap, you have found a cause. If they do not, you have ruled out one, which is also worth knowing.
The fix sits upstream
The cure is dull, which is a good sign.
Make the five fields mandatory before the first invoice. Not “recommended”. A customer record without them is not ready to be billed.
Give the setup an owner on the collections side. Credit or collections should see the record before it goes live, because they are the people who will pay for what it is missing. A short sign-off turns a data-entry task into a controlled handover.
Verify with a real touch. A name typed into a field is a claim. A welcome call, a test invoice or a confirmation email that gets an answer is evidence.
Re-check on a schedule, and on events. Once a year is a start. Better is to trigger a review when something changes: a customer moves to a new ERP, merges with another company, outsources its payables or gets a new controller. Those are the moments when a correct record becomes a wrong one without anybody telling you.
Treat a blank like an open invoice. It is a liability with a long fuse. It will become a late payment on a date nobody can predict, and it will be handled by someone who did not create it.
Back to the invoice
The perfect invoice at the start of this article never had a chance. It was correct, on time and sent to the right address, according to the record. The record was the problem.
So here is the question to take back to your desk. For your biggest customer, can you name the person who pays your invoice? Can you name the second one? Can you say who reads the inbox, and how you would know if they stopped?
If you can, the work has started. If you cannot, that is where collections should begin, and the invoice is not due yet.
