العربية — This page is not in Arabic yet. Opens the Arabic home page.

Start free trialBook a demo

Browse the documentation

Documentation

All appsHow the apps connectTeam workflowsCompare

Apps

HR ManagementRecruitment (ATS)Payroll & WPSTime & AttendanceAccounting & E-InvoicingCRM & Sales PipelineSales Orders & FulfilmentInventory, Purchasing & WarehousingProcurement & TendersConstruction & ContractingContracts & E-SignatureProducts & Online StorePoint of SaleRentalsSubscriptions & LicensingHelpdesk & TicketingSocial Media SuiteInfluencer Marketing & Campaign ROIProject ManagementActivities WorkspaceDocument ManagementPDF Tools & E-SignatureCorrespondence RegisterTeam Chat & CallsMeetings & VideoLearning & Certification (LMS)Asset ManagementFleet ManagementRecognition & GamificationContacts & PartnersNotification CentreReports & DashboardsInsights — Business Intelligence & AppsAI CopilotAI Agents & AutomationAI Diagram StudioWebsite BuilderISO Compliance Suite (Imtithal)App MarketplaceCustomer & Partner PortalSecurity, Access & Compliance

Payroll Approver — Payroll guide

Sign off a payroll you can defend.

The second pair of eyes. Reads what the specialist prepared, compares it with last month, then approves, pays and posts it — and cannot change a single input.

What you will be able to do

  • See what moved since last month, person by person
  • Read the flags and the explanations before you agree
  • Approve, release the money, and post it to the accounts
  • Send a run back with a reason instead of fixing it yourself

What this role can and cannot do

CanCannot
  • Approve a payroll run
  • Record that the bank has paid
  • Write the payroll into the company's accounts
  • Agree to lend, or reject a request
  • Approve, pay and post a leaver's final settlement
  • See what the bank did with every file sent
  • Download a bank file again from the log
  • Dismiss an odd-looking figure, with a reason
  • Open anybody's payslip
  • Create a payroll run
  • Calculate a run, and hand it over for approval
  • Put somebody on the payroll, or change their pay
  • Add a one-off amount to somebody's payslip
  • See the hours a run will pay
  • See court orders and other obliged deductions
  • Record a loan, settle it or reschedule it
  • payroll:payslip:reveal_grant

17 steps, each one carried out in the product on .

See what is waiting for you #

Where Payroll » Overview

  1. From the launcher, click the Payroll tile.
  2. Read the Runs to review card.
Screenshot: See what is waiting for you, Payroll Approver view
Runs that stopped short of being posted, with the state each stopped at.

You should see The runs that stopped short of approval, and what each one stopped at.

Watch out A run sitting in review for three days is not waiting for the system. It is waiting for you.

Open the run register #

Where Payroll » Payroll runs

  1. In the left menu, under RUN PIPELINE, click Payroll runs.
  2. Open the State filter and choose Review.
Screenshot: Open the run register, Payroll Approver view
There is no New run button on this page for you.

You should see Your queue. There is no New run button on this page for you, which is the point: the thing you check is not the thing you make.

Watch out If your queue is empty, ask the person who prepares runs. There is nothing here for you to start.

Open the run and read its four numbers #

Where Payroll » Payroll runs » Open

  1. From the launcher, click the Payroll tile.
  2. In the left menu, under RUN PIPELINE, click Payroll runs.
  3. Press Open on the run you want.
  4. Read the four figures across the top.
Screenshot: Open the run and read its four numbers, Payroll Approver view
Payslips, total gross, total net, employer cost — with the stage stepper above them.

You should see These are the four figures you are signing for, with the stage stepper above them showing how the run got here.

Watch out Employer cost is gross plus the employer's own contributions. It is the number that hits the budget, and it is not the number people mean when they say "the payroll".

The row of decisions on a run #

Where Payroll » Payroll runs » Open » Lifecycle actions

  1. On the same run, read the row of actions.
  2. Hover over any that are greyed out — each is only enabled at the stage it belongs to.
Screenshot: The row of decisions on a run, Payroll Approver view
Reject and Reopen send work back. Approve locks the payslips. Mark paid records the bank going through. Post to GL writes the cost into the accounts.

You should see Reject and Reopen send work back. Approve locks the payslips to the rulebook version they were calculated under. Mark paid records that the bank went through, and Post to GL writes the cost into the company's accounts.

Watch out Approving is not the end. A run that is approved but never posted is money that left the bank and never reached the accounts — and it is invisible until somebody reconciles the month.

Worth knowing Approving is not the end. A run that is approved but never posted is money that left the bank and never reached the accounts.

Read the variance first — before anything else #

Where Payroll » Payroll runs » Open » Variance

  1. From the launcher, click the Payroll tile.
  2. In the left menu, under RUN PIPELINE, click Payroll runs.
  3. Press Open on the run you want.
  4. Press Variance.
  5. Read the headline, then every person listed underneath.
Screenshot: Read the variance first — before anything else, Payroll Approver view
Headcount, net and employer cost against the previous run, then every person who moved beyond the threshold, with the reason, and the joiners and leavers.

You should see Headcount, gross, net and employer cost against the previous run, then every person whose net pay moved beyond the threshold, with the reason, and the joiners and leavers. This is the single most useful screen you have.

Watch out Read this BEFORE the totals look reasonable to you. A payroll that is right in aggregate can still be wrong for eleven people, and the aggregate is what makes you stop looking.

Worth knowing The same comparison appears again inside the Approve confirmation, so you get one last look at it with your finger on the button.

Read the flags and the explanations left on them #

Where Payroll » Payroll runs » Open » Anomaly detection flags

  1. From the launcher, click the Payroll tile.
  2. In the left menu, under RUN PIPELINE, click Payroll runs.
  3. Press Open on the run you want.
  4. Scroll to Anomaly Detection Flags.
  5. Read the open flags, and the reasons on the dismissed ones.
Screenshot: Read the flags and the explanations left on them, Payroll Approver view
A dismissed flag still shows who dismissed it and why.

You should see A dismissed flag still shows who dismissed it and why. If a reason does not convince you, send the run back rather than accepting it.

Watch out If a reason does not convince you, reject the run with that as the reason. Accepting a weak explanation is how a bad payroll gets signed.

Go from a total to the person behind it #

Where Payroll » Payroll runs » Open » Payslips

  1. Open the run and scroll to the payslips, or open Payslips from the left menu.
  2. Sort by net, or search for the person the variance flagged.
  3. Press View on their row.
Screenshot: Go from a total to the person behind it, Payroll Approver view
The breakdown groups every line into basic, allowances, deductions and net.

You should see Every payslip in the run, led by the person's name, and each one opens the full line-by-line breakdown.

Watch out If the variance flagged somebody, open their slip rather than accepting the reason on the summary. It takes ten seconds.

Read the bank file's history #

Where Payroll » Payroll runs » Open » Bank / WPS

  1. From the launcher, click the Payroll tile.
  2. In the left menu, under RUN PIPELINE, click Payroll runs.
  3. Press Open on the run you want.
  4. Scroll to the bank panel.
  5. Read the submission log and the banner above it.
Screenshot: Read the bank file's history, Payroll Approver view
Each file's status, the bank reference, the deadline and the days left.

You should see Every file generated for this run, what the bank said about it, the bank reference and how long is left on the statutory window.

Watch out A file marked generated and never submitted looks the same as one nobody made. If the log is empty on a paid run, ask why before you post it.

Record what the bank said #

Where Payroll » Payroll runs » Open » Bank / WPS » Mark submitted

  1. In the bank panel, press Mark submitted on the file you sent.
  2. Enter the reference the bank gave you.
  3. When they confirm, press Accepted. If they bounce it, press Rejected and type the reason.
  4. After a rejection, press Regenerate + resubmit.
What each field wants
FieldWhat to put in it
Bank / MOHRE referenceWhatever the bank or the portal gave you back. This is what you will be asked for if a salary goes missing.
Rejection reasonRequired on a rejection. Copy the bank's own wording rather than paraphrasing it.
Screenshot: Record what the bank said, Payroll Approver view
The log stops being a list of files and becomes the answer to "was everyone paid, and if not, why not" — with the statutory deadline counting down beside it.

You should see The log stops being a list of files and becomes the answer to "was everyone paid, and if not, why not" — with the statutory deadline counting down beside it.

Watch out Record the submission the same day. The deadline in the log is statutory and counts from the end of the pay period, not from when you got round to it.

Check the file can actually be produced #

Where Payroll » Payroll runs » Open » Bank / WPS » Pre-flight

  1. In the same bank panel, choose the format and press Pre-flight.
Screenshot: Check the file can actually be produced, Payroll Approver view
Errors and warnings counted separately, with every offending line named.

You should see Approving a run whose bank file cannot be produced only moves the problem to the day the salaries are due. Two seconds here saves that.

Watch out Approving a run whose file cannot be produced only moves the problem to payday. Two seconds here saves that.

Decide on the loans waiting for you #

Where Payroll » Loans & advances » open a loan

  1. Open Loans & advances.
  2. Click a pending row to open it.
  3. Read the principal, the term and the schedule.
  4. Press Approve, or Reject with a reason.
Screenshot: Decide on the loans waiting for you, Payroll Approver view
Approving builds the instalment schedule that every future run then deducts on its own.

You should see Approving generates the instalment schedule that every future run deducts automatically. Rejecting keeps your reason on the record.

Watch out You cannot approve a loan you asked for yourself — the system refuses it. If the loan is yours, somebody else decides it.

Worth knowing You cannot approve a loan you asked for yourself. If a loan is yours, somebody else decides it.

Decide on the leavers waiting for you #

Where Payroll » Final settlements

  1. In the left menu, under COMPENSATION, click Final settlements.
  2. Click a leaver's name.
  3. Read the itemised lines and the clearance list, then approve.
  4. Once approved, use Pay, then Post to GL.
Screenshot: Decide on the leavers waiting for you, Payroll Approver view
Outstanding clearance items are counted, and approval refuses while they are open.

You should see End of service, unused leave, notice and the final month, less loans and anything not handed back. Outstanding clearance items are counted, and approval refuses while they are open.

Watch out A settlement walks the same one-way road as a run: draft, approved, paid, posted. Cancel is only available before it is paid.

You cannot create the thing you check #

Where Payroll » Payroll runs

  1. Open Payroll runs and look at the top of the page.
Screenshot: You cannot create the thing you check, Payroll Approver view
There is no New run button.

You should see If your queue is empty, that is a question for the person who prepares runs — not a button for you. The checker creating the work would collapse the whole control.

Watch out This is deliberate and it is not negotiable. The checker creating the work would collapse the whole control.

You cannot change what anyone is paid #

Where Payroll » Employment contracts

  1. Open Employment contracts.
  2. Tick a few rows and look at the bar that appears.
Screenshot: You cannot change what anyone is paid, Payroll Approver view
It offers you nothing that changes them.

You should see Reading what somebody is paid is a completely different authority from changing it, and the split is enforced on the batch exactly as it is on one row.

Watch out Reading what somebody is paid and changing it are different authorities, and the split holds on a batch of four hundred exactly as it does on one.

The hours behind the run are closed to you #

Where Payroll » Work entries is not in your menu.

  1. Look down the left menu.
  2. There is no Work entries entry, and no Salary attachments entry.
Screenshot: The hours behind the run are closed to you, Payroll Approver view
What you CAN see is the result: the payslips, the variance and the reports.

You should see You approve the RESULT of the hours, not the hours. Changing an input after seeing the total is precisely what the split exists to prevent.

Watch out If the hours look wrong, reject the run and say so. Fixing the hours yourself would make your own approval worthless.

Check what the month cost before you release the money #

Where Payroll » Payroll reports » Headcount cost

  1. In the left menu, click Payroll reports.
  2. Set the two dates, press Headcount cost and read the employer cost column.
Screenshot: Check what the month cost before you release the money, Payroll Approver view
What the company pays out for the period, by department.

You should see What the company is paying out for the period, by department, from the same payslips — so you are approving the full cost, not just the net pay.

Watch out You are approving the full cost, not just what lands in people's accounts.

Giving someone access to real payslips is not yours #

Where Payroll » Payslips

  1. Open Payslips and scroll to the bottom of the page.
  2. The list is followed only by the suggestions strip: there is no Payslip access card.
Screenshot: Giving someone access to real payslips is not yours, Payroll Approver view
You read every payslip in full, but you cannot extend that to anyone else. The person who checks the run does not also decide who else may see what people are paid.

You should see You read every payslip in full, but you cannot extend that to anyone else. The person who checks the run does not also decide who else may see what people are paid.

Use cases — the work, step by step

Each one is a sequence somebody actually performs, with the screen behind every step. Every screen here was opened in the product as this role before it was published.

monthlySign off a payroll you can defend #

In this order, because the variance is the only screen that finds the eleven people a correct total hides — and once you have seen a reasonable total, you stop looking.

  1. Open the run that is waiting for you. Read the four figures, then stop reading them.

    Payroll Approver doing "Sign off a payroll you can defend" in Tarleaks ERP — Open the run that is waiting for you. Read the four figures,
    Payroll » Payroll runs » Open — verified: the page says “Lifecycle actions”
  2. Open the variance and read the person list. Joiners and leavers should explain most of the movement; anything they do not explain is your question.

    Payroll Approver doing "Sign off a payroll you can defend" in Tarleaks ERP — Open the variance and read the person list. Joiners and leav
    Payroll » Payroll runs » Open » Variance — verified: the control is offered
  3. Read the flags and the reasons left on the dismissed ones. If a reason does not convince you, it is not a reason.

    Payroll Approver doing "Sign off a payroll you can defend" in Tarleaks ERP — Read the flags and the reasons left on the dismissed ones. I
    Payroll » Payroll runs » Open » Anomaly detection flags — verified: the page says “Anomaly Detection Flags”; no “duplicate_iban” anywhere on the page; no “salary_spike” anywhere on the page; no “no_attendance” anywhere on the page; no “zero_deductions” anywhere on the page
  4. Open the payslips of anybody the variance named. It takes ten seconds and it is the difference between signing and rubber-stamping.

    Payroll Approver doing "Sign off a payroll you can defend" in Tarleaks ERP — Open the payslips of anybody the variance named. It takes te
    Payroll » Payroll runs » Open » Payslips — verified: the page says “Payslips”; 25 row(s) listed
  5. Pre-flight the bank file before you approve, so you are not approving a run that cannot be paid.

    Payroll Approver doing "Sign off a payroll you can defend" in Tarleaks ERP — Pre-flight the bank file before you approve, so you are not
    Payroll » Payroll runs » Open » Bank / WPS » Pre-flight — verified: the control is offered; no “company_iban” anywhere on the page
  6. Approve — the confirmation shows you the variance one last time — then release the money and post it to the accounts.

    Payroll Approver doing "Sign off a payroll you can defend" in Tarleaks ERP — Approve — the confirmation shows you the variance one last t
    Payroll » Payroll runs » Open » Lifecycle actions — verified: the page says “Lifecycle actions”; the page says “Mark paid”
  7. Record what the bank did with the file. A file generated and never marked submitted looks exactly like one nobody made.

    Payroll Approver doing "Sign off a payroll you can defend" in Tarleaks ERP — Record what the bank did with the file. A file generated and
    Payroll » Payroll runs » Open » Bank / WPS » Mark submitted — verified: the control is offered

urgentSomething does not look right — send it back #

Fixing it yourself would destroy the only thing that makes your approval worth having.

  1. Confirm what is wrong: open the variance, then the payslips of the people it names.

    Payroll Approver doing "Something does not look right — send it back" in Tarleaks ERP — Confirm what is wrong: open the variance, then the payslips
    Payroll » Payroll runs » Open » Variance — verified: the control is offered
  2. Press Reject and write what the preparer must fix. The reason stays on the run and they are told.

    Payroll Approver doing "Something does not look right — send it back" in Tarleaks ERP — Press Reject and write what the preparer must fix. The reaso
    In the product — verified: the control is offered; the control is offered
  3. If you have already approved it and it is not yet paid or posted, Reopen clears the approval instead. A paid or posted run cannot be reopened, and that is correct.

    Payroll Approver doing "Something does not look right — send it back" in Tarleaks ERP — If you have already approved it and it is not yet paid or po
    Payroll » Payroll runs » Open » Lifecycle actions — verified: the page says “Lifecycle actions”; the page says “Mark paid”

weeklyDecide the loans and the leavers waiting on you #

Both queues are people waiting for an answer, and neither one sends you a reminder.

  1. Open a pending loan, read the amount, the term and the schedule it would create, then approve or reject with a reason.

    Payroll Approver doing "Decide the loans and the leavers waiting on you" in Tarleaks ERP — Open a pending loan, read the amount, the term and the sched
    Payroll » Loans & advances » open a loan — verified: the control is offered; the action is not offered to this role; no “Loan · Loan” anywhere on the page; the action is not offered to this role
  2. Open the leavers' settlements. Outstanding clearance items are counted, and approval refuses while they are open.

    Payroll Approver doing "Decide the loans and the leavers waiting on you" in Tarleaks ERP — Open the leavers' settlements. Outstanding clearance items a
    Payroll » Final settlements — verified: the page says “Final settlements”
  3. Check the employer's own cost for the period before you release anything — you are approving the full cost, not just the net.

    Payroll Approver doing "Decide the loans and the leavers waiting on you" in Tarleaks ERP — Check the employer's own cost for the period before you rele
    Payroll » Payroll reports » Headcount cost — verified: the page says “Headcount cost”; 18 row(s) listed

You cannot change a single input — not an hour, not a wage, not a payslip. If something is wrong, reject it with a reason and it goes back to the person who prepared it. Fixing it yourself would destroy the only thing that makes your signature worth having.

All payroll role guides

Last updated