Seeing the HSBC error code PG6 when viewing your transaction history in Internet Banking indicates there are no transactions found for the timeline you specified. The full error message reads: “There are no historic transactions for this account. Please try filtering with a different date period; otherwise, there may be no transactions to report.”
Key Takeaway
- Error PG6 means no transactions found for specified dates
- Try broadening the date filter or range
- Your account may have no transactions within that period
- Confirm account activity dates and filters if needed
Why You Might Get Error Code PG6
There are a few reasons why HSBC may return a PG6 error when querying your transaction history online:
No Activity in Date Range
If there were simply no transactions on your account within the specific date range entered, HSBC will produce the PG6 error indicating it found nothing to match that date filter.
Widening the date parameters or picking a busier period for your account should return some transaction results.
Incorrect Date Range
If you fat-fingered the start and end dates, like entering them backwards or with typos, your date filter itself may be invalid or mismatching the actual timeframe you want to view.
Double check the dates entered are correct.
System Date Mismatch
In rare cases, the dates shown on the HSBC website may not match the true dates in their system databases. A mismatch like this could cause transactions to not appear correctly.
Refreshing the page or logging back in may align the dates between the front-end and back-end.
New Account
On a brand new HSBC account, there may legitimately be no transactions initiated yet if you just opened the account. Any date range will return PG6 until initial activity begins.
Viewing Wrong Account
When filtering transaction history, be sure the account number you are viewing matches the account you want to check. mixups could lead to HSBC error code PG6.
How to fix HSBC Error Code PG6
If HSBC gives you error PG6 for no transactions found, here are some troubleshooting tips:
- Widen the start and end dates to a broader period
- Double check date entries are correct with no typos
- Ensure you are viewing the desired account number
- Refresh the page or re-login to sync date displays
- Verify whether your account had activity in the timeframe
- Call HSBC support if PG6 persists inexplicably
Avoiding Future HSBC code PG6 error
Follow these best practices when querying transaction history to avoid PG6 errors:
- Note any account opening dates to find the earliest activity
- Spot check various wide date ranges to get a sense of transaction history
- Adjust filters gradually to pinpoint recent transactions
- Take note of large transactions as reference points
- Correct any incorrect date filters that return PG6 right away
- Confirm account numbers before viewing history or filtering
Getting a PG6 error when checking your HSBC account history means no transactions were found matching the exact date range entered. Try broadening your search dates or ensuring you are viewing the right account before contacting HSBC support for troubleshooting assistance. Recording your account activity dates helps reconstruct date filters that avoid PG6 errors.
