Paddle Billing payout mismatch: filter by remittance reference
Updated · 3 min read
A Paddle Billing payout can contain movements associated with older transactions. To explain one payout, filter the reconciliation report by remittance_reference, not simply the month when transactions were last updated. The default updated-date population can omit a real payout component.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Build the payout report
- Open Reports → Build reports → Build report and choose the payout reconciliation report.
- For one payout, select remittance_reference and the actual remittance. The documented
remittance_reference,transaction_updated_atandbalance_movement_datefilters are mutually exclusive, not simultaneous intersecting filters. - Choose Generate and use the emailed download. Retain the original and filter context.
- Keep every included movement and sum balance_movement_in_balance_currency, with its currency. Do not replace the remittance population with only customer transactions updated in the current month.
Paddle’s payout-reconciliation specification defines the filters and amount field; its report-generation guide describes the download process.
For one remittance, retain all included rows and sum balance_movement_in_balance_currency. Transaction currencies can differ; their values are not a valid combined payout total. Rebates and SWIFT-fee rows also affect the bridge. Keep them rather than selecting only customer transactions.
Tie the remittance to the supporting documents
Authorized Admin or Finance access can obtain payout documents. A remittance may comprise one or two reverse invoices according to the actual US and rest-of-world entities involved. A monthly statement can exist even without a payout; it is not independent proof of cash sent. Keep actual entity and document identities with the remittance reference. Source: payout-document and reverse-invoice scope.
The synthetic remittance exercise gives balance-currency movements of 500, 40, 5 and −10: total 535. The 40 component belongs to a transaction updated before the selected month but moved in this remittance. An updated-month filter incorrectly yields 495. Summing foreign customer-currency amounts is rejected separately.
| Stipulated balance movement | USD amount | Why it stays in the remittance |
|---|---|---|
| Current component | +500 | Included movement |
| Older-updated transaction component | +40 | Belongs to this remittance despite earlier update |
| Additional component | +5 | Included movement |
| Negative component | −10 | Included movement |
| Correct remittance total | 535 | All stipulated members |
| Updated-month shortcut | 495 | Omits the 40 component |
The fixture supplies the USD balance unit and separately identifies EUR and GBP transaction currencies; it does not supply a conversion rate or assign each component to a specific fee type. Do not invent either from the signed values.
Verify the bank currency and arrival
Balance currency need not equal bank currency. Obtain evidenced conversion and bank charges where needed rather than forcing the report sum to the bank line. Retain reference, documents, movement currency and bank observation. Missing conversion or unexplained components remain open. The exercise verifies its supplied membership and signed sum, not a live Paddle export, fee schedule or transfer.
For a PDF-only bank source, download LocalExtract. It processes one PDF locally to date,description,amount CSV; it does not access platform accounts or synchronize accounting records.
Official sources and scope
Documentation checked October 16, 2026. Official reference 1 — lead-01 · Official reference 2 — lead-10 · Official reference 3 — paddle-generate
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy