Skip to content

Payroll

NextHealth Flow

Sold separately; requires Flow HR

NXH Flow Payroll prepares salary runs from the staff records maintained in Flow HR. Salary components, approved overtime, loans and salary advances feed the calculation. Each run passes through HR, finance and final approval before it is marked paid, with a payroll register available for finance. Teams can review the calculation and approval sequence together rather than treat the final figure as the only record. Flow Payroll is selected separately and requires Flow HR to operate.

Follow the salary run through each approval

  1. Step 1

    Prepare

    Review salary components and adjustments

  2. Step 2

    Calculate

    Build the salary run from HR

  3. Step 3

    Approve

    Complete HR finance and final approval

  4. Step 4

    Record

    Review the register and paid status

What your team can do

  • Build salary structures from the components your team maintains.
  • Include approved overtime in the relevant salary run calculation.
  • Account for staff loans and salary advances during processing.
  • Route the run through HR, finance and final approval.
  • Provide the payroll register for the finance team’s review.
Why it is hard to do well

Every salary total needs a reviewable route to approval.

Follow the salary run through each approval

A salary run needs an explanation as well as a total. HR and finance need to understand the salary structure, approved overtime and adjustments before agreeing that a run is ready. Keeping those decisions close to the calculation makes the review easier to follow.

NXH Flow Payroll uses the staff records in Flow HR. Salary components, loans, advances and approved overtime feed the run, which passes through HR, finance and final approval before being marked paid. The payroll register gives finance a record to review alongside that approval sequence.

Payroll reads the staff and attendance records in Flow HR, so Flow HR must be in your scope. Approved payroll records show how a run was calculated and who approved each stage. They are not a bank submission, and they do not show that a bank or any authority has accepted a payment.

Illustrative example: one salary run

This example uses synthetic data.

A synthetic staff member has a salary structure with a basic component and an allowance. For the month, Flow reads the attendance summary, deducts one unpaid leave day, adds approved overtime and takes the loan instalment. HR reviews the run, finance approves it and a final approver completes the approval. The run is marked paid, loan instalments are settled and the payroll register shows the figures for finance.

Bring a sample salary structure and an overtime or advance example to your demonstration. Follow the calculation and each approval before reviewing the register. Establish your payment process separately: marking a run paid does not transfer money.

Common questions

  • Flow Payroll is sold separately and requires Flow HR. The HR and Payroll pairing brings both modules together; Payroll is not a standalone option without HR.

  • A recorded paid status is not a promise of a bank transfer. Confirm the payment execution arrangements separately from the calculation and approval workflow.

  • The described calculation includes salary components, approved overtime, staff loans and salary advances. Demonstrate your own structure to check how those items are represented.

Not answered here? Contact the team

Our clients

See every client

Bone Care One Day Surgery Center

See Payroll in action

Tell us how your team works today. We will focus the demonstration on the tasks, handovers and information you want to review.