This article covers two specific cases regarding bank transactions:
- Missing transactions for a specific time period
- Duplicate transactions
1. Missing Transactions for a Specific Time Period
⚠️ Important: This section applies only to situations where transactions are missing for a limited time range.
If no new transactions are appearing at all, this may indicate a different issue. In that case, please contact our Support Team directly.
Why are transactions missing?
In most cases, the root cause lies with the bank. If transactions are missing for a specific period, this usually results from a temporary issue or delay on the bank’s side in providing the data.
Why we assume the issue is with the bank:
If the issue were caused by our system (e.g. a technical error in the data request), it would typically be permanent and not just affect a short time frame. A system-wide issue would likely impact all or many users.
What can you do?
You have a few options:
Remove and reconnect the bank connection:
You can delete the current bank connection and reconnect it. This triggers a new data request.⚠️ Warning:
When reconnecting, banks may only deliver data for a limited time range.
Older transactions might be lost if they are outside the bank’s delivery window.
🔒 Important:
We strongly recommend creating a backup of your data before removing a bank connection.
To find out how to perform a backup before reconnecting, please contact the partner through whom you are using our service.
Can missing data be retrieved later?
Unfortunately, from a technical perspective, it is not possible to retroactively retrieve missing transactions from a bank using an existing connection. This limitation is set by the banking infrastructure.
2. Duplicate Transactions
Occasionally, duplicate transactions may appear. Our system includes a duplicate-detection algorithm that compares key transaction attributes (e.g. amount, date, recipient) to avoid duplicates.
Why can duplicates still occur?
One common reason is transaction status changes by banks:
- Some banks differentiate between “pending” and “booked” transactions.
- Between these two states, certain transaction details may change (e.g. a reference or status marker).
- If our system retrieves data during both stages, it may not recognize the two entries as identical and may display them as separate transactions.
What to do in case of recurring duplicates?
In rare cases, certain types of transactions may appear consistently duplicated. This may be due to a specific pattern in the transaction data or a processing anomaly.
In such cases, we rely on our banking data partner to investigate. Due to compliance restrictions, we do not have direct access to the raw bank data. We depend on our partner to send us the affected transactions for analysis.
Once we receive the relevant data, we will investigate the root cause and make necessary corrections.
Summary
| Problem | Likely Cause | Suggested Action |
|---|---|---|
| Missing transactions (specific time range) | Temporary data delivery issue at the bank | reconnect the bank (make backup first) |
| No new transactions at all | Technical error or broken connection | Contact support |
| Duplicate transactions | Status changes or data variations from the bank | Usually self-resolving; contact support if recurring |
Comments
0 comments
Please sign in to leave a comment.