The 10 requirements, up front
Standard software handles plenty of AP processes well. The ones that outgrow it tend to share the same ten requirements. If a process needs several of them at once, that’s the signal it needs something built for that complexity. The ones that don’t tend to share the same ten requirements. If a process needs several at once, that’s the signal it has outgrown what a one-size-fits-all SAAS tool was built for:
- Multiple approval paths across business units or legal entities
- Exception handling that stays inside the business process and therefore audit trail, not outside it
- Data that has to remain inside the organization’s own Microsoft 365 tenant
- Live, two-way integration with the ERP of record, not a batch export, or integration with other 3rd party applications as party of a workflow path
- Support for both PO and non-PO invoices in the same workflow
- Invoice capture accurate enough to reduce manual review and dynamic invoice formats
- Approval workflow that can be reconfigured without proprietary knowledge or custom development
- A configurable audit trail flexible enough to satisfy a regulator or external auditor
- Support for multiple entities, currencies, or tax jurisdictions in one process
- Implementation and support sized to the complexity, not a one-size template
The rest of this post walks through what each requirement means in practice, and why it matters more than invoice volume alone.
Why these ten, and not invoice volume
It’s tempting to size an AP automation decision by invoice count. That’s the wrong variable. A single-entity company processing 50,000 standard invoices a year can be served well by standard SaaS. A three-entity nonprofit processing 4,000 invoices a year, with different approval rules per entity and a funder that audits its controls annually, often can’t be, regardless of volume.
Multi-entity organizations feel this first in exception rates and cost. Across the broader AP population, invoice exceptions run around 22% of volume; at best-in-class organizations with workflows designed for their complexity, that rate drops to roughly 9%. Processing cost follows the same pattern: organizations report a median cost of $5.83 per invoice, with top-quartile performers at $2.07 and the bottom quartile above $10. Multi-entity organizations tend to sit toward the expensive end for a structural reason, not a competence one: every duplicated approval path or disconnected system means a duplicated touch per invoice.
Grouping the ten requirements
Workflow (1, 2, 7, 9). Approval routing that changes by entity, department, or amount. Exception handling that doesn’t require pulling an invoice out of the system to resolve it. Routing that can be reconfigured without a developer. Support for however many entities, currencies, or tax jurisdictions the business requires.
Data and integration (3, 4, 5). Invoice data stays inside the organization’s own Microsoft 365 tenant rather than a third-party database. The connection to the ERP of record is live, so approved invoices post in real time. Both PO and non-PO invoices run through one workflow instead of separate tools.
Accuracy and accountability (6, 8). Invoice capture, OCR or AI-assisted, is accurate enough to cut the number of invoices needing manual review. The resulting audit trail is detailed enough to survive an external audit, not just an internal one.
Fit (10). Implementation and ongoing support match the complexity of the process. A templated, self-service setup works for a templated process. A process with multiple approval paths, entities, or data residency requirements needs a partner who has configured that complexity before.
EasyAP365 was built against this list. It captures invoices from email, vendor portals, or mobile upload, extracts data with Microsoft Document Intelligence OCR, and posts approved invoices directly into the ERP in real time for both PO and non-PO types. Approvals route through Microsoft Power Automate, which makes multi-entity, multi-path approval logic a configuration choice rather than custom code. The application runs inside the customer’s own Microsoft 365 tenant and connects live to ERPs including Dynamics 365 Business Central and Finance, SAP, Acumatica, NetSuite, Sage Intacct, and Oracle, among others.
FAQ
Does a complex AP process need all ten requirements to justify moving off standard SaaS?
No. Two or three together, especially multiple approval paths combined with a data residency requirement, are usually enough to signal the fit has changed. All ten rarely show up in one organization at once.
Is invoice volume part of this list on purpose?
It’s deliberately left off. Volume affects cost and staffing, but it doesn’t determine whether a process is complex in the sense that matters here. A low-volume, multi-entity process can be harder to automate well than a high-volume, single-path one.
How is this different from what a standard ERP module already does?
Most ERP-native AP functions either don’t exist or were built around a single approval chain and a single entity’s rules. They can be stretched further, usually through customization the organization then must maintain, which is a different cost structure than a product built for the complexity from the start.
What’s the fastest way to check fit against this list?
Score the process against the ten requirements directly, or run it through a structured assessment that asks about approval paths, data residency, ERP integration, and compliance requirements in one pass.
Sources
- Ardent Partners, AP Metrics That Matter in 2025, as reported by Stampli — invoice exception rate benchmarks
- APQC benchmark data (≈1,485 organizations), as reported via Corpay’s multi-entity AP analysis citing CFO.com’s “Metric of the Month: Accounts Payable Cost”
- DynamicPoint, EasyAP365 product overview — product capabilities and supported ERPs
