Platform · How it works
One platform, managed connections, and governed AI
Every APIXX Connected App runs on one shared foundation — one identity and permission model, one canonical object model, and one connector fabric that keeps integrations alive after go-live.
- Supplier Collaboration
- Export Compliance
- Order Manager
APIXX platform
One core, shared by every app
- Identity & permissions
- Canonical objects
- Tasks & approvals
- Documents & evidence
- Audit history
- Search & dashboards
- Rules & tenant policy
- Exception center
- ERP
- Ecommerce
- WMS
- 3PL
- Finance
- Systems of record stay authoritative — only approved outcomes write back
- Every action is audited and attributable to a person, a supplier, or a service
- Tenant policy governs data, retention, and access per customer
- AI proposes; deterministic services execute; humans approve anything consequential
The connector fabric
Connections we operate, so you do not have to
We handle authentication, schema drift, retries and reprocessing, and monitor every flow after go-live. Only approved outcomes write back.
Your system
Stays the system of record
Managed connector
- Auth handled
- Monitoring
- Retries
- Reprocessing
- Schema drift
Canonical objects
Approved outcomes write back
Shared services
One platform for every app
Identity, roles, permissions, canonical objects, tasks, approvals, documents, audit, search and tenant policy — built once, reused across the portfolio.
- Organization, location, user and counterparty model
- Identity, roles and granular permissions
- Canonical product, customer, supplier, order, PO, shipment and inventory objects
- Tasks, work queues, approvals and escalation
- Documents, attachments and structured evidence
- Rules, policies and configurable business logic
Managed integrations
Connectors that stay connected
Pre-built connectors, tenant-scoped flows, synchronization, monitoring and reprocessing — configuration, not custom code.
- Pre-built connectors to ERP, ecommerce, WMS, 3PL and finance systems
- Tenant-scoped flows with monitoring and automatic reprocessing
- Systems of record stay authoritative; only approved outcomes write back
- No customer-specific forks — configuration, not custom code
Governed AI
AI assists, humans approve
AI summarizes exceptions, extracts document data, suggests classifications and explains holds. Consequential changes always wait for a person.
- Summarizes supplier, order, inventory and compliance exceptions
- Extracts structured data from documents
- Suggests classifications and mappings with source evidence
- Recommends replenishment and allocation actions
- Explains why a transaction is held
- Requires human approval for consequential compliance, financial or inventory changes
- 1
AI proposes
Summarizes exceptions, extracts document data, suggests classifications.
- 2
Evidence attached
Every suggestion carries its sources and a confidence, not a bare answer.
- 3
Human approves
A person signs off on anything consequential — compliance, financial, inventory.
- 4
Service executes
Deterministic services apply the approved change and record the outcome.
Prompts, sources, recommendations, approvals and outcomes preserved in the audit history
Integration · How it works
Sage Intacct: in beta with design partners
Sage Intacct stays your system of record. APIXX adds the workflow between it and your suppliers — your processes, approvals, and close are unchanged.
Sage Intacct
Your system of record
Connected Apps
Connection layer, workflow, rules & exceptions
Setup
Five steps, a scoped partner rollout
We scope setup around your systems, approvals and supplier base. Design partners work with us through connection checks and a focused pilot.
- 01
Connect
Scoped with youCreate a Web Services user in Sage Intacct with the permissions we list. Paste the credentials into APIXX.
We validate the connection immediately and tell you exactly what is missing, if anything is.
- 02
Sync
After connection checksWe read your vendors, purchase orders, and payment records.
Nothing is written back at this stage — the connection starts read-only.
- 03
Configure
One sittingSet your branding, required onboarding fields, confirmation deadlines, and who gets which alerts.
Suppliers see your company's name and logo, not ours.
- 04
Invite
Your paceStart with ten suppliers or your whole base. Invitations go out under your company's name.
Track who has accepted, who needs a nudge, and who is live.
- 05
Run
Day oneOrders flow, confirmations come back, exceptions surface.
Your Intacct workflows, approvals, and period close are unchanged.
Data flow
What moves, and in which direction
Reads are broad so the workflow has context. Writes are narrow, staged, and gated by your approval.
We read from Intacct
- Purchase orders & lines
- Vendor records
- Payment status
- Company & GL context
Read-only at connect. Stays read-only where you want it.
Writes back — only approved
- Invoice drafts — posted only on your approval
- Confirmations & commit dates from suppliers
- Advance shipment notices, staged for review
- Vendor profile change requests, verified by you
Everything arrives as a draft. Nothing posts itself.
The narrowest permission set that works
APIXX connects through a dedicated Intacct Web Services user you create and control. We publish the exact permission list before you connect, and you can revoke access at any time from Intacct.
No shared logins, no screen scraping, no access to anything outside the list.
- Accounts PayableRead
- PurchasingRead
- Vendor recordsRead
- General LedgerRead
- Cash ManagementRead
- CompanyRead
Control
Sage Intacct stays in charge
APIXX never posts on its own. Every supplier response follows the same path: draft, approval, write-back.
- 01
Draft in APIXX
Supplier responses arrive as staged records — confirmations, dates, invoices.
- 02
Your team approves
You review, edit, or reject. Rules can auto-approve the routine cases.
- 03
Posts to Intacct
Only approved results are written back, with a full audit trail on both sides.
- Purchase orders and lines read directly from Intacct
- Invoices created as drafts, posted only on your approval
- Vendor profile changes applied only after your verification
- Full audit trail on every action, on both sides
- Connects with your Intacct Web Services user — no rebuild of your workflows
Your accounting system, today or next
Sage Intacct is in beta with design partners. Xero, QuickBooks Online, SAP Business One, Acumatica and Microsoft Dynamics 365 Business Central are on the roadmap — in that order. Running one of these? Design partners shape the connector and get priority onboarding.
- On the roadmap
Xero
Purchase orders, bills, contacts
- On the roadmap
QuickBooks Online
Purchase orders and bills
- On the roadmap
SAP Business One
Purchasing and AP documents
- On the roadmap
Acumatica
Purchase orders and receipts
- On the roadmap
Microsoft Business Central
Purchasing and payables
- Beta
Sage Intacct
Beta — live with design partners
Every connection works the same way: your accounting system stays the system of record, and nothing posts without your approval. Logos are the property of their respective owners and do not imply endorsement.
The bigger picture
This page covers the connection setup. For what a connected process looks like end to end — anatomy, examples, and when it fits — see Connected processes.
Connect a sandbox in a working session
We connect to a sandbox or walk your open PO list. Your data stays yours.