How to Evaluate AP Automation ERP Integrations: Native, API, or File-Based

Judge an AP automation ERP integration by its type, its sync and mapping behavior, and who fixes it when it breaks. Then prove each point in a sandbox with your own data.

Every vendor on your shortlist will say it integrates with your ERP, and most will show you a page of logos. That page answers almost nothing. The integration you're buying shows its quality in month two, when a sync fails at 2 a.m., a GL mapping breaks after someone adds a department, and the vendor and your ERP partner each think the other one owns the fix.

Key Takeaways

• AP automation connects to an ERP through a native app, an API connection, or scheduled file transfers, and each type fails differently.

• The questions that separate good integrations from weak ones are sync direction, field mapping, sync frequency, error handling, and who maintains the connector.

• ERP vendors retire their own interfaces. NetSuite is removing SOAP web services in its 2028.2 release, so ask every vendor which interface its connector uses.

• Virtual cards reconcile cleanly when one single-use card pays one invoice and the card's transaction data posts against that bill.

• The best ERP integration is the one that passes a sandbox test script on your ERP, not the one with the longest logo list.

What are the types of AP automation ERP integrations?

AP automation ERP integrations come in three types. A native integration is built into or certified for the ERP, an API integration connects through the ERP's web services from the vendor's side, and a file-based integration exchanges flat files over SFTP on a schedule.

The type matters because integration is still where most software projects stall. The average enterprise manages 897 applications, and only 29% of them are integrated, according to the 2025 MuleSoft Connectivity Benchmark Report. AP is usually one of the integrations that gets done, because the ledger demands it, but how it gets done decides how much manual work survives.

Most vendors use more than one type, depending on the ERP. Corpay offers 100+ ERP integrations, including NetSuite, Sage Intacct, Business Central, and Acumatica, and a vendor with that range should be able to tell you exactly which type it uses for your ERP and version. If the answer is vague, ask to speak with the person who maintains that connector.

Is a native integration always better?

No. A native integration is usually faster and easier to set up, but "native" describes where the code runs, not how well it handles your data.

Native apps run inside the ERP, so they inherit ERP permissions and show up in the ERP's own audit log, which auditors like. They also depend on the vendor keeping pace with the ERP's release schedule. A well-built API integration that syncs every few minutes and logs every error can beat a native app that can't see your custom segments. Treat "native" as one fact about the connector, then keep asking the questions below.

When is a file-based integration the right call?

A file-based integration is the right call when the ERP is on-premises, heavily customized, or doesn't expose the records you need through its web services. It's slower, but it's predictable and easy to audit.

The weakness is silence. When an API call fails, it returns an error. When a file doesn't arrive, nothing happens unless someone built an alert for the missing file. File formats also change underneath you. The Federal Reserve moved the Fedwire Funds Service to the ISO 20022 message format on July 14, 2025, retiring its older proprietary format, according to its 2025 Fedwire Funds PFMI Disclosure. Any payment file your AP process produces lives on a format someone else controls, so ask who updates the file layouts when the bank or network changes them.

What should you check in any ERP integration?

In any ERP integration, check which records sync in each direction, how fields map, custom fields and dimensions included, how often it syncs, how errors are surfaced and fixed, and who maintains the connector. Those five predict more about your first quarter live than any feature demo.

The pain buyers describe after go-live is almost always one of them. In reviews, users of AP platforms complain about "syncing issues between NetSuite and the platform" and "manual entry challenges due to syncing issues leading to confusion and inefficiencies." Neither complaint is about missing features. Both are about a sync that nobody could see failing.

Here's what to ask for each:

• Sync direction. A record-by-record list showing whether vendors, invoices, purchase orders, GL accounts, and payments move one way or both ways

• Field mapping. Whether the connector reads your custom fields, segments, and dimensions, and who changes the mapping when you add one

• Sync frequency. Real time, every few minutes, or a nightly batch, and whether you can trigger a sync manually before close

• Error handling. Where failed records go, who gets alerted, and whether a failed record blocks the rest of the batch

• Maintenance owner. Whether the vendor, your ERP partner, or your team fixes the connector when the ERP changes

Which data should sync in each direction?

The ERP should own master data and purchasing records, and the AP platform should own invoice approval and payment execution, with each record syncing one way from its owner. Problems start when both systems can edit the same record and nobody decided which one wins.

Vendors are the usual battleground. If AP staff can add a vendor in the platform and someone else can add the same vendor in the ERP, you'll get duplicates, and duplicate vendors are how duplicate payments start. Decide on one system of record for vendors, GL accounts, and purchase orders before go-live. Purchase orders and receipts also need to reach the platform intact for three-way matching to work, so check that partial receipts and PO line changes sync, not just the PO header.

Multi-entity ERPs add a layer. A connector that handles one subsidiary well may still post intercompany bills to the wrong entity, which is why companies running NetSuite across multiple subsidiaries should test with at least two entities from day one.

Who maintains the connector when the ERP changes?

The vendor should maintain the connector and commit, in writing, to supporting new ERP releases on a stated timeline. ERP vendors retire their own interfaces, and a connector that isn't maintained stops working on the ERP's schedule, not yours.

That isn't hypothetical. Oracle's SOAP Removal Plans FAQ says NetSuite's 2025.2 SOAP endpoint is the last planned one, that new SOAP integrations can't be built from the 2027.1 release, and that with 2028.2 all SOAP endpoints are disabled and SOAP-based integrations stop working. The same FAQ says new integrations from 2027.1 must use OAuth 2.0 rather than token-based authentication. Microsoft made a similar move earlier. Integrations that connected to Business Central online with web service access keys stopped working after October 1, 2022, and Microsoft's list of deprecated Business Central features shows Microsoft pages can no longer be exposed as SOAP endpoints in version 29.0 or as OData endpoints from version 30.

So ask which interface and authentication method the connector uses for your ERP today, and what the vendor's plan is for the next deprecation. A vendor that answers with dates is maintaining its connector. A vendor that answers "we're fully integrated" probably hasn't looked.

A common break comes when an ERP partner adds a required custom segment to the chart of accounts. Every bill the platform tries to post fails validation, the errors land in a queue nobody was told to watch, and AP finds out days later from a vendor asking about a late payment. The connector works exactly as designed. Nobody owns the change. If you're changing ERPs at the same time, the questions get sharper, and an ERP migration is the worst time to discover who owns the connector.

How do virtual cards reconcile with ERP systems?

Virtual cards reconcile with an ERP when each card payment carries the invoice reference and the card transaction posts against the matching bill automatically. A single-use card issued for one invoice makes that match one to one.

The mechanics are simpler than card statement reconciliation. The AP platform issues a card number for an approved bill, the supplier charges it, and the transaction comes back with the card number, amount, and reference, so the platform marks the bill paid and posts the payment to the right GL account. Corpay issues single-use virtual cards tied to one payment, so there's no monthly statement to pick apart. Richer transaction detail, such as the Level 2 and Level 3 card data some suppliers send, helps with line-level coding but isn't required for the match. The step-by-step posting flow is in this guide to virtual card ERP integration.

Check that card payments and bank payments land in the ERP the same way. Most suppliers still get paid by ACH, which carried close to 8.1 billion B2B payments in 2025, up almost 10%, according to Nacha, out of 35.2 billion ACH payments worth $93 trillion across the whole network. If cards post in real time and ACH posts in a nightly file, your payment reconciliation runs on two clocks, and month-end will show it.

How do you test an ERP integration before you buy?

Test an ERP integration in a sandbox connected to a copy of your ERP, using your own vendors, GL accounts, and dimensions, and run a script of normal and broken transactions. Ask the vendor to run it with you, live, rather than showing a prepared demo.

A sandbox script that catches most problems:

1. Create a vendor in the ERP and confirm it appears in the platform, then edit it in the platform and see what happens in the ERP.

2. Run a PO-backed invoice with a partial receipt through matching and approval, and check the bill that posts.

3. Code a non-PO invoice across two departments and a project, and check every segment in the posted bill.

4. Add a new GL account or dimension value in the ERP and see how long the platform takes to pick it up.

5. Force a failure by posting to a closed period, and find where the error appears and who's alerted.

6. Pay one bill by virtual card and one by ACH, and confirm both post with the right dates and accounts.

7. Void a payment and check that the ERP reverses it cleanly.

Step 5 is the one vendors least like to run, and it's the one that tells you the most. A sandbox won't tell you how the connector behaves at 4,000 invoices on the last day of the quarter, and I don't know of a good way to test that before you're live. Ask for a reference customer on your ERP at roughly your volume, and build time for this testing into your AP automation implementation timeline.

Which AP automation platform has the best ERP integrations?

The platform with the best ERP integrations is the one whose connector for your specific ERP passes your test script, has a named maintainer, and has a written plan for your ERP's next interface change. There isn't a universal winner, because connector quality varies by ERP, even within one vendor.

A vendor can have an excellent NetSuite app and a weaker file-based link to an on-premises system, so evaluate the connector for your ERP, not the vendor's average. Each ERP has its own quirks worth reading up on before the demo:

• NetSuite AP automation, where SuiteTalk REST and OAuth 2.0 are the interfaces to ask about

• Sage Intacct AP automation, where dimensions drive most mapping questions

• Dynamics 365 AP automation and Business Central AP automation, where Microsoft's list of deprecated features is worth reading first

• Acumatica AP automation in practice, where native limits shape what a connector has to add

The same reasoning applies to virtual card programs. The best card for ERP integration is the one whose transactions post against your bills without a person in the middle.

Connect Corpay to the ERP you already run

The integration questions above come down to whether your ERP stays the system of record while AP work moves out of it. That's the job Corpay is built to do.

Corpay AP automation connects through 100+ ERP integrations, including NetSuite, Sage Intacct, Business Central, and Acumatica, so approved bills and payments post back to the ledger you already run. Corpay pays suppliers by virtual card, ACH, or check from one approval flow, and Corpay virtual cards are issued as single-use cards that match one-to-one with the bills they pay. With Corpay's fully managed AP, supplier enrollment and payment follow-up are handled for you, AP teams save about 40% of the time they spend on processing, and most customers are live in weeks.

Frequently Asked Questions

How do you integrate AP automation with an ERP?

You integrate AP automation with an ERP through a native app, an API connection, or scheduled file transfers. Set the system of record for vendors and GL accounts, map your fields and dimensions, test in a sandbox, and assign someone to watch the error queue after go-live.

What is the difference between a native and an API integration?

A native integration runs inside the ERP as an installed app under ERP permissions. An API integration runs on the vendor's servers and calls the ERP's web services with stored credentials or tokens. Both can work well, so judge them on sync, mapping, and error handling.

How often should AP automation sync with the ERP?

AP automation should sync master data and approved bills at least every few minutes, or on events, during the working day. Nightly batches can work for low volume, but they push exceptions to the next morning and make close harder.

What is the best B2B virtual card with ERP integration?

The best B2B virtual card for ERP integration issues a single-use card per invoice and posts each card transaction against the matching bill in your ERP automatically. Test it in a sandbox with your own ERP before choosing.

What happens to the integration when the ERP is upgraded?

When the ERP is upgraded, the vendor should update and retest the connector before the upgrade reaches your environment. Ask for the vendor's support policy for new ERP releases in writing, including how it handles retired interfaces.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation

Virtual Card