Search for articles
Bank Import Errors
The Business plan includes a bank statement parser designed to automatically identify subscriptions from your financial records. If you encounter an error during the upload process, it is usually related to file compatibility or data clarity.
Last updated on
1. Supported File Formats
The parser is optimized for specific document types. To ensure a successful import:
Standard PDF: Most bank-generated PDF statements are supported.
Text-based CSV: You can also upload text-based CSV files exported from your banking portal.
No Password Protection: Ensure the file is not encrypted or password-protected, as the system cannot read locked documents.
Readable Content: Avoid uploading scanned images or photos of statements (JPEGs or PNGs), as the parser requires digital text to identify transaction amounts and vendors.
2. Subscription Identification
If your statement uploads but certain tools are missing from the "detected" list:
Clear Vendor Names: The system looks for recognizable software names (e.g., "Slack," "Adobe," "Google"). If a transaction is labeled with an obscure merchant ID, the parser may skip it.
Recurring Patterns: The parser is most effective at identifying tools that appear as consistent monthly or yearly charges.
Manual Correction: If a tool is missed, you can always use the Manual entry tool or the CSV import as a secondary method to ensure your stack is complete.
3. Plan Requirements
If you cannot see the option to import a bank statement:
Check Your Tier: This advanced automation feature is exclusive to the Business plan.
Trial Period: If you are on a 7-day free trial, ensure you selected the Business tier to test this specific functionality.
Troubleshooting
