Dev.to WebDev 🛠 Dev 👁 0 📖 3 min read

Why your Shopify Payments payout never matches your sales, and how to book it

If you run a Shopify store and keep proper books, you have met this problem: you sold 1,240 EUR this week, and Shopify Payments wired you 1,187.32 EUR. The transfer matches no invoice and no daily total. Your accountant

If you run a Shopify store and keep proper books, you have met this problem: you sold 1,240 EUR this week, and Shopify Payments wired you 1,187.32 EUR. The transfer matches no invoice and no daily total. Your accountant asks what it is, and you open the payout page in Shopify and start copying numbers.

Here is how that payout actually breaks down, and how to book it so the bank reconciles to the cent. I'll use French accounting accounts as the example, but the logic is the same in any double-entry system.

What a payout contains

Shopify Payments groups several days of card payments into one bank transfer and subtracts a few things on the way:

  • the processing fee on each order;
  • the refunds issued during the period;
  • disputes, reserves and adjustments, when there are any.

So the payout is not revenue. It is a settlement of money customers already owe you (or already paid you, from your books' point of view), minus a cost (fees), minus money you gave back (refunds).

The entry that makes it reconcile

The clean way is one journal entry per payout, bridging your customer invoices and the bank line:

credit  411 customer accounts   amount paid for each order in the payout  (settles each invoice)
debit   411 customer accounts   each refund in the payout                 (settles each credit note)
debit   627 bank fees           Shopify Payments fees
debit   58  internal transfers  net amount of the payout                  (the bank line settles this)
debit/credit 471 suspense       anything unexplained (dispute, reserve)   (for the accountant to assign)

The key idea is the internal transfer account (58 in the French chart, "clearing" elsewhere). The payout entry lands the net amount there, and when the bank statement line arrives, it clears that account. Every invoice is matched, fees are isolated as an expense with a supporting line per order, and nothing floats.

Two details that bite people:

  1. Refunds belong in the payout they were deducted from, not on the date you clicked "refund". Shopify tells you which payout each balance transaction belongs to.
  2. Rounding. Shopify computes tax per line; an accounting tool may recompute it on the invoice total. A 3 x 9.99 EUR basket at 20% VAT has no exact net price, so you either accept a one-cent rounding line or your invoice total drifts from what was actually paid, and the payout never matches.

Doing it by hand vs. automating it

By hand, each payout means opening it in Shopify, listing the orders and fees, and typing the entry. A few minutes each, and much more the day a dispute shows up.

Through the Shopify Admin API you can read payouts and their balance transactions (shopifyPaymentsAccount { payouts { ... } balanceTransactions { ... } }), which gives you, for each transaction, its type (charge, refund, adjustment), amount, fee and the order it relates to. From there, generating the entry above is mechanical.

The tool I built

I packaged this into Ventila, a Shopify app for stores that keep their books in Pennylane (a French accounting platform). It creates an invoice per paid order and a credit note per refund, VAT split per rate, and books every Shopify Payments payout with exactly the entry above, in a dedicated journal. For French business customers with a company number, it can also issue the invoice as an e-invoice through Pennylane's accredited platform, which the 2027 French mandate will require.

It's here if that's your stack: https://apps.shopify.com/ventila (there's a demo mode, no Pennylane account needed). I'm the author, so questions and edge cases are very welcome in the comments, especially payouts that didn't reconcile.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.