Salary structures with many components
Basic, allowances, a variable component paid quarterly or annually, and reimbursements on claim. Revisions are frequent and effective-dated, so a promotion cycle in one month produces arrears in the next run.

Monthly salaried staff, variable pay and bonus schemes, flexible benefits, remote allowances, and a finance team that wants cost by practice or client.
Consulting, software, agencies and firms of accountants or architects pay salaried people monthly, with the complexity in the variable parts and in where the cost lands. The configuration for this shape.
Basic, allowances, a variable component paid quarterly or annually, and reimbursements on claim. Revisions are frequent and effective-dated, so a promotion cycle in one month produces arrears in the next run.
Annual and quarterly bonuses run as their own runs with their own approval. They are taxed on the pay date's rules and posted to the cost centre of the practice or team.
Health, dental, life and retirement plans with employee-chosen coverage, an open enrolment window once a year and life-event changes outside it.
Locations for people working from other regions, each with its holiday calendar and regional rule, and allowances as components on the salary structure.
Assignments put salary cost in the practice cost centre; approved timesheets can split hourly components across cost centres. Allocating salaried pay or all employer cost by client effort requires an agreed allocation extension and reconciliation.
Positions carry a salary band, requisitions are approved against headcount, and an offer within band is approved by the HR Manager while one above band goes to the controller as well.
Annual leave accruing monthly with a carry-forward cap, sick leave with certificate rules, and a leave liability accrual the controller posts each quarter.
Flexible benefits
Bonus and off-cycle runs · Remote and hybrid staff · Hiring against bands
Salary structures with many components · Cost by practice or client · Leave that accrues and carries
Same records, same gates. The configuration changes how the process runs for this team.
At year-end the YearEndStatement and EmployeeTaxCertificates are produced from the year's payslips, Finance Controller approves the statement (Status: Prepared → PendingApproval → Approved), employee certificates link their ApprovalStatement before PublishedOn is set, and Finance Controller locks the TaxYear (Status: Open → Locked), and posting into it requires reopening by a named role.
HR Manager approves it (Status: PendingApproval → Active).
Approval conditions.
At year-end the YearEndStatement and EmployeeTaxCertificates are produced from the year's payslips, Finance Controller approves the statement (Status: Prepared → PendingApproval → Approved), employee certificates link their ApprovalStatement before PublishedOn is set, and Finance Controller locks the TaxYear (Status: Open → Locked), and posting into it requires reopening by a named role.
Finance Controller reviews it in Journals to Post and posts it (Status: Draft → Posted);
Payroll Officer runs the calculation (Status: InputsLocked → Calculated).
Payroll Officer submits the run (Status: Calculated → PendingApproval).
| Pay Run Number | Legal Entity | Pay Calendar | Pay Period | Run Type |
|---|---|---|---|---|
| PR-80607 | LE-41929 | PC-8258 | PP-10416 | Regular |
| PR-62914 | LE-56964 | PC-7164 | PP-98417 | OffCycle |
| PR-79369 | LE-53781 | PC-4633 | PP-48246 | Bonus |
| PR-38822 | LE-24818 | PC-5174 | PP-53519 | FinalSettlement |
| PR-37094 | LE-74136 | PC-3625 | PP-86388 | Arrears |
| PR-34638 | LE-49049 | PC-8181 | PP-36724 | Regular |
HR Manager approves it (Status: PendingApproval → Active).
Active waits for the hr manager.
Practice or team leads as Line Managers, Employees in self-service are configured as roles at rollout; the spec has no matrix column for them yet.
Owns the employee master, assignments, positions, policies, offers and exits, and decides leave exceptions and compensation revisions.
Manage Employees, EmployeeAssignments, EmployeeDocuments, Positions, Departments, Locations, Holidays, WorkPatterns, CompensationRecords, CompensationLines, LeavePolicies, LeaveBalances, BenefitPlans, BenefitEnrolments, Policies, PolicyAcknowledgements, OnboardingTasks, ExitsApprove JobOpenings, Offers, CompensationRecords, EmployeeAssignments, BenefitEnrolmentsApprove LeaveRequests assigned through the entity's escalation ruleRuns openings from requisition to accepted offer.
Manage JobOpenings, Candidates, Interviews, OffersView Positions, Departments, Employees (directory fields)Submit JobOpenings and Offers for approvalPrepares the pay run: employee pay setup, inputs, calculation, review, payslips, bank file and statutory returns.
Manage PayRuns, PayPeriods, PayrollInputs, Payslips, PayslipLines, Garnishments, LoansAndAdvances, PaymentBatches, Payments, PayComponents, PayCalendars, Shifts, StatutoryRules, StatutoryRuleBands, StatutoryFilings, EmployeeTaxDetails, CompensationLines, BankAccountChangeRequestsEdit draft CompensationRecords (PayBasis, AnnualGross, HourlyRate, DailyRate, Currency, EffectiveFrom, EffectiveTo, RevisionReason)Edit Employees (TaxIdentifier, SocialInsuranceNumber, PaymentMethod, PayCalendar)Approval waits for the payroll officer.
Approves the pay run, authorises the bank file, owns the payroll journal and its reconciliation to the ledger, and locks periods and tax years.
Approve PayRuns and return submitted runs for correctionAuthorise PaymentBatches only when not the run preparer or approverApprove StatutoryFilings year-end statements and authorise statutory paymentsActive waits for the hr manager.
The employee record, assignments and the org chart, documents with verification and expiry, tax details, salary structures, onboarding checklists and exits.
Pay components, calendars and periods, inputs from attendance and benefits, gross-to-net calculation under statutory rules and the employee's tax details, review, approval, payslips, the bank file and the payment behind each payslip.
Plans with premiums and employer contributions, eligibility and enrolment windows, coverage levels, dependants and nominees, and the deductions payroll takes from them.
Leave policies and balances, requests and approval, work patterns, shifts and rosters, daily attendance from devices, and the timesheets with a line per day that payroll reads at cutoff.
Statutory rules and their bands as effective-dated data, monthly and year-end returns built from posted pay runs, employee tax statements, the tax year lock, policy acknowledgement and the documents that expire.
Ledger accounts and cost centres, the payroll journal drafted for every approved run, allocation by cost centre and timesheet line, accruals with their reversals, reconciliation of clearing and liability accounts, and the period lock.
Requisitions against approved positions, candidates through stages, interviews with feedback, and offers approved against the band before they are sent.
Employer cost by entity, cost centre, component and month, reconciled to the posted payroll journal.
Posting waits for the finance controller.
This run against the previous run per employee, flagging changes in gross or net above the entity's threshold with the input or revision that caused them.
Approval waits for the payroll officer.
Every payslip in a run with days paid, gross, each deduction, employer contributions and net; the document the approver signs off.
Approval conditions.
Statutory rules are effective-dated rows per jurisdiction. A flat rule carries rates and a ceiling; a banded rule carries its bands for progressive tax; each names the wage base it applies to and the component it posts to. The employee’s side, the tax code or filing status, allowances and declared reliefs, is a verified record per employee per tax year. Implementation configures and verifies the rules and filing formats for the agreed entities and jurisdictions. This specification does not certify any jurisdiction or supply current statutory rates. A later change requires an effective-dated revision and repeat checks before use.
Related questionYes. A pay calendar sets frequency, cutoff and pay day for a group of employees in an entity and generates its periods. Monthly salaried staff and weekly hourly staff run separately in the same entity, and their journals land in the same ledger month. Hourly staff carry an hourly rate on their compensation record.
Related questionConfigured and tested device, mobile or web connections, imports or manual entry build daily attendance rows against the rostered shift. Approved leave marks the days, managers correct flagged rows, and hourly staff submit a timesheet with a line per day that the manager approves. At cutoff the attendance status, approved hours and shift premiums become inputs to the run with their source record as the reference.
Related questionYes. Off-cycle runs pay a missed joiner, a correction or a bonus; arrears runs apply a back-dated revision; final settlement runs pay a leaver. All follow the same lock, calculate, approve, pay and post sequence.
Related questionAn exit record runs notice and clearance, then a final settlement run pays to the last working day. It includes the terminal amounts approved by HR and applies configured entitlement, recovery and tax rules. Final settlement needs payroll approval, independent payment authorisation and journal posting. Agree former-employee access and retention during rollout.
Related questionSalary fields are visible to HR Managers, Payroll Officers and the Finance Controller. National ID and bank account are masked for everyone except HR Managers and Payroll Officers. A bank account change is a separate request tied to the exact verified proof. A Payroll Officer other than the requester matches the proof and proposed account before it becomes the current verified account. The preparer of a run cannot approve it, and the bank authoriser must be different from both the preparer and approver.
Related questionNothing per user. Credits pay for machine work and never expire. See pricing.
Related questionMonthly salaried staff, variable pay and bonus schemes, flexible benefits, remote allowances, and a finance team that wants cost by practice or client.
Plants, warehouses, stores, hotels and care facilities: rosters, biometric attendance, overtime rules, shift premiums, hourly and monthly staff on different calendars, and joiners and leavers every week.
Several employing companies under one management: separate registrations, calendars and bank accounts, moves between entities, shared-services cost attribution, and one headcount and cost view across the group.
Charities, research institutes and programme delivery bodies: staff funded by several grants, hourly cost allocation and configurable funder reporting, fixed-term contracts that follow the grant, and reports each funder can audit.
Create your ERP.AI account and get started with Proto.
We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy
We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.
Learn more about how we use cookiesThese cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.
These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.
These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.