Match on Transaction Number and Amount Feature in NetSuite 2026.1

Intelligent Transaction Matching in NetSuite has been enhanced with the introduction of a new rule: Match on Transaction Number and Amount. This feature is essential for accurately reconciling imported bank data with existing account transactions, ensuring both efficiency and accuracy in managing financial records.

What is the Match on Transaction Number and Amount Rule?

This rule allows the Intelligent Transaction Matching to align imported bank lines with account transactions under specific criteria:

• The imported transaction ID must exactly match the account transaction's check number (referred to as the NetSuite Check Number).
• The transaction amounts must be identical.
• The account transaction date needs to be the same as or earlier than the imported transaction date.

This process is crucial for maintaining consistent and accurate financial data within NetSuite.

How Does It Handle Complex Matches?

The rule also accommodates many-to-one and many-to-many matching scenarios. If there are groups of transactions sharing the same transaction number, it will match transactions based on the total amount of the imported bank lines aligning with that of the account transactions.

However, if the defined criteria are not met, the Intelligent Transaction Matching process will automatically proceed to the next active system rule for transaction matching.

User Considerations

Implementing this new matching rule can significantly streamline the reconciliation process, reducing the time needed to manually select correct transaction matches. If your organization frequently deals with numerous imported transactions, enabling and utilizing this feature would enhance financial accuracy and operational efficiency.

Key Takeaways

• The new Match on Transaction Number and Amount rule improves transaction matching accuracy in NetSuite 2026.1.
• Requirements for matching include exact ID and amount matches plus adherence to date conditions.
• The feature works for both simple and complex transaction matching scenarios.
• It enhances operational efficiency by reducing manual reconciliation needs.