Most companies think they know their customers.
Sales knows what they buy. Operations knows what they need. Credit knows whether they were approved. Accounts Receivable knows whether they pay.
And somewhere inside the ERP, CRM, A/R platform, credit bureau, spreadsheets, email inboxes, and the institutional knowledge of the people managing those accounts is an enormous amount of information about how those customers actually behave.
The problem is that we rarely put all of it together.
Accounts Receivable departments have traditionally used their data for a relatively narrow purpose: getting paid. We look at aging reports, past due balances, DSO, collection notes, promises to pay, disputes, credit holds, and payment history because those things help us determine who needs attention today. There's nothing wrong with that, but I think we're leaving a tremendous amount of information on the table.
A/R isn't simply a record of who owes you money. It's a record of how your customers behave. Once you start looking at it that way, Accounts Receivable becomes much more than a collection function.
It becomes a source of Revenue Intelligence.
We Collect More Than Money
Think about what happens after a customer is approved and begins doing business with you.
They start creating data.
They buy certain products and services. They purchase at a certain frequency. They use particular locations or branches. Their volume increases, decreases, or remains relatively stable. They pay by check, ACH, credit card, or portal. They pay early, on time, ten days late, or thirty days late.
They request extended terms.
They dispute invoices.
They return products.
They ask for credits.
They hit their credit limit.
They go on hold.
They make promises to pay and either keep them or don't.
Their payment behavior improves or deteriorates.
Their purchasing behavior changes.
Individually, each of these things might look like an ordinary transaction. Collectively, they begin telling a story about the customer. Yet most organizations split that story into pieces. Sales, Credit, Accounts Receivable, Operations, Finance, and that is just a small portion.
The ERP has some of it. The CRM has some of it. The A/R platform has some of it. And, inevitably, Susan has a surprisingly important portion of it sitting in her inbox. Then we wonder why nobody seems to have a complete picture of the customer.
The Aging Report Is Only the Beginning
Aging reports are useful. DSO is useful. Past due percentages are useful, but those are outcomes. They tell us what happened after thousands of individual customer behaviors, operational decisions, invoices, payments, disputes, credit decisions, and purchasing decisions occurred.
What if we started looking underneath those outcomes? Consider two customers that both have a $100,000 balance and $20,000 past due. From a traditional aging report, they might look similar.
What if Customer A has grown revenue by 25%, produces strong margins, uses several of your product categories, consistently pays seven days beyond terms, rarely disputes an invoice, and has done business with you for eight years?
Meanwhile, Customer B's purchasing has declined for six months, margins are weak, payment behavior has moved from five days late to twenty-five days late, disputes are increasing, and they recently requested longer terms.
Those aren't the same customers. The aging report simply isn't designed to tell you that, and that's okay. The problem isn't that the aging report is bad.
The problem is when we expect one financial metric to tell us the entire customer story.
Payment Behavior Is Customer Behavior
I've always found payment behavior particularly interesting because companies often treat it as something that matters only to Credit and Collections. It doesn't.
How a customer pays is part of how that customer behaves. A customer that historically paid five days beyond terms and gradually moves to ten, then fifteen, then twenty-five days beyond terms is telling you something.
Are they experiencing cash-flow pressure? Are your invoices are becoming harder for them to process? Is there an unresolved operational issue? Has their purchasing increased faster than their ability to pay? Maybe their own customers are slowing down, or maybe nothing serious is happening at all.
That's where human judgment still matters. The point isn't that one late payment predicts disaster.
The point is that changes in behavior create information. The same is true in the opposite direction.
A customer whose revenue is growing, payment behavior is improving, disputes are declining, and product usage is expanding may be telling you something too.
Credit traditionally asks: How much risk should we take with this customer?
Revenue Intelligence allows us to ask: What else can this customer's behavior tell us?
Disputes Are Data
The same principle applies to disputes. A dispute is obviously important because it prevents an invoice from becoming cash, but disputes also contain information.
If one customer disputes a freight charge, you probably have an invoice problem. If fifty customers dispute freight charges, you might have a process problem.
If one branch generates twice the dispute rate of every other branch, that tells you something. If a certain product category consistently produces credits and rebills, that tells you something. If your largest customers are also your most administratively expensive customers because every invoice requires manual intervention, that tells you something.
We often treat disputes as individual fires. Fix the invoice, issue the credit, and send the backup. Get the approval, collect the money, and move on.
But recurring problems aren't simply work. They're also data. That data becomes much more valuable when we stop looking at transactions individually and start looking for patterns.
Revenue Alone Doesn't Tell You Who Your Best Customers Are
This becomes even more interesting when we combine A/R information with commercial data. Most organizations can quickly tell you who their largest customers are. That's easy.
Sort revenue from largest to smallest, but does largest automatically mean best?
What if your largest customer has low margins, consistently pays late, generates frequent disputes, requires significant administrative effort, and buys from only one product category?
Meanwhile, another customer generates slightly less revenue but produces stronger margins, pays reliably, buys across multiple categories, uses several locations, has grown steadily for three years, and rarely creates operational problems.
Which customer is more valuable?
That's a much harder question, and revenue alone can't answer it.
Neither can Accounts Receivable. Neither can Sales. Neither can Credit. No one can answer this question alone.
However, when we start combining information from those functions, we begin developing a much more complete understanding of customer value. That's where Revenue Intelligence starts getting interesting.
Your A/R Team May Know Things Your CRM Doesn't
Companies have spent enormous amounts of money building CRM systems to understand customer relationships. That is the right decision, but it only provides incomplete data. Some of the most useful customer intelligence in the company may never make it into the CRM.
Your collector may know that a customer recently changed Accounts Payable personnel and payments have slowed ever since. Credit may know that external risk indicators have started deteriorating. Cash Application may know that the customer suddenly changed how it remits payments. Operations may know that the customer is opening another location. Sales may know that a competitor is aggressively pursuing the account.
None of those pieces necessarily mean much by themselves. But together...they might.
This is one reason I think Revenue Operations has to eventually extend beyond the traditional Sales, Marketing, and Customer Success definition.
The customer doesn't stop producing useful information when the deal becomes Closed-Won. In many ways, that's when the most useful information starts being created. Before someone becomes a customer, we're largely working with what they tell us and what external data tells us. After they become a customer, we get to observe what they actually do.
That's an incredibly valuable distinction!
The Goal Isn't More Dashboards
Whenever we start talking about data, the natural response is to build another dashboard. I like dashboards. I also think we have plenty of dashboards nobody looks at.
Revenue Intelligence isn't about taking every field in your ERP and putting it into a prettier visualization. It's about identifying information that helps the organization make better decisions.
Which customers deserve more attention?
Which customers may be deteriorating?
Which customers have room to grow?
Which relationships are more profitable than they initially appear?
Where are operational problems creating unnecessary friction?
Which customers look similar to our best relationships?
Which former customers might be worth pursuing again?
Which metrics actually help us predict what happens next rather than simply explaining what happened last month?
Those are business questions. The technology should help us answer them.
Accounts Receivable Is Sitting on a Gold Mine
For years, companies have viewed Accounts Receivable primarily through the lens of working capital.
How much is outstanding? How much is past due? What's DSO? How much cash did we collect?
Those questions matter, and they will always matter. A/R sits at one of the most interesting points in the entire customer lifecycle. Sales knows what the customer said they would do. Accounts Receivable eventually learns what they actually did.
Did they pay according to the agreement? Did they dispute frequently? Did they grow or shrink? Did they require constant exceptions? Did they become easier or harder to work with? Did their behavior change?
Those answers tell us if the relationship become more or less valuable over time. That history is incredibly difficult to recreate from outside the organization.
And...you already own it.
But..in many companies, we're using only a fraction of it.
This Is Where Revenue Intelligence Begins
Revenue Intelligence doesn't have to start with artificial intelligence, predictive models, or some enormous technology implementation.
It can start with a much simpler question: What do we already know about our customers that we aren't using?
Start connecting payment behavior with revenue.
Connect revenue with margin, disputes with customer segments, and credit risk with purchasing behavior. Connect purchasing behavior with product penetration, customer tenure with profitability, and connect branches, locations, jobsites, product categories, payment patterns, disputes, and growth.
Then start looking for patterns.
You might discover that your largest customers aren't necessarily your best customers.
You might discover that certain customer characteristics consistently correlate with stronger relationships.
You might discover that customers begin behaving differently months before they become serious collection problems.
You might discover that some inactive customers look remarkably similar to your best active customers.
You might discover that existing customers have significant revenue opportunities hiding inside relationships you already have.
Eventually, you may be able to use what you've learned from your existing customers to identify which prospects deserve your attention next. That's where the possibilities become much bigger than any single department or piece of information, and you may find one of the best places to start is by looking at your accounts receivable data.
Final Thoughts
For decades, Accounts Receivable has been asked to answer a fairly simple question:
When are we getting paid?
It's still an important question. I just don't think it's the only question our data can answer. Every invoice, payment, dispute, credit decision, collection conversation, purchasing pattern, and customer interaction adds another piece to the story. The opportunity is to stop treating those pieces as isolated transactions and start understanding what they're telling us about the customer.
Buried inside your A/R data isn't just information about outstanding invoices.
There's information about risk, customer behavior, operational problems, growth.
There may even be information about where your company should look for its next dollar of revenue.
Your A/R data knows more about your customers than you think. Maybe it's time we started asking it better questions.
Because at the end of the day...
Revenue is created in Sales.
Revenue is protected through Credit Operations.
Revenue becomes cash through Accounts Receivable.
Revenue Intelligence identifies growth opportunities.
Revenue Operations ensures none of those steps fail.
