How Can We Handle Growing Invoice and Collections Volume Without Hiring More AR Staff?

To handle more invoices without hiring, automate the repetitive AR work first: follow-ups, portal uploads and payment matching. Keep people on disputes, key accounts and decisions that change what a customer owes.

Cash FlowBy George Kurdin8 min read

To handle more invoices without hiring, automate the repetitive work first: follow-up emails, AP portal uploads and payment matching. Keep your people on disputes, key accounts and anything that changes what a customer owes. Most AR teams spend most of their week on work software can do.

Here is how it usually goes. Invoice volume grows from 800 to 1,500 a month. The AR team is still two people. Follow-ups slip from weekly to “when we get to it”. Portal uploads pile up. Unapplied cash sits for two weeks. DSO creeps up, and the first answer is a job posting. It doesn’t have to be.

This applies whichever vendor you pick, Monk included.

Where Does AR Time Actually Go?

Before you change anything, find out where the hours go. Ask each person to log their week for two weeks.

Most teams find the same pattern:

Task Typical share of the week Can software do it?
Sending and chasing follow-up emails High Yes, with approval rules
Uploading invoices to customer AP portals High at enterprise accounts Yes, for most portals
Matching payments to invoices High Mostly, with a person on exceptions
Answering “can you resend the invoice?” Medium Yes
Working disputes and deductions Medium Partly. People make the call
Key account calls and escalations Low No. Keep people here

The top four rows are where your hiring budget is going. They are also the easiest to automate.

Which Work Should You Automate First?

Start with the work that is high volume and low risk. Move to harder work once the first part is running well.

  • Follow-up emails on small invoices. These are the highest volume and the lowest risk. Start here.

  • Invoice copies and status questions. “Can you resend INV-4471?” should never need a person.

  • AP portal uploads. Enterprise customers often pay only through Coupa, Ariba or their own portal. Each upload done by hand means logging in, finding the PO and attaching the file.

  • Exact payment matches. Payments with a clear invoice reference should apply on their own.

  • Suggested matches. Lump sums and PO-only references come next, with a person confirming each one at first.

Leave write-offs, new payment terms and dispute outcomes with people. Those change what a customer owes. Our post on how to set human approval rules for AI collections covers where to draw that line.

What Should Your People Do Instead?

Automation only pays off if you move people to higher-value work. Give them a clear new job.

  • Own the exceptions. One person owns short pays, disputes and unknown payments, with due dates.

  • Work the top 20 accounts. Your largest balances deserve a call, not a template.

  • Fix the causes. If the same customer short-pays every month, fix the pricing or contract issue behind it.

  • Approve the queue. Someone reviews drafts and suggested matches each morning. Same-day approval is a good goal.

  • Watch the numbers. DSO, unapplied cash and the age of the oldest open dispute, every week.

This is the difference between an AR team that chases and one that manages.

How Do You Keep Control When Software Does the Work?

Control comes from rules, not from checking everything. Set the rules before you turn anything on.

  • Set an amount limit. Above it, a person approves every email and every match.

  • Flag key accounts. Top customers and anyone with an open dispute always go to review.

  • Split by action type. Sending an email is lower risk than posting cash. Posting cash is lower risk than a write-off.

  • Never send by default. If a draft passes its approval deadline, it waits. It doesn’t send on its own.

  • Log everything. Every email, match and change should have a record you can show an auditor.

Our post on which overdue invoices AI should email automatically has a starting rule set.

What Does This Look Like at 1,500 Invoices a Month?

Take a team of two, sending 1,500 invoices a month to 400 customers.

  • Before. Both people spend most of the week on follow-ups, portal uploads and matching. Disputes wait. The top 20 accounts get the same template as everyone else.

  • Month one. Follow-ups on invoices under $5,000 go out automatically after two weeks of approved drafts. Portal uploads run on their own for the 30 customers who require them. Exact payment matches apply on their own.

  • Month two. Suggested matches for lump sums start. The AR lead confirms each one each morning. Write-offs and payment plans still need the controller.

  • Month three. One person owns exceptions and disputes. The other works the top 20 accounts by phone. Nobody is hired.

The goal isn’t zero people. It is the right people on the right work.

How Do You Know It Is Working?

Pick four numbers and track them weekly from day one.

Metric What it tells you Direction you want
DSO How fast cash comes in Down
Unapplied cash, and its age How well matching is running Down
Invoices per AR person Whether volume is growing without headcount Up
Oldest open dispute Whether exceptions are being worked Down

If invoices per person go up and DSO goes down, it’s working. If DSO goes up, look at the exceptions queue first.

What Should You Ask Vendors?

Ask each vendor to show you, on your data:

  • One follow-up thread end to end. Including what happens when the customer replies “we already paid”.

  • One portal upload. Pick your hardest customer portal.

  • One lump-sum payment. From remittance to the posted record in your ERP.

  • The approval screen. Who approves what, and what happens if they’re out.

  • The go-live plan. A date, and what your team must do to hit it.

Our build vs. buy guide covers the wider trade-offs.

How Does Monk Handle This?

Monk is an AI-native accounts receivable platform covering collections, cash application, AP portal submission, disputes and cash forecasting. Monk resolves 87% of collections with zero human intervention. Julia, Monk’s AI collections email agent, reaches customers with a 24% higher response rate than standard dunning.

Monk integrates directly with more than 600 corporate AP portals and uploads 87% of portal invoices autonomously, with its team handling the exceptions. Cash application matches 80% of payments automatically, rising to 95% with suggested rules. Deterministic checks run before any action reaches a customer or the ledger, and every action is logged.

Teams go live in under a month.

Where Should You Start?

  1. Log two weeks of AR time. Use the task table above.

  2. Pick one high-volume, low-risk task. Follow-ups on small invoices are the usual first choice.

  3. Write your approval rules. Amount limit, key accounts, action types.

  4. Approve every draft for two weeks. Then let the low-risk group send on its own.

  5. Track four numbers weekly. DSO, unapplied cash, invoices per person and the oldest dispute.

Frequently Asked Questions

Can AR automation replace an AR hire?

It can absorb the volume growth that would have needed a hire. You still need people for disputes, key accounts and decisions that change what a customer owes.

What should we automate first?

Follow-up emails on small invoices. They are high volume and low risk, so you see results quickly.

Will customers notice the emails are automated?

They notice when emails are generic. Good tools write from the invoice and the customer’s history, and route replies that need a person.

How do we stay in control?

Set rules by amount, account and action type before you start. A person approves anything above the limit or anything that changes the books.

How long does it take to see results?

Most teams see the effect on follow-up volume in the first month. Track DSO and unapplied cash weekly from day one.

Do we need to replace our ERP?

No. AR automation should sit on top of your ERP and write back to it. See our post on automating AR without replacing your accounting software.