HumaRun is loading.
Skip to content
Finance & payroll teams

A clearer path to payroll review.

Bring approved time, leave and pay changes into one run, clear what is still open, and hand the outputs to your own payment and accounting process.

All solutions

Late changes slow the close.

A change that arrives after cutoff, time nobody approved or an exception nobody owns becomes rework on payroll day. Settle them before the run, so reviewers see only what is genuinely unusual.

A suggested preparation sequenceThree steps · not a product screen
Suggested
  1. SetupSet up pay terms and cutoffsComponents, pay groups, account mappings and who approves
  2. Each runRun the same steps each periodApproved inputs, readiness, review and approval, then lock
  3. First periodsRun in parallel firstCompare your first pay periods with your current payroll
Set up once, then repeat each pay period

Each period, the same four steps.

Setup happens once; these steps repeat every pay period.

  1. Collect approved inputs

    Approved time, leave, loan instalments and pay changes come in. Anything still waiting for approval is flagged.

  2. Resolve what is open

    The readiness check lists blockers and exceptions, such as unapproved time or missing bank details. A run waits until they are cleared.

  3. Review and approve

    Calculation, payroll review, finance approval and final approval, each with its own permission.

  4. Lock and produce outputs

    Lock the run, then produce statements, proof and a payment batch. A journal from your account mappings.

Clear owners, restricted pay data.

Each step has its own permission, and pay data is restricted.

  • Prepare and review

    A payroll manager prepares the run and clears its readiness exceptions before anyone approves. Calculating it and reviewing its variances.

  • Approve in two steps

    Finance approval and final approval are separate permissions. The person who prepared a run cannot approve it; where nobody else can approve, the sole approver’s decision is recorded.

  • Pay data stays restricted

    Salary and payroll amounts, bank details and payment files each need their own permission. A read-only auditor role can review without changing anything.

What payroll covers and how it is controlled.

HumaRun runs, checks and finalizes payroll; your organization sends the payment.

What a run produces

  • Net pay for each employee, and finalized pay statements
  • Pay calculated from the earnings, deductions, overtime, unpaid leave and loan instalments your organization sets up, with each payslip and export marked non-statutory
  • Income tax and social contribution rules are prepared country by country and switched on one country at a time after review
  • Payroll proof that traces each figure to its inputs
  • A payment batch with a bank payment file, approved by someone other than the person who prepared it; where nobody else can approve, the sole approver’s decision is recorded
  • A balanced payroll journal from your account mappings, and the accounting files written from it
  • Pay calendars, period and year close, and void after finalization; a closed year takes no new period and no void
  • Split pay kept in the payment's own currency, and contractor payments approved by someone other than the person who submitted them or added the payee; where nobody else can approve, the sole approver’s decision is recorded
  • Variance checks against earlier runs, and payroll calendars that prepare a draft run before each cut-off for a person to review

Controls built in

  • A parallel run for a new organization's first pay periods, compared with your current payroll person by person until your organization confirms it
  • Finance approval and final approval as separate permissions; the person who prepared a run cannot approve it, and where nobody else can approve, the sole approver’s decision is recorded
  • Your organization sends the bank payment file to its own bank
  • Accounting files laid out for import into Xero, QuickBooks Online and Sage, not verified by those vendors

Bring the right questions.

A clear conversation starts with how your payroll runs today.

  • How often do you pay, and in which currencies?
  • Which inputs feed pay (time, leave, loans, adjustments), and when are they cut off?
  • Who reviews exceptions, and who approves a run?
  • Which outputs do you need: statements, a journal or a payment file?
  • Who sends the payment file to your bank?

These are for your own preparation, and nothing is submitted from this section. Use fictional examples, and please do not send employee, salary, banking or confidential candidate records.