Leadership in AR, or the Lack-thereof
Why Accounts Receivable Deserves Real Leadership, Not Just Management
Nobody grows up wanting to run accounts receivable.
It isn't glamorous. It doesn't get written up. When it's going well, nobody in the executive suite thinks about it at all, and when it's going badly, the conversation is about the number, never about the department.
I've spent thirty years in this function. I started on a dialer at Nissan Motor Acceptance, calling people who were behind on their car payments. I got promoted into repossessions. I spent years at Bank of America working past-due credit cards. I've been a director with a team of twenty-four, and I've rebuilt an entire AR operation from the ground up after a company offshored it and had to reverse the decision.
In almost every one of those buildings, I walked into the same thing.
AR was an afterthought.
What an Afterthought Looks Like
It doesn't announce itself. Nobody circulates a memo saying this department doesn't matter. You find it in the details.
Cash application is three weeks behind, so collectors are calling customers about invoices that were already paid. Credit limits are set by whoever closed the deal. Nobody can tell you what's in the over-90 bucket without pulling a report and studying it for an hour. The team reports to whichever leader happened to have room on the org chart. And the people doing the work have had the same title for seven years and can tell you the exact date of their last increase.
That last one is the tell. Show me a department where nobody's been promoted in five years, and I'll show you a department nobody's leading.
Here's the part that still blows my mind: this is the function where the money actually arrives.
Sales books revenue. Operations delivers. Finance reports it. But every dollar the company earned is theoretical until somebody in AR converts it into cash in the account. That's not a support function. That's the last mile of the entire business, and it's routinely staffed with the fewest people, the oldest systems, and the least leadership attention of any team in the building.
Why It Happens
AR looks like a transaction function.
On the org chart, it's a box. In the budget, it's a cost center. In the monthly close, it's a metric. Everything about how a company represents AR to itself suggests a process that runs, rather than a team that performs.
So it gets managed instead of led. Somebody tracks the queue, approves the write-offs, escalates when a big account goes quiet, and calls that leadership.
It isn't. Managing the queue is maintenance. And a department on maintenance will hold steady right up until the moment it doesn't, which is usually the quarter you needed it most.
I lead people. I manage processes and procedures. Those are two different jobs, and only one of them can be delegated to a system.
What Leadership in AR Actually Looks Like
It starts with knowing what you have.
Not the summary number—the actual composition. Which accounts are aging because the customer is in trouble, which are aging because your own invoice was wrong, and which are aging because nobody has called. Those three problems look identical on a report and require completely different responses. A leader knows which is which. A manager knows the total.
It means owning the credit decision, or at minimum having a real seat at it. If sales sets terms and AR absorbs the consequences, you don't have a receivables problem. You have an accountability problem wearing a receivables costume.
It means putting your most capable people in front of your hardest conversations and giving them the title and the money that goes with it. When I rebuilt that offshored function, I built three teams—credit, cash posting and reconciliation, and collections—six people each. At another company, seven analysts became senior analysts, with real scope, first stop for their own teammates before anything reached my desk. That isn't generosity. A department where the only decision-maker is the director is a department that stops functioning the day the director is out.
And it means training the thing nobody trains: how to talk to a person who owes you money and doesn't want to hear from you. How to make an ask without apologizing for it. How to listen—actually listen, because listening is half of communicating, and it's the half everybody skips.
You can teach the system in a week. You can teach judgment over a career.
The Part the Metrics Don't Hold
I will defend every number on the scorecard. DSO, aging distribution, contact rate, promise-to-pay conversion, cash application accuracy, bad debt as a percentage of revenue. I've been measured on all of them, and I've hit them.
But the numbers describe outcomes. They don't produce them.
What produces them is a collector who has a working relationship with someone in that customer's AP department and who gets a call back when an invoice goes sideways. What produces them is an analyst who flags a deteriorating account in week two instead of month four because she isn't afraid of what happens when she brings you a problem. What produces them is a customer who has been treated decently for three years and therefore puts your invoice near the top of the stack when cash is tight.
None of that appears in a report. All of it is the reason the report says what it says.
If you cannot connect with people, you will fail on all fronts. Externally, because those customers are paying your payroll, your vendors, and your lights. Internally, because the analyst who won't come to you at four o'clock will hand you a surprise at month-end.
What I'd Ask of Executives
Look at your AR department the way you'd look at any team you took seriously.
When did someone last get promoted out of it? Who's next, and does that person know? Is there a career path, or is there a queue? If your best collector left tomorrow, how much would go with her—and how much of what she knows exists anywhere but in her head?
Then ask the harder question. Is that department underperforming, or has it simply never been led?
I've walked into a lot of buildings where the answer was the second one. Every single time, the talent was already there. Somebody just had to notice.
