Native API vs Middleware: What Breaks in Practice

Every FP&A platform's marketing site says "integrates with Sage Intacct," or "integrates with NetSuite" or "integrates with QuickBooks." The word "integrates" does enormous work in those sentences. It can mean three completely different things, and the difference is the difference between a system that runs itself and a system that breaks every two weeks.

This is the technical due diligence piece. Bring your IT lead.

‍

Three integration architectures, ranked

1. Native API (best)

The FP&A platform's backend speaks directly to the ERP's REST API. There's no third-party connector, no scheduled job that batches data, no file transfer. Actuals can flow on a sub-minute cadence. Schema changes in the ERP (new accounts, renamed dimensions) propagate automatically. The integration code is owned by the FP&A vendor and version-controlled with their releases.

Detectable by: continuous API call logs, sub-minute data freshness, no "integration tier" pricing for the connector itself.

2. Middleware (acceptable for simple cases, fragile for complex ones)

A third-party connector — Workato, Boomi, Mulesoft, or a custom ETL — sits between the ERP and the FP&A platform. The middleware polls the ERP on a schedule (usually hourly or nightly), transforms the data, and pushes it into the FP&A platform.

This works for steady-state operation. It breaks when:

• The ERP adds a new field. Middleware mappings have to be updated; until they are, the new field is invisible to the FP&A platform.
• The middleware connector has an outage. Your FP&A platform shows stale data with no warning.
• The schema transform loses information. Dimensions get flattened in transit.
• The middleware vendor changes their pricing or shuts down. (This has happened multiple times in the last decade.)

Detectable by: extra subscription cost on the integration, hourly or nightly sync windows, a "data freshness" indicator in the platform UI.

3. CSV / file import (sold as "integration" — it isn't)

Someone — usually you — exports a file from the ERP on a schedule and uploads it to the FP&A platform. Or the FP&A platform pulls a file from an SFTP location that the ERP drops nightly. The platform parses the file and updates its actuals.

This is what FP&A integrations looked like in 2008. Some platforms still ship this in 2026 and call it integration. It breaks when:

• Someone forgets to run the export.
• The file format changes.
• Anything in the data is malformed.
• You add a dimension to the ERP — the file format doesn't include it.

Detectable by: an "upload data" button in the FP&A platform UI, a daily or weekly cadence, no API documentation from the FP&A vendor for the ERP in question.

‍

The 24-hour rule: how to spot middleware in a sales call

Ask: "In your platform, if I post a journal entry in [Sage Intacct / NetSuite / QuickBooks] right now, how long until it shows up in your model?"

• Native API: "Within a minute." Or sometimes: "Real-time."
• Middleware: "Within the next sync window — typically every X hours."
• CSV: "Tomorrow morning, after the overnight import runs."

If the answer is anything other than near-real-time, ask the follow-up: "What sits between Sage Intacct and your platform?" Listen for the names of third-party connectors. Listen for vague language like "our integration framework" or "our data pipeline."

‍

Failure modes by architecture

Native API failures

Native API integrations fail in two ways: the ERP's API has an outage (rare, well-documented, recoverable), or the FP&A vendor introduces a bug that breaks the sync (debuggable inside one vendor's stack). Both are fast to fix because the responsibility is unambiguous.

Middleware failures

Middleware has three potential failure surfaces: the ERP API, the middleware vendor, and the FP&A vendor. When something breaks, the first 48 hours go to figuring out which one. You're often dependent on a middleware support contract you didn't know you had.

Also: middleware versions get out of sync. The middleware vendor upgrades; the FP&A vendor's mapping is still on the old schema; data flows but is corrupt. This is sometimes invisible for weeks because the values look plausible.

CSV-import failures

Everything breaks. The file isn't there. The file is malformed. The file has 247 rows when it should have 248. Someone changes the column order. Someone uses a different date format. The export schema diverges from what the importer expects because nobody documented the contract. Half of these only surface at month-end close.

‍

What to ask a vendor before signing

1. Is the integration native, middleware-based, or file-based?
2. If middleware: who owns the middleware contract — you, us, or a third party?
3. What's the sync cadence in production today, across your existing customers?
4. What happens when the ERP adds a new field — automatic pickup or manual ticket?
5. Do you write back to the ERP, or read-only? (Most FP&A platforms should be read-only. Write-back is rare and usually a tell that the integration is bespoke.)
6. Show me your API call log against a real Sage Intacct customer. A vendor who can show this on the spot is native. A vendor who needs to "get back to you" is something else.

‍

Centage's integration architecture

Centage runs native API integrations to every supported ERP — QuickBooks (Online + Desktop), Sage Intacct, NetSuite, Microsoft Dynamics 365, Acumatica, SAP Business One, and Blackbaud. No middleware. No CSV imports. No third-party connectors in the dependency graph.

The AI-Powered Automations handle the integration mapping itself. When you connect a new ERP, Centage's AI reads the full structure — accounts, dimensions, hierarchies — and builds the mapping automatically in minutes. New accounts and dimensions added in the ERP after Centage goes live appear on the next sync without a support ticket.

If your current FP&A platform has you doing CSV uploads or running a middleware job at 2 am, the difference is going to be immediate. 

Get a demo or check out our AI-Powered Automations page.

‍

Frequently Asked Questions

How does Centage integrate with Sage Intacct technically?

Native REST API. Centage calls Sage Intacct's published API directly, on a sub-minute cadence. No third-party connector, no scheduled file transfer, no middleware subscription.

What happens when Sage Intacct adds new fields?

The native integration picks up new accounts, dimensions, and dimension values on the next sync. The AI-Powered Automations re-evaluate the mapping when changes appear and surface conflicts before they become errors.

How often does Centage pull actuals from Sage Intacct?

Continuously. There's no nightly window — Centage polls the API at a cadence appropriate to your data volume, typically every few minutes.

Does Centage write back to Sage Intacct?

No. Centage is read-only against the ERP. Your books stay clean; planning data lives in Centage.

What if my ERP isn't on the supported list?

Centage has API support for custom integrations beyond the standard seven. Talk to a Centage Advisor — most customer ERPs that aren't on the list can still be integrated natively.