Amazon marketplace reconciliation in NetSuite should connect order activity, settlement adjustments and bank deposits without recording sales twice. Use settlement detail to explain the clearing balance and classify each amount according to an approved accounting map. A net deposit is the result of several financial events, not a reliable substitute for gross sales data.
Keep this work separate from the fulfillment integration. An order can ship correctly while fees, refunds or reserves remain unreconciled. Finance needs its own completeness checks and evidence for the settlement population.
Identify each seller account, marketplace, currency and legal entity. Determine which system already records orders, sales, tax and refunds. Include both merchant-fulfilled and Amazon-fulfilled activity where relevant to the business.
Amazon's current SP-API documentation says settlement reports are automatically scheduled and can be located with the supported report-listing operation. It identifies the Flat File V2 report as the replacement for deprecated XML and older flat-file formats.
Verify the connector's supported report type and current deprecation guidance before implementation. Do not assume an old parser remains suitable merely because it processed a previous month's file successfully.
The V2 report uses amount-type, amount-description and amount fields, with identifiers for the settlement and related activity. Amazon also warns that amounts use local currency formatting.
Design a mapping that combines the relevant type and description with sufficient transaction context. Review sales-related amounts, refunds, fees, promotions, adjustments and other categories present in the actual account. Unknown categories should be reported for review rather than silently assigned to revenue or expense.
Preserve source sign conventions and test the parser with negative amounts, decimal commas and empty optional fields. A file can import without an error while interpreting 95,00 incorrectly, so include arithmetic control totals in testing.
Document which source creates the customer sale or summarized sales entry. Then decide which settlement categories clear that activity, create supported expenses or represent another balance-sheet movement.
If both the order integration and settlement integration create refunds, define a single authoritative posting path and a reconciliation relationship for the other source. Otherwise, the customer return can reduce revenue twice while the net payout still matches the bank.
Keep operational reimbursement, fee and inventory questions separate. A marketplace reimbursement may require finance review of the underlying event; it should not automatically add physical stock or reverse a warehouse adjustment.
For each settlement, retain its identifier, covered dates, currency, total and source file reference. Sum the classified detail and reconcile it to the settlement total. Then match the related deposit to bank evidence under the approved cutoff policy.
At month end, explain the opening marketplace clearing balance, current activity, completed payouts and ending balance. Identify unsettled activity and any supported held balances separately. A settlement period may cross the accounting month boundary, so the reporting policy must address that timing.
Do not force every month to reconcile using only deposits dated within the month. Doing so can omit sales activity that has not yet been paid out and include cash relating to earlier activity.
Assume a settlement includes 50,000 currency units of customer-related gross charges, 4,000 of refunds, 6,000 of fees and a supported 500 positive adjustment. With no other categories, the expected net is 40,500.
The analyst traces each component to the approved NetSuite mapping and confirms the 40,500 bank deposit. If the gross sales were already recorded from orders, the settlement feed clears the corresponding balance and records the approved adjustments without creating another sale.
Now introduce a new 300 deduction with an unmapped description. The process should surface the category, preserve the source line and hold the accounting decision for review. It should not bury the 300 in a generic fee just to make the import complete. This hypothetical example excludes the detailed tax and reserve treatment that a real seller must validate.
Maintain a register of expected and received settlement identifiers. Record file version or checksum, import batch, processing status and target transaction references. A second copy of the same report must not create another accounting batch.
If a report is regenerated or corrected, compare it with the previously processed population and use an approved amendment procedure. Do not overwrite the original evidence or assume the latest download is identical.
Amazon documents report-document retrieval and download as separate steps after the report is identified. Treat each stage as a monitored outcome, retain report identifiers and keep credentials and temporary download links out of business-facing logs.
Where APIs are used, separate report availability from successful download and successful posting. A job marked complete may only mean that the file was retrieved, while a subset of its lines remains unclassified.
Confirm:
Have a qualified accountant review tax presentation, marketplace-facilitated tax treatment, principal-versus-agent questions and reimbursements for the applicable jurisdictions. A connector's default account map is not an accounting opinion.
Age missing reports, unmatched deposits and unmapped categories separately. Follow each material timing difference into the subsequent settlement so old errors do not remain hidden under a recurring explanation.
A CuriousRubik integration review can assess the report, mapping and clearing bridge together. The desired result is a marketplace balance that finance can explain independently of the order feed, with each financial event recorded once and traceable to its source.