How Many Invoices Can One AP Person Realistically Handle?

This is one of the most common questions finance leaders ask when they're trying to figure out if they need to hire, automate, or both — and it's also one of the hardest to answer with a single number, because invoice complexity varies so much between businesses that a generic benchmark ends up being close to meaningless for any specific team.

Why there's no one universal number

• PO-backed invoices with clean data take a fraction of the time of invoices requiring manual research to figure out what they're for.
• A high exception rate — mismatches, missing coding, unclear vendor details — eats far more time per invoice than a clean one.
• The number of approval layers matters as much as the invoice count; three invoices requiring four approvers each can take longer than thirty simple ones.
• Vendor concentration matters too — fifty invoices from five well-known vendors process faster than fifty invoices from fifty different, unfamiliar ones.

A framework for figuring out your own number

1. Track total AP hours for a full month, across everyone touching the process, not just the primary AP person.
2. Divide by invoices processed that month to get a rough hours-per-invoice figure.
3. Segment by type — PO-backed versus not, exception versus clean — since a blended average hides where the real time is going.
4. Watch the trend over a few months rather than trusting a single month, since volume and complexity both fluctuate.

What changes capacity more than headcount does

Before concluding the answer is "hire another person," it's worth checking whether the actual constraint is invoice complexity rather than raw volume. A team drowning in exceptions and PO-less invoices will hit a wall at a much lower invoice count than a team with clean vendor data and strong PO discipline — which means fixing the inputs sometimes raises capacity more than adding a person does.