Healthcare finance teams rarely pay one clean vendor category. A typical week can mix medical supply invoices, lab and imaging bills, facility costs, contract clinician expense reports, and credits that arrive after returns or pricing disputes. When those payables sit in different NetSuite paths, AP spends more time assembling the payment calendar than controlling it. NetSuite 2026.2 introduces Payment Runs to bring that work into a single, reviewable process.
What Is a Payment Run?
A Payment Run is a NetSuite accounts payable transaction that lets your team prepare, review, approve, and process payments for multiple payables in one place. Instead of opening each vendor bill or related document separately, AP can group eligible items into a run, confirm the payment account and amounts, then submit the batch for processing.
Payment Runs can include:
- Vendor bills
- Vendor credits
- Journal entries
- Expense reports
- Bill payments (where applicable)
When you select a payment account, NetSuite uses that account to set important context such as subsidiary and currency for the run. After submission, NetSuite’s bulk processing creates the resulting vendor payments in a way that will feel familiar if your team already uses Pay Bills.
For a multi-location dental group, ambulatory network, specialty clinic, medical device company, or life sciences organization, that means one payment cycle can cover several payable types without losing a durable record of what was selected and approved.
Payment Runs vs. Intelligent Payment Automation
The names sound related, and Oracle Help also uses the phrase “payment run” inside Intelligent Payment Automation. They are not the same feature.
Payment Runs in NetSuite 2026.2 are a native accounts payable workflow described in the 2026.2 release notes. The goal is to prepare, review, approve, and process multiple payables from one NetSuite transaction, then create vendor payments through NetSuite’s bulk processing in a way that aligns with classic Pay Bills behavior.
Intelligent Payment Automation is a NetSuite SuiteApp powered by BILL. It adds a Payment Automation dashboard where teams can create payment runs that are funded from bank accounts linked to BILL, then submit those payments to BILL for disbursement. Setup, vendor enablement, and bank verification for BILL are part of that product path.
Healthcare teams can use either, both, or neither, depending on how they disburse today. If your AP process ends in NetSuite vendor payments and bank files or checks you already run, Payment Runs are the 2026.2 workflow to evaluate. If your team is adopting BILL as the payment rail inside NetSuite, Intelligent Payment Automation is the documentation path you will see under Payment Automation.
When you search Oracle Help for “payment run,” confirm which product the article is describing before you update policy docs or training.
Why Healthcare AP Teams Feel This Pain
Healthcare AP is often high volume and high scrutiny at the same time.
Vendor mix is broad. Supply distributors, laboratories, specialty pharmacies, staffing agencies, landlords, IT vendors, and professional services firms may all hit the same weekly payment calendar.
Entities multiply. Practices, clinics, holding companies, and shared services subsidiaries create subsidiary and bank account complexity that classic bill-by-bill payment habits do not handle well.
Approvals and audit expectations are strict. Controllers, CFOs, and external auditors want a clear answer to what was paid, under which approval, from which account, and whether the same invoice was selected twice.
Expense reports sit beside vendor bills. Traveling clinicians, field specialists, and site teams create expense activity that still needs to land in the same cash plan as trade payables.
Payment Runs help because they treat the payment batch as a first-class NetSuite transaction, not as a personal checklist in someone’s inbox.
Why Payment Runs Matter in Healthcare Finance
Clearer disbursement batches. Finance can see what is about to leave an operating or shared-services bank account as one set of work, which is easier to review before cash moves.
Stronger traceability. Related payment activity stays connected to the source transactions. That helps when a practice manager, controller, or auditor asks which run covered a lab invoice, a supply credit, or a clinician expense report.
Fewer accidental duplicates. Selecting the same open payable twice is harder when the work lives in a single run with a defined lifecycle. Duplicate vendor payments are expensive in any industry. In healthcare, they also burn trust with high-volume suppliers.
Familiar NetSuite controls. Payment Runs can work with standard NetSuite capabilities such as roles and permissions, approval workflows, custom fields, saved searches, and (where supported) SuiteScript, REST, and CSV patterns your team already uses.
Payment Runs are not a bank reconciliation feature. They are not patient billing, claims management, or revenue cycle software. They are also not a substitute for invoice capture tools that sit upstream of NetSuite. They focus on the payment preparation and processing step after healthcare payables are already approved and ready to pay.
How a Payment Run Works
Most healthcare AP teams will recognize these stages:
- Create the Payment Run and choose the payment account that should fund the batch.
- Add eligible payables for the subsidiaries and currencies that fit that account, such as supply bills, lab invoices, credits, and approved expense reports.
- Review amounts, discounts, holds, and exclusions while the run is still editable.
- Route for approval if your policy requires a controller, treasury lead, or second AP reviewer before cash moves.
- Submit the run so NetSuite can process the payments through its bulk processing framework.
- Confirm results on the Payment Run and on the related vendor payment and source transactions.
The exact labels and options in your account can vary based on features, permissions, and customization. Treat the first production cycle as a controlled rollout, not a quiet preference flip.
A Healthcare Example
Imagine a regional specialty group with several clinic subsidiaries and a shared services entity that owns the main operating accounts.
On Thursday, AP needs to pay:
- Medical supply invoices for three clinics
- A laboratory statement with one credit memo
- Facility and equipment invoices coded to different locations
- A small set of clinician expense reports already approved in NetSuite
Without Payment Runs, that work often becomes several Pay Bills sessions, spreadsheet side notes, and follow-up questions about what was included.
With Payment Runs, the team can assemble one run per payment account, review the full batch, route it for approval, and keep a durable record of the Thursday disbursement cycle.
That structure is especially useful when private equity backed groups, DSOs, or multi-site provider networks are standardizing AP across newly acquired locations.
Payment Runs vs. Classic Pay Bills
Pay Bills remains a useful path for many healthcare organizations. Payment Runs add structure around multi-document payment preparation.
If your healthcare AP calendar is weekly or biweekly and several people touch selection, approval, and payment confirmation, Payment Runs are usually worth a sandbox walkthrough.
When Payment Runs Are a Good Fit for Healthcare
Payment Runs tend to help when:
- AP pays a high volume of clinical, supply, lab, and facility vendors on a repeating schedule
- Multiple document types feed the same cash cycle, including credits and expense reports
- Finance supports multiple practices, clinics, or legal entities from shared services
- Controllers want a cleaner approval and audit trail before funds leave the bank
- Newly acquired locations are being brought onto one NetSuite AP operating model
They may be less urgent when:
- Payment volume is low and one clerk owns the full cycle end to end
- Most disbursements already leave through a tightly controlled external payment platform, and NetSuite is only recording the result
- Your biggest AP pain is still invoice capture, coding, PO match, or location-level approval upstream of payment
In those last cases, stabilize intake and approval first. Payment Runs work best when the healthcare payables entering the run are already reliable.
Practical Tips Before Healthcare Teams Enable Payment Runs
Start in sandbox with a real Thursday cycle. Use actual supplier mixes, credits, expense reports, and at least one multi-subsidiary scenario that matches how clinics and shared services are set up today.
Map roles early. Decide who can create a run, who can edit selections, who can approve, and who can submit. In healthcare groups, that often means separating clinic-level requestors from shared-services AP and controller approval.
Define “ready to pay” by payable type. A medical supply bill, a lab credit, and a clinician expense report may all reach payment readiness through different upstream paths. Document the rule before the first live run.
Align with existing AP automation. If you use tools such as Stampli or another invoice intake platform, document where that process ends and where Payment Runs begin. Closed periods, approval status, and entity coding should be explicit.
Test searches and reports used by healthcare finance. Update AP aging, cash requirement, location spend, and payment history views so controllers can find runs as easily as they find individual vendor payments today.
Train on exceptions. Credits, vendor holds, partial payments, acquired-location catch-up bills, and last-minute exclusions are where new processes usually stumble. Practice those before go-live.
Key Takeaways
- Payment Runs in NetSuite 2026.2 let healthcare AP teams prepare and process multiple payables as one controlled transaction.
- The feature is about payment batching, review, approval, and processing, not patient revenue cycle, bank reconciliation, or invoice capture.
- Multi-location provider groups, dental organizations, specialty clinics, medical device companies, and life sciences finance teams with recurring mixed payable cycles usually see the clearest benefit.
- A sandbox pilot with real entities, approvals, and exception cases is the safest way to adopt the feature.
How Salora Can Help
Salora ERP helps healthcare and life sciences finance teams evaluate NetSuite release features against the way AP actually runs across clinics, shared services, and operating companies. If you are planning a 2026.2 upgrade, we can help you decide whether Payment Runs belong in your first wave, how they should sit next to your current approval and disbursement tools, and what to test before the first live payment calendar.
Ready to walk through Payment Runs in a healthcare NetSuite sandbox? Contact Salora and we will route you to the right finance lead.