Guide · 8 min read
AP automation software vs a solution built around your business
Most AP automation products demo beautifully. An invoice goes in, the fields light up, and a bill appears. The question that decides whether it works in your business comes after the demo: what happens to the invoices that don't match?
Short answer
Should we buy AP automation software or build a custom solution?
Buy a product if most of your invoices match their purchase orders cleanly, you run one entity on a well-supported finance system, and your exceptions are handled within finance. Products are quick to start and do invoice capture and standard approvals well.
Build around your business if your time goes on the invoices that don't match: partial deliveries, receipting errors, unit-of-measure differences, several entities, or variances that have to be resolved by supply chain or the warehouse rather than finance. Those rules are specific to your business, and they are where AP automation either saves the hours or leaves them manual.
The common ground
What every AP product does well
If this is most of your AP effort, a product is likely to be the faster and cheaper answer.
Invoice capture
Invoices are collected from an inbox or upload and stored in one place, with duplicates detected.
AI extraction
Supplier, invoice number, dates, totals and GST are read reliably from most invoice layouts, and line items from most.
Standard approvals
Invoices are routed to approvers by amount or cost centre, with reminders.
Integration with popular finance systems
Products connect well with the systems most of their customers use, especially cloud accounting platforms.
Where products stop
The part of AP that is different in every business
Your matching rules
Partial deliveries, unit conversions, miscellaneous PO lines, freight and surcharge tolerances by supplier or category. A product gives you its own settings to choose from. If your rule isn't one of them, the invoice becomes an exception.
Exceptions that sit outside finance
A price variance needs supply chain. A quantity variance needs the warehouse. A missing receipt needs someone on the floor to check the delivery. Most products route approvals between finance people. Routing work to other teams, and tracking it until it is resolved, is where they run out.
Your systems as they actually are
A mid-market or on-premises ERP, operations and finance in separate systems, several entities. Products integrate deepest with the most common platforms, and less deeply with the rest.
What happens after the bill
Credit note tracking, price disputes, supplier status questions and statement reconciliation usually sit outside the product, so they stay in email and spreadsheets.
Side by side
How the two approaches compare
| Off-the-shelf AP software | Built around your business | |
|---|---|---|
| Invoice capture and AI extraction | Strong | Strong (Azure AI and AI Builder) |
| Matching rules | The product's settings | Any rule your business uses |
| Exception routing | Mostly within finance | To any team, including supply chain and the warehouse |
| ERP fit | Deepest with common platforms | Built for the ERP you run, through its API |
| Where your data lives | The vendor's platform | Your own Microsoft tenant |
| Pricing | Ongoing subscription, often per invoice or per user | Build cost plus Microsoft licences you may already hold |
| Time to first use | Days to weeks | A few weeks for a first release |
| Changing the rules | Limited to what the product supports | Changed to match how your process changes |
Buy a product
When off-the-shelf software is the right answer
- Most invoices match their purchase order without anyone adjusting them
- You run one entity on a cloud finance system the product connects to natively
- Exceptions are resolved within the finance team
- You process a few hundred invoices a month or fewer
- You want something running in days and are happy to work the product's way
Build around your business
When AP automation needs to fit your rules
If three or more of these are true, a product is likely to leave most of your exceptions manual.
- Goods arrive in part shipments, or invoices arrive before goods are receipted
- Items are bought in one unit and invoiced in another
- Freight, surcharges and other extra charges regularly appear on invoices
- Price variances are resolved by supply chain and quantity variances by the warehouse
- You run several entities, or operations and accounting in separate systems
- Your ERP is on-premises or not one the products integrate with deeply
- Supplier costs need to reach the right job or production order
- Credit notes, disputes and supplier status questions take up a real share of AP's week
The fair question
What if the person who built it leaves?
It's the right question to ask about anything custom. A solution that only one person understands creates the same key-person risk that AP automation is meant to remove.
That is why we build on the Microsoft Power Platform, in your own Microsoft tenant, rather than in custom code on our servers. The automation is documented, runs under a dedicated service account rather than a person's login, and sends failure alerts to a named person. Development, test and production are kept separate. Your business owns it, and another Power Platform partner or your own team can support it.
The middle path
You may not have to choose
If you already own an AP product that captures invoices well, the parts it doesn't cover can often be built around it, where the product has an API: variance routing to supply chain and the warehouse, receipt chasing, credit note tracking and supplier status updates.
Either way, start with the invoices that don't match today. Pull the last month of exceptions, group them by reason, and you'll see quickly whether your problem is reading invoices or everything that happens after.
Questions we get asked
Frequently asked questions.
Is custom AP automation more expensive than AP software?
Usually more up front and less over time. A product is an ongoing subscription, often priced per invoice or per user. A solution built on the Microsoft Power Platform is a build cost plus Microsoft licences, which many businesses already hold some of. The bigger difference is usually how many invoices go through without a person, because that is where the cost of AP actually sits.
How long does a custom AP automation take to build?
A first release covering invoice capture, extraction and three-way matching for your main suppliers typically takes a few weeks to build and test. Exception routing and approvals follow in the next increments.
Can we change the rules later?
Yes. Tolerances, approvers and routing are held as configuration your team can see, so most changes don't need a rebuild. New rules can be added as your process changes.
What licences does a Power Platform AP solution need?
Typically Power Automate Premium for the account that runs the automation, AI Builder or Azure AI capacity for invoice extraction, and Microsoft 365 for the people using Teams and SharePoint. We confirm licensing in discovery before anything is built.
Can it work alongside the AP software we already have?
Often, yes. Where your product has an API, the exceptions it doesn't handle, such as variance routing to supply chain and the warehouse, can be built around it rather than replacing it.
Next steps
Not sure which side of the line you're on?
Bring a month of AP exceptions to a 30-minute call. We'll group them by reason and tell you honestly whether a product or a solution built around your business fits better.
Related reading
- Accounts payable automation
- AP automation for manufacturers
- System integration
- What is workflow automation?
Prefer to talk it through? A 30-minute call is usually enough.
Bring us the process that is slowing you down.
A 30-minute discovery call is enough to work out whether automation is the right answer, and what it would take.
