Input reference · tested layouts
Supported bank statement formats
Payout Reconciler reads bank-side files locally in your browser. A format being listed means selected fixture or structural layouts were tested—not that every bank dialect is guaranteed.
| Format | Current pilot status | Important limitation |
|---|---|---|
| CSV | Supported for common delimited statements | Column names, dates, decimals and currency may need review or mapping. |
| XLSX | Supported for tested OOXML workbook shapes | Multiple plausible sheets require selection; formulas are not calculated. |
| CAMT.053 | Supported for tested XML layouts | Bank dialect and namespace variations may differ. |
| MT940 | Supported for tested statement layouts | Field structure varies between institutions. |
| OFX / QFX / QBO | Supported for tested structured samples | Institution-specific extensions may be rejected. |
| QIF | Supported with an explicit currency when absent | Currency is not safely guessed when the file omits it. |
| BAI2 | Supported for tested samples | Account-specific record variants may need review. |
| Text-based PDF | Experimental; tested layouts only | Complex, multi-account, ambiguous, damaged, or scanned/image-only PDFs may be rejected. OCR is not available. |
What the bank file needs
For reliable mapping, the statement should expose a date and amount or debit/credit fields. A description, reference, and currency help explain matches. If the currency is absent, the application can ask you to select it manually.
Safety boundary: The application does not upload the file, infer unsupported formats from an extension alone, or claim universal bank compatibility.
Have a statement to check?Check a payout
Read how local processing and diagnostics work or troubleshoot a mismatch.