Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Marketplace · Finance
Connect Sage Intacct + Amazon Seller Central
Automate marketplace sale, refunds and returns, fees (referral, fba, storage, advertising as agreed), settlement / payout, reserves and adjustments between Sage Intacct and Amazon Seller Central — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects Sage Intacct and Amazon Seller Central.
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between Sage Intacct and Amazon Seller Central, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
This page is for finance teams closing in Sage Intacct while selling on Amazon as a third-party seller, including FBA.
What needs to be in place
- An Amazon Seller Central account with API access, and the marketplaces you sell in identified.
- Sage Intacct with API access and a service user permitted to create the transactions in scope.
- Agreed accounts for marketplace revenue, each fee category, refunds, reserves and settlement clearing.
- A finance owner for posting grain and fee-mapping decisions.
When you may not need this
If Amazon is marginal and a manual settlement journal satisfies your auditors, hold off. This pays for itself when settlement variance becomes hard to explain, when FBA fee categories multiply, or when close depends on someone downloading reports by hand.
What is out of scope
- This page covers third-party Seller Central activity. Amazon wholesale (Vendor Central) is a different document flow — see the Vendor Central page.
- Marketplace-facilitator tax determination stays with your advisors; we post to the codes you nominate.
- Which settlement reports and financial event data are available for your account is confirmed in scoping.
What actually moves, and who owns it
A representative Amazon-to-Intacct posting scope. Objects and cadence are agreed before build.
Sage IntacctAPIWORX (mapping, retries, exception queue)Amazon Seller Central
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Marketplace sale | Amazon Seller Central | Sage Intacct | Amazon (order) / Intacct (ledger) | Order or settlement reaches an agreed status | Held in exception queue; nothing partially posted | APIWORX |
| Refunds and returns | Amazon | Sage Intacct | Amazon | Refund appears in financial events | Queued for finance review | APIWORX |
| Fees (referral, FBA, storage, advertising as agreed) | Amazon settlement data | Sage Intacct | Amazon | Settlement data available | Unrecognised fee types queued rather than posted to a catch-all | APIWORX (delivery) / you (account mapping) |
| Settlement / payout | Amazon settlement report | Sage Intacct | Amazon | Settlement period closes | Unmatched amounts held in clearing for review | APIWORX |
| Reserves and adjustments | Amazon | Sage Intacct | Amazon | Present in settlement data | Held for review rather than absorbed into revenue | APIWORX (delivery) / you (treatment) |
| Item / SKU mapping | Agreed mapping table | Sage Intacct | Intacct | Applied per line where itemised posting is used | Unmapped SKU raises a named exception | APIWORX (maintenance) / you (approval) |
Three decisions that make or break this integration
Order-level or settlement-level posting
Amazon accounting splits into two schools: post per order and reconcile fees afterwards, or post from the settlement report so revenue and deductions arrive together. Both are defensible and each has consequences for cut-off and reporting, so the choice is made deliberately with your controller.
- Order-level posting gives daily revenue visibility and needs a disciplined fee reconciliation.
- Settlement-level posting reconciles cleanly to deposits but follows Amazon's settlement periods.
- Settlement periods spanning a month end are handled with an agreed cut-off treatment.
- Intacct dimensions carry marketplace and channel so reporting stays usable either way.
Fee categories and FBA
FBA multiplies fee categories: referral fees, fulfilment fees, storage, removals, returns processing, advertising if you include it. Posting them to distinct accounts is what turns a shrinking deposit into an explainable cost structure.
- Each fee category maps to a nominated account rather than one marketplace-expense line.
- New fee types raise an exception instead of being silently absorbed.
- Reserves and adjustments are surfaced rather than netted invisibly against revenue.
- Finance can see contribution after marketplace costs, not just gross sales.
Settlement clearing and month end
Sales and cash do not arrive together, so a clearing position holds the difference. What sits in it is revenue earned but not yet settled — the number a controller wants to see and explain during close.
- Sales, refunds and fees accumulate in a clearing account you nominate.
- Settlement records clear it and match the bank deposit.
- Unmatched amounts are held for review rather than forced to balance.
- The APIWORX team works exceptions and escalates when an accounting decision is required.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every posting is logged against the source order or settlement reference so finance can trace a ledger line back to the channel record.
- Failed postings are retried on a defined schedule; anything still failing is held in an exception queue rather than posted partially.
- Duplicate prevention keys on the channel's own identifier, so a replayed message cannot create a second transaction.
- Exceptions are worked by the APIWORX team and escalated to your named finance contacts when an accounting decision is needed.
- New SKUs, accounts, dimensions, fee types and tax codes are handled as mapping maintenance inside the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How a transaction is traced
Illustrative — not customer data
An illustrative reference trace from Amazon activity to the Intacct ledger.
| Amazon order ID | Intacct transaction reference |
|---|---|
| Settlement report ID | Clearing-account clearing entry |
| Fee category from settlement data | Nominated fee expense account |
| Refund event | Credit against the original sale reference |
Scope and questions
- Do you post per order or per settlement?
- Either. We agree the grain with your controller in scoping, because it changes cut-off treatment and the reconciliation work involved.
- Does this cover multiple Amazon marketplaces?
- Multiple marketplaces are normally handled with dimension values per marketplace. Currency treatment is agreed with finance where you sell in more than one.
- Is Amazon Vendor Central included?
- No — vendor wholesale is a different flow with POs, ASNs and invoices. See the Sage Intacct + Amazon Vendor Central page.
- How are FBA inventory movements handled?
- Inventory treatment is a separate decision with its own system of record and is scoped explicitly. This page describes the financial flow.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your Amazon Seller Central + Sage Intacct integration
Tell us your systems and documents. A specialist confirms scope by email.