Payout Reconciliation & Bank Credit Report

What does Processor Payout Exception Report do?

For bookkeepers and finance operators who already have processor and bank exports, this report turns payout review into a short queue with exact amounts and source-row evidence. Check whether signed transaction totals match a declared payout and whether the bank allocations you explicitly supply match that payout. Download JSON, evidence CSV, review CSV and an HTML report.

Use it at each payout review or monthly close when your handoff still involves exports and spreadsheets. It needs no processor or bank login. It does not infer bank matches, move money or create accounting entries. Stripe’s own reconciliation report may already cover your workflow; this Actor adds a reviewable comparison against your separately supplied payout and bank evidence.

Price: $0.50 per completed report, with platform usage included. A new run is billable again. Check the active price on the Pricing tab before running.

Try a known exception in Apify Console

1. Open the Actor’s Input tab in Apify Console. The prefilled input is synthetic and can contain several independent review examples. A completed report uses the listed report price or any applicable Apify credit.
2. For the simpler one-payout walkthrough, download the setup kit, then paste demo/input.json into the Console’s JSON input editor.
3. Start the Actor and open its output links. In this walkthrough, the supplied net total and bank allocation are $87.00, while the declared payout is $86.00. Both residuals are +$1.00. Review the declared payout record before changing any ledger or matching decision.
4. Open the downloaded HTML report, then trace the payout row’s sourceRefs back to the supplied rows. The kit includes the same generated report, so you can inspect the example before a cloud run.

The walkthrough is a synthetic example, not a customer result or a missing-money finding. Mathematical agreement concerns your supplied records only. The Actor cannot authenticate the exports or determine the cause of a variance.

Prepare your own exports once, reuse the setup

The setup kit contains five small CSV templates, a saved configuration, a browser preparation page and a repeat-period checklist. Unzip the kit and open prepare.html locally. Choose your CSV files, review the scope and download input JSON; no software installation or account access is needed. Your files stay in the browser. An optional Node.js 22 script supports the same preparation without packages or network requests.

For a Stripe account’s own automatic payouts, use the documented itemized payout reconciliation CSV, plus your independently declared payout table and bank credits. The kit maps exact transaction and payout IDs and signed major-unit amounts. It deliberately excludes manual/instant payouts and Connect activity. See GUIDE.md in the kit for the current supported columns and export steps.

For normalized CSVs, use templates/transactions.csv and select the normalized recipe. The preparation recipe still covers automatic payouts only. The underlying Actor accepts broader normalized inputs through its Input tab, with unresolved evidence reported honestly.

Prepare one processor/account/currency scope at a time. Provide an account alias, explicit currency scale, fixed UTC asOf, an arrival-date window for transactions and a posting-date window for bank evidence. Mark coverage complete only after checking that your export includes all relevant records. IDs stay literal and case sensitive; only the Stripe currency code is converted to uppercase. Amounts stay signed decimal strings.

Bank allocations are always your decision. Populate deposit-links.csv with exact payout/deposit IDs and explicit signed allocations. The script checks that linked allocations conserve each full deposit. An unlinked credit remains unlinked even when its amount and date resemble a payout. This preparation workflow does not guess or silently repair links.

What is in the report?

Output	What to review
Summary	Payout counts, review/unknown counts and overall supplied-record outcome
Payout evidence	Declared amount, eligible transaction net, linked bank amount and signed residuals
Review queue	Issue codes, explanations and source table/row pointers
Scope	Your explicit account/currency, date windows, coverage and arrival-review policy

Download the dataset in formats such as JSON, CSV or Excel. The output links also expose full nested JSON, flat evidence CSV, findings CSV and standalone HTML. CSV exports neutralize spreadsheet formulas, including negative-looking amounts; use the JSON decimal strings for machine arithmetic. For the simple walkthrough, a shortened payout example is:

{
  "payoutId": "po_demo_001",
  "expected": "86.00",
  "transactionNet": "87.00",
  "residual": "1.00",
  "linkedAmount": "87.00",
  "bankResidual": "1.00",
  "transactionStatus": "variance",
  "bankStatus": "variance"
}

Input limits and repeat use

See the Input tab for all supported options. Each table can be a {"rows":[...]} wrapper or a CSV specification with explicit mappings/defaults. Input is limited to 2 MB and 10,000 combined rows. Currency scales are explicit integers from 0 to 4. Dates are YYYY-MM-DD; asOf is an exact UTC timestamp. Exponents, thousands separators, numeric JSON amounts and ambiguous date formats are rejected.

Reuse an Apify Task for each new period, replacing the evidence and updating the windows and asOf. Save your account alias, currency scale and mappings separately. A schedule reruns saved input; it does not fetch fresh processor or bank exports. For current-data automation, prepare a new input file and call this Actor from your workflow through its API tab.

Identical exported identities are counted once and flagged by the Actor; conflicting IDs and unusable allocations remain quarantined. Partial coverage cannot establish clean agreement. The setup script is stricter: it stops on duplicate identities, out-of-window evidence or unsafe allocations before upload. Fix preparation or use the Actor’s advanced normalized inputs when you intentionally need an uncertainty report.

FAQ and support

Can I upload a bank statement PDF or raw Shopify CSV?

This setup kit does not parse PDFs or promise direct support for raw Shopify exports. It accepts the documented Stripe automatic itemization recipe and the normalized CSV templates. Supply stable explicit IDs and context rather than inventing a join from a date or amount.

Does a review item mean a payout is missing?

No. It can indicate conflicting records, incomplete coverage, a variance or an absent explicit link. The caller-defined arrival-review threshold uses UTC calendar days without a weekend/holiday calendar. Review the evidence and your original records before taking action.

Where is my data stored, and what is charged?

Preparation stays local. A cloud run stores uploaded input and results in Apify run storage under your retention/sharing settings. Minimize records and use account aliases; remove names, bank/card numbers and unrelated columns. The Actor does not log customer rows or call an external data/model service. It charges one report event after successful report delivery; no separate startup or item charge is configured. Same-run recovery verifies saved-report integrity and preserves the one-report charge; a fresh run is billable again.

This report provides operational arithmetic evidence rather than source authentication, fee-policy assessment, FX conversion, financial/tax advice, journal entries or payment approval. Report reproducible mapping problems through the Issues tab using synthetic minimized data. Use the API tab for programmatic examples.

Download the synthetic worked HTML report. Open it locally to inspect the sample before starting a paid run.