Product guide

Payroll runs in Circlz: from draft to finalised

How a payroll run is prepared, reviewed, approved and finalised in Circlz, and why statutory values come from a reviewed rule pack.

Published: 25 September 2026 · Updated: 25 September 2026

Reviewed by Circlz product team on 25 September 2026

In one paragraph

A Circlz payroll run moves from draft to calculated, in review, reviewed, approved and finally finalised. Three different people prepare, review and approve it. Once finalised, a run is locked: postings and loan repayments are written exactly once, payslips are released to employees, and nothing in that run changes again.

Statutory values come from a reviewed rule pack

Income-tax brackets, exemptions, social-insurance limits and rates, and rounding are not written into Circlz's code. They live in a versioned rule pack. A production Egypt pack is entered with its legal source, reviewed by a named qualified reviewer who is not its author, and only then activated. Each run records the pack version it used, so a later version never rewrites an earlier period.

The current environment ships a synthetic pack for testing. Its values are invented, it cannot be edited or activated as a real pack, and every run and payslip calculated with it carries a clear synthetic label. Production environments can refuse synthetic calculations entirely.

Preparing and calculating

Runs are created per pay group and month; off-cycle runs and final settlements name specific employees. Calculation uses salary structures with effective-dated versions, one-off inputs, and leave and attendance inputs where available. Every result is explainable: each line, bracket slice and rounding step is written to the employee's trace.

Review, approval and finalisation

A run with blockers, such as a missing rule pack, cannot be submitted. The reviewer must be someone other than the preparer, and the approver someone other than both. Approval and finalisation recalculate from current inputs; if anything changed, the run returns to calculated for another look instead of finalising stale numbers.

Finalising is safe to retry and produces results once. Finalised does not mean paid: payment, export and filing are tracked separately.

After a run is finalised

  • Bilingual PDF payslips released to employees in My workspace at the release time.
  • Bank transfer files through pluggable formats; a generic CSV ships, and each bank's own format is added once its specification is accepted.
  • A balanced journal export mapped to the company's general-ledger accounts.
  • Loan and advance instalments recorded once in the loan ledger.

All resources