Payment Application Suggestions Auto-Create and Match Bill Payments for Open Payables

What changed

The Match Bank Data page (Transactions > Bank > Bank Matching and Reconciliation > Match Bank Data) now surfaces payment application suggestions on the Match Suggestions subtab. When an imported bank transaction can be paired with an open payable, NetSuite presents either an Apply Payment or Review Payment Options action. Submitting the suggestion causes NetSuite to:

1. Create a bill payment record.
2. Apply it to the open payable.
3. Match the bill payment to the imported bank transaction.

The matched pair then appears on the Reconcile Account Statement page for final reconciliation.

Header field copy behavior

When NetSuite creates the bill payment, it copies the header-level Class, Department, and Location values from the source payable (bill, expense report, etc.) to the payment record.

Constraints

• One-to-one, full-amount only. Partial payments and applying a single bill payment to multiple payables are not supported through suggestions. Use the manual flow on the Transactions to Match subtab for those scenarios.
• Mandatory field limitation. If a mandatory field on the bill payment form requires a value that the suggestion cannot supply — in particular, mandatory line-level Class, Department, or Location fields, or any other custom mandatory field — the suggestion will fail. You must either make the field optional on the payment form or create the bill payment manually.
• Incompatible with Vendor Payment Approval Routing. Suggestions are not generated when Vendor Payment Approval Routing is enabled (custom workflow-based approvals for vendor payments).

Suggestion invalidation

NetSuite periodically validates outstanding suggestions and automatically removes any that become stale. A suggestion is invalidated when:

• The payable is paid, fully credited, voided, deleted, or otherwise closed.
• The amount due changes and no longer matches the imported transaction amount.
• The payable's posting/approval state, account, currency, vendor, or subsidiary changes, making it ineligible.

Rejecting a suggestion moves the imported transaction back to the Transactions to Match subtab. A new suggestion can be generated during a subsequent bank data import or by manually running reconciliation rules.

Note: Undoing reconciliation on the Reconcile Account Statement page does not delete the bill payment that was created from the suggestion. The payment record persists and must be handled separately.

Prerequisites

• The accounting preference Generate Match Suggestions for Accounts Payable must be enabled (it is on by default). Navigate to Setup > Accounting > Accounting Preferences and verify under Bank Matching and Reconciliation.
• Users need the Reconcile and Pay Bills permissions with at least create-level access.
• The payable must be open and posting, and its subsidiary and currency must match the bank account.

What to do

1. Verify the accounting preference. Confirm that Generate Match Suggestions for Accounts Payable is enabled in your target account. It defaults to on, but may have been turned off.
2. Check Vendor Payment Approval Routing. If your account uses custom workflow-based approval routing for vendor payments, be aware that payment application suggestions will not be generated. You must continue using the manual matching flow.
3. Audit mandatory fields on bill payment forms. If your custom bill payment transaction form has mandatory line-level Class, Department, or Location fields — or other custom mandatory fields — those payments cannot be created via suggestions. Either make the fields optional on the form or plan for manual creation.
4. Review permissions. Ensure users who will interact with the Match Suggestions subtab have Reconcile and Pay Bills permissions at create level or above.
5. Downstream scripting impact. If you have beforeSubmit or afterSubmit User Event scripts on the vendorpayment record type, test them against bill payments created via this flow. The system-generated payment may not populate every field your scripts expect. Validate that script logic handles the header-only Class/Department/Location copy and potentially absent line-level values.
6. SuiteFlow / workflow considerations. Any workflows triggered on bill payment creation will fire for suggestion-generated payments. Confirm that approval or notification workflows behave correctly for these system-created records.