Edge Case: Failed Bank Sync / Statement Import¶
Last reviewed: 2026-04-01
Scenario¶
A customer's bank statement upload fails, produces incorrect data, or (in future) an automatic Mono bank sync fails.
Current State¶
- Mono automatic sync: Not yet available ("Coming Soon")
- Manual upload: Supports CSV, Excel, and PDF (GTBank, Providus, Zenith only)
Common Failure Modes¶
1. PDF parsing failure¶
Symptom: Upload returns an error or parses transactions incorrectly (wrong amounts, missing rows).
Causes: - Unsupported bank (only GTBank, Providus, Zenith PDFs are supported) - Unusual statement format (consolidated statement, different layout version) - Password-protected PDF
Fix: Ask customer to export CSV or Excel from their bank portal instead. If the bank IS supported and parsing still fails, escalate to Tier 2.
2. CSV column mismatch¶
Symptom: Amounts appear in wrong columns, dates are misinterpreted, or all transactions show ₦0.
Causes: - Bank CSV uses a non-standard column layout - Date format differs from expected (DD/MM/YYYY vs MM/DD/YYYY) - Currency symbols or thousand separators confuse the parser
Fix: Ask customer to check that the CSV has clear columns for Date, Description, Debit, Credit (or Amount). If the format is non-standard, escalate to Tier 2.
3. Duplicate transactions on re-upload¶
Symptom: Customer uploads the same statement twice, creating duplicate imported transactions.
Fix: Delete the duplicates from the imported transactions list before matching/creating entries.
Future: Mono Sync Failures¶
When Mono integration goes live, potential failure modes include: - Bank authentication expired (customer needs to re-authenticate) - API rate limits exceeded - Bank downtime (Mono depends on bank API availability) - Transaction date range gaps
Escalation¶
- Tier 1: Advise CSV/Excel instead of PDF; help identify duplicate imports
- Tier 2: PDF parsing failures for supported banks; column mapping issues
- Tier 3: Imported transactions with incorrect amounts that affected GL