Payroll for Organisations in Timor-Leste · How Xefe Works — Payroll an Auditor Can Follow · Pricing — One Rate, Agreed Annually · Request Access to Xefe · Accountant Access in Xefe · The Xefe Engine — Timor-Leste Payroll Law in Code · Security for Your Xefe Account · Xefe Documentation — How Timor-Leste Payroll Really Works · Getting Started — Xefe Documentation · Running Payroll — Xefe Documentation · Taxes & Statutory Filings — Xefe Documentation · Invoices, Bills & Expenses — Xefe Documentation · Attendance, Leave & Shifts — Xefe Documentation · Privacy Policy · Terms of ServiceRunning Payroll — Xefe DocumentationFrom opening the wizard to handing out payslips — what happens at each step, and the one place Xefe asks you to subscribe.Every payroll run in Xefe follows the same path: build it, get someone else to approve it, pay it, and hand out payslips. The engine handles the tax and social-security arithmetic; you review the numbers before they go anywhere.Before you runTwo things need to be in place before you open Run payroll.

Every employee needs a salary, contracted hours and a tax residence (resident or non-resident) set on their profile — the run names anyone still missing one before it will compute.

Attendance is the one hours-entry workflow in Xefe. Whatever you record there — worked hours, overtime, absences — flows into payroll automatically; you don't re-enter anything.

Night hours (21:00–06:00, including shifts that cross midnight) are detected automatically and paid at the statutory premium.

The run

Open Run payroll — Start a new run from the Payroll menu.

Confirm the period — The pay period and pay date are pre-filled from your configured pay frequency. Adjust them only if this run is a genuine one-off.

Review each employee — Check hours, overtime, bonuses and deductions for everyone on the roster. Validation flags a missing salary, zero hours, or overtime past the legal 16 h/week cap before you can move on. It also warns — without blocking — when a worker under 18 has overtime or night hours, when a 15- or 16-year-old is over the light-work limits, and when the small-employer INSS discount looks unmet: more than ten workers, under 60% Timorese nationals, or an INSS month left unfiled.

Let the engine do the maths — Withholding tax (WIT) and INSS contributions are calculated per employee, following Timor-Leste's statutory rules — never estimated. Every figure stays visible for review.

Submit for approval — This writes the run and its records. Building and reviewing a run is free on every plan — submitting is too. The run now waits for someone else to approve it.

Raises, back pay and premiumsTwo pay movements are handled from the employee's profile, so nothing is retyped into a run.

A raise is recorded by editing the employee's salary, with the month it takes effect and a reason. When a raise is agreed late and back-dated — agreed in April, effective from March — the next run suggests the missing amount as its own retroactive-pay line, computed from that recorded history. Adjust or clear the suggestion on the run if you disagree; once paid it is never suggested again, and it is taxed in the month it is paid, because Timor-Leste's wage tax follows wages paid (Law 8/2008). A raise effective mid-month is flagged for you to price by hand — Xefe only suggests whole months.

An attendance premium (prémio de assiduidade) is set on the employee's profile: the monthly amount, and whether unjustified absence forfeits it entirely or reduces it in proportion to hours missed. Each run resolves it against that period's absence automatically — approved leave and sick days never cost the premium, and someone who joined mid-period keeps theirs. The premium is wage income for tax and sits inside the INSS base.

ApprovalA payroll run can't be approved by the person who created it. A second person with payroll access has to open it and approve it — a database rule, not just a screen, so even a request that bypasses the app is refused if the approver and the creator match.Approving is also the one paid step anywhere in Xefe. Building, reviewing and reporting stay free on every plan; approving a run — what Xefe calls finalizing it — needs an active subscription. If you're on the free plan, you'll only be asked to subscribe at this step.PaymentOnce a run is approved, mark it as paid. Xefe asks for the payment date and a bank reference — both are required, and once attached to the run, that evidence can't be changed; a mistake gets fixed with a reversing entry, never by rewriting the record.If you pay by bank transfer, marking a run paid also generates your salary bank pack. (Paying in cash is a first-class path in Xefe — it posts against cash on hand instead, and there is no pack to send.) For BNU, that's the emailed Excel transfer list and signed payment order the bank actually expects — the same style pack is available for BNCTL as a best-effort layout, worth confirming with your branch.Settlement journal — on payment

2210 Net salaries payable (Dr)

11xx Cash / bank (Cr)

Salaries leave the bank through the bank's own salary-batch process, with a signed payment order.PayslipsEvery employee gets their own payslip as soon as the run is approved — you don't need to wait until it's paid. Each one is a PDF, in English, Portuguese, Tetun and Indonesian, with gross pay, every earning and deduction, and net pay laid out line by line. The PDF and its email come in the language set on the employee's profile; without one, English with a Tetun note.Every approval, journal and statutory deadline is recorded as it happens, so an accountant or auditor can follow the whole month from the run itself — who ran it, who approved it, when it was paid and when it was filed.