SP-API · financial reconciliation done-for-you · fixed price
Statement

Your Amazon settlement
doesn't add up. I find the money it's hiding.

Fees renamed without notice, deferred vs released mixed up, transactions double-counted or dropped — the payout looks fine and the numbers quietly rot. I reconcile it against the source and show you exactly where money leaks.

Settlement · group 88214before → after
Settlement net (Amazon)$142,880.12
Sum of transactions (your books)$141,306.44
Unexplained gap− $1,573.68
After reconciliation$0.00 reconciled
► Request the reconciliation audit or see my work on GitHub

The button opens an email prefilled with 4 quick questions — reply and I come back with what I'd check and a fixed quote.

What you get
Reconciliation reportsettlement net vs the transactions behind it, per settlement group — every dollar accounted for or flagged✓
The leaks, quantifieddouble-counted fees, dropped transactions, deferred-vs-released mismatches, currency-conversion gaps — with amounts✓
A reconciliation that stays correctidempotent by transaction id — re-running never double-counts; a renamed fee shows up as a residual, not a silent loss✓
Done-for-you build (optional)the reconciliation wired to your data as a repeatable monthly close — quoted after the audit✓
How it runs

  1. You give me read-only access to your settlement reports + Finances API (no write access, ever).

  2. I reconcile each settlement group: sum(listTransactions) == settlement net, released vs deferred kept apart.

  3. You get the report: where it balances, where it doesn't, and how much is at stake.

  4. If you want it ongoing, I build it into a monthly close you can trust. Never double-counts.

◆ The reason numbers rot — and the fix

Amazon's settlement flat-file is an account-level summary; the Finances API is the per-transaction truth. Reconciling them is where money is found — but only if you match by FINANCIAL_EVENT_GROUP_ID, keep deferred apart from released, and key on transaction id so a re-pull never counts a row twice. That's the discipline the Amazon SP-API team validated in my work publicly.

Investment
Reconciliation audit (fixed)$450
Mandatory call / meeting$0
Credited toward the full buildyes, 100%
To start$450

If the audit finds nothing you didn't already know, you don't pay for it. One silently double-counted fee category across a year is usually worth many times this.

Why me
Validated byAmazonSP-API

The Amazon SP-API developer team publicly confirmed my reconciliation approach in their official repo (issue #5353). I run five SP-API integrations in production and a platform with 115 endpoints handling payments and webhooks. Reconciliation — "never count a dollar twice" — is my daily work.

Questions
Do you need my seller password or write access?

No. Read-only Reports + Finances API access, or even the exported settlement files. I never write to your account and never ask for your Seller Central password.

Which marketplaces / regions?

Any — US, EU, and beyond. Multi-marketplace is where most of the hidden gaps live (currency conversion, account-level fees with no marketplace), so it's exactly where the audit pays off.

What if it's actually all correct?

Then you get a clean bill of health with the reconciliation to prove it — and you don't pay for the audit. Either way you leave knowing, not guessing.

Do we need a call?

No. 100% in writing — you approve scope and see the report by message. No meetings.

► Request the reconciliation audit

GABRIEL BARRETO · PROFICIENTSTACK.COM · SP-API RECONCILIATION, INTEGRATIONS & AUTOMATION
100% in writing, no calls. Read-only access only — your credentials stay yours. Stop guessing whether Amazon's numbers are right.