Do Shopify payouts and Amazon settlements match the books?
Match every Shopify payout and Amazon settlement to its NetSuite deposit and journal. Find the lines nobody booked, and keep them apart from payouts that simply haven't landed yet.
Open QuerriWhat you'll need
Querri (Free trial) to match payouts, deposits and journals
Shopify, Amazon Seller Central and NetSuite: Step 1 says what each adds
Your posting rules: so each settlement line maps to one account
Free resources
Start your free trial here →Sample data sets
Synthetic data for Curio Supply, a made-up home goods brand. Not real customer, retailer or marketplace data.
Need help?
If you have any questions, you can request a demo or email our team.
Before we begin
At month end the deposit check usually passes: the cash Shopify and Amazon said they'd send arrived. A matching deposit says nothing about whether every line inside the settlement was booked. A Shopify payout is net of fees and refunds, an Amazon settlement mixes sales, fees, refunds and reimbursements, and the ledger is gross, so proving the two agree means rebuilding each payout from its lines.
This playbook totals every October payout and settlement from its own lines, matches each to its NetSuite deposit and journal, and breaks any gap down by line type.
How it works:
- • Connect Shopify, Amazon Seller Central and NetSuite
- • Total October payouts and settlements by channel
- • Match each payout and settlement to a booked deposit
- • Break the Amazon gap down by line type
- • Build the month-end reconciliation view
Follow the steps
Connect Shopify, Amazon Seller Central and NetSuite
Three sources, one project:
- •
Shopify: payouts and the payment transactions inside each one.
- •
Amazon Seller Central: settlement reports, one line per sale, fee, refund and reimbursement.
- •
NetSuite: booked deposits and the journal entries for each payout and settlement.
All three connect directly and sync on a schedule. Querri rebuilds each payout from its own lines before comparing it with the books.
Tip: Include the two weeks before the month, so a settlement that started in September and was deposited in October is matched too.
-
Shopify payouts -
Amazon settlements -
NetSuite deposits and journals
Total October payouts and settlements by channel
First, check each payout adds up from its own lines:
"Total October's Shopify payouts and Amazon settlements, and check each one adds up from its own lines."
22 Shopify payouts total $1,718,119.37 and 3 Amazon settlements $1,284,220.34. Every one rebuilds from its own lines to the cent, so any gap that follows isn't arithmetic.
| Channel | Count | Amount |
|---|---|---|
| Shopify payouts | 22 | $1,718,119.37 |
| Amazon settlements | 3 | $1,284,220.34 |
| Total | 25 | $3,002,339.71 |
Shopify payouts dated in October 2026 and Amazon settlements deposited in October 2026.
Match each payout and settlement to a booked deposit
Then compare each with its NetSuite deposit and the amount booked for it:
"Match every October payout and settlement to its NetSuite deposit and to the amount booked for it. Which don't tie?"
Shopify ties to the cent. Every Amazon settlement has its deposit, yet the books record $12,306.48 less than the settlements, all on the October 15 to 28 settlement.
| Channel | Paid | Booked gap |
|---|---|---|
| Shopify payouts | $1,718,119.37 | $0.00 |
| Amazon settlements | $1,284,220.34 | $12,306.48 |
Paid against booked, October 2026.
Break the Amazon gap down by line type
Compare that settlement's lines with its journal, account by account:
"For the Amazon settlement that doesn't tie, compare its lines with the journal account by account. Which line type is missing?"
One account differs: 4930 Amazon Reimbursements. 47 WAREHOUSE_LOST lines, $12,306.48, have no journal line; the reversal lines that were booked match.
| Line type | Settlement | Journal |
|---|---|---|
| WAREHOUSE_LOST (47 lines) | $12,306.48 | $0.00 |
| REVERSAL_REIMBURSEMENT (4 lines) | $167.52 | $167.52 |
| Total | $12,474.00 | $167.52 |
Account 4930 Amazon Reimbursements, settlement of October 15 to 28, 2026.
Build the month-end reconciliation view
Four numbers for the close, and what each open item needs.
The narrative Querri writes:
The books understate Amazon reimbursements by $12,306, and the only Shopify difference is a payout still in transit.
What you can create or export:
- The table, to Excel, CSV or Google Sheets
- A live dashboard that refreshes with each sync
- A presentation for the meeting, to PDF or PowerPoint
| Item | Amount | Next step |
|---|---|---|
| WAREHOUSE_LOST reimbursements with no journal line | $12,306.48 | Review for booking |
| Shopify payout dated October 30, in transit | $50,271.20 | Confirm the deposit |
Open items, October 2026 close.
Find the line nobody booked before the books close.
Try it on your own dataTips for a month-end reconciliation people trust
Rebuild every payout from its lines
A payout that adds up from its own transactions rules out arithmetic. Any gap left is a booking question, which is a much shorter list.
Keep timing apart from gaps
A payout dated at month end often deposits days later. Label it timing, check that it lands, and keep it off the list of things to book.
Teach Querri your rules once. Every answer after that follows them.
Which account each settlement line posts to, how long a deposit may trail its payout, what counts as timing: say each rule once and Querri applies it to every question on that data.
Show me how
Say it in chat
Settle a rule in conversation and the Librarian records it as a fact under Facts & Rules, attached to the table it governs. Every later question on that data applies it, whoever asks, and every view built afterwards carries it.
"Amazon settlement lines of type WAREHOUSE_LOST post to account 4930 Amazon Reimbursements. Save that as a rule for the Amazon settlements table."
Or bring the document that already says it
Upload your month-end close checklist like any other file. Querri files a From a document card in the Inbox with the statements it found, each with its page and exact words; tick the ones to keep and they become facts. The rules this playbook depends on:
- Shopify payout: charges less refunds and fees
- Amazon settlements: counted in the month they are deposited
- Deposit match: same amount, up to five days after the payout
- Booked: the journal lines for a payout or settlement, by account
- Reimbursements: every type posts to 4930 Amazon Reimbursements
- Timing: a payout with no deposit yet, dated in the last five days
"Read our month-end close checklist and propose the rules it states about marketplace settlements. I'll review them in the Inbox."
Where the rules reach
A rule is attached to the data, not to one person's chat, so it follows the data everywhere:
- • Every question asked in chat, by anyone on the finance team
- • Every view the Librarian builds on that data
- • Every step of a project, including the code it writes
- • Dashboards and scheduled runs, each time they refresh
- • Claude and ChatGPT, when they ask Querri
You stay in control
Every rule is listed under Facts & Rules next to the data it governs, where you can edit or remove it. Rules from a document wait for your tick in the Inbox, and a Worth remembering card is how Querri offers one it noticed itself. Workspaces and roles decide who can change what. Company-wide rules go in Settings → Customize; the Library is where the rest lives.
The payoff at month end
The close starts with one line to review and one deposit to watch. Adding a new line type is a sentence.
Frequently asked questions
Why isn't a matching deposit enough?
What are WAREHOUSE_LOST lines?
Did Amazon pay too little?
How do net payouts tie to a gross ledger?
What about a payout that hasn't landed?
How are settlements that cross month end handled?
Does Querri post the entry?
How often should this run?
Other popular resources
Playbook
SKU margin by channel
Which SKUs lost margin last month, and in which channel?
Playbook
Deductions against promos
Which retailer deductions match a promo we agreed to?
Demo
Request a walkthrough
See Querri in action with your own data.
Pricing
Compare plans
Find the right plan for individuals, teams, or enterprise.