--- title: Common Reporting Pitfalls | Shopware Community Hub description: >- Recognize six recurring reconciliation failure modes—timing, reserves, FX, cross-period refunds—and apply sanity checks before escalating. canonical_url: 'https://hub.shopware.com/learn/unit/common-reporting-pitfalls' --- # Common Reporting Pitfalls - **Recognize** the **six recurring failure modes** when reconciling Shopware, **PayPal**, and bank data. - **Apply** quick **sanity checks** before sharing payment numbers with leadership or opening a support ticket. - **Distinguish** when a delta is **expected by design**—timing, reserves, **FX**, or cross-period refunds—versus a true defect. # Unit 5: Common Reporting Pitfalls The month-end checklist from Unit 4 surfaces gaps. This unit explains what those gaps usually are. Six pitfalls account for the large majority of reconciliation escalations across merchants of all sizes. None of them are platform defects. All of them are predictable once you know to look for them. **Strum & Co.'s** owner used to open every reconciliation conversation with "something is broken in PayPal." After working through this unit, she opens it with "let me check which of the six this is." That shift — from panic to process — is the goal. --- ## Pitfall 1: Comparing Gross Revenue to Net Payout **The mistake:** comparing gross order revenue from **Shopware administration** directly to the net payout on the bank statement. **The reality:** they cannot match by design. Fees, refunds, chargebacks, timing gaps, and reserve movements all sit between gross revenue and net payout. **The fix:** compare payout net to Activity-derived nets for the same payout period — not to shop gross alone. Use the payout net formula: captured transactions − fees − refunds − chargebacks ± reserves. --- ## Pitfall 2: Expecting Revenue and Payout to Match by Calendar Month **The mistake:** expecting January revenue to equal January's payout. **The reality:** transactions captured on the last days of a month often settle and pay out in the following month. A capture on January 31st may appear in the February payout batch. **The fix:** reconcile on transaction date and payout date consciously. Document which report uses which date basis — and align finance on the distinction before the first close. --- ## Pitfall 3: Cross-Period Refunds **The mistake:** anchoring reconciliation only on the order date. **The reality:** a refund processed this month against a sale last month reduces this month's payout — not last month's. The refund event date in the **Activity Report** is what determines which period it hits. **The fix:** track refund event date in **Activity**, not order date. Explain cross-period refunds to finance before they surface as unexplained payout reductions. > **For Strum & Co.:** two February guitar returns were processed in March. March's payout was €680 lower than the Activity-derived gross for March. The finance lead flagged it as a discrepancy until she filtered the March Activity Report by transaction type and found the two refund rows referencing February order IDs. --- ## Pitfall 4: Forgetting Reserve Movements **The mistake:** assuming every settled amount appears in the next payout. **The reality:** when **PayPal** holds a reserve, that amount is withheld from payouts and appears in a separate reserve section in **Money / Payouts** — not as a fee, not as a refund, but as a held balance that will be released later. **The fix:** read the **Money / Payouts** reserve section before closing any period. Include ± reserve movements in the payout formula. Do not book reserve movements as fees — they are held funds, not costs. --- ## Pitfall 5: FX Timing Differences **The mistake:** treating a multi-currency delta as a reconciliation error. **The reality:** settlement uses the exchange rate at settlement time — not the rate at the time the order was placed. The difference between the two is FX gain or loss, not a missing transaction. **The fix:** book FX gain or loss explicitly as a separate line item. Do not force shop order currency to equal bank currency line by line without a defined FX policy. For **Strum & Co.** selling to UK customers in GBP and settling in EUR, this is a recurring reconciliation line — not a monthly surprise. --- ## Pitfall 6: Chargeback Cash-Flow Timing **The mistake:** expecting chargeback accounting to feel like a single clean reversal. **The reality:** chargebacks typically debit your balance immediately when received, with a chargeback fee charged at the same time. If you win the chargeback, the re-credit may arrive weeks or months later — in a different payout period than the original debit. **The fix:** flag open chargebacks in **Resolution Center** reporting and model the timing separately. Finance should track win/loss outcomes and expected re-credit dates — not just whether a chargeback was received. --- ## Quick Sanity Checks Before You Escalate Run through these five questions before opening a support ticket: - Did we compare the **same date basis** — order date vs. transaction date vs. payout date? - Did **refunds** land in this period for **prior-period** sales? - Is there an active **reserve or hold** message in the **Merchant Dashboard**? - Are we operating in **multiple currencies** without an explicit FX policy? - Is there an **open dispute** temporarily moving funds in the **Resolution Center**? If all five answers are no and transaction IDs still do not match, open a **Shopware Support** ticket with the transaction IDs and Activity Report export attached. --- ## Summary Six pitfalls explain most reconciliation escalations: - **Gross vs. net** — they cannot match by design - **Calendar month timing** — settlement date ≠ capture date - **Cross-period refunds** — refund date determines which period is affected - **Reserve movements** — held funds, not fees - **FX differences** — rate at settlement, not at order - **Chargeback timing** — debit and credit land in different periods Design your expectations around these six. Investigate real defects only after ruling them out. --- Dispute handling closes the path: distinguishing dispute, claim, and chargeback stages in the Resolution Center, responding within realistic timelines, building lean evidence packs, and adopting habits that reduce dispute volume.