Enterprise use case · Amazon Seller + NetSuite + Xero
Marketplace sales to accounting
Marketplace activity, ERP invoices and bank deposits are reconciled in spreadsheets. Marketplace activity is reflected in NetSuite and reconciled in Xero, with differences approved by finance.
Systems involved
What each system contributes
10 actions
- FBA5
- FBM5
38 actions
- Invoices10
- Items10
- Base8
41 actions
- Invoices13
- Payments8
- Bank Transactions10
Amazon Seller pre-built actions cover FBA and FBM fulfilment operations. Marketplace data outside those actions is read through the Amazon Selling Partner API and normalized in Rules + Code. No Amazon trigger is used: a schedule, HTTP poll or webhook starts the run. Settlement and fee data outside FBA and FBM actions comes through the same API.
Architecture
One governed run
How it starts: A schedule starts the run, typically per settlement period.
Step by step
How the process runs
- 01
Marketplace activity
FBA and FBM actions return fulfilment context for the period.
- 02
ERP context
NetSuite invoices and items are read or created for the same period.
- 03
Reconcile
Rules + Code compares totals with Xero invoices, payments and bank transactions.
- 04
Exceptions
Differences above tolerance wait for finance.
Control
Human decision and exception path
Human decision
Finance approves any adjusting entry before it is written to Xero.
Exception path
- Unmatched deposits route to finance.
- Duplicate entries are blocked.
- Partial periods are held until complete.
Evidence
What gets audited
- Period data.
- Reconciliation result.
- Approval.
- NetSuite and Xero references.
Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- Shopify-NetSuite integration
Integration pattern · Storefront orders and inventory stay aligned with ERP invoicing and items.
- Stripe-Xero integration
Integration pattern · Billing events become reconciled accounting entries with exceptions reviewed.
- Amazon Seller connector
10 pre-built actions
- NetSuite connector
38 pre-built actions
- Xero connector
41 pre-built actions
- Compliance evidence
Evidence produced by the work itself.
- Order to cash across CRM, ERP and billing
Another enterprise use case.
FAQ
Questions about this use case
- Does Nexus replace any of these systems?
- No. Each system keeps its own records. Nexus runs the process between them and records each decision.
- How does the run start?
- A schedule starts the run, typically per settlement period.
- What if a step is not covered by a pre-built action?
- Amazon Seller pre-built actions cover FBA and FBM fulfilment operations. Marketplace data outside those actions is read through the Amazon Selling Partner API and normalized in Rules + Code. No Amazon trigger is used: a schedule, HTTP poll or webhook starts the run. Settlement and fee data outside FBA and FBM actions comes through the same API.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.