Accounts receivable collections explained by Intelligent Contacts

An invoice went out correct. The balance sat still. A week later it was still sitting there, and the team that owns cash has to turn it back into money without creating a complaint, a dispute, or a record nobody can defend. This guide from Intelligent Contacts explains how that work gets done.

That is the daily work of accounts receivable collections. It is written from an operator's view, for people who already run high-volume recovery under real rules. The reader in mind works in healthcare revenue cycle, financial services, insurance, utilities, or government, in the United States or Canada. The Telephone Consumer Protection Act (TCPA), Fair Debt Collection Practices Act (FDCPA), Regulation F, Fair Credit Reporting Act (FCRA), Health Insurance Portability and Accountability Act (HIPAA), and Payment Card Industry Data Security Standard (PCI DSS) sit on every attempt.

Most costly failures don't come from a weak script. They come from a wrong balance, a stale number, or a contact that nobody logged.

What accounts receivable collections covers and why it matters

When a utility invoice is correct and undisputed but the balance stops moving, billing has done its job. Accounts receivable collections is the follow-through: turning unpaid invoices and balances into cash, from the first reminder through payment, settlement, or write-off.

Billing sends the invoice to the address on file. Collections follows up using the account's balance, contact details, and record of prior activity. If the address or phone number is wrong, or an attempt is not logged, outreach can fail and the team may have no record to support what happened.

A 2013 presentation by the Federal Reserve Bank of Philadelphia, given at a Federal Trade Commission (FTC) and Consumer Financial Protection Bureau (CFPB) roundtable, estimated that, around 2010, the U.S. third-party debt-collection industry had about 4,200 firms and approximately 143,000 people, with more than 1 billion consumer contacts a year. It put the median recovery rate at 13% of face value in 2011, citing ACA International benchmarking data.

At that recovery level, a creditor should plan for most delinquent balances not to return. Each extra point is cash the creditor keeps. The presentation also reported roughly $54 billion in gross collections and $11.7 billion in industry revenue. Most recovered money goes back to the creditor, while collectors keep fees or commissions rather than the full face amount.

What moves that rate

Four operating factors influence whether recovery improves.

• Debt age: A balance in the first month is generally easier to resolve than one that has been delinquent for months.

• Debtor contactability: A working phone number gives the team a route to reach the account holder; repeated attempts to a dead number do not.

• Account data quality: Ownership, balance, and dispute status must match the system of record before outreach begins.

• Payment capacity: A firmer script cannot make an unaffordable payment affordable.

Dialing, messaging, payments, and records need to work as one system. When the account data is wrong or contact activity is missing, a well-run script cannot fix the underlying problem.

Healthcare, financial services, insurance, utilities, and government teams all depend on accurate records across the collection process. A reminder that misses a dispute flag can trigger inappropriate follow-up. A payment that fails to post back to the account leaves the balance and its history out of sync, creating more work and a risk of complaints.

Collection stages by account age and the right channel for each

Accounts do not sit in one pile. They move from current to late, and the right action changes at each boundary. Treat the path below as the default for a U.S. or Canadian portfolio, then adjust it to the creditor's written instructions.

Inaccurate balances, missing phone numbers, and dispute flags that never reach the dialer cost more than a weak script. The channel only works when data, dialing, messaging, payments, and the account record agree.

Early buckets

Current to 30 days past due. Many of these balances come from a failed card, a forgotten draft, or a bill that landed in the wrong inbox. Automated SMS, email, and IVR are enough when the contact on file is still good. Confirm consent, and log every contact so frequency is not guessed later. A live call here spends a skilled agent on a problem a payment link would have cleared.

31 to 60 days past due. The account has now missed a cycle. Outbound contact plus a payment-plan offer is the right move, from a predictive dialer or a live agent, after you confirm the number still belongs to the right person. Before each attempt, check the call count on that specific debt. A second debt on the same person is a separate counter. I would not add attempts until the last contact from the early bucket is written back to the account.

61 to 90 days past due. Look for a dispute before anyone offers a plan. If a dispute is open, suppress SMS, email, dialer attempts, and agent calls until the balance is confirmed. If the dispute is closed, a live agent with a secure payment link is the channel. Do not send the account back to a blast reminder. A dispute marked closed in one system and still open in another will freeze an account that can pay.

Later buckets and inbound

91 to 180 days past due. Run a documented hardship review, then a written final demand where the workflow requires one. The reviewer should see income signals, prior promises, and every earlier attempt. A final demand with no file behind it is just a louder letter. If earlier contacts were never stored, you cannot tell what was already offered.

Beyond 180 days. Placement, settlement, or write-off is a creditor decision, not an agent improvisation. Keep the records. A buyer, an auditor, or a regulator will ask what was offered and what was refused.

Inbound follows the same map. A person who calls about a balance should reach a balance lookup and a payment option before a queue. Parking that caller behind a general greeting throws away a right-party contact you did not have to find. If the lookup shows a stale address or no mobile on file, fix the record before the next outbound pass.

A utility balance 35 days old, with consent on file and no dispute, goes to a text reminder and a payment link. A 75-day medical balance with a prior dispute does not get a call until someone reviews the balance. Same team, different path, because the age and the flag changed.

An omnichannel collection approach only works if each bucket has an owner and the account data is current enough to route. Accounts should move forward. A bucket that stops moving points to a broken handoff, and that is fixable. Fix the handoff, and the missing contact fields, before you add attempts.

Compliance rules that shape every call, text and record

Compliance isn't a checklist someone applies after the calls are done. It's the set of counters, flags, and records the workflow has to write as it runs. If the record doesn't exist, the attempt didn't happen in a way you can defend.

Call frequency under Regulation F

Under Regulation F, a debt collector is presumed compliant with the FDCPA's ban on repeated or continuous calls when it doesn't call a person more than seven times within seven consecutive calendar days about a particular debt, and doesn't call within seven consecutive days after speaking with that person about the debt. The CFPB's debt collection rule FAQs are clear that crossing either line creates a presumption of a violation, with specified exceptions.

Counters belong on the individual debt. A phone-number total, or a portfolio total, will hide a violation on one account while another account still has room. Directly consented calls are an exception when the person gives that consent to the collector and the calls fall within seven consecutive days after the consent is received. Store who consented, on which debt, and on what date. A note that says "ok to call" isn't enough.

Texts, cells, and health information

The Federal Communications Commission (FCC) unwanted-communications guidance states that the TCPA generally prohibits non-emergency autodialed and prerecorded calls to cellular phones unless the called party has given prior express consent. If that prerecorded or autodialed call contains an advertisement, the consent must be in writing. Advertising calls to a number on the National Do-Not-Call Registry, including manually dialed live calls, are prohibited unless an established business relationship exists or the called party gave prior express written consent. Consent provenance, message type, mobile status, and suppression belong in the dialer, not in a side spreadsheet.

Healthcare adds a disclosure limit. HIPAA's minimum necessary standard, as the U.S. Department of Health and Human Services (HHS) describes it, requires covered entities to limit protected health information to what the task needs. Standardized transactions can still carry the elements those standards require. A collector confirming a balance doesn't need the diagnosis. A HIPAA-ready workflow hides that field by role, instead of trusting every agent to remember.

An auditor asks for four things first: consent provenance, call-level counters, suppression lists with dispute flags, and an audit trail of every attempt.

Those four records should be producible by debt, by channel, and by date. A clean script won't save a file that can't show them. Channel choice still has to respect the same records, which is why communication channels need the counters built in rather than bolted on after a complaint.

Payment plans and self-service payments that recover cash

The offer changes once you separate inability to pay from unwillingness to pay. Job loss, a deferred visit, or a balance that appeared after a life event points to hardship. More calls won't fix it. A person who can pay and is choosing not to is a different conversation, and mixing the two burns both relationships and complaints.

An April 2025 ADAP Advocacy survey of U.S. patients, filed with the Office of Information and Regulatory Affairs (OIRA), found that 77% of respondents had delayed or avoided medical care because they couldn't afford it, 71% had delayed or avoided prescription purchases, and 66% were receiving debt collection notices for medical services. Early pressure that ignores those signals can push a patient off care and off the provider, which makes the balance harder to collect later.

Which plan fits

Set eligibility from balance size, an income signal, and account age, and write the rule down so two agents don't invent two plans. Offer a plan before final demand. A plan made while the person still answers keeps the relationship. A plan offered after a demand letter often arrives too late.

Self-service belongs in the same design. IVR and text-to-pay work after hours and take routine payments off the queue. Watch completion rate, not how many links you sent. A link that opens and dies at the card step is a failed recovery, even if the text went out on time. Payment plans should be something the person can start alone and an agent can see the next morning.

Card data on the phone

Telephone payments are in scope for card security. The PCI Security Standards Council states that PCI DSS applies wherever card account data is stored, processed, or transmitted, and that voice over IP (VoIP) traffic carrying cardholder data is in scope like any other IP traffic with that data. Voice isn't outside the card environment because someone read the numbers aloud. Mask card entry on recorded calls, and keep card data off agent desktops. Flows should be built to meet PCI-DSS standards, with redaction on the recording path.

Use a short rule set:

• Weak income signal: Offer a plan, and document the hardship instead of stacking calls.

• Aged balance plus a lump sum, full recovery unlikely: Offer a reduced settlement with a clear deadline.

• Open dispute: Pause every plan offer until the balance is validated.

Gross dollars collected will look better if you ignore breaks in these plans. Next quarter's bad debt is where that choice shows up.

Where AI agents fit and where human agents stay essential

An automated agent confirms a three-payment plan, and midway the person mentions a job loss. The account now needs a human to assess the changed circumstances, review the balance and contact history, and decide what response fits. A handoff is only useful if the person receives the full record rather than starting from a cold call.

Automation also multiplies errors across thousands of accounts. A wrong balance, incorrect account owner, or debt the person does not owe can become a repeated message before staff catch the underlying data problem. Collections works as one operating system of account data, dialing, messaging, payments, and records. Accurate information and complete contact history matter as much as the script.

The CFPB's 2025 consumer-response report recorded approximately 387,400 debt-collection complaints, with volume increasing during the year, and 79% were sent to companies for review and response. CFPB reporting separately identified attempts to collect debts consumers said they did not owe as the most common issue in 2024. Those problems call for reliable account records, not more contact attempts.

Controls before any automated attempt

Reconcile billing, the agency system, and the dialer to one balance and one account owner. Validate the balance and ownership before the first text, email, or call. If a dispute is open, suppress automated messages as well as agent dials until the account is reviewed.

Some cases need human judgment. A job loss, language barrier, or threat of self-harm should prompt a person to assess the next step, not an optimized script branch. Keep the interaction record across channels, and review outcomes across languages and groups to catch uneven contact patterns.

Artificial intelligence (AI) collection agents can handle routine outreach, while staff remain responsible for ambiguous or sensitive cases. Intelligent Contacts offers Grace, an AI collection agent that operates within configured compliance policy and escalates complex disputes and human requests to a live agent. Automation still has to follow the applicable consent rules: AI voice calls are subject to TCPA requirements, and prior express consent must be on the account before an automated voice attempt to a cell phone.

Measure handoffs by whether payments are validated, disputes are accurately handled, complaints and opt-outs are controlled, and the next agent receives a usable record. Call volume alone cannot show whether automation is improving recovery or multiplying bad account data.

Automation handles routine work. People assess disputed, vulnerable, and unclear cases.

Use automation where account data is sound and the next action is clear. Keep human judgment in the workflow wherever the record, the customer's circumstances, or the appropriate response is uncertain.

Metrics that show real recovery beyond dollars collected

Set the scorecard before reviewing performance. Define each metric consistently, then read the measures together by segment, channel, and account age. A single measure can reward activity that does not produce a clean outcome.

How to read the set

Rising right-party contact with stable or falling complaints suggests outreach is reaching the intended people without adding friction. If contact and complaints rise together, review targeting and handling before increasing attempts. High attempts paired with low right-party contact point to a phone file that needs attention. More dials cannot correct missing or outdated contact records.

Safe resolution rate keeps automation accountable to outcomes. Count payments that validate, disputes handled accurately, and handoffs that include the account history. A promise to pay that never posts is incomplete, and a transfer that forces someone to repeat the issue has not resolved it.

What to report, and to whom

Report monthly, broken out by segment, channel, and account age. That view helps a finance lead identify where recovery is slowing and a compliance lead see whether a channel is producing avoidable complaints. In healthcare, review bad debt alongside care continuity. Early collection activity may recover a small balance while damaging a relationship worth more than the invoice.

Ask one question per metric during the review. For roll rate: which bucket stopped, and who owns the next action? For plan completion: which term length is breaking? For disputes: which source system supplied the balance being challenged? For safe resolution: which channel produced a validated payment, and which produced a complaint?

Keep the definitions stable from one review to the next. Otherwise, changes in how teams count outcomes can make performance appear to improve or decline when the underlying work has not changed. A shared scorecard gives finance and compliance a common basis for deciding what to investigate and where to adjust the workflow.

Audit your collections workflow before you change tools

Pull last quarter's aging export before you book a demo. Sort by age, then mark accounts with no owner, a number that has not connected, or a balance that does not match billing. Most gaps appear in a simple aging export.

These five checks test whether data, dialing, messaging, payments, and records work as one system.

1. Find holes in the age map. Apply the stage path above and look only for buckets with no owner. A bucket with no owner is where accounts stall. In the same export, flag blank or stale contact records. A wrong number fails under any dialer.

2. Sample the controls already in place. Consent, attempt counters, and dispute suppression were set earlier. Pull a few live accounts and confirm the blocks fire on text and email, not only on the agent desktop. A desktop-only flag still lets the text go out.

3. Score the last two quarters on the set you already report. Safe resolution, complaint volume, and plan completion are enough. If complaints rose while dollars rose, the extra cash was expensive.

4. Trace one payment and one dispute across systems. The dialer should see an open dispute before the call. The payment link should write the result back to the account. If either handoff fails, another logo will fail the same way.

5. Set two targets. Pick one 90-day target on roll rate and one on complaint volume, and review both monthly. Two numbers show whether the path moved.

Compare those gaps to the stack you run now, before you choose any provider. I would not add capacity until the file names the right person and the right balance.

Intelligent Contacts brings dialing, messaging, payments, and records into one platform, so those handoffs sit in a single system rather than a disconnected stack. Grace runs inside the policy you configure and hands complex disputes and human requests to a live agent. See how that operating model fits your book at Intelligent Contacts.