AP Department Best Practices: How High-Performing Teams Operate

AP department best practices are the operational habits, policies, and review rhythms that separate top-quartile accounts payable teams from the rest. They are not primarily about software — they are about the structure that makes any software work correctly and consistently.

Top-performing AP departments hit specific benchmarks: under $2.78 per invoice processed, 2.8-day cycle times, 80% straight-through processing, and 23,333 invoices per FTE annually. Average teams sit at $5.83 per invoice, 4-day cycles, and 10,853 invoices per FTE. Bottom performers spend $10+ per invoice, take 7+ days, and process just 6,082 invoices per FTE (Ardent Partners, APQC). The gap is almost entirely explained by whether the team has these ten practices in place.

The 10 Practices

1. Centralize Invoice Intake to One Channel

All invoices arrive through a single, monitored channel — one dedicated AP email address or a vendor portal. The most common cause of duplicate payments is not fraud; it is the same invoice arriving by email, mail, and fax simultaneously.

What it looks like: [email protected] is the only address vendors use. All other intake routes are closed or auto-forwarded. Every incoming invoice gets a timestamped acknowledgment within one business hour.

2. Publish Internal SLAs

Define your turnaround commitments and share them with budget owners and vendors: invoice coded within 24 hours of receipt, approval completed within 48 hours of routing, payment released on due date (no earlier, no later unless a discount applies). AP teams that skip SLA publication spend roughly 30% of their time fielding status queries — time that disappears when the answer is already documented.

What it looks like: A one-page SLA document posted in your vendor portal and distributed to every department head who approves invoices.

3. Enforce Segregation of Duties Through Your ERP

No single person should code an invoice, approve it, and release payment. This is the most commonly skipped control at mid-market companies — and the one that allows fraud and error to compound undetected. Three-person control minimum: AP specialist codes, manager approves, separate user releases payment.

What it looks like: Role permissions in your ERP enforce the separation — not a policy memo that staff may or may not follow.

4. Automate Three-Way Matching for PO-Backed Invoices

Purchase-order invoices should flow from receipt to payment with zero manual intervention. PO-backed invoices reach 92% touchless processing when matching is properly configured against the purchase order and goods receipt. Non-PO invoices require different handling — but PO invoices should never require manual review unless the match fails.

What it looks like: Less than 5% of PO invoices require manual intervention. Exception reports show only genuine discrepancies, not routine matches.

5. Track Exception Root Causes by Vendor

Exception rate is a KPI, but exception root cause is the practice. Most exception volume in any AP department comes from the same five to seven vendors — wrong GL codes, missing PO numbers, or invoice format issues. Fixing one vendor's invoice template can eliminate 40 hours of monthly rework.

What it looks like: A weekly exception log tagged by vendor and root cause, reviewed every Monday. Any vendor generating three or more exceptions in a month gets a structured conversation about standardization.

6. Set Invoice-Per-FTE Targets and Review Quarterly

This is the single most honest health metric for an AP department. The benchmark: 6,082 invoices per FTE annually for manual teams, 10,853 for average teams, 23,333 for fully automated teams. If your team is under 6,000, automation is the gap. If your team is between 6,000 and 10,000, process discipline is the gap.

What it looks like: A monthly dashboard showing invoices processed per FTE, trended over 12 months. Reviewed quarterly in the AP manager's business review.

7. Run Weekly Aging Reviews

Monthly aging reviews create a seven-day surprise window — enough time for a $50,000 invoice to miss its discount window or accrue a late fee. Top-performing AP teams review aging weekly, flagging invoices due within 48 hours and cash discount windows before they close.

What it looks like: A 30-minute Friday review of all invoices within 48 hours of due date. Any discount with a capture window closing in five days gets escalated to payment.

8. Define Escalation Rules in Writing

Every stuck invoice needs a clear escalation path: who gets notified, at what threshold, with what response SLA. Without documented rules, AP specialists self-escalate to whoever they know — which breaks under volume and creates inconsistent outcomes.

What it looks like: "Invoices over $10,000 stuck in approval for more than 24 hours → escalate to AP manager. Over $50,000 → escalate to Controller. Vendor threatening credit hold → AP manager notifies CFO within one business hour."

9. Maintain Vendor Master Data Hygiene

Outdated vendor records are the root cause of more duplicate payments and payment fraud than most teams recognize. Banking details change. Addresses move. Tax IDs get updated. Top AP departments audit vendor master records quarterly, with any bank detail change requiring dual authorization — one person to request, a different person to verify and approve.

What it looks like: Quarterly review of all active vendor records. Any vendor with an unpaid invoice in the past 90 days gets validated. Banking detail changes require a callback to a phone number on file, not the number provided in the change request.

10. Run a Formal AP Close Cadence

The AP close is a structured monthly review of open items, accruals, and discrepancies — completed before the finance team closes the books. Teams that treat the close as informal hand the Controller surprises on day two. Documented close checklists, completed by the second business day of each month, are the signal of a mature AP function.

What it looks like: A five-step close checklist: open invoice reconciliation, accrual submission to accounting, payment batch confirmation, exception report to AP manager, and exception resolution log updated. See AP month-end close checklist for the full process.

Self-Assessment: Where Does Your Team Stand?

Count how many of these ten practices are fully operational — not planned, not partially in place, actually running:

Score	Status
8–10 practices	Top quartile — benchmark against invoice-per-FTE targets
5–7 practices	Developing — close the two lowest-cost gaps first (SLAs and exception tracking)
Under 5 practices	High-risk — prioritize controls (practices 3, 8, 9) before optimizing efficiency

Most AP managers score themselves a six or seven on first pass, then discover two or three practices are "planned" rather than operational. The difference between planned and operational is a documented process, a person accountable for it, and a metric that confirms it is running.

AP Department Best Practices vs AP Automation

These practices apply whether your AP function runs on spreadsheets or enterprise software. Automation accelerates each practice — but it does not replace the operational foundation. An automated AP department without SLAs still fields vendor status queries. Automated matching without segregation of duties still has a fraud exposure. The practices come first; technology scales them.

Key Takeaways

• Invoice-per-FTE is the best department health metric: average is 10,853, top performers hit 23,333
• Centralized intake prevents the most common source of duplicate payments — multi-channel invoice arrival
• SLA publication cuts inbound status queries by roughly 30% — the hidden productivity gain most teams ignore
• Segregation of duties is the most commonly skipped control at mid-market — and the most consequential to skip
• Exception root-cause tracking by vendor eliminates most recurring manual work within 60 days

Related Terms

• Accounts Payable KPIs — The metrics that measure whether these practices are working
• Three-Way Matching — The matching process that drives practice 4
• Invoice Processing — The end-to-end workflow these practices govern
• Accounts Payable Automation — The technology that scales practices 4 and 6
• AP Audit Trail — Why practices 3, 8, and 9 are audit-critical