Almost every AP automation vendor will tell you they integrate with your ERP. What they mean by that varies enormously — and the difference between real integration and a sophisticated CSV workflow is felt immediately in month-end close, audit prep, and daily reconciliation. It's worth understanding exactly what to ask before you sign.
The test case is simple: after an invoice is approved in your AP automation system, how does that approval get reflected in your ERP's AP subledger? If the answer is anything other than "an API call writes a posted transaction directly to the ERP within seconds," you have something less than real integration. That's not necessarily a dealbreaker, but it's worth knowing what you're actually getting.
The Spectrum of "ERP Integration"
There are roughly four tiers of ERP connectivity that AP automation vendors offer, typically in ascending order of implementation complexity and operational reliability:
Tier 1 — CSV export/import: The AP tool processes invoices and approvals internally. When you're ready to post to the ERP, you export a CSV from the AP tool and import it manually into the ERP. This is the lowest tier. It requires a human to run the export, handle format mapping, and execute the import. It's error-prone, typically runs once or twice daily at best, and creates a reconciliation gap between the AP tool's view of reality and the ERP's view.
Tier 2 — Scheduled file transfer: The AP tool automates the file export on a schedule (hourly, nightly) and pushes it to a directory the ERP's import routine picks up. Still file-based, but the human step is removed. The ERP is still hours behind the AP tool's state. Not suitable for high-volume environments where same-day visibility into AP subledger balances matters.
Tier 3 — API-based sync with batching: The AP tool uses the ERP's API to push approved transactions, typically on a near-real-time schedule (every 5–15 minutes). Better than file-based, but transactions are still batched. An invoice approved at 9:03 AM might not be visible in the ERP until 9:15 AM at the earliest — and if the batch fails, there's a gap until the next scheduled run.
Tier 4 — True real-time API sync: Every significant event in the AP tool — invoice received, matched, approved, payment scheduled, payment sent — fires an API call to the ERP immediately. The ERP reflects the current state of every invoice in near-real-time. This is what enterprise-grade ERP integration looks like. It's also the most complex to implement correctly and the most sensitive to ERP configuration and API rate limits.
Most mid-market AP automation vendors operate at Tier 3. Some offer Tier 4 for specific ERP integrations. "We integrate with NetSuite" tells you nothing about which tier unless you ask specifically.
What Real-Time Sync Actually Changes
The practical difference between Tier 2 and Tier 4 isn't just latency — it changes which finance processes are possible and which remain bottlenecks.
Month-end close acceleration: In a file-based integration environment, the Controller cannot run a reliable AP aging report until the last file import from the AP tool has been processed and reconciled against the ERP. Any timing mismatch — an invoice approved at 11 PM on the last day of the month that doesn't make it into the ERP until the next morning — creates a close adjustment. With real-time sync, approved transactions post to the subledger immediately. The AP aging report in the ERP reflects the same data as the AP tool at any moment during the month, not just at close.
Vendor master synchronization: In the reverse direction — ERP to AP tool — you need vendor master data: vendor names, payment terms, bank account details, tax IDs, and AP contact information. In a file-based integration, vendor master changes in the ERP (new vendor added, payment terms updated, bank account changed) propagate to the AP tool on the next import schedule. Real-time sync means vendor changes are available in the AP tool within seconds. This matters most when a new vendor submits their first invoice and needs to be onboarded quickly.
Duplicate detection reliability: Effective duplicate invoice detection requires that the AP tool knows about all invoices already posted in the ERP, not just the ones it processed. If there are invoices manually entered in the ERP that didn't come through the AP tool, those need to be visible to the AP tool's duplicate detection logic. A file-based integration with a 24-hour sync cycle creates a window where duplicates can slip through. Real-time sync closes that window.
The GL Coding Question
One integration test most buyers overlook: how does GL coding work? Specifically, where are GL codes maintained, and how does an approved GL code assignment get into the ERP?
The best-practice answer is that the ERP's chart of accounts is the single source of truth. The AP tool fetches GL codes from the ERP at runtime — not from a static list configured during setup. When the Controller adds a new account code in NetSuite or Sage Intacct, that code is immediately available in the AP tool's coding interface without any manual synchronization step.
When this bidirectional GL code sync isn't in place, you get configuration drift: the AP tool has an old copy of the chart of accounts, and AP clerks start coding to accounts that don't exist in the current ERP configuration, or to account codes that have been deprecated and reclassified. The resulting import errors generate reconciliation work that negates much of the efficiency gain from automation.
Questions to Ask Every AP Automation Vendor
These are the specific questions that distinguish real ERP integration from marketing language:
- "When an invoice is approved, how many seconds until it appears as a posted transaction in my ERP's AP subledger?" If the answer involves a scheduled job, a batch window, or a manual step, you're below Tier 4.
- "Does your integration write to the ERP's native AP module, or does it create journal entries?" Writing native AP transactions (bills, vendor invoices) is substantially better than creating JEs — it preserves vendor-level AP aging, 1099 tracking, and AP subledger drill-down capability.
- "How are GL code changes in the ERP reflected in your AP tool?" The answer should be "in real time via API" — not "we do a weekly resync" or "you update them manually in our settings."
- "What happens when the API call to the ERP fails?" This is a reliability question. Does the AP tool queue the transaction and retry? Does it alert the AP team? Or does the transaction silently fail and create a reconciliation gap?
- "Can your system write back payment status to the ERP after a payment is sent?" Closing the loop — marking an invoice as paid in the ERP when the payment clears — is often the weakest link in AP automation integrations. Many tools handle pre-payment well and post-payment poorly.
The NetSuite, Sage Intacct, and QuickBooks Distinction
Not all ERP integrations are created equal even within a single vendor. An AP automation tool might have a native, deep integration with NetSuite and a much thinner integration with QuickBooks — because NetSuite's SuiteScript API is significantly more capable than QuickBooks Online's API for AP use cases.
NetSuite's SuiteScript 2.0 allows AP automation tools to create vendor bills, associate them with purchase orders, record item receipts, and trigger payment authorization workflows — all through native ERP objects. This is the gold standard because every action in the AP tool creates a native NetSuite transaction that behaves identically to a transaction entered directly in NetSuite.
QuickBooks Online's API is useful but more limited for complex AP workflows — particularly around purchase order management and multi-entity posting. If you're running QuickBooks in a multi-entity or multi-currency environment, understand exactly which workflows the AP tool can handle natively versus which require workarounds.
We're not saying QuickBooks integration is insufficient for all AP automation use cases — for a company with straightforward AP workflows, a QuickBooks integration that handles vendor bills, GL coding, and payment sync is entirely adequate. The point is to understand what the integration actually covers for your specific workflow before you deploy, not after.
The Implementation Reality
Deep ERP integration is also where AP automation implementation timelines live or die. A vendor that promises a 30-day implementation on a complex NetSuite environment with multi-subsidiary AP workflows and custom approval chains is either very good or very optimistic. The actual integration work — OAuth2 authentication, API scope configuration, chart of accounts mapping, vendor master import, historical transaction import for duplicate detection baseline — takes time proportional to the complexity of your ERP configuration.
Asking for a detailed implementation project plan specific to your ERP before signing is not excessive diligence — it's the right question. Any AP automation vendor with genuine experience in your ERP environment should be able to produce one. If the answer is a generic 30-day onboarding timeline with no ERP-specific details, treat that as a signal about implementation depth rather than implementation speed.
