Bill Payments Can Now Be Created Directly from Bank Matching & Reconciliation

What changed

A new Create Bill Payment button is available on the Transactions to Match subtab at Transactions > Bank > Bank Matching and Reconciliation > Match Bank Data. You can now select one or more outbound bank lines and generate bill payment records without leaving the reconciliation screen.

Supported scenarios

• Bills and bill credits denominated in the bank account currency.
• Installment schedules.
• Partial applications against open balances.
• Payment discounts.

Constraints

• The user must hold the permission required to create bill payment transactions (typically Transactions > Bill Payment at Create level or higher).
• Bill payments that require approval (Pending Approval status) cannot be matched from this screen. Those payments must be created and approved through the standard workflow before they appear as matchable transactions.

Why it matters

Previously, reconciling outbound bank lines against vendor payments required creating bill payments in a separate transaction form, then returning to the Match Bank Data screen to complete the match. This inline creation removes that context switch and reduces the risk of unmatched payment lines sitting in the reconciliation queue.

What to do

1. Verify permissions — Confirm that users responsible for bank reconciliation have the Bill Payment transaction permission at Create level or above. Check via Setup > Users/Roles > Manage Roles.
2. Review approval workflows — If your account enforces bill-payment approval routing (via SuiteFlow or the native approval-routing preference), note that pending-approval payments will not be available for matching. Adjust your process so approvals complete before the reconciliation window, or create those payments outside this workflow.
3. Audit custom scripts on bill payments — If you have User Event or Client scripts deployed on the vendorpayment record type, verify they behave correctly when the record is created from the bank-matching context. The source does not specify whether the standard beforeSubmit/afterSubmit pipeline fires identically, so test in Sandbox.
4. Multi-currency accounts — Only bills and bill credits in the bank account's currency are eligible. If you reconcile a multi-currency bank account, payments in non-base currencies may still need to be created through the standard bill payment form.

Open questions

Oracle's documentation is light on technical detail. Items worth confirming in Sandbox or via support:

• Whether SuiteScript User Event hooks on vendorpayment execute fully when the record is created from this UI.
• Whether the new button is exposed in the bank-matching Suitelet context for any scripted extensions.
• Whether SuiteFlow / approval-routing workflows can be bypassed or deferred for payments created here, or if the feature is hard-gated to auto-approved payments only.