How Zera Books automatically identifies multiple accounts within a single bank statement PDF and splits them into individual output files — detection methodology, output specs, and edge case handling.
Many banks issue combined statements for multiple accounts (e.g., a business checking account and a business savings account in a single 12-page PDF). Zera Books detects account boundaries automatically using a multi-signal approach.
Each page is scanned for account number patterns. When the account number field changes from one page to the next, a new account boundary is established.
Section headers like "Business Checking," "Money Market Savings," and "Visa Credit Card" are recognized as account type signals. The AI identifies these even when formatting varies across banks.
When a new "Opening Balance" or "Beginning Balance" line appears after a "Closing Balance," this signals the start of a new account section within the same PDF.
Column structure changes (e.g., switching from a debit/credit layout to a charge/payment layout) indicate a different account type (checking vs. credit card).
Each detected account gets its own output file, named automatically: e.g., "Chase_Business_Checking_8423.xlsx" and "Chase_Business_Savings_1047.xlsx".
Zera Books classifies and separates the following account types when found in a combined statement.
| Account Type | Detection Signal | Output Columns |
|---|---|---|
| Checking Account | Header keyword, debit/credit columns, routing/account number | Date, Description, Debit, Credit, Balance |
| Savings Account | Header keyword, interest credit patterns, monthly statements | Date, Description, Deposit, Withdrawal, Balance |
| Money Market Account | Header keyword, daily balance tables, interest calculation lines | Date, Description, Deposit, Withdrawal, Balance, Interest |
| Credit Card Account | Charge/payment column layout, APR disclosure, credit limit line | Date, Description, Charge, Payment, Balance, Category |
| Line of Credit | Available credit line, draw/payment columns, interest rate disclosure | Date, Description, Draw, Payment, Balance |
Zera Books automatically splits checking, savings, and credit card accounts without any manual work.
Try for one week →Each detected account produces a separate output file with complete metadata and transaction data for that account only.
Files are named: [Bank]_[AccountType]_[Last4Digits].[ext]. Example: TD_BusinessChecking_7823.xlsx. Filename uses underscores, no spaces.
Each output file includes: Bank Name, Account Type, Account Number (last 4 digits), Statement Period Start, Statement Period End, Opening Balance, Closing Balance.
Only transactions belonging to that specific account are included. No transactions from other accounts appear in the file — boundaries are strictly enforced.
Running balance column is included and arithmetically verified. The closing balance in the output matches the closing balance in the original statement (or a flag is raised if not).
All standard output formats apply to each split file: Excel (.xlsx), CSV, QBO, IIF, Xero import, Sage import. Users select format once and all split files are generated in that format.
After reviewing, users can merge selected split files into a single consolidated export. Merged output includes an "Account" column to identify source account per transaction.
| Edge Case | Handling Approach |
|---|---|
| Account section with no header | Detected via balance reset + column structure change. Flag added for user review. |
| Same account number across periods | Treated as continuation of same account (not split). Period dates updated per section. |
| Account sections without opening balance | Opening balance inferred from first transaction + closing balance math. Flagged as inferred. |
| Credit card with multiple cardholders | All transactions included in single credit card file. Cardholder names preserved in description field. |
| Joint account with shared transactions | All transactions included. Joint account flagged in metadata. |
Zera Books scans each page for account number changes, account type header transitions (e.g., "Checking Account" to "Savings Account"), and structural layout shifts. When a new account section is detected, the system creates a separate extraction context for that account.
Zera Books can separate checking accounts, savings accounts, money market accounts, credit card accounts, and line of credit accounts. Each account type is placed in its own output file named with the account type and last 4 digits.
All accounts are extracted with the same statement period dates. Each output file contains the correct open/close balances and transaction list for that specific account. The period dates are not modified.
Yes. After reviewing the split files, users can select multiple output files and merge them into a single consolidated export. The merged file includes an Account column to identify which account each transaction belongs to.
Explore related Zera Books features and documentation.
Upload any combined bank statement and Zera Books automatically separates each account into its own clean output file.
Try for one week →