The two people chasing the same customer
In most companies, two people have a relationship with the same customer and neither can see the other's. The account manager knows the delivery has been late twice and the client is quietly unhappy. The credit controller knows the invoice is forty days overdue.
Neither knows what the other knows. So the reminder goes out on schedule to a customer who is withholding payment for a reason, and the account manager finds out when the client mentions it, irritated, on a call about something else.
Why batching makes it worse
Collections is usually run as a monthly exercise. A list is exported, everyone on it gets broadly the same treatment, and the effort is spread evenly across customers who are not remotely equivalent.
The customer who has paid at sixty-five days for four years gets chased at thirty-five and is annoyed. The customer who has broken two promises gets the same polite email and ignores it, as they ignored the last one. Uniform effort applied to non-uniform situations produces the worst available outcome in both directions.
Chasing is a relationship activity
The framing that causes the damage is treating collections as an administrative function. It is not. Asking someone for money is one of the more delicate conversations a business has, and it is routinely handed to whoever has the least context about that customer.
The cases that go badly are almost never about the money. They are about being chased for something already paid, or being escalated to while a legitimate complaint sits unanswered, or receiving a formal letter from a company whose account manager rang the day before as though nothing were wrong.
What working from one record changes
Three things change when both people read the same customer. Disputes are visible before an escalation goes out, so a delivery problem is handled as a delivery problem. Payment history is visible, so effort goes to the customers where it will change something. And the account manager knows a chase is happening before the client tells them.
None of that is sophisticated. It is the difference between two teams sharing a record and two teams maintaining their own, which is the same difference that shows up everywhere else in a business and is nowhere more expensive than here.
If you want the practical version — reminder schedules, tolerances, when a person should call — it is in the guide. This post is only making the case that collections is not an administrative function and should not be organised as one.