Amazon FBA to NetSuite reconciliation
Amazon FBA settlement reconciliation to NetSuite
A channel guide for Amazon sellers that need settlement reports to tie cleanly to NetSuite without burying fees and adjustments.
The method
How do you reconcile Amazon FBA settlements to NetSuite?
Amazon FBA settlement reconciliation to NetSuite maps Amazon settlement report lines to the orders, refunds, reimbursements, fees, reserves, and timing differences behind each disbursement. The safe method normalizes the report first, reviews exceptions by cause, and posts only reconciled activity into NetSuite.
Key takeaways
- Amazon settlement reports need normalization before NetSuite matching.
- Fees, refunds, reimbursements, reserves, and timing gaps need separate treatment.
- Net deposits should not be trusted until the source lines explain the cash movement.
- Exceptions should be reviewed by cause before any adjustment reaches the ledger.
01 · The pattern
Why are Amazon FBA settlements hard to reconcile in NetSuite?
Amazon settlement reports combine many activity types into one settlement window. Orders, refunds, fulfillment fees, referral fees, reimbursements, reserves, and other adjustments can all affect the disbursement. NetSuite needs those lines translated into accounting treatment before the payout can be trusted.
- Amazon settlement windows do not always align with NetSuite accounting periods.
- Fulfillment and marketplace fees can be spread across many transaction types.
- Refunds, reimbursements, reserves, and adjustments often arrive after the original order event.
- A single disbursement can hide both valid timing differences and true exceptions.
02 · The pattern
What Amazon settlement detail should be reviewed?
Finance should review the settlement report categories that change revenue, cash, fees, refunds, reserves, or receivables. Each category needs a NetSuite destination, a reason-code path when it fails, and enough supporting detail for the close package.
| Amazon detail | NetSuite treatment | Review gate |
|---|---|---|
| Order and principal activity | Sales, receivable, payment, or deposit matching | Confirm the activity maps to the expected NetSuite transaction population. |
| FBA, referral, and service fees | Fee expense or configured clearing treatment | Review account mapping and isolate fees from gross sales. |
| Refunds and reimbursements | Refund, credit, reimbursement, or exception path | Tie the line to the original event or hold it for review. |
| Reserve and timing activity | Reserve tracking, clearing, or timing exception | Do not force timing differences into current-period revenue or fees. |
03 · The pattern
How does Altura make Amazon settlement reconciliation governed?
Altura treats Amazon settlement work as a governed workflow: normalize report categories, match source detail to NetSuite, isolate fees and reserves, document timing gaps, and route unresolved differences to a human review gate. Vista Recon carries that method into repeatable settlement reconciliation for NetSuite.
- Preserve Amazon settlement line detail before aggregation.
- Separate expected timing from missing or misclassified activity.
- Use reason codes for fees, refunds, reserves, reimbursements, and unmatched lines.
- Post only the reconciled result, with exception detail retained for review.
Shared vocabulary
What terms matter on this page?
These definitions keep the method precise and extractable for answer engines, while giving finance a shared vocabulary for source files, NetSuite treatment, and review gates.
Settlement report
A settlement report is the marketplace file that explains what activity and adjustments produced a disbursement.
Reserve
A reserve is an amount held back from immediate payout, usually creating a timing difference that must be tracked.
Reimbursement
A reimbursement is marketplace activity that returns money for a prior adjustment, inventory event, or dispute outcome.
Where it goes next
When the pattern becomes an operating decision
This pattern sits between the settlement library, productized reconciliation, and the service paths that explain why the mismatch keeps recurring.
If this reconciliation pattern is caused by connector behavior, the operating decision belongs with a Celigo NetSuite integration partner. If the issue comes from a stalled implementation or brittle partner handoff, compare it with NetSuite HealthCheck and recovery. If the same pattern recurs every close, evaluate Vista Recon against the full NetSuite payout reconciliation.
Authorship
Who wrote this guide?
Written by Dave Charland, Founder, Altura Innovation. Last updated 2026-06-16.
FAQ
Frequently asked questions
Need this payout source to tie to NetSuite?
Tell us where the source file, NetSuite record, and close process stop agreeing, and we will help scope the safest Vista Recon path.