TL;DR: NetSuite already ships a subledger. The real architecture question is not whether you get order- and SKU-level detail — every serious tool offers that now — but where that detail lives. Post it into NetSuite as native transactions and the ERP computes COGS from actual inventory movement, inside the audited books. Keep it in a vendor’s external subledger and your general ledger stays small, but item-level truth sits outside the system your auditor tests. Both are defensible. Which one is right depends on where your inventory master already lives.
Looking for the product rather than the architecture? Entriwise is a purpose-built Amazon NetSuite integration that posts native accounting documents, moves unit-level inventory, and reconciles every payout.
You Already Own a Subledger
A subledger is not a new idea and it is not a product category. It is standard double-entry structure: the general ledger carries a control account with one balance, and the subsidiary ledger carries the line-by-line detail that sums to it. Your A/R control account says $500,000; the A/R subledger says which 400 customers owe it.
If you run NetSuite, you have already licensed several. NetSuite ships item records with a real costing engine, inventory subledgers by item and location, item receipts and fulfillments, inventory adjustments, and — under OneWorld — subsidiaries, currencies, and elimination structures on top of all of it.
You can see the same principle at work in a well-built Amazon close. Proving Amazon A/R and A/P through a subledger roll-forward against the clearing account is only possible because the ledger holds the supporting documents. Take those documents away and the roll-forward has nothing to reconcile.
So when a marketplace integration offers you a subledger, the honest framing is that it is offering to keep detail somewhere other than the subledger you are already paying Oracle for.
The Two Architectures
Both approaches solve the same visible problem: your marketplace data has to reach your accounting system without burying it in a million documents. They diverge on where the item-level record ends up.
| Ledger-native posting | External subledger | |
|---|---|---|
| What reaches the GL | Native accounting documents — cash sales, refunds, invoices, bills, inventory transfers | Summarized entries per settlement or period |
| Where item detail lives | Inside NetSuite, on the transaction | Inside the vendor’s database, linked to the summary |
| Who computes COGS | NetSuite’s costing engine, from actual inventory movement | The vendor, from costs you maintain, posted as a value |
| Inventory quantities | Move as units in NetSuite | Typically do not move in NetSuite |
| What an auditor tests | Transactions in the ERP | A vendor export |
| If you cancel | The records stay in your ledger | The detail leaves with the subscription |
Neither column is a trick. The second one exists for good reasons, and we will get to them.
Where the Difference Actually Shows Up
1. Inventory valuation on the balance sheet
This is the one with the largest number attached to it. If Amazon activity arrives as a summarized value entry, your NetSuite inventory asset account is only as accurate as the cost figures someone maintains in the vendor’s tool. The units themselves never moved.
That works until landed cost changes. Freight surcharges, tariff shifts, currency movement, and multiple purchase batches at different prices all produce costing layers — and a single seller-maintained average cost per SKU cannot represent them. The classic discovery in an ecommerce close is inventory that sold but was never properly expensed: a reported 68% gross margin that turns out to be 32%.
When posting is ledger-native, NetSuite consumes the actual FIFO or average costing layers as units leave inventory. The valuation is not an estimate carried in from outside; it is what your ERP computed.
2. Portability
An external subledger is a rented record. It is a second system to reconcile, a second thing to keep in sync, and — the part that tends to surface only at renewal — it leaves when the subscription does. Export the data and you have a spreadsheet, not an auditable ledger.
Documents posted into NetSuite are yours permanently. If you replace your integration next year, the last three years of Amazon accounting stay exactly where they are.
3. Auditability
Auditors, lenders, and acquirers test transactions inside the accounting system. Sampling an invoice in NetSuite is routine work with a defined procedure behind it. Sampling a vendor’s proprietary subledger means accepting an export as evidence and forming a view on a system that sits outside your control environment.
For a mid-market brand heading toward a diligence process, that is not a theoretical distinction. It changes how much of your close a third party is willing to rely on.
4. Two sets of numbers
Analytics layers built on an external subledger produce profitability reporting that is parallel to the books rather than derived from them. The dashboard says one thing, the P&L says another, and reconciling the two becomes somebody’s recurring job.
When SKU profitability is computed from the same ledger COGS that produced your gross margin, there is only one answer. The margin in the report is the margin in the financial statements, because they came from the same inventory movement.
When an External Subledger Is the Right Call
It genuinely is, in four situations, and it is worth being straight about them:
- Your inventory master already lives outside NetSuite. Plenty of brands run a dedicated IMS or 3PL system as the source of truth and use NetSuite as a financial consolidation ledger. If that decision is already made, an external subledger is consistent with your architecture rather than a duplicate of it.
- Your NetSuite administrator mandates journal entries only. In heavily customized accounts, native transaction posting can collide with scripts, approval workflows, custom segments, and revenue recognition rules. “Send us a summary and nothing else” is a legitimate procurement position, and the less invasive tool wins it.
- You are on a ledger without a real inventory engine. If the accounting system cannot compute costing layers, moving units into it accomplishes nothing. An external subledger is the only way to get item-level detail at all.
- Amazon is a minority channel. When Amazon is 15% of revenue and five other channels make up the rest, breadth of coverage can matter more than depth on any one of them.
A2X is the most common tool in this category and it is good at what it was built for — settlement summarization and payout reconciliation. If your requirements stop there, it is a reasonable answer, and we have never pretended otherwise.
The trade-off only becomes expensive when inventory is the point of the business.
The Test a Controller Can Run in Five Minutes
Open NetSuite. Pick a SKU that sold on Amazon last week. Ask one question:
Did the units leave NetSuite inventory, and did NetSuite compute the COGS?
If the answer is yes, your ERP understands your largest sales channel. If the answer is no — if inventory only moved as a dollar value, or did not move at all — then your inventory records, demand planning, replenishment signals, and margin reporting are all blind to Amazon. You are running an enterprise ERP as a consolidation ledger and doing the actual inventory accounting somewhere else.
That may be a deliberate choice. It is frequently not.
What Ledger-Native Posting Looks Like in Practice
Getting detail into NetSuite is not the same as getting all the detail into NetSuite. Posting every Amazon order individually consumes transaction-line allowance and can push you into a higher service tier — the scaling problem covered in the Amazon NetSuite integration guide. The workable pattern keeps documents compact while preserving accounting and inventory meaning:
- Daily summarized documents for FBA activity, mapping natively to NetSuite cash sales, refunds, and checks — with itemized posting available where order-level records are genuinely required.
- Unit-level inventory movement through inventory transfers for FBA inbound and adjustments for lost, damaged, or reimbursed stock, so quantities and costing layers stay correct.
- Fee mapping to NetSuite items routed to the expense accounts, departments, classes, and subsidiaries you choose, so referral, fulfillment, storage, and advertising costs land where they belong.
- Automatic settlement reconciliation, matching the sum of posted activity against each payout rather than leaving the difference for someone to chase.
- Correct deferred handling under Amazon’s DD+7 policy. Fulfillments post as invoices and Amazon fees post as bills; both stay open, recognizing revenue and expense on accrual timing, and close when the payment and fee charge actually settle. No clearing-account workaround, and no pretending the money is sitting in a reserve.
- SKU profitability from ledger COGS, pairing actual costing layers with variable commissions, fulfillment fees, returns, and product-level ad spend — the method described in the FBA product margin guide.
The same architecture carries across Amazon Seller Central into QuickBooks Desktop Enterprise and NetSuite, which matters if you expect to move up the stack rather than replace your integration when you do.
Quick Answers
- What is an accounting subledger? A subsidiary ledger holding the line-by-line detail behind a general ledger control account. A/R, A/P, fixed assets, and inventory are the standard ones.
- Does NetSuite have a subledger? Yes. NetSuite includes native inventory, A/R, and A/P subledgers, along with a costing engine supporting FIFO, LIFO, average, standard, and specific costing.
- Why do marketplace integrations sell external subledgers? Because tools built on summarized posting have no item-level record in the ledger to drill into. An external subledger restores that detail without changing how they post.
- Is an external subledger auditable? It can support an audit, but the evidence is a vendor export rather than a transaction inside your accounting system. Auditors weigh those differently.
- Should Amazon inventory post into NetSuite? If NetSuite is your inventory system of record, yes — otherwise the ERP cannot value inventory, compute COGS, or plan replenishment for your largest channel. If inventory truth already lives in a separate IMS, the answer changes.
- Can you get item-level detail without bloating NetSuite? Yes. Daily summarized documents plus unit-level inventory movement keep transaction counts low while preserving costing accuracy.
The Question Worth Asking a Vendor
Not “do you give me SKU-level detail?” Everyone says yes now.
Ask instead: does that detail post into my ledger, and does my ledger compute the cost?
The answer determines whether your Amazon business is something NetSuite accounts for, or something NetSuite receives a summary about. For brands where inventory is the business, that is the difference between an ERP implementation and an expensive consolidation tool.
If you are weighing integration approaches more broadly — purpose-built connector, iPaaS build, or manual process — the Amazon NetSuite integration guide covers the full comparison, and the Celigo alternative analysis goes deeper on the iPaaS path.