This error describes Zoho Books bank feeds that stop picking up all transactions or create duplicate entries (for example, one transaction with a value date and one with the posted date). It appears when the feed mapping or the bank connection returns inconsistent rows to Zoho Books, often after MFA or statement-format changes.
What it means
Zoho Books received transaction data from the bank connector that either omitted some rows or returned the same transaction twice because the bank supplied both a posted date and a value date (or the connector resent the same item). This can happen when the bank uses multi-factor authentication flows or when the feed format changed, causing the feed parser to treat two records as distinct instead of one [1][2].
Common causes
- Bank returns both posted date and value date in the transaction description, creating two separate feed records for one payment [1].
- Multi-factor authentication (MFA) or token expiry caused a partial sync, then a reconnect duplicated recent items [2].
- The feed mapping or parser changed after a bank-side update, so Zoho Books sees the same transaction with different keys (description, timestamp) and does not deduplicate [1].
- Manual re-import of the same statement file without clearing earlier imported rows creates duplicates.
How to fix it
- Reconnect the bank feed: go to Zoho Books > Banking > Bank Feeds, find the affected account and choose Reconnect or Refresh. Complete the bank MFA flow if prompted. This forces a fresh sync and refreshes the bank token [2].
- Force a manual refresh and check recent transactions: in Banking > Bank Feeds click Refresh for the past 30 days and review the Unmatched / Feed Transactions list for duplicates or gaps.
- Compare with the bank statement: download the statement from your bank and inspect posted date vs value date. If the bank shows two separate dates in the description, mark that as the reason for duplicated rows and reconcile using the bank statement as source of truth [1].
- Remove duplicates safely: in Banking > Feed Transactions mark the duplicate feed entries as Deleted or reject the duplicate feed import, then reconcile the single correct transaction. Export a small sample before bulk deletes if you want an audit trail.
- Import missing transactions if sync won’t recover them: in Banking > Upload Statement upload the bank statement CSV/OFX/QFX for the missing date range to add missing rows; map columns exactly and avoid importing rows already present.
- If the feed repeatedly returns duplicates, open a support ticket with: bank name, account last 4 digits, exact date range, screenshots of duplicate feed rows, and a CSV export of the bank statement. This lets support compare what the bank returned to what Zoho parsed.
When to escalate
Escalate to Zoho Support when re-authenticating and forced refresh still leave missing or duplicated transactions, or when the bank changed its API/MFA flow and reconnect fails; provide the bank statement, screenshots, and the feed logs so the engineering team can trace the connector parsing.
[1]: Bank Feeds Missing some transactions and duplicating some (https://help.zoho.com/portal/en/community/topic/bank-feeds-missing-some-transactions-and-duplicating-some)
[2]: Zoho Books: Get Bank Feeds from Wells Fargo, Chase and many more (https://www.zoho.com/blog/books/get-bank-feeds-from-wells-fargo-chase-and-more.html)