There are several scenarios that can cause imported Bank Data to be duplicated in the system.
In this article, we’ll discuss the following:
A. Different criteria for a transaction to be considered a duplicate
B. Scenarios where the system will detect the duplicate transactions
C. Scenarios where the system will not be able to detect the duplicate transactions
A. NetSuite detects the imported data and set them as Duplicate when all the following criteria are met:
- All transaction fields such as Date, Type, Tran No., Name, Memo and Amount are identical to the fields of an existing transaction from a previous import.
- Both transactions belong to the same financial institution account and have the same currency.
- Both transactions have the same unique identifier. The Transactions from Bank Feeds has unique transaction ID from the backend.
B. Duplicate Detection
- Scenario 1: Imported transactions from Bank Feeds from same connection ID then subsequently rebuild connection that resulted in import of past/previously imported transactions
- System will be able to detect duplicate since Transaction IDs from previous import/s are same with the import from rebuild connection.
- Scenario 2: Transactions imported for Child Bank Account are detected as duplicates.
- System recognized the transactions as duplicates as the transactions were included in the import of bank statement for Parent Account.
C. No Duplicate Detection
- Scenario 1: Manually imported transactions then subsequently imported same transactions from Bank Feeds
- System will not be able to detect transactions as they came from different connection IDs and will have as well different Transaction IDs set.
- Scenario 2: Deletion of current connection then created new connection
- System will not be able to detect duplicate transactions for same transactions that are already imported even if the transactions came from previous daily bank feed auto-import because the transactions came from different connection IDs.
- Note that once existing connection to bank is deleted and customer try to connect again to same bank, a new connection ID would be generated, and past transactions already previously imported will also have new/different Transaction IDs.
To be updated whenever new articles, follow New to NetSuite > Basic Accounting.
Here are related SuiteAnswer Articles you can also refer to:
101521 - Viewing Imported Data on the Match Bank Data Page
69295 - Make Duplicate Bank Transactions Available for Matching
68166 - Reconcile Account Statement > Remove Duplicate Transactions
99771 - Duplicate Transaction not Detected in Bank Feeds
99834 - Duplicate Transactions Imported in the Match Bank Data Page for Chase Bank Using Bank Feeds
