Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Marketplace · Finance
Connect Sage Intacct + eBay
Automate marketplace sale, customer record, refund / cancellation, marketplace fees and deductions, payout / deposit between Sage Intacct and eBay — 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 eBay.
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 eBay, 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 the books in Sage Intacct while a meaningful share of revenue arrives through eBay.
What needs to be in place
- Sage Intacct with API access and a service user that can create the transaction types you want written.
- An eBay seller account with API access, and the managed-payments payout arrangement in use identified.
- An agreed chart of accounts position for marketplace revenue, fees, refunds and payout clearing.
- Someone on your side who owns the accounting decisions — summary versus itemised posting is a policy call, not a technical one.
When you may not need this
If eBay is a small side channel and a monthly manual journal is acceptable to your auditors, you may not need this. It earns its place when eBay volume affects your close, when fee variance needs explaining, or when payouts stop tying out to recorded revenue.
What is out of scope
- APIWORX does not act as your accountant: we implement the treatment you and your advisors agree.
- Sales-tax and marketplace-facilitator determination stays with your tax advisors; we post to the accounts and codes you nominate.
- Which eBay settlement and payout data can be ingested for your account is confirmed during scoping.
What actually moves, and who owns it
A representative eBay-to-Intacct posting scope. The final object list, direction and cadence are agreed in writing before build.
Sage IntacctAPIWORX (mapping, retries, exception queue)eBay
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Marketplace sale | eBay | Sage Intacct | eBay (order) / Intacct (ledger) | Order reaches an agreed status | Held in exception queue; nothing partially posted | APIWORX |
| Customer record | eBay | Sage Intacct | Per agreed rule (summary customer or named buyer) | At posting | Transaction held rather than creating duplicates | APIWORX (delivery) / you (rule) |
| Refund / cancellation | eBay | Sage Intacct | eBay | Refund recorded on the marketplace | Queued for finance review | APIWORX |
| Marketplace fees and deductions | eBay settlement data | Sage Intacct | eBay | Settlement or fee data available | Unrecognised fee types queued rather than posted to a catch-all | APIWORX (delivery) / you (account mapping) |
| Payout / deposit | eBay payout data | Sage Intacct | eBay | Payout data available | Unmatched amounts held in a clearing position for review | APIWORX |
| Item / SKU mapping | Agreed mapping table | Sage Intacct | Intacct | Applied per line at posting | Unmapped SKU raises an exception naming the SKU | APIWORX (maintenance) / you (approval) |
Three decisions that make or break this integration
Deciding what an eBay order becomes in Intacct
The decision that shapes everything else is the posting grain. An eBay order can land as an itemised invoice, an order-level transaction or a summarised journal per day or per payout. Each supports different reporting and each carries a different reconciliation burden, so it is fixed before build rather than discovered afterwards.
- Itemised posting gives SKU-level margin reporting but demands a maintained item mapping.
- Summary posting is lighter to run and still supports channel-level reporting through Intacct dimensions.
- Dimension mapping — location, department, channel — is agreed once and enforced on every transaction.
- Whatever grain you choose, the eBay order number is written to a field your team can search.
Fees, refunds and the variance nobody wants to explain
Marketplace revenue rarely arrives as a clean number. Final value fees, promoted-listing charges, shipping labels, refunds and adjustments all move the payout away from gross sales. Posting fees as they appear in settlement data — to accounts you nominate — is what makes the difference between a payout that ties out and a month-end investigation.
- Each fee type maps to a named account rather than a single catch-all expense line.
- Refunds and partial refunds are posted against the original sale reference where the data allows.
- Fee types eBay introduces later raise an exception instead of being silently absorbed.
- Finance sees the deductions itemised, so a lower deposit has an explanation attached to it.
Payout reconciliation and the clearing position
Because eBay pays out on its own rhythm rather than per order, revenue recognition and cash arrival are separated. Sales post to a clearing position, and payouts clear it. What remains in that position at any moment is money earned but not yet received — which is exactly the number a controller wants during close.
- Sales, fees and refunds accumulate against a clearing account you nominate.
- Payout records clear the position and are matched to the bank deposit.
- Unmatched or partially matched amounts are held for review rather than forced to balance.
- The APIWORX team works those exceptions and escalates when an accounting decision is required.
Reliability and ownership
Finance integrations are judged on whether they can be trusted at close. These are the operating rules that apply to this workflow.
- 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 trace showing which references connect an eBay sale to its Intacct entry. Actual field placement is agreed in scoping.
| eBay order number | Intacct transaction reference |
|---|---|
| eBay payout ID | Clearing-account clearing entry |
| Fee type from settlement data | Nominated fee expense account |
| Refund record | Credit entry against the original sale reference |
Scope and questions
- Can you post at item level rather than summary?
- Yes, subject to a maintained SKU-to-item mapping in Intacct. We confirm which grain your reporting actually needs during scoping, because itemised posting adds ongoing mapping work.
- Do you handle marketplace-facilitator sales tax?
- We post to the accounts and tax codes your advisors specify. We do not make tax determinations.
- What happens when eBay adds a new fee type?
- It raises an exception rather than posting to a default account. The APIWORX team brings it to you, the mapping is agreed, and the held items post.
- Is the payout reconciliation automatic?
- Payout data clears the sales position where the data supports the match. Amounts that do not match are held for review rather than forced — which settlement sources are available for your account is confirmed in scoping.
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 eBay + Sage Intacct integration
Tell us your systems and documents. A specialist confirms scope by email.