The person who knows how to clear unapplied cash is on vacation, and a customer gets a reminder for an invoice it paid last week. The team has enough people to send reminders. Nobody else knows where the remittances land. Before you ask for another head, find out whether you are short of people or short of handoffs.
A capacity problem means the hands-on work exceeds the hours available. A handoff problem means work sits waiting for one person, one inbox, or one approval. Software can help with the first. Only ownership and process fix the second.
Separate hands-on time from waiting time
Pick a routine week and a busy one. Pull invoices from both and trace each from receipt to approval. Ask the people who handled them where they worked outside the system: chasing a receipt in chat, checking a supplier statement by hand, forwarding a PDF to a manager.
Keep two columns for every item:
- Hands-on time tells you whether staff capacity is the constraint.
- Waiting time tells you whether the item will make the next payment run.
An invoice can take four minutes of work and sit for nine days. Faster capture does nothing for that invoice. If invoices are arriving faster than your team can enter them, test capture. If they are sitting in an approver’s inbox, faster capture just gets them to that inbox sooner.
| What you find | What to change first |
|---|---|
| AP keys the same fields from familiar supplier invoices | Test extraction on those suppliers and record which fields AP still corrects |
| Bills wait for someone to confirm delivery | Give receiving the invoice line and PO so they can answer without searching their inbox |
| One manager is the only approver for several teams | Assign backup coverage and review which approvals need that manager’s authority |
| The same invoice enters through email and a supplier portal | Choose one entry queue and test duplicate checks across both sources |
| Cash sits unapplied while collections follows up | Link remittance and bank evidence in the AR queue |
Start with invoices that missed a payment run. They show you where the process breaks under real conditions.
Model a busy week on paper
Split the queue into three kinds of work: routine items, items that need a document from someone, and items that need a decision. Estimate volume and minutes for each, then compare the load by owner. AP may have room for more bills while one buyer is already at capacity for price disputes.
Worked example (illustrative)
These figures are invented to show the method. Two AP clerks each have about 30 hours a week for invoice work, so AP capacity is 60 hours. A buyer has about 8 hours a week for invoice questions.
Normal week
| Work type | Volume | AP minutes each | AP hours | Buyer hours |
|---|---|---|---|---|
| Routine | 400 | 3 | 20 | 0 |
| Needs a document (receipt, statement) | 80 | 15 | 20 | 0 |
| Needs a decision (price, quantity dispute) | 30 | 10 | 5 | 30 × 20 min = 10 |
| Total | 510 | 45 | 10 |
Busy week (volume up 40%)
| Work type | Volume | AP minutes each | AP hours | Buyer hours |
|---|---|---|---|---|
| Routine | 560 | 3 | 28 | 0 |
| Needs a document | 112 | 15 | 28 | 0 |
| Needs a decision | 42 | 10 | 7 | 42 × 20 min = 14 |
| Total | 714 | 63 | 14 |
Check the arithmetic: 560 × 3 = 1,680 minutes, or 28 hours. 112 × 15 = 1,680 minutes, or 28 hours. 42 × 10 = 420 minutes, or 7 hours. AP needs 63 hours against 60 available, a 3-hour gap. The buyer needs 14 hours against 8, a 6-hour gap.
Even in the normal week the buyer is over capacity (10 hours against 8), which explains why disputed invoices already age.
Now test a fix. If draft preparation cuts routine handling from 3 minutes to 1.5, busy-week routine time falls to 560 × 1.5 = 840 minutes, or 14 hours. AP’s total becomes 14 + 28 + 7 = 49 hours, well inside 60. But the buyer is still 6 hours short, and those 42 disputed invoices will still miss runs. A second hire in AP would not have fixed that either.
The model gives you a specific next step: get the buyer backup authority for disputes under a set amount, or move price-variance review to someone with time. Then attack the “needs a document” row, which is now AP’s biggest block of time.
During any pilot, count time spent checking drafts, correcting coding, and cleaning up failed handoffs. Those minutes are real, and they tend to disappear from vendor estimates.
Run an absence drill before close
Pick a routine day and give the backup a few completed cases to replay with their own access. Leave the regular owner out of the first pass. Write down where the backup stops and what would have let them continue.
| Give the backup | Ask them to show you |
|---|---|
| A bill blocked on a missing receipt | The order, the missing line, and who can confirm delivery |
| A payment covering several invoices | The remittance, proposed allocation, and where to record a disputed amount |
| A reconciliation with a carried balance | Last signed reconciliation, why the item is open, next follow-up date |
| A journal prepared late on close day | The source schedule and the reviewer with authority to sign off |
Then fix the first missing handoff. If remittances arrive in personal inboxes, move them to a shared queue with the right access. If nobody knows who owns an unresolved reconciliation, put an owner and a follow-up date in the close record. If staff retype the same fields, test whether software can prepare that work and leave a record the backup can use. Run the same cases again after each change.
Keep duties separate when people cover for each other
Stretching a small team creates a specific risk: the backup who prepares a payment also inherits authority to release it. Check your coverage plan for that. The GAO’s federal internal control standards, the Green Book, cover segregation of incompatible duties and succession and contingency planning for key roles (GAO Green Book). They are written for government entities, but the design principles transfer well to a small finance team.
Three pairs to keep apart, even when short-staffed:
- Entering or changing vendor bank details, and approving payments to that vendor.
- Preparing a payment run, and releasing it.
- Preparing a reconciliation, and signing it off.
If supplier bank change requests arrive, route them to someone who verifies by calling a known number, not the number on the request. The duplicate payments and vendor master controls guide covers that procedure.
What changes as you grow from 20 to 200 people
Headcount gives you a rough sense of scale. The work that keeps bouncing back to finance tells you what to change.
When the founder’s inbox is the approval queue
At 20 people, the founder may know who bought every tool. Once departments buy on their own, finance gets invoices nobody wants to approve: the contract signer is out, the renewal date passed, and the vendor wants a pay date. Give each department an owner and a backup who can approve within a written limit. Decide what happens when a bill crosses two budgets: both owners approve, or one has authority for the total. Work through that example before writing routing rules. The invoice approval workflows guide has routing patterns that don’t stall.
Move incoming bills to a shared queue and keep the original document with the approval. A bill forwarded by three people should still be one record.
When more customers pay by bank transfer
Give AR a way to link bank receipt, remittance, and open invoices. Test with a deposit covering several invoices and one with no usable reference. For the second, leave the uncertain amount unapplied and assign someone to identify the payer. Let collections see that a receipt is under review before sending another reminder; that matters once the person applying cash and the person calling customers no longer sit together. See cash application automation for split deposits and short pays.
When close depends on one person’s memory
Open last month’s close checklist. For each recurring task, record the source report, owner, backup, and evidence that shows it is done. Start with the task that blocked the next person: a card reconciliation, a late supplier bill, a deposit waiting for application.
If you add automation, test how it behaves against a locked period. NetSuite, for example, provides a Period Close Checklist and uses preliminary locks to limit posting before the period closes (Oracle’s accounting period close documentation). A transaction that hits a lock should go to the controller with its intended date and the failure reason, and the controller decides. The month-end close automation guide has a checklist built to survive turnover.
When you add an entity
| What keeps happening | Fix the handoff first | Test the result |
|---|---|---|
| Finance forwards the same bills to several people | Assign ownership by budget and name a backup | Route a split bill while one approver is away |
| The same invoice shows up in the card feed and the AP inbox | Check payment status before creating a bill | Deliver the invoice and the card charge in both orders |
| A new entity inherits the old approval rules | Confirm who approves and posts for each entity | Try an invoice from a supplier shared by both entities |
When you actually need to hire
Some work needs a person with authority and time. If every backup is already committed at close, or one role is over capacity even after the handoffs are fixed, the drill and the model give you the case for staffing. You will be able to say which role, how many hours, and which control it protects. That is a stronger request than “invoice volume is up.”
If you are weighing a hire against software or an outsourced provider, AI agents vs. RPA vs. outsourcing compares them on the same work.
Before you write the headcount request
- Pull ten invoices that missed the last payment run and log hands-on and waiting time for each.
- Rerun the busy-week model at your highest expected volume and compare hours to capacity by owner, not just for AP.
- Check that no backup holds both preparation and release authority for payments.