Shopify / Prestashop / Stripe reconciliation with Pennylane and Sqalie: the 2026 method

Short answer. On an e-commerce running 500+ orders/month, reconciling the order (Shopify or Prestashop), the PSP (Stripe, PayPal, Shop Pay) and the bank (Qonto) cannot be done by hand. The three-way method we apply in the firm relies on an analytical layer (Sqalie) on top of the accounting platform (Pennylane), with a written cycle handbook. This guide describes each step and each control point.

In a modern e-commerce, money transits through at least three actors before hitting the bank:

• the order (Shopify, Prestashop, Amazon)
• the PSP (Stripe, PayPal, Shop Pay, Alma)
• the bank account (Qonto, BNP, etc.)

Without three-way reconciliation, you can neither rebuild net revenue (post-PSP fees), spot ongoing disputes, nor isolate partial refunds. On a file we took over in late 2025, EUR47,000 of Stripe chargebacks had gone unnoticed for 9 months for lack of this discipline.

For a standard multi-PSP e-commerce month, your accounting hub (Pennylane) must receive at minimum:

1. Gross revenue by channel (account 707, split by market or marketplace)
2. Output VAT by country (account 4457, split France, OSS EU, IOSS)
3. PSP fees (account 627, deductible, split by PSP)
4. Customer refunds (account 7097 or revenue reversal)
5. Chargebacks and disputes (account 658 then 791 on recovery)
6. Marketplace commissions (account 622, deductible, reverse-charged for EU VAT)
7. Ad spend (account 623, reverse-charged for Meta Ireland, Google Ireland)

Each entry must be traceable to the source order via Sqalie.

Sqalie is the piece that makes the method sustainable above 500 orders/month. Without Sqalie, three-way matching stays theoretical.

Our cycle handbook prescribes a 30-minute weekly check:

• Monday: import Stripe and PayPal payouts of the week
• Tuesday: Sqalie ↔ Pennylane reconciliation (accounts 411 and 707)
• Wednesday: review of open Stripe disputes
• Thursday: review of partial refunds and retained shipping
• Friday: country-by-country OSS VAT consistency check

This cadence prevents the drift that makes monthly close unbearable.

Stripe disputes#

Stripe sets a provision on the next payout. Bookkeeping-wise: account 491 (provision) as expense, then settled when the dispute resolves (win or loss). See the Stripe pricing and disputes documentation.

Partial refunds#

Distinguish retained shipping (booked as ancillary revenue or shipping reduction) from refunded shipping (pure reversal). Most common error: full refund while shipping was billed without VAT.

Quarterly OSS#

Sqalie splits VAT by destination country. Pennylane consolidates the quarterly OSS return. The CPA controls the gap between the OSS total and the sum of country-by-country revenue. See our 2026 e-commerce VAT guide.

On files where the method is applied, we close a month in 4 days:

Without the method, expect 15 to 25 days, with undetected residual errors.

Can this reconciliation be done without Sqalie? Yes below 200 orders/month with manual CSV exports. Above that, the time cost beats Sqalie's price.

Is Pennylane enough without an analytical layer? For VAT and year-end, yes. For channel margin and large-scale three-way matching, no — that's where Sqalie comes in.

How long to deploy the method? 2 to 6 weeks depending on volume, number of PSPs and history to clean up. Our e-commerce CPA practice page describes the scoping phase.

Does it work for Amazon FBA? Yes, with extra connectors (Amazon Seller Central API). See our international marketplace OSS/IOSS guide.

What is the first mistake to avoid? Keeping a parallel Excel reconciliation file alongside Pennylane. It doubles the sources and guarantees drift. Single source = Sqalie + Pennylane.

To deploy this method in your e-commerce, contact our e-commerce CPA practice or explore the Sqalie, Pennylane and Prestashop tools.