Customer Payments Can Now Be Created Directly from Bank Matching

What changed

A new Create Payment button is available on the Transactions to Match subtab within the manual bank reconciliation interface at Transactions > Bank > Bank Matching and Reconciliation > Match Bank Data.

When you select one or more inbound bank lines on that subtab and click Create Payment, NetSuite generates a Customer Payment record automatically. This removes the previous workflow of navigating away to create the payment record separately before returning to match it.

Scope and limitations

• Only inbound (deposit-side) bank lines are eligible — outbound lines are not supported for this action.
• The created customer payment supports application against invoices and credit notes denominated in the bank account currency.
• Installments, partial applications, and payment discounts are supported during creation.
• The user must hold the permission to create customer payments (typically the Customer Payment transaction permission at Create level or above).

Technical notes

Oracle's documentation is light on implementation details. The following points are worth verifying in your environment:

• SuiteScript hooks — If you have User Event scripts deployed on the Customer Payment record (customerpayment), confirm that beforeSubmit and afterSubmit fire as expected when payments are created through this new path. Bank-matching UI flows have historically bypassed some client-side triggers.
• Workflows — Any SuiteFlow workflows triggered on Customer Payment creation should be tested against this new entry point.
• Saved searches / SuiteAnalytics — Payments created this way should appear as standard customerpayment records. Verify that the createdby context and any custom sourced fields populate correctly.
• Roles and permissions — The feature checks for Customer Payment create permission. Roles that have bank reconciliation access but lack payment creation rights will not see the Create Payment button.

What to do

1. Review roles assigned to users who perform bank reconciliation. If they should use this feature, ensure they have Customer Payment > Create permission.
2. If you restrict payment creation to specific approval workflows, test that payments created from the Match Bank Data page still route through your approval logic.
3. Test any User Event scripts or SuiteFlow workflows on the customerpayment record type to confirm they trigger correctly from this new creation path.
4. If you use SuiteScript customizations on the Bank Matching page (e.g., client scripts on bankmatchandreconciliation), verify no conflicts arise with the new button.