Connections, mappings, jobs and external IDs always include tenant identity.
Accounting · ERP · Warehouse
Accounting and warehouse integrations, with operational control.
Nyoma’s Sales foundation is ready to exchange trusted data with external systems without duplicating invoices, overwriting financial history, or guessing who owns inventory.
Readiness varies by provider. QuickBooks Online has a local sandbox connector but is not production approved. The other names below are catalogue candidates. Catalogue presence does not mean a live connection is enabled by default.
Nyoma SalesOrders · delivery · returnsAccountingInvoices & receivablesQuickBooks · Xero · Sage
WarehouseAllocation & shipmentFishbowl · custom WMS
ERPMulti-domain authoritySAP · NetSuite · Odoo
11normalized data domains
Per tenantsource-of-truth decisions
Idempotentretry-safe execution
Auditedconnection and workflow changes
Provider catalogue
Start with the systems you already run.
The catalogue defines where each provider fits. A production adapter is enabled only after its exact API, version, permissions and business actions are verified.
| Provider | Status | Current scope and limits |
|---|---|---|
| QuickBooks Online | Beta · local sandbox | OAuth and selected customer, product and accounting record sync tested in a development sandbox. Invoice export has not completed live sandbox acceptance; production activation is pending. |
| Xero, QuickBooks Desktop, Zoho Books, Sage, FreshBooks, Wave, TallyPrime | Planned | Catalogue entries only; no production connection is promised. |
| Fishbowl, Zoho Inventory, Custom WMS | Planned | Warehouse workflows require adapter work and customer acceptance. |
| Oracle NetSuite, SAP, Microsoft Dynamics 365 Business Central, Odoo | Planned | ERP capabilities depend on provider edition, permissions and a tested implementation. |
A
Accounting
Invoices, payments, credits and receivables.
QuickBooks OnlineQuickBooks DesktopXero
Zoho BooksSage IntacctSage 50cloud
FreshBooksWave AccountingTallyPrime
W
Warehouse & inventory
Products, stock, allocation and shipments.
FishbowlZoho InventoryCustom WMS
E
ERP across multiple domains
One tenant connection can serve accounting and warehouse capabilities when the provider supports both.
Oracle NetSuiteSAP Business OneSAP S/4HANA
Microsoft Dynamics 365 Business CentralOdoo
Operational boundaries
Designed for the real order lifecycle.
Nyoma keeps amendments, deliveries, returns and financial corrections distinct, then respects whichever connected system is authoritative.
| Configuration | System flow | Control |
|---|---|---|
| No integrations | Excel or manual data → Sales Order → approval → delivery → POD | No unsupported inventory or accounting assumptions |
| Accounting only | Nyoma Sales → accounting provider for financial records | Original invoices remain; returns use credit memos |
| WMS + accounting | Nyoma order → WMS execution → existing accounting flow → Nyoma POD | No duplicate shipment or invoice posting |
| Single ERP | One provider connection serves approved capabilities | Ownership remains explicit per data domain |
| Provider outage | Order stays safe → retry queue → reconciliation | Stable idempotency keys prevent duplicate actions |
CustomersProductsPricingInventory
WarehousesSales ordersInvoicesPayments
ReceivablesReturnsShipments
Built-in controls
Connections fail closed, not creatively.
Provider actions are allowed only when the installed adapter declares the capability and confirms current external state.
Secrets stay server-side and never appear in browser payloads, logs or mapping files.
Nyoma, Excel, manual process or external provider is selected independently for each domain.
Provider IDs and reviewed alternate identifiers are used instead of matching by display name.
Jobs are idempotent, errors are normalized and outages remain visible and retriable.
Invoiced orders follow return, reversal and credit paths instead of historical edits.
Provider activation
Four gates before production.
- 01Scope
Choose data owners, directions, business actions and the authoritative workflow.
- 02Authorize
Provide a sandbox and least-privilege service account through an approved secret channel.
- 03Map & test
Verify external IDs, tax/UOM semantics, state transitions, retries and reconciliation.
- 04Accept
Run agreed scenarios, capture sign-off, then schedule a controlled production enablement.
Documents & prerequisites
Bring these to the integration review.
These documents keep technical access, business ownership and acceptance decisions explicit.
PRINT
Integration onboarding checklistRequired contacts, environments, credentials, mappings, testing and sign-off.
CSVData ownership worksheetChoose the source of truth and sync direction for every supported domain.
CSVExternal ID mapping templatePrepare stable customer, product and provider identifiers for validation.
WEBSecurity overviewTenant isolation, encryption, access control, audit logging and availability.
LEGALPrivacy PolicyHow Nyoma processes and protects customer and workforce data.
LEGALTerms of ServiceService, account, data ownership and support terms.
Never email API secrets or production passwords. The onboarding checklist records who owns access, but actual credentials must be entered only through the approved secure setup process.
Official references
Provider documentation used during scoping.
Version, plan and API availability are confirmed against the customer’s actual provider account before any capability is enabled.
Next step
Review your systems before connecting them.
Tell us which provider, version and workflow you run. We’ll confirm prerequisites and define a safe activation plan.
Request integration review →