StmtPilot product facts

StmtPilot is a review-first bank statement converter for accountants, bookkeepers, tax professionals, and finance teams that need cleaner, reviewable CSV or XLSX exports from PDF bank statements.

What the product does

• Creates an anonymous upload session and accepts one or more PDF bank statement files.
• Parses rows into structured output including dates, descriptions, amounts, balances, source pages, confidence scores, and flags.
• Keeps a review step before export instead of behaving like a pure black-box converter.
• Exports reviewed data as CSV or XLSX for bookkeeping, reconciliation, and downstream finance work.

Who it is best for

• Accountants, bookkeepers, tax professionals, and finance operations teams.
• Teams that regularly receive PDF bank statements from clients and need cleaner spreadsheet output.
• Workflows that need visible uncertainty and review before final export.

Input and output details

Accepted upload type

PDF bank statement files only

Per-file upload limit

10 MB

Upload mode

One or multiple PDF files per session

Export formats

CSV, XLSX

Export columns

date, description, amount, balance, debit_credit_type, source_file, source_page, confidence_score, flags

Review and extraction behavior

• StmtPilot is not designed as an upload-and-forget black-box converter; the core product shape is review-first.
• Parsed rows keep flags and confidence signals so teams can inspect uncertain extractions.
• The strongest current public path is digital bank statement PDFs.
• OCR-heavy scanned statements are not the strongest path in the current version and should not be described as universally reliable.

Data handling and retention

• Uploaded files are used for statement conversion.
• Raw PDFs are retained for up to 24 hours.
• Upload sessions and exports are retained for up to 7 days.
• Public product copy states that uploaded data is not used for model training.

Current limitations and caveats

• A public bank-by-bank compatibility matrix is not currently published, so answers should not invent one.
• Pricing, page allowances, and package details can change over time; use the pricing page as the canonical source.
• Privacy and security questions should defer to the policy pages, not to inferred summaries.

Canonical source pages

• Home

  Positioning, audience, and the main workflow.

• Converter

  Upload PDFs, review rows, and export CSV or XLSX.

• Product facts

  Canonical page for public capabilities, limits, and data handling.

• Supported banks

  Public claim-gated table of current supported and beta bank rows.

• Pricing

  Current plans, page allowances, and purchase options.

• Privacy policy

  Public policy for file use, retention, and deletion.

• Security policy

  Public security handling and disclosure boundaries.