Shopify payout reconciliation without the month-end spreadsheet
Platforms pay out net of fees, refunds, chargebacks and reserves, bundling many orders into one bank deposit, so the books rarely match on sight. We build a workflow that pulls payout summaries from Shopify Payments, PayPal, Stripe and marketplace settlement reports, matches them to orders, prepares summarized entries for QuickBooks Online or Xero and flags anything that does not tie out for your bookkeeper. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.
The problem
Why ecommerce payouts never match the bank
A single Shopify payout can cover hundreds of orders, minus processing fees, refunds and adjustments. PayPal, Stripe, buy-now-pay-later providers and Amazon settlements each pay on their own schedule with their own reports.
Bookkeepers end up exporting CSVs and building pivot tables every month, so true margin by channel is known weeks late, and small leaks such as unrecovered chargebacks or duplicate refunds go unnoticed.
What we build
What our Shopify payment reconciliation includes
Payout collection
Payout and settlement data pulled from Shopify Payments, PayPal, Stripe and marketplace reports on a schedule.
Order-level matching
Each payout broken down into charges, refunds, fees and adjustments and matched to orders.
Summarized journal entries
Clean entries prepared for QuickBooks Online or Xero, split by channel, fees and tax as your accountant prefers.
Bank deposit match
Expected net payouts compared with bank feed deposits.
Mismatch queue
Anything that does not tie out goes to the bookkeeper with the underlying transactions.
Margin report
Monthly gross sales, fees, refunds and net by channel.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Payouts pulled
Payout summaries and settlement reports are collected after each payout.
-
02
Automated
Transactions matched
Charges, refunds, fees and adjustments are matched to orders.
-
03
Automated
Entries prepared
Summarized entries are drafted in the accounting tool.
-
04
Team review
Bookkeeper reviews
The bookkeeper checks mismatches and approves entries.
-
05
Founder or ops lead decides
Financial decisions
Write-offs, tax treatment and chart of accounts are decided by the founder with their accountant.
How it behaves
How ecommerce reconciliation behaves
What the founder sees
- A monthly margin report by channel
- Books that close faster
What the bookkeeper sees
- Draft entries ready to approve
- A mismatch queue with the underlying transactions
- Bank deposits matched to payouts
What the automation does
- Collects payout and settlement data
- Matches transactions to orders and fees
- Logs every entry it prepares
Edge cases and fallbacks
- Chargeback spans two payouts
- Linked across both and flagged until resolved.
- Currency conversion on a multi-currency store
- Converted amounts and fees recorded as the provider reports them; differences flagged.
- Payout held or reserve applied
- Recorded as a reserve movement and shown on the mismatch queue.
- Provider or accounting API outage
- The run retries later and nothing posts from partial data.
Architecture
Payout reconciliation for an online store at a glance.
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 Payout data arrives from Shopify Payments, PayPal, Stripe and marketplace settlement reports.
- 2 n8n breaks each payout into charges, refunds, fees and adjustments and matches them to orders.
- 3 Summarized entries are drafted in QuickBooks or Xero; mismatches go to the bookkeeper.
- 4 A monthly margin report shows gross, fees, refunds and net by channel.
Project planner
How the project runs, phase by phase.
Shopify payout & marketplace reconciliation project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Payment providers, marketplaces, chart of accounts and how your bookkeeper reconciles today.
-
02
Design
2 to 3 days
Entry structure agreed with your accountant, matching rules and mismatch tolerances.
-
03
Build
1 to 2 weeks
Payout collection, matching, draft entries, bank match and reporting.
-
04
Shadow run
About 1 week
One month reconciled in parallel with the manual process.
-
05
Launch
1 to 2 days
Switch to the automated process and hand over the run book.
-
06
Support
Ongoing
New providers, account changes and monitoring.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Providers, entry structure and matching rules.
$200 – $400
-
Build
Collection, matching, entries and reporting.
$500 – $1,300
-
Integrations
Store, payment providers, marketplaces and accounting.
$150 – $400
-
Testing and shadow run
One month reconciled in parallel.
$100 – $250
-
Launch and training
Handover and bookkeeper walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Each extra marketplace with its own settlement format may add to the scope. Accounting and n8n subscriptions are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Accounting software: Your QuickBooks Online or Xero plan.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
Your accountant owns the treatment
We prepare entries in the structure your accountant approves; we do not give tax or accounting advice.
Access by least privilege
Shopify payout data needs the view_payouts permission; we request only the scopes the workflow needs.
Source: shopify.devEU and UK: financial records contain personal data
Order-level data includes customer details, so it is processed under processor contracts and kept out of summaries where not needed.
Source: gdpr-info.euFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Shopify payout & marketplace reconciliation questions, answered.
It is matching each Shopify Payments payout that lands in your bank to the orders, refunds, fees and adjustments it contains, so your books show gross sales and costs correctly rather than one net deposit.
Yes, through the QuickBooks Online and Xero Accounting APIs. Many connector apps exist; we build or configure the route that gives your accountant the entry structure they want, and handle the providers the apps miss.
Yes. Each provider has its own reports or API; we pull them on a schedule and match them the same way.
We start with draft entries the bookkeeper approves. Once a few months tie out cleanly, routine payouts can post automatically with mismatches still held for review.
It separates tax collected in the entries if your store records it, which makes filing easier. Registration, nexus and filing decisions stay with your accountant.
Days to close the month, share of payouts reconciled without manual work, unresolved mismatches and unrecovered chargebacks.
Free 20-minute call
Want this for your e-commerce brand?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for e-commerce brands
All servicesEcommerce CRM & customer lifecycle automation
Bring orders, browsing and support history into one ecommerce CRM, then run welcome, post-purchase, replenishment and win-back flows that stop the moment a shopper buys or opts out.
From $1,000 · About 4 weeks Details
WISMO automation & order tracking replies
Answer "where is my order?" tickets with live carrier tracking, send proactive delay notices before customers chase, and route lost or stuck parcels to an agent with the history attached.
From $1,000 · About 3 to 4 weeks Details
Returns management & refund automation
Check every return request against the right policy for the customer's market, issue labels for eligible items, route faulty goods to an agent and prepare refunds when the warehouse confirms receipt.
From $1,000 · About 4 weeks Details