BYTE · HR · Payroll Coming soon

Payroll approval in BYTE: a second signature before salaries are paid

Payroll moves real money, so one person should not draft a run and also post it. BYTE prices the run once when it is submitted, lets the signers approve that priced result, and posts exactly the signed figures. If a figure changes after signing, the run refuses to post.

Last updated: 18 November 2026

Payroll run, MarchWaitingEmployees50Priced on31 MarchSignatures1 of 2Valid for30 daysSignerStatusFinance managerSignedHR managerWaitingGross pay, priced once40,000.000
Illustration of a payroll run waiting for two signers: the priced gross pay, the signers with their status, and the waiting status. The names and figures are examples, not a screenshot.

What it covers

  • A payroll run is priced once, at submission, by the same code that posts it. The signers approve that priced result.
  • The approval is recorded as a signed copy of the run. After the last signature, posting uses exactly the signed figures, with no second pricing.
  • Posting refuses by name if a fact moved after signing: an attendance summary, an employee's pay or bank record, or the month's leave. It also refuses a run whose priced figures are more than 30 days old.
  • Signers hold the payroll approval permission. A line manager, an approval chain or a department head does not sign by role.
  • The people who drafted or submitted the run cannot sign it.
  • Settlements, which cover a leaver's final pay, need a second signature by default. A payroll run needs one when the organisation switches it on.
  • A signed run can be withdrawn by the person who submitted it or by an organisation administrator, and then re-submitted and re-signed.

How it works

  1. Draft the payroll run for the month and submit it. The run is priced at that moment.
  2. The signers see the priced figures, and each signs the approval.
  3. When the last signature is in, the run is ready to post. Posting uses the signed figures.
  4. If a figure moves before posting, the run is withdrawn, submitted again, and signed again.

A worked example

A payroll run of JOD 40,000 gross for 50 employees, priced at submission and signed by two signers. The figures are examples.

StepGross pay (JOD)Result
Run submitted and priced40,000.000Waiting for two signatures
First signature40,000.000Signed by the finance manager
Second signature40,000.000Signed by the HR manager
A salary changed after signing40,250.000Posting refused, run withdrawn
Submitted and signed again40,250.000Posted with the new figures

Posting uses the signed figures only. A change after signing stops the posting until the run is withdrawn, priced again and signed again.

At a glance

Built means the feature is in BYTE's current build. BYTE is coming soon, so ask us for the status of anything you need.

AreaWhat BYTE doesStatus
PricingOnce, at submission; signers approve that priced resultBuilt
PostingPosts exactly the signed figures; refuses by name if a fact movedBuilt
Time limitA priced run more than 30 days old is refusedBuilt
SignersHolders of the approval permission; never a line manager or a department headBuilt
Who cannot signThe people who drafted or submitted the runBuilt
DefaultsSettlements need a second signature by default; runs once switched onBuilt

Ask us before you decide

  • Ask who drafts payroll, and who should sign it, by amount.
  • Ask how often a run changes after it is drafted, such as late attendance or a pay change.
  • Ask whether you want a second signature on leavers' final pay as well.

Questions about payroll approval in BYTE

What is payroll approval in BYTE?

A second person signs the payroll run as it was priced at submission. Posting then uses exactly the signed figures.

Who can approve a payroll run?

Holders of the approval permission. A line manager, a chain of approvers or a department head is not a signer by role.

What happens if a salary changes after the run is signed?

Posting refuses the run by name. It must be withdrawn, priced again and signed again before it posts.

Is a second signature required for every run?

Settlements need one by default. A payroll run needs one once the organisation switches it on.

Can a signed run be cancelled or changed?

A signed run is withdrawn first by the person who submitted it or an organisation administrator, then cancelled or submitted again.

Who can sign their own run?

Nobody who drafted or submitted the run. A leaver cannot sign their own final pay.

Be first to try BYTE.

Send us a short note about your business and the modules you care about. We will tell you when early access opens.

Talk to us See all of BYTE