Payout Reconciler V0.2.0
Financial files stay local
Payout checker · before accounting · Public pilot

Reconcile Stripe payouts against your bank statement.

Use the files you already have. No Stripe connection. No bank connection. Financial contents stay in your browser.

Evidence-based matching. Ambiguous rows stay visible for review.
STRIPE PAYOUT RECONCILIATION

Stripe bank reconciliation without an account connection

Payout Reconciler is a payout reconciliation tool for people who need to compare Stripe payouts with bank deposits. Upload a Stripe payout export and a bank statement to check amounts, dates, fees, refunds, adjustments, and unexplained differences in one report.

This Stripe bank reconciliation workflow runs locally in your browser. It is useful for ecommerce operators, freelancers, agencies, and bookkeepers who want to reconcile Stripe payouts before posting entries to accounting software.

A verification layer before accounting: review the evidence here, then continue with your accountant or bookkeeping workflow. This is not an accounting integration.

Stripe payout reconciliation Stripe bank reconciliation Stripe payout matching Bank deposit reconciliation Stripe CSV to bank statement

Bank statements: CSV · XLSX · CAMT.053 · MT940 · OFX · QFX · QBO · QIF · BAI2
Also available: text-based PDF (tested layouts)
Tested formats; bank-dialect coverage varies. Text-based PDFs are supported for tested layouts; complex, multi-account, scanned, or ambiguous layouts may be rejected for safety.

01 · INPUT

Choose a Stripe CSV and bank statement

1
PAYMENT PLATFORM

Stripe CSV

Waiting

What Stripe file should I upload?

A. Stripe Payout reconciliation report — Itemized/Detailed CSV Recommended
Recommended for automatic payouts. It can provide payout breakdown and explanation of fees, refunds, and adjustments. Real Stripe export compatibility is being validated during the public pilot.

B. Payout-level Stripe CSV
Requires payout ID, date, amount/net, and currency. Use for payout-to-bank matching only; detailed explanations may be unavailable. Real Stripe export compatibility is being validated during the public pilot.

Automatic payouts can include transaction-level attribution. Manual payouts may not; this pilot does not recreate attribution Stripe does not provide.

2
BANK

Bank Statement

Waiting

Export a CSV, XLSX, or text-based PDF statement containing incoming deposits.

Minimum: date; amount or debit/credit; description/reference recommended; currency or a manually selected currency.

Text-based PDFs are supported for tested layouts. Complex, multi-account, or ambiguous PDFs may be rejected for safety; scanned/image-only PDFs are rejected because OCR is not supported.

days

Financial files stay in your browser.
Optional anonymous technical telemetry is off by default. Anonymous aggregate pageview counting is enabled without cookies or identifiers.

HELP

Pilot FAQ

What files stay local?

Selected CSV, XLSX, structured bank files, and text-based PDF files are read and reconciled in your browser. The files and transaction rows are not uploaded. PDF support is limited to tested layouts.

Do I need a Stripe or bank login?

No. Export the files from your provider, then select them here. The pilot never connects to a Stripe, bank, or accounting account.

What if my format is not supported?

Use the safe diagnostics download and email only the reviewed structure and error codes to payoutreconciler@proton.me. Do not attach a real statement.

How privacy works

Anonymous technical events are off.

Exact privacy notice: Your financial files and transaction data stay in your browser. The app sends one anonymous aggregate pageview event per page load to Cloudflare to measure overall traffic; it contains only a timestamp and coarse country/Cloudflare location buckets when available, never cookies, identifiers, IP addresses, or financial data. If you opt in, anonymous technical import events are also sent to Cloudflare Workers Logs to improve file compatibility. Events never include file contents, amounts, transaction dates, account/card/IBAN numbers, payout or transaction IDs, references, descriptions, filenames, extracted PDF text, or raw rows. No cookies or persistent identifiers are used. Cloudflare sees the connection IP transiently at the network level; this application does not read or log it, and automatic invocation logs are disabled. Pilot event logs are retained for up to 3 days.

Diagnostic downloads are separate: they are created locally only after your click and are never sent automatically. See the complete schema and retention notice.