ERP coexistenceImplementation-scoped

Connect Exact ERP to an AI-first operating layer

Keep Exact authoritative for the finance and ERP records it already owns while SOBERAN coordinates selected operational workflows across systems and channels.

A SOBERAN–Exact implementation starts with one operating outcome and the Exact product in use. Exact publishes REST and XML APIs plus webhook support; the available objects, company divisions, permissions, custom fields, sync cadence, and allowed writes are confirmed before production.

01

Typical Exact data mapping

The implementation contract names the owner, direction, identity key, cadence, and permitted action for every object.
ObjectSourceDestinationPurpose
Account and contactExactCustomer or supplier context

Resolve identity across commercial, purchasing, service, and collections workflows.

Item, warehouse, and stockExact or WMSPlanning context

Support availability, allocation, and replenishment decisions.

Sales and purchase documentsExactOperating workflow

Coordinate orders, suppliers, delivery commitments, and exceptions.

Approved outcomeSOBERANAuthorized Exact record

Return only a permitted status, activity, or transaction after policy checks.

02

A practical Exact coexistence workflow

  1. 01

    Choose one operating result

    Start with replenishment, order exceptions, purchase follow-up, service, or collections.

  2. 02

    Inventory the Exact environment

    Confirm Exact Online or Globe+, country edition, company divisions, modules, add-ons, custom fields, and interfaces.

  3. 03

    Validate read quality

    Reconcile IDs, units, balances, states, timestamps, and document counts before enabling action.

  4. 04

    Activate governed writeback

    Enable approved writes gradually with least privilege, idempotency, thresholds, evidence, and rollback.

03

Exact integration controls

Product and country boundary

Document the Exact product, country edition, modules, divisions, and available integration surface.

Least-privilege access

Restrict credentials to the divisions, objects, and actions included in scope.

Identity and idempotency

Use durable Exact IDs, external references, duplicate checks, and replay-safe writes.

Approval and reconciliation

Keep spending, credit, and accounting-sensitive actions behind policy and reconciliation.

04

Exact integration checklist

  1. Exact product, country edition, company divisions, modules, and environments
  2. REST or XML API, webhooks where applicable, authentication, and limits
  3. Objects, custom fields, add-ons, ownership, units, and identity keys
  4. Read cadence, events, allowed writes, approvals, retries, and exceptions
  5. Reconciliation, monitoring, audit evidence, rollback, and support owner

05

Best fit

  • Teams retaining Exact for accounting, wholesale, manufacturing, or project administration
  • Inventory-heavy operations adding cross-system agents without forcing an ERP replacement
  • Businesses connecting Exact records to CRM, suppliers, WhatsApp, voice, service, or commerce channels

Frequently asked questions

Does SOBERAN replace Exact?

Not by default. Exact can remain the financial or transactional system of record while SOBERAN coordinates a scoped operational workflow. Replacement is evaluated separately.

How can SOBERAN connect to Exact?

Exact publishes REST and XML APIs and supports webhooks. The exact route depends on Exact Online or Globe+, the country edition, modules, permissions, and objects required.

Can SOBERAN coordinate inventory and orders around Exact?

Yes, when the required item, warehouse, stock, customer, supplier, and document data is available. Writes remain limited to agreed actions and controls.

Does Exact already have AI agents?

Exact now markets AI Agents and an AI Assistant inside Exact Online. Buyers should compare the specific workflows, products, regions, controls, and cross-system reach required rather than assuming either platform has no AI.