Payment Application Suggestions Automate AR-to-Bank-Transaction Matching

What Changed

The Match Bank Data page now includes a Match Suggestions subtab that surfaces system-generated payment application suggestions. When an imported bank transaction can be matched one-to-one against an open invoice for the full outstanding amount, NetSuite proposes an Apply Payment or Review Payment Options action. Submitting a suggestion causes NetSuite to create a customer payment record, apply it to the invoice, and match the payment to the bank transaction — all in one step.

Scope and Limitations

• Only one-to-one, full-amount matches are supported. Partial payments and multi-invoice applications against a single customer payment are explicitly excluded; those still require manual creation via the Transactions to Match subtab.
• The feature copies header-level Class, Department, and Location from the invoice to the generated customer payment. Mandatory line-level Class/Department/Location fields — or any other custom mandatory fields the suggestion cannot populate — block payment creation entirely. The workaround is to make those fields optional on the payment form or to create the payment manually.
• Automated Cash Application coexists with this feature. If ACA creates a match for a transaction that already has a payment application suggestion, NetSuite removes the suggestion from the Match Suggestions subtab. Use ACA when you need invoice-ID-driven application, customer identification, or mapping flexibility.

Automatic Invalidation

NetSuite periodically validates outstanding suggestions and removes any that become invalid. Invalidation triggers include:

• Invoice is paid, fully credited, voided, deleted, or otherwise closed.
• Amount due changes so it no longer equals the imported transaction amount.
• Invoice posting or approval state changes, or its account, currency, customer, or subsidiary is modified.

After removal the imported bank transaction remains eligible and will appear on the Transactions to Match subtab. A new suggestion can be regenerated on the next bank data import or manual reconciliation-rule run.

Reconciliation Behavior

If you undo reconciliation on the Reconcile Account Statement page, the customer payment created by the suggestion is not removed. This is a notable difference from a pure match removal — the payment record persists and must be voided or deleted separately if it was created in error.

Prerequisites

• Accounting preference: Generate Match Suggestions for Accounts Receivable must be enabled (on by default). Path: Setup > Accounting > Accounting Preferences > Bank Matching and Reconciliation section.
• Permissions: Reconcile and Customer Payment with at least Create-level access.
• Data requirements: Invoice must be open and posting. Invoice subsidiary and currency must match the bank account.

What to Do

1. Verify the preference is enabled. Navigate to Setup > Accounting > Accounting Preferences and confirm Generate Match Suggestions for Accounts Receivable is active.
2. Audit mandatory fields on customer payment forms. If your payment body form has mandatory line-level Class, Department, or Location fields (or custom mandatory fields), the suggestion engine cannot populate them and will silently fail to generate a payment. Either make those fields optional on the payment form or plan to handle those cases manually.
3. Review ACA interaction. If you run Automated Cash Application, be aware that ACA matches will preempt payment application suggestions for the same transaction. Decide which workflow owns which transaction types.
4. Confirm role permissions. Any user who will act on suggestions needs both Reconcile and Customer Payment at create level or above.
5. Train AR staff on the undo-reconciliation gap. Undoing reconciliation does not void the customer payment — this is a likely source of confusion. Build a process for cleaning up erroneous payments when reconciliation is reversed.