PDF Parsing Issues
PDF parsing is more complex than CSV. Here are solutions to common issues.
Timeout error
Cause: The PDF took too long to process (over 60 seconds).
Fixes:
- Try uploading again — server load varies
- If the PDF has many pages, try splitting it into smaller files
- Use CSV format instead if your bank offers it (faster and more reliable)
"No transactions found"
Cause: The parser couldn't locate transaction data.
Fixes:
- Make sure this is a real bank statement PDF (not a screenshot or photo)
- Check that the PDF contains selectable text (try highlighting text in a PDF viewer)
- Scanned or image-based PDFs need OCR first — GigBooks doesn't support OCR
- The built-in parser may not support your specific statement layout — try allowing AI extraction
"Unsupported bank"
Cause: No built-in parser matches your statement.
Fixes:
- Allow AI extraction when prompted — it works with most formats
- Or export as CSV from your bank's website instead
Password-protected PDF
Cause: The PDF requires a password to open.
Fixes:
- Remove the password protection first using a PDF tool
- Most bank PDFs use your date of birth or last 4 digits of your account number as the password
- Upload the unlocked version
Incorrect amounts
Cause: The parser may have misread some numbers.
Fixes:
- Compare the total in GigBooks against your statement's summary
- Spot-check individual transactions in the Review tab
- Report persistent issues to support@gigbooks.ca
Related articles
CSV Upload Not Working
Fix common CSV upload issues in GigBooks — wrong format, encoding problems, missing columns, and bank-specific tips.
Transactions Showing Wrong Amounts
Fix issues with incorrect transaction amounts in GigBooks — sign conventions, currency formatting, and debit/credit confusion.
Missing Transactions After Upload
Why some transactions may not appear after uploading to GigBooks — date ranges, duplicates, fiscal year splitting, and pending items.