HSBC statements use separate Credit and Debit columns in some formats, while others use a single Amount column with signs. Treating one layout like the other leads to wrong amounts or flipped signs. We automatically detect which layout is used and normalize the output.
Multiple Currencies in One Table
HSBC Hong Kong statements mix multiple currencies (SGD, USD, EUR, etc.) in a single table, making it easy to misattribute amounts to the wrong currency. We automatically split and label each currency correctly, ensuring your CSV has separate rows with proper currency identification.
Multiple Accounts Mixed in One Table
HSBC statements combine multiple accounts (e.g., primary cardholder and supplementary cardholders, or multiple sub-accounts) in a single transaction table. We automatically detect and split transactions by account, ensuring each transaction is correctly associated with its account.
Transactions Split Across Multiple Tables
These statements split transactions into separate tables by type (deposits, withdrawals, checks, online transfers, etc.), each with different column layouts. Manually merging these into a single timeline is tedious and error-prone. We combine all tables into one chronological list while preserving transaction type information.
Missing Year in Dates
HSBC Hong Kong statements omit the year from transaction dates (e.g., "15/03" instead of "15/03/2025"), which makes it impossible to sort or reconcile without guessing. We infer the correct year from the statement period and surrounding context.
Sparse Balance Column (End-of-Day Only)
The bank's statements show end-of-day balances, which can create empty cells for certain transactions that occur mid-day. We handle these gaps correctly and ensure all transactions are captured with their proper balance information.
Currency Symbols Breaking Numeric Parsing
HSBC statements embed currency symbols (e.g., "$1,234.56") directly in amount cells, which breaks numeric parsing in Excel and most CSV importers. We strip these symbols so amounts import as clean numbers.
Amount on Continuation Row
These statements place the date and description on one row, but the transaction amount appears on the next row. We detect rows that start with a date as new transactions and merge the amount from the following row.
Blank Dates for Same-Day Transactions
HSBC Hong Kong statements only print the date on the first transaction of each day — the rest have blank date cells. If you paste this into a spreadsheet, most rows will have no date at all. We automatically fill in the missing dates from context.
Inconsistent Date Formats
The bank's statements use different date formats within the same document (e.g., "30 Jun 2025" for statement dates and "15/03/2025" for transactions), which can cause date parsing errors or silent misinterpretation. We normalize all dates to a consistent format automatically.
Sparse Running Balance Column Filled
HSBC statements print a running balance column but leave some transaction rows blank. We fill only the gaps that reconcile exactly between printed balance anchors.
Running Balance Cross-Check
These statements include a running balance column that most converters ignore. Without validating it, missing or duplicate transactions go undetected. We extract this balance and cross-check it against opening/closing balances to ensure every transaction is accounted for.
HSBC statements place the date and description on one row, but the transaction amount appears on the next row. We detect rows that start with a date as new transactions and merge the amount from the following row.
Separate Credit & Debit Columns
HSBC Hong Kong statements use separate Credit and Debit columns in some formats, while others use a single Amount column with signs. Treating one layout like the other leads to wrong amounts or flipped signs. We automatically detect which layout is used and normalize the output.
Multiple Currencies in One Table
HSBC statements mix multiple currencies (SGD, USD, EUR, etc.) in a single table, making it easy to misattribute amounts to the wrong currency. We automatically split and label each currency correctly, ensuring your CSV has separate rows with proper currency identification.
Multiple Accounts Mixed in One Table
These statements combine multiple accounts (e.g., primary cardholder and supplementary cardholders, or multiple sub-accounts) in a single transaction table. We automatically detect and split transactions by account, ensuring each transaction is correctly associated with its account.
Transactions Split Across Multiple Tables
HSBC Hong Kong statements split transactions into separate tables by type (deposits, withdrawals, checks, online transfers, etc.), each with different column layouts. Manually merging these into a single timeline is tedious and error-prone. We combine all tables into one chronological list while preserving transaction type information.
Missing Year in Dates
The bank's statements omit the year from transaction dates (e.g., "15/03" instead of "15/03/2025"), which makes it impossible to sort or reconcile without guessing. We infer the correct year from the statement period and surrounding context.
Sparse Balance Column (End-of-Day Only)
HSBC statements show end-of-day balances, which can create empty cells for certain transactions that occur mid-day. We handle these gaps correctly and ensure all transactions are captured with their proper balance information.
Blank Dates for Same-Day Transactions
These statements only print the date on the first transaction of each day — the rest have blank date cells. If you paste this into a spreadsheet, most rows will have no date at all. We automatically fill in the missing dates from context.
Inconsistent Date Formats
HSBC Hong Kong statements use different date formats within the same document (e.g., "30 Jun 2025" for statement dates and "15/03/2025" for transactions), which can cause date parsing errors or silent misinterpretation. We normalize all dates to a consistent format automatically.
HSBC Sprint Account
个人账户
HKD Current (HKD)HKD Savings (HKD)Foreign Currency Savings (USD)
此格式的常见难点：
Separate Credit & Debit Columns
HSBC statements use separate Credit and Debit columns in some formats, while others use a single Amount column with signs. Treating one layout like the other leads to wrong amounts or flipped signs. We automatically detect which layout is used and normalize the output.
Transactions Split Across Multiple Tables
HSBC Hong Kong statements split transactions into separate tables by type (deposits, withdrawals, checks, online transfers, etc.), each with different column layouts. Manually merging these into a single timeline is tedious and error-prone. We combine all tables into one chronological list while preserving transaction type information.
Missing Year in Dates
HSBC statements omit the year from transaction dates (e.g., "15/03" instead of "15/03/2025"), which makes it impossible to sort or reconcile without guessing. We infer the correct year from the statement period and surrounding context.
Sparse Balance Column (End-of-Day Only)
These statements show end-of-day balances, which can create empty cells for certain transactions that occur mid-day. We handle these gaps correctly and ensure all transactions are captured with their proper balance information.
Blank Dates for Same-Day Transactions
HSBC Hong Kong statements only print the date on the first transaction of each day — the rest have blank date cells. If you paste this into a spreadsheet, most rows will have no date at all. We automatically fill in the missing dates from context.
Amount on Continuation Row
The bank's statements place the date and description on one row, but the transaction amount appears on the next row. We detect rows that start with a date as new transactions and merge the amount from the following row.
Inconsistent Date Formats
HSBC statements use different date formats within the same document (e.g., "30 Jun 2025" for statement dates and "15/03/2025" for transactions), which can cause date parsing errors or silent misinterpretation. We normalize all dates to a consistent format automatically.
Currency Symbols Breaking Numeric Parsing
These statements embed currency symbols (e.g., "$1,234.56") directly in amount cells, which breaks numeric parsing in Excel and most CSV importers. We strip these symbols so amounts import as clean numbers.
Bilingual Column Headers
HSBC Hong Kong statements show column headers and metadata labels in two languages (e.g., "Date / Tarikh"). We detect the relevant fields across both languages so transactions are captured consistently.
Multiple Currencies in One Table
The bank's statements mix multiple currencies (SGD, USD, EUR, etc.) in a single table, making it easy to misattribute amounts to the wrong currency. We automatically split and label each currency correctly, ensuring your CSV has separate rows with proper currency identification.
Multiple Accounts Mixed in One Table
HSBC statements combine multiple accounts (e.g., primary cardholder and supplementary cardholders, or multiple sub-accounts) in a single transaction table. We automatically detect and split transactions by account, ensuring each transaction is correctly associated with its account.
Dates Crossing Year Boundary
These statements contain transactions from two different calendar years (e.g., December and January) but omit the year from dates. Without the statement period for context, there is no way to know which year each transaction belongs to. We analyze the date sequence and statement period to assign the correct year to every transaction.
Sparse Running Balance Column Filled
HSBC Hong Kong statements print a running balance column but leave some transaction rows blank. We fill only the gaps that reconcile exactly between printed balance anchors.
