Summary
Duplicate transactions can appear when the same transaction is received more than once during sync or when there’s an overlap between pending and confirmed entries.
Why This Happens
Duplicates are usually temporary and caused by how banks send transaction data.
1. Pending vs Confirmed Transactions
Some banks first send a pending transaction and later send a confirmed version.
In certain cases, both may briefly appear as separate entries.
2. Bank Re-sending Data
During sync, banks may resend the same transaction:
- After updates or corrections
- Due to API inconsistencies
This can result in duplicate entries being fetched.
3. Sync Overlap Between Cycles
Since Nance syncs automatically based on system activity and time windows, the same transaction may be picked up again if the bank reports it slightly differently across cycles.
4. Manual + Auto Entry Overlap
If you manually added a transaction and the same one later comes from your bank, both will appear as separate entries.
Important to Know
- Most duplicates are temporary and get resolved in later sync cycles
- Nance improves accuracy over time by identifying repeat patterns
- You can manually delete or ignore duplicate entries if needed
- If duplicates persist for a long time, reconnecting your bank account can help reset the sync state
Nance always prioritizes bank-provided data, so confirmed transactions will eventually stabilize into a single accurate record.