The most common AR team structure at mid-market B2B companies — those running between $20M and $200M in annual revenue — is not what you'd design if you were building from scratch. It's what you end up with after years of adding revenue without proportionally adding AR headcount, because AR is an overhead function and headcount requests from finance are less visible than headcount requests from sales.
The resulting structure usually works until it doesn't. Understanding the typical pattern — and specifically where the load-bearing points are — helps you identify which part of your AR process is actually under strain before DSO climbs 20 days and the CFO is asking questions.
The typical structure at $20M–$60M revenue
At this revenue band, the AR function is usually handled by one or two people, often with overlapping responsibilities. The most common configuration:
- AR Specialist (1 FTE): Handles invoicing, cash application, aging report review, and collection follow-up. In many cases, this person also handles some AP tasks, vendor bill processing, or payroll support — AR is not their sole responsibility.
- Controller or CFO (part-time AR oversight): Reviews weekly aging reports, approves credit holds, handles escalated accounts, and signs off on write-offs. They don't work the daily collection queue but they're the decision-maker when a situation requires it.
This works at lower invoice volumes — under about 200 open invoices at any given time — because a single AR specialist can realistically review the aging report, identify past-due accounts, and make individual follow-up decisions daily. The process is manual but it's manageable.
The breaking point: when monthly invoice volume crosses 80–100 new invoices, a single AR specialist can no longer keep up with both the invoicing/cash application workload and the collection follow-up workload. The collection queue starts falling behind. The specialist starts triaging — following up on the largest dollar amounts and the loudest accounts, letting smaller invoices drift. DSO climbs slowly over several quarters before anyone notices the structural cause.
The typical structure at $60M–$150M revenue
Growing companies that add AR headcount usually land at a two-or-three person team with more defined roles:
- AR Specialist / Billing (1 FTE): Focused primarily on generating invoices accurately and on time, managing credit applications for new customers, and cash application.
- Collections Specialist (1 FTE): Primarily responsible for follow-up on past-due accounts — working the aging report, sending reminders, handling disputes, and managing the escalation queue.
- AR Manager or Controller (oversight): Sets collection policy, manages the credit hold process, handles major escalations, and reports to the CFO.
The role separation helps. When invoicing and collections are managed by the same person, invoicing urgencies (month-end close, customer billing disputes) regularly crowd out collection follow-up. Separating the functions means the collections specialist can focus on the aging report without being pulled into billing emergencies.
At this revenue band, invoice volumes typically range from 300–700 open at any time. A dedicated collections specialist managing 400+ accounts with manual tools — usually the ERP aging report plus Excel — is at capacity by mid-afternoon on a normal day. The follow-up process is consistent for the top 30–40 accounts by dollar value, and progressively less consistent as you move down the aging report.
The structure at $150M–$250M revenue
Larger mid-market companies often add a third layer: a dedicated AR team with specialization by customer segment or account type.
- AR Specialists (2–3 FTE): Often split by account portfolio — one handles key accounts (the top 50–100 customers by revenue), another handles the mid-tier, a third handles the high-volume/low-dollar tail.
- Collections Analyst or Coordinator: Owns the reporting function — weekly aging analysis, DSO trending, collection rate reporting to CFO. May also manage the dispute resolution workflow.
- AR Manager (dedicated): Full-time AR team lead, manages credit policy, staffing, process improvement, and external collections agency relationships.
This structure is more scalable, but it introduces coordination complexity that smaller teams don't have. The key accounts specialist knows her portfolio well. The mid-tier specialist knows his. But the account that crosses from mid-tier to key account status as the customer relationship grows? The handoff process is often informal and context gets lost. The new specialist picking up an account may not know that this customer always pays when you escalate to their CFO directly, not their AP contact.
Where the structure breaks down — across all bands
There are several failure modes that show up consistently regardless of company size or team structure:
Institutional knowledge concentration
In most mid-market AR teams, one person holds the majority of the institutional knowledge about customer payment behavior. They know which customers need a phone call, which ones pay faster when you reference the PO number, which ones have AP contacts that are hard to reach on Fridays. This knowledge lives in their head, not in any system.
When that person goes on leave, changes roles, or leaves the company, the team's effective collections performance drops immediately. The new person starts from scratch. Accounts that would have been escalated at day 15 go to day 30 because nobody knows the trigger. Write-offs go up in the quarter following a key AR team member's departure — this is a real and observable pattern at growing companies.
The coverage gap at scale
Mid-market AR teams are almost universally understaffed relative to invoice volume. The benchmark that consultants often cite — one collections FTE per $30M–$40M in accounts receivable — is not what most companies actually have. They have roughly half that. The result is that the collections specialist managing 500 open invoices can't realistically give each account the attention the aging report says it deserves.
This coverage gap is not a hiring problem in isolation. Adding an AR headcount to solve the coverage gap adds $60,000–$90,000 per year in fully loaded cost, but it doesn't change the underlying process — it just runs the same manual process with more people. The coverage gap is a process efficiency problem that headcount alone doesn't fix.
The escalation threshold confusion
Most AR teams don't have a written escalation policy. The threshold for "this account gets a phone call" or "this account goes on credit hold" is usually informal, applied inconsistently across the team, and biased toward the largest accounts regardless of other risk signals. An account with $200K outstanding at 45 days gets escalated. An account with $15K outstanding at 65 days might not, even though the dollar amount is meaningful and the age is worse.
The absence of a consistent escalation framework means that some accounts that should have been escalated at day 20 are sitting at day 50 waiting for a first call. The consistency problem doesn't improve with team size — it often gets worse, because more people are applying their own judgment about what deserves escalation.
Reporting that reflects the past, not the future
The standard AR reporting cadence at mid-market companies is backward-looking: the Monday morning aging report shows what happened last week. It shows which accounts moved into each bucket, which ones paid, and what the total outstanding balance is. It does not show which accounts are likely to move into the past-due bucket next week, based on their historical behavior.
AR teams that are reacting to the aging report are always one step behind. By the time an account appears in the 30-day past-due bucket, the optimal intervention window — the first 5–7 days after the due date — has often passed. A proactive process that identifies likely-late accounts before their due date and initiates outreach earlier compresses DSO in a way that reactive aging-report management can't.
What this means for how you structure the work
The mid-market AR team structure doesn't need a major redesign. The headcount is roughly right for most companies — the issue is what the headcount is spending its time on. AR specialists who spend 3–4 hours per day on manual follow-up tasks are doing work that a well-instrumented process should handle automatically. That capacity freed up should go to the 20–30 accounts that genuinely need human judgment, relationship context, and direct conversation to resolve.
The structural improvement that moves DSO most reliably isn't hiring another AR specialist. It's ensuring that the AR specialists you have are spending their time on decisions that require their expertise — not volume follow-up that can be systematized — and that the institutional knowledge about customer payment behavior is encoded somewhere accessible to the whole team, not held by one person who might leave.
That reorientation of where AR team capacity goes is what allows a two-person team at a $60M company to manage 500 open invoices with DSO in the same range as companies with twice the headcount. The team size matters less than the fraction of their time that goes toward high-value judgment work versus repeatable follow-up tasks.