Privacy-First Bank Statement Import (PDF, CSV, XLSX)
Drag & drop official bank statements from any institution worldwide. Auto-extract, normalize, and de-duplicate transactions without sharing bank credentials with third parties.
The Flaws of Mandatory Bank Logins
- Handing financial usernames and passwords to third-party aggregators creates security risks.
- Bank connections break constantly due to MFA updates, rate limits, and portal changes.
- Many international banks, credit unions, and wealth portals don't support automatic sync.
The Moza Way: Local & Encrypted File Ingestion
- Import official PDF, CSV, or XLSX statements directly from your bank portal.
- Multi-format layout engine extracts dates, descriptions, amounts, and balances in < 500ms.
- Automatic de-duplication prevents duplicate transaction rows when statements overlap.
Key Capabilities
- Universal File Parser: Supports PDF, CSV, and XLSX statements from thousands of banks, credit unions, and cards worldwide.
- Smart De-duplication: Cross-references dates, amounts, and normalized descriptions so overlapping files never double-count.
- Multi-Currency Normalization: Converts foreign currency statement lines to your primary workspace currency using historical rate archives.
- Password-Protected PDF Support: Safely decrypts password-protected PDF bank statements locally during import.
Frequently Asked Questions
Can I import bank statements without linking my bank account credentials?
Yes! Moza is built privacy-first. You can drag and drop PDF, CSV, QFX, OFX, or XLSX bank statements directly into your browser with 100% zero bank password sharing.
Are password-protected PDF bank statements supported?
Yes. Moza decrypts password-protected PDFs locally inside your browser using client-side AES-256 parsing without sending your bank password to any external server.
How does Moza handle duplicate transactions when importing overlapping date ranges?
Moza calculates a unique SHA-256 hash for every statement line (date + amount + normalized vendor string). Duplicate lines are flagged with a skip badge before anything hits your ledger.
What happens to cryptic bank descriptions like TST* WHOLEFOODS MKT?
Moza's 7-stage normalization pipeline cleans messy bank descriptions into human-readable merchant names (Whole Foods Market) and applies your historical category preferences.
Will credit card statements map to the right account type?
Yes. Credit card statements are automatically detected and mapped to liability accounts (CREDIT), maintaining proper debt tracking and net worth accounting.
Does anything hit my ledger before I review it?
No. All extracted statement items arrive in a bulk review queue (/scans/:id). You review high-confidence and flagged rows before confirming the import to your ledger.
How are AI Credits consumed for statement imports?
Processing a bank statement consumes 15 AI Credits per import session (not per row). If file parsing fails or is canceled, credits are refunded automatically.
Can I edit transaction categories or add notes during statement review?
Yes. You can edit categories, add notes, split shared transactions, or adjust currencies for single rows or bulk selections directly inside the review screen.
Back to All Features or explore Pricing.