Call it introspective or prudent but one of the first areas I research in an acquisition is Finance. We were evaluating the acquisition of another collection agency, considering deeply the combined synergies, overlapping client businesses and prospective ROI.

And here I was, like many finance executives, my first instinct was to understand the leadership team. Who was the CFO? Who owned finance? Who owned accounting? Who would ultimately own the integration?

Those seemed like reasonable questions.

Instead, I found myself asking a very different one. What exactly are we integrating?

At first glance the answer seems obvious.

• Consumer accounts.
• Collectors.
• Clients.
• Technology.
• Processes.

But that answer quickly began to unravel. Every collection agency has developed its own operational vocabulary. What exactly is a payment? Gross versus Net? Commission rules and protocols? Client contract specifications? Remittance methodologies? Settlement rules? Payment processing interfaces and terms?  

Common themes each with their own accounting interpretations, interface architectures, and internal controls.

Or, in some cases, the absence of them.

In integration planning, what initially appeared to be a technology conversion increasingly looked like something else.

An attempt to preserve the economic meaning of millions of transactions while moving them into an entirely different operational and accounting environment.

That realization changed how I thought about the entire industry.

I wandered into the collections industry several years ago.

Like many who arrive from outside, I brought my own assumptions.

Joining as a CFO, I expected my focus would revolve around the traditional responsibilities of the role: capital allocation, funding, acquisitions, technology investment, financial strategy, and helping determine where the next dollar of investment would create the greatest long-term return.

Those conversations certainly existed. But they weren’t what captured my attention.

The deeper I immersed myself in the business, the more I found myself drawn toward something far more fundamental. Not strategy.

Foundations and internal controls.

At first, I assumed this was simply my own bias. I have spent most of my career looking at businesses through the lens of accounting, financial reporting, and the often invisible systems that quietly determine whether organizations can be trusted. Perhaps I was simply seeing the world through a controller’s eyes rather than an operator’s.

But the question stayed with me. Why?

Why did this industry evolve the way it did? What shaped its priorities? Why are some investments embraced almost universally while others seem to receive comparatively little attention?

And perhaps most importantly…

Has the nature of risk changed faster than the industry’s conception of internal control?

To answer that question, I found myself looking backward before looking forward.

An Industry Built by Operators

The collections industry did not emerge from accounting firms or investment banks. It grew from entrepreneurial agencies.

• Collectors on telephones.
• Relationships with creditors.
• Letters.
• Payment arrangements.
• Recovery rates.
• Client service.

That made perfect sense. In the early days, the business wasn’t capital intensive. Success depended on finding consumers, persuading them to pay, maintaining client relationships, and moving cash. Accounting largely reflected those operational activities after the fact. There was little reason to think of the collection platform as part of the financial reporting system.

The mission was clear: collect more money for clients. Everything else supported that mission. Accounting largely followed operations. Technology existed to help collectors reach consumers. Management measured liquidation rates, collector productivity, placements, commissions, and client retention.

As regulation expanded, compliance naturally became another major investment. More recently, cybersecurity, privacy, consumer protection, and artificial intelligence have become central strategic priorities.

Viewed through that history, the industry’s evolution makes perfect sense. Its priorities reflected the business it was built to perform.

Operations versus Accounting

Throughout my career I have often heard the phrase: “Accounting records what operations does.”

In collections, I no longer believe that is an adequate description. Operations and accounting are not sequential. They are simultaneous.  Every operational decision has accounting consequences. Every accounting rule changes operational behavior.

A settlement isn’t simply an operational event. It determines:

• revenue
• remaining balance
• client remittance
• future collections

The settlement rule is both an operational workflow and a revenue-recognition policy. A payment allocation is both a consumer-service event and a financial-reporting event. A client contract is simultaneously a commercial agreement and an accounting policy manual. The collection platform is not merely executing operational processes. It is executing financial logic.

The distinction matters because organizations naturally optimize what they can see. Consumer interactions are visible. Financial architecture is largely invisible—until it fails.

Looking for CFOs…Finding Something Else

As I became more involved in acquisitions and competitive research, I found myself looking at leadership teams. Who were the CFOs? Who were the controllers? Who owned financial architecture?

The answers varied, and many companies are private enough that public information is incomplete. But over time I realized I had been asking the wrong question.

Whether an organization has a CFO is almost beside the point. What I was really looking for was something much older.

Controllership.

Not bookkeeping. Not month-end close. Not producing financial statements after the fact.

Rather, the discipline of designing operational systems so that every economic event is captured completely, interpreted correctly, processed consistently, and ultimately reflected faithfully in the financial statements.

That distinction became increasingly important as I learned how collections actually works.

Consignment: The Inventory That Never Appears on the Balance Sheet

Manufacturers receive inventory. Retailers receive inventory. Debt buyers purchase receivables.

Third-party collection agencies receive something entirely different. Information. Millions of consumer obligations entrusted to the agency for collection.

The agency generally owns none of them. They remain the client’s asset. Yet embedded within every placement file are accounting decisions waiting to happen.

• Principal balances.
• Interest balances.
• Fee balances.
• Settlement authorities.
• Commission structures.
• Client-specific contractual terms.
• Legal restrictions.
• Ownership rules.
• Revenue-sharing arrangements.

Accounting has already begun, even though no journal entry has yet been recorded. In onboarding the financial architecture has already been defined.

One Payment. Many Economic Events.

The paradox, onboarding defines the accounting architecture, but there are no accounting entries for the consigned inventory.  Nothing to record until that first dollar is collected. No cash. No balance sheet. No revenue. No entries.

Then, operationally, a consumer makes a payment. The process appears simple.  The consumer pays $100. The agency collected $100.

But economically, that single payment creates multiple simultaneous events.

• Consumer clicks Submit.
• Virtual agent accepts.
• Processor authorizes.
• Bank settles.
• CRM posts.
• Trust account updated.
• Client payable updated.
• Revenue recognized.
• Invoice generated.
• Remittance prepared.
• Financial statements updated.

Cash has been received. Some or all of that cash belongs to the client. So a liability to the client now exists. Revenue is earned but not yet billed. The consumer balance changes. Future remittances change. Financial statements change – the balance sheet, income statement and cash flow.

Those events are not independent. They are different views of the same transaction.

The Contract Is the Accounting Engine

This was perhaps the biggest surprise. Revenue recognition is not simply “25% of collections.” Every client contract defines different economics. One client calculates commissions only on principal. Another includes principal and interest. Another excludes legal costs. Another awards commissions on direct payments received by the client – but only within a window after the date of placement. Another excludes them entirely.

Some require gross remittances followed by separate invoices for agency fees. Others permit net remittances. But what is the definition of “Net”? Even “net remittance” is not a universal concept. Does net mean after commissions on collected funds? After commissions on both collected funds and direct payments? After NSF adjustments? Before chargebacks?

Each answer creates different accounting entries. Different client liabilities. Different invoices. Different remittance calculations. Different cash movements. Different reconciliation requirements.

The CRM is not simply tracking collections. It is executing accounting policy. Thousands of times each day.

Timing Matters Just as Much

Revenue recognition has always depended on timing. It has never been about cash.

Manufacturing has long debated when a sale occurs. FOB shipping point. FOB destination. Delivery. Transfer of control.

Collections faces its own version of those same questions.

When exactly was payment accepted? When did the payment processor authorize it? When did settlement occur? When was the payment posted to the CRM? When was revenue earned under the client contract? When did an ACH return NSF? Should expected returns be estimated through a reserve? Or recognized only when they occur?

These are not technology questions. They are accounting policy questions implemented through technology. Just as manufacturing spent decades refining when a sale occurs, collections is increasingly being forced to define precisely when a payment becomes an accounting event.

Internal Controls Begin Long Before the General Ledger

Traditional accounting often emphasizes reconciliations. The prototypical historical perspective of accounting past transactions.

• Bank reconciliations.
• General ledger reconciliations.
• Trial balances.
• Month-end close.

Those remain essential. But they are downstream controls. Detective controls.

The more I studied the transaction flow, the more I realized that internal control begins much earlier.  Every payment moves through multiple systems.

• Consumer portal.
• Virtual agent.
• Payment gateway.
• Bank.
• Treasury.
• Collection platform.
• Client ledger.
• General ledger.
• Invoice engine.
• Client remittance.
• Financial statements.

Every transition passes through an interface.  Every interface is an input/output relationship. Every transaction accepted by one system must be received by the next. Completely. Accurately. Once. Only once.

Every interface is more than a technical integration. It is the transfer of economic meaning.

A payment accepted by a consumer portal must become the identical payment processed by the payment gateway. That payment must become the identical payment recorded by the CRM. That payment must become the identical payment reflected in the client ledger. That payment must become the identical payment recognized within the general ledger. Finally, it must become the identical payment reflected within the client’s remittance.

Every interface preserves more than data. It preserves trust.

A dropped transaction should not simply be unlikely. It should be categorically impossible without detection.

That is not merely reconciliation. That is architectural design.

Internal control has not changed. The principles remain exactly what they have always been. Transactions should be authorized. Complete. Accurate. Properly valued. Recorded in the correct accounting period. Faithfully represented in the financial statements.

What has changed is where those controls now live.

Increasingly, they are embedded not in accounting departments, but in software configuration, contractual interpretation, system interfaces, AI decision logic, and transaction-processing design.

Ask yourself where the pricing rules sit in your CRM and who controls those settings. The design permeates control over revenue recognition and Internal Control over Financial Reporting.

Automation Changes the Mathematics of Risk

Historically, one collector’s mistake affected one consumer. Today, one incorrectly configured business rule may affect hundreds of thousands.

Automation does not create bad logic. It amplifies it.

Artificial intelligence accelerates this even further. A virtual agent operating from an incorrect contractual rule can execute that error flawlessly and at enormous scale.

Technology did not create the error. It multiplied its consequences. The legal implications change as well. Individual mistakes become systematic process failures. Systematic failures attract systematic scrutiny. An individual lawsuit or fine morphs quickly into a material Class Action, a threat to even the longest held trusting relationship with clients.

SOC 2 Is Not SOC 1

The industry has appropriately invested heavily in cybersecurity, consumer privacy, and information security. Those investments are essential. We proudly advertise PCI and SOC2 compliance. Necessary, but is it sufficient?

SOC 2 examinations provide confidence that systems are secure, available, confidential, and well governed. But protecting information is fundamentally different from protecting financial integrity.

SOC 1 addresses whether transaction processing and related controls can be relied upon for financial reporting.

A perfectly secure system can still calculate client commissions incorrectly. An encrypted database can still produce inaccurate remittances. Outstanding cybersecurity does not guarantee accurate accounting.

Both forms of assurance matter. They simply answer different questions.

What Is Internal Control Over Financial Reporting?

Traditionally, ICFR is often viewed as an accounting exercise performed after transactions occur. I increasingly think it begins much earlier. ICFR begins where economic events are first defined. It determines whether those events are interpreted consistently, transmitted completely, processed accurately, and ultimately represented faithfully within the financial statements.

Where do we go from here…

I entered the collections industry expecting to think like a CFO about capital allocation, acquisitions, and financial strategy. Instead, I found myself rediscovering something much older. Not accounting. Not finance. Engineering. Engineering the integrity of a transaction. Not because strategic finance became less important. Quite the opposite.

The industry has spent decades engineering the consumer experience. Finding consumers. Reaching consumers. Protecting consumers. Artificial intelligence promises to transform those interactions yet again.

Perhaps the next evolution lies somewhere less visible. Engineering the financial transaction with the same rigor we now engineer the consumer interaction. Because every payment tells only one story.

The challenge is preserving that story—contractually, operationally, technologically, and financially—as it moves through every system, every interface, every accounting entry, and every decision along the way.