RowRecon
Convert a credit-card statement to CSV
Use credit-card reconciliation when previous balance, payments, charges, and new balance are present.
Credit-card layouts vary. A Chase-hosted public coupon/summary sample fail-closed because it had no transaction table. Do not assume all card PDFs extract.
The generic local parser may attempt the file. Bank-specific support is not claimed.
RowRecon shows users where extraction may be wrong before they rely on the export.
Convert locally
Upload a PDF, review flagged rows and reconciliation, then export CSV or Excel. The file is not sent to take payment.
Upload a statement PDF
PDF only. Maximum 15 MB and 40 pages. Scanned pages use local OCR in this browser (up to 20 pages) when the file has no usable text layer. Review uncertain rows before export.
Try a sample
Synthetic fixtures only. Samples run through the same local extractor. Output is not hardcoded.
Report a problem
Sends privacy-safe metadata only (parser, counts, recon status, replay fingerprint). The PDF never leaves this browser. Download a redacted layout replay to recreate the issue in tests.
How it works
- Choose a statement PDF (or a synthetic sample).
- Extraction runs in this browser, including local OCR when there is no text layer.
- Uncertain rows stay visible. Click a row to see the source region.
- Where totals exist, reconciliation checks whether balances tie out.
- Export CSV or Excel after review.
FAQ
- Are all credit-card issuers validated?
- No. Synthetic card tables exercise the generic parser. Real issuer validation is recorded only when a real statement has been run privately.
- What if the PDF is only a payment coupon?
- RowRecon fail-closes when it cannot find usable dated transaction rows instead of inventing them.
- Does local OCR invent amounts?
- OCR-derived amounts stay in REVIEW. Ambiguous characters are not auto-corrected to inflate accuracy.