Bank Accounts¶
Last reviewed: 2026-04-01 · Nnamdi
Status: Complete
Route: /bank-accounts
1. What is it?¶
Bank Accounts is the module for connecting Nigerian bank accounts and importing bank transactions into Finora. It supports two methods: automatic bank syncing via Mono (coming soon) and manual bank statement upload via CSV or Excel. Imported transactions can be matched against existing Finora records (invoices, expenses, receipts) or used to create new transactions. The module also supports PDF statement parsing for major Nigerian banks.
2. How does it work in Finora?¶
2.1 The Bank Accounts page (/bank-accounts)¶
Header: - Heading: "Bank Accounts" - Subtitle: "Connect your Nigerian bank accounts for automatic transaction syncing" - Upload Statement button — navigates to the statement upload flow - Connect Bank Account button — disabled, "Coming Soon" (Mono integration not yet live)
Empty state (no accounts connected):
"No Bank Accounts Connected — Connect your Nigerian bank account to automatically sync transactions, or upload a bank statement manually."
Two action buttons in empty state: - Upload Statement — available - Connect Bank Account — disabled, "Coming Soon"
2.2 Upload Bank Statement flow (/bank-accounts/upload-standalone)¶
Clicking Upload Statement navigates to a dedicated upload page:
Header: - Heading: "Upload Bank Statement" - Subtitle: "Import transactions from CSV or Excel file" - Back navigation button
Step 1: Select Bank Account
"Choose an existing bank account or create a new one for this statement"
Create New Bank Account form:
| Field | Required | Placeholder |
|---|---|---|
| Bank Name | Yes | e.g. GTBank, Access Bank, UBA |
| Account Number | Yes | 0123456789 |
| Account Name | Yes | Business Name |
Create & Continue button — creates the account and proceeds to file upload.
Step 2: Upload File After creating the account, the user uploads a CSV, Excel, or PDF bank statement. Finora parses the file and presents transactions for review.
Step 3: Review & Import Transactions are displayed for matching against existing records or creating new entries (invoices, receipts, expenses).
2.3 Connected bank account (when active)¶
Once a bank account exists, the page shows:
| Field | Description |
|---|---|
| Bank name | e.g., GTBank |
| Account number | Last 4 digits visible |
| Account name | Business name on the account |
| Balance | Last known balance (from statement upload) |
| Transactions | Count of imported transactions |
| Last updated | Date of last statement upload or sync |
3. Business rules & constraints¶
| Rule | Detail |
|---|---|
| Mono integration is "Coming Soon" | Automatic bank syncing via Mono is not yet available — only manual uploads work |
| Supported file formats | CSV, Excel (.xlsx), PDF (for select Nigerian banks) |
| PDF parsing templates | GTBank, Providus, Zenith (as of Feb 2026) — other banks require CSV/Excel |
| Transactions are imported, not posted | Imported transactions need to be reviewed and matched/created before they affect the GL |
| One statement per upload | Each upload covers one bank account and one statement period |
| Bank account creation is required first | You must create or select a bank account before uploading a statement |
| Bulk draft creation | Multiple transactions can be turned into draft entries (invoices, expenses, receipts) in bulk |
4. Nigerian regulatory context¶
Bank reconciliation¶
Nigerian accounting standards require businesses to reconcile their books with bank statements regularly. The Bank Accounts module facilitates this by importing transactions and allowing matching against existing records — highlighting discrepancies.
Bank statement formats¶
Nigerian banks issue statements in various formats: - PDF statements — most common from bank portals; Finora supports parsing for GTBank, Providus, and Zenith - CSV/Excel — available from most bank portals as "transaction history export" - Customers using unsupported banks should export CSV/Excel from their bank portal
Mono integration (planned)¶
Mono is a Nigerian open banking platform that provides API access to bank accounts. When the Mono integration goes live, businesses will be able to connect their accounts for automatic daily transaction syncing — eliminating manual uploads.
5. Common customer questions¶
Q: "When will automatic bank syncing be available?"
The Connect Bank Account feature (via Mono) is marked as "Coming Soon." There is no confirmed date. For now, use the Upload Statement option to manually import transactions from CSV, Excel, or PDF files.
Q: "Which banks are supported for PDF upload?"
GTBank, Providus, and Zenith have built-in PDF parsing templates. For other banks, export your statement as CSV or Excel from your bank's online portal.
Q: "I uploaded a statement but the transactions aren't in my books yet."
Uploaded transactions are imported for review — they are not automatically posted to the GL. You need to match them against existing records (invoices, expenses) or create new entries from them.
Q: "Can I upload statements for multiple bank accounts?"
Yes — create a separate bank account for each account number, then upload statements to the appropriate one.
Q: "My PDF statement didn't parse correctly."
PDF parsing depends on the bank template. If the format is unexpected (e.g., a different statement layout), the parser may fail. Try exporting as CSV instead, or escalate to Tier 2 for template support.
6. Known edge cases¶
Connect Bank Account is disabled¶
The Mono integration is not yet live. "Connect Bank Account" is disabled with a "Coming Soon" badge. This will remain until the Mono integration is deployed. All customers must use manual Upload Statement for now.
PDF parsing only works for 3 banks¶
Only GTBank, Providus, and Zenith PDFs are supported. Customers with other banks (Access, UBA, First Bank, etc.) must use CSV/Excel exports. This is a common support question.
No bank accounts in test business¶
The test business has no connected bank accounts, so the page shows the empty state. Once a bank account is created via Upload Statement, it will appear in the list.
7. Escalation trigger¶
Escalate to Tier 3 (Founder) if: - PDF statement parsing fails for a supported bank (GTBank/Providus/Zenith) - Imported transactions show incorrect amounts or dates - Upload Statement button fails or shows an error
Escalate to Tier 2 (Support Lead) if: - Customer needs help exporting CSV from their bank portal - Customer's bank is not supported for PDF parsing and they need guidance - Customer needs to bulk-import transactions from multiple months of statements - Customer needs to delete or re-import a previously uploaded statement
8. Last reviewed¶
2026-04-01 — Nnamdi. Verified against production. Bank Accounts page for COA Test School Academy: "No Bank Accounts Connected" empty state. Upload Statement button confirmed (navigates to /bank-accounts/upload-standalone). Connect Bank Account button disabled with "Coming Soon" badge. Upload Statement page: "Upload Bank Statement — Import transactions from CSV or Excel file." Create New Bank Account form: Bank Name / Account Number / Account Name (all required). Create & Continue button confirmed. Back navigation button confirmed.