Which software should your accounts payable team use for approvals?

We compared accounts payable approval software on what an accounts payable (AP) team, the group that pays supplier invoices, handles every day. It covers how flexibly invoices route to approvers, how purchase order and three-way matching work, how approved invoices reach the company’s enterprise resource planning (ERP) accounting system, and which controls surround the approval workflow. It is written for European finance teams, so we also checked hosting, local accounting connectors, and e-invoicing support, drawing capabilities from each vendor’s help centre or product documentation and e-invoicing dates from official tax-authority sources.

Key takeaways

• Spendesk suits European finance teams that want approval rules, budgets, cards, expense claims and supplier invoices in one system, with controls set before money is spent.

• Ramp is built first for US-registered companies, and its availability beyond the UK in Europe is not yet confirmed.

• SAP Concur, an established enterprise travel-and-expense platform, makes most sense for large groups running SAP ERP.

• Several tools put routing conditions, delegation or matching behind specific plans or add-ons, so check what your plan includes.

• Vendor implementation timelines are estimates that stretch with ERP depth, entity count and data quality.

How we evaluated

We scored each tool on five criteria that decide whether an approval workflow holds up at month-end. The angle throughout is a European finance team that books in local accounting systems, receives structured e-invoices, and runs more than one entity.

• Approval routing flexibility: We looked at amount thresholds, sequential steps, conditions by cost centre, supplier or GL code, role-based approvers, and how delegation works when someone is away.

• PO and three-way matching: We checked whether the tool matches invoices to purchase orders and goods received notes at line level, and what happens to an invoice that does not match.

• ERP integrations: We separated native integrations from file exports and partner connectors, and noted country restrictions on each connector.

• Internal controls: We looked for self-approval prevention, duplicate detection, audit history and segregation between supplier setup, approval and payment.

• Implementation and European fit: We noted stated onboarding times, data hosting location and e-invoicing support in France, Germany and Belgium.

Best accounts payable approval software at a glance

The table compares each platform on fit and European infrastructure, using the vendors’ own documentation:

Our top picks

Each pick below suits a different team. Spendesk fits European finance teams that want AP, cards, and expense claims in one system. Ramp suits US-registered companies, and SAP Concur suits large SAP-centred enterprises.

Best overall: Spendesk

Spendesk fits European finance teams because approval rules, budgets and AP sit in the same system as smart company cards and expense claims. Finance therefore sets the control before a purchase happens instead of reconciling it afterwards. An approver sees the budget impact of a request before approving it. The invoice arrives already linked to an approved purchase order.

Approval workflows. Spendesk’s approval workflow builder works as a tree of conditions.

• Each node can carry one or more amount thresholds (the help centre gives “Up to €5,000”, “From €5,000 to €50,000” and “Above €50,000” as examples), and each threshold holds one or more approval steps that run in sequence.

• Approvers can be a named user, the cost centre owner or the requester’s reporting manager.

• Cost centre routing is available on all plans; routing by spend type, expense category or custom analytical field depends on plan.

• If the requester is also the approver, Spendesk moves the request to the next step or to the Account Owner, so nobody approves their own spend.

• A Finance Review step after approval gives the finance team a second check before payment, and version history records who changed the workflow and when.

Delegation has limits worth knowing. Approvers delegate their own rights manually, per entity, and restore them with an “I’m back” banner. The help centre states that start and end dates cannot be scheduled.

Matching.

Accounts payable automation in Spendesk runs line-level three-way matching by default for customers using purchase orders. With Spendesk’s delivery notes, you record the goods received note against each PO line, and accounts payable automation flags lines billed but never ordered, lines billed but not delivered, and overbilled lines. Controllers see the alert and resolve it before approving payment.

Where no PO exists or the PO has no lines, matching falls back to the invoice total. An optional setting lets invoices linked to an approved PO skip budget-owner approval, provided the PO status, unbilled amount, and matching rules allow it. If your policy relies on percentage tolerances, the next step is to ask how matching handles them.

Purchase requests flow through procure-to-pay, where you can route each request by annualised spend, vendor risk level, and intake form answers.

ERP export.

Native integrations cover NetSuite, Xero, Sage 100, DATEV Unternehmen Online, Microsoft Business Central, Odoo, ACD, and Exact Online (NL, BE, and FR only), with QuickBooks Online for US companies; DATEV Kanzlei Rechnungswesen is labelled beta. Each pulls master data such as the chart of accounts, tax codes, and analytical dimensions, then exports prepared payables.

Two details matter to whoever owns the export: native integrations export each payable once, and edits made after the first export do not sync automatically. Sage 50 runs through a file import rather than a native connector. The integrations catalogue lists the data flow for each system.

Duco Technology’s close fell from up to three days to one day after it adopted Spendesk with NetSuite, as the company reports in Spendesk’s customer story. That is one implementation’s outcome rather than a benchmark.

E-invoicing and coding.

Spendesk processes XRechnung and ZUGFeRD invoices in Germany. It is a certified Peppol Access Point for Belgian companies using the AP module. It registered as a Plateforme Agréée in France on 15 January 2026, where it acts as a reception platform only. Bookkeeping automation combines deterministic coding rules with machine-learning suggestions. The accountant reviews and confirms those suggestions.

Spendesk describes standard onboarding as three to four weeks, with longer timelines possible when procurement is in scope. To see how your approval rules and ERP export would work together, book a Spendesk demo.

Best for US-focused teams with international needs: Ramp

Ramp combines bill pay, corporate cards and procurement, and its eligibility rules centre on US-registered businesses. Its help centre requires a US-registered corporation, LLC or LP with at least 25,000 USD in a US business bank account, and offers a separate path for Canadian companies.

Ramp launched in the UK in September 2026, according to Bloomberg, and it acquired the Swedish payments company Billhop to expand into Europe.

• Approval routing. Admins build Bill Pay approval workflows from conditions, approval steps, notifications and an early “approve bill” exit, layered and nested. Amount-based routing is available to all customers; conditions on entity, vendor and accounting categories require Ramp Plus.

  Changes to the vendor, amount, payment details or payment date always restart approval. Delegation is a Ramp Plus feature, with calendar-based automatic delegation during absence in beta.

• Matching. Ramp supports two-way and three-way matching. Three-way matching on POs created in Ramp needs the Procurement add-on; three-way matching on POs imported from an ERP needs Ramp Plus.

  NetSuite customers can import item receipts automatically, and Sage Intacct import is rolling out to eligible businesses.

• ERP fit. Native integrations include QuickBooks Online, Xero, NetSuite, Sage Intacct, Business Central, Acumatica and Zoho Books, with Workday, Oracle Fusion and Dynamics 365 Finance and Operations on Enterprise. DATEV and Exact Online do not appear in Ramp’s listed integrations, and the retrieved trust documentation does not state a hosting region.

Best for large complex enterprise: SAP Concur

SAP Concur, an established enterprise travel-and-expense platform, handles supplier invoices through Concur Invoice, and its integration depth with SAP ERP is the main reason to shortlist it.

Approval routing. Concur Invoice uses custom approval workflows with ordered steps, rules, and cost object approvers. Under limit-based cost object approval, an invoice goes directly to the approver whose amount limit applies, and manager hierarchies can extend up to five levels before the processor.

Delegates can be set to preview without approving, and a workflow setting decides whether delegates may approve invoices they created themselves. The documentation notes that a cost object approver can approve their own invoices, because the system does not skip that step, which is a configuration point to review with your auditors.

Matching. You can run two-way or three-way matching in Concur Invoice, using individual rules (one invoice against one PO) or life-to-date rules (all invoices against one PO). For three-way matching, you can capture receipts in Concur Receiving or import them.

Integrations. You can connect SAP ECC and SAP S/4HANA to Concur through SAP Integration with Concur Solutions. Its documentation lists Concur Invoice Professional/Premium editions only. SAP also publishes NetSuite and Xero setup guides. Microsoft Dynamics, Sage Intacct, and Oracle connections come mainly through partner connectors on the SAP Concur App Center. SAP states that customers can choose a US or EMEA hosting zone, with EMEA data on AWS in Germany.

Other options we considered

Six other tools came up repeatedly in our research. Each covers routing and matching differently, and none appears above mainly because its fit or European footprint is narrower:

• Stampli: Approval rules can evaluate up to five condition fields at once, including vendor, GL account, subsidiary and amount, and Stampli runs two-way and three-way matching at header and line level, skipping approval when a match falls within customer-defined tolerances. It connects to NetSuite and Sage Intacct by API and to SAP S/4HANA and Sage 100 through a bridge, and stores databases on AWS in Ireland.

• BILL: Approval policies can combine multiple criteria, with up to 300 active policies per account. Three-way matching requires POs maintained in NetSuite or QuickBooks, and automatic two-way sync with NetSuite, Sage Intacct and Microsoft Dynamics sits on BILL’s Enterprise tier.

• AvidXchange: Invoices can route by amount, department and GL code at header or line level, and the AvidBuy module offers two-way and three-way matching. Its integrations lean towards US sector systems such as Yardi, MRI and Rent Manager, alongside Sage Intacct, NetSuite and Dynamics 365.

• Tipalti: Bill approval rules support sequential and parallel approvers, reminders and email approval without logging in, though the help centre notes these rules do not yet cover POs or expenses. Matching covers two-way and three-way with tolerances by amount, percentage, bill or line.

• Pleo: Pleo describes multi-step review flows by team, amount or custom tags and warns when an invoice differs from its linked PO, but its own pages do not confirm three-way matching against a goods received note. Approval workflows depend on plan.

• Payhawk: A workflow designer handles bill approvals, PO approvals can route by amount, department, subsidiary, project or category, and two-way and three-way matching run on PO-linked invoices. Payhawk describes a bidirectional NetSuite sync and states that where POs are raised in SAP S/4HANA it works as an AP and expense layer.

How to choose

Start from your company’s structure and accounting system, then test routing and controls against your real approval policy. The steps below follow the order most AP teams reach these questions.

Match the tool to your size and structure

A small team with one entity and QuickBooks or Xero needs fast setup and amount-based routing more than conditional logic. A growing company with several cost centres and a local European ERP needs conditional routing, line-level matching, and native connectors to DATEV, Exact Online, or Sage. A multi-entity group needs separate policies, approvers, and accounting structures per entity, plus a consolidated view. Spendesk’s multi-entity management keeps each entity’s approval workflow distinct. Delegation, though, has to be repeated per entity.

Check the routing mechanics against your policy

Write down your current delegation of authority and test it against each tool’s builder. Check four mechanics:

• Thresholds: Confirm whether bands sit at node level, step level or as one global ladder.

• Multiple tiers: Confirm whether steps run in sequence, in parallel or as “any one of” these approvers.

• Conditions: Confirm which dimensions (cost centre, supplier, GL code, entity) your plan includes.

• Delegation: Confirm whether delegation can be scheduled, who can set it, and whether the audit history shows who approved on whose behalf.

The Intel procurement case written up by Art of Procurement shows why thresholds need monitoring: a buyer kept each invoice under her 20,000 USD approval limit so she could approve them herself, and the fraud went unnoticed for nearly a year.

Test the controls before the features

Segregation of duties is the control auditors ask about first. The Institute of Chartered Accountants in England and Wales (ICAEW) recommends clear separation between who sets up suppliers, who approves invoices, and who makes payments. For supplier bank detail changes, EY recommends call-back verification to known numbers, dual approval, and cooling-off periods. The Federal Bureau of Investigation (FBI) advises using previously known phone numbers rather than those supplied in the email request. The next step is to ask each vendor to show duplicate invoice detection, self-approval handling, the approval audit history, and who can edit supplier bank details. That shows whether the tool enforces the separation in practice. Spendesk’s security page and Trust Center hold its certification documents.

Look past QuickBooks for ERP depth

Most tools connect to QuickBooks and Xero; the differences appear with NetSuite subsidiaries, Business Central, DATEV and SAP. For each system, ask whether the connection is native, partner-built or a file export, which objects sync in each direction, and what happens when a payable is edited after export. Country limits matter too: Spendesk’s Exact Online connector covers NL, BE and FR, and its QuickBooks connector is for US companies only.

Plan the implementation around your data

Vendor timelines vary widely and almost all are vendor-advertised. Ramp’s implementation guide gives a range of two to twelve weeks. Medius states eight to twelve weeks for multi-entity AP. Spendesk describes three to four weeks as standard. Together they show how wide the spread is, from two weeks to twelve. SAP Concur lists the depth of ERP integration, the number of entities and currencies, and the volume of approval hierarchies as factors that lengthen a project. Ramp names data quality as the main blocker. A Spendesk specialist can scope modules and integrations for your structure.

Frequently asked questions

Can AP approval software route invoices by both amount and role?

Most tools combine amount thresholds with role-based approvers such as the cost centre owner or the requester’s manager. The difference lies in which other conditions your plan includes, such as supplier, GL code or entity, and whether steps run in sequence or in parallel. Test the builder against your delegation of authority before signing.

Will the software sync approved invoices to our ERP?

It depends on the connector rather than the vendor. Native integrations usually pull master data and push approved payables. Partner connectors vary in what they sync. File exports need an import step on the ERP side. Ask whether edits made after export flow back automatically, because many native connectors export each payable once.

Which controls help prevent invoice fraud?

Segregation between supplier setup, invoice approval, and payment is the foundation. Duplicate invoice detection, self-approval prevention, and an approval history that records delegated actions come next. The next step is to verify supplier bank detail changes by calling a number you already hold rather than one supplied in the email request, and to review payments that sit below approval thresholds.

How long does implementation usually take?

Vendors commonly advertise a few weeks for a single entity on a mainstream accounting system and several months for multi-entity groups with deep ERP integration. Data quality in the supplier master, the number of entities, and the complexity of your approval policy shift the timeline more than the software itself.