In short

Most tools read your ERP. Nexus writes back.

The ERP Bridge is how Nexus connects to the systems you already run. Every connector is governed by a configuration-driven registry that holds the field mappings, sync frequency, authentication and retry policy, so adding a source is configuration rather than a project. Connections are bi-directional where the system allows: validated records are written back to the ERP, the vendor master is de-duplicated across systems of record, and purchase order amendments are cascaded to every open transaction.

Sources

What it connects to

Ten pre-built source channels, each governed by the same connector registry.

Oracle ERP

AP and finance. REST API, OAuth 2.0, bi-directional, real time.

SAP Ariba

Procurement. REST API with an API key, bi-directional, scheduled.

Coupa

Invoice management. Webhook with OAuth 2.0, push events.

NetSuite

SuiteQL REST with OAuth 1.0a, bi-directional.

EDI gateway

AS2, ANSI X12, with the 810, 850, 855, 856, 820 and 997 transaction sets.

Email, cloud storage and custom APIs

IMAP/SMTP with attachment extraction; Google Drive, SharePoint, Box and OneDrive by folder watch; inbound REST with HMAC authentication for anything else.

What you get

The output

Not a one-way read. Records validated in Nexus go back to the system of record.

Validated write-back

Approved invoices published as AP vouchers into Oracle and SAP, with rollback if the write fails.

Golden record

Records published bi-directionally, so the ERP and Nexus agree on what was approved.

One vendor master

Vendors de-duplicated across every system of record that holds them.

Amendments cascaded

A purchase order amendment applied to every open transaction that hangs off it.

Questions

Common questions

Do we need middleware?

No. Each source connects directly through the connector registry. There is no middleware layer at any phase of the rollout.

Does our ERP need customising?

No. Nexus uses the interfaces your ERP already exposes. Nothing inside the ERP is modified.

What happens if a write to the ERP fails?

It is rolled back, so the ERP is never left holding a partial record.

Which EDI transaction sets are supported?

810 invoices inbound, 850 purchase orders outbound, 856 advance ship notices and 855 PO acknowledgements inbound, 820 remittance outbound, and 997 functional acknowledgements in both directions.

Related

Keep reading

Nexus overview

How the reconciliation engine works end to end, from intake to close.

AP & Three-Way Match

Purchase order, receipt and invoice reconciled before payment.

Security & trust

Encryption, access control, audit trail, and an honest account of what we are compliant with.

Which of your systems would Nexus read first?

Tell us where your documents and records live. We will show you how they connect, with nothing to customise.

7-day free trial · Card required before the trial ends · No migration