Payroll accounting is where people operations and finance meet, yet in many organizations the two still live in separate tools. HR keeps contracts and attendance in one place, payroll is calculated in a spreadsheet or a separate package, and the accounting team receives a summary file at month end that it re-keys into the ledger. Every handover adds delay, and every re-keyed figure is a figure nobody can trace back to its source
This guide explains how to run HR, payroll and wider workforce operations on the same financial core as your ledger: the employee file and contract, attendance and leave, salary structures in several currencies, an approved payroll run that posts an accrual entry and a payment entry, payroll cost by department, liabilities to employees, onboarding and offboarding, confidential files and evidence-based performance review. It ends with an implementation checklist and the pitfalls that most often undermine a payroll project
Why HR and payroll should post to the same ledger
When payroll sits outside the ledger, the general ledger only ever sees a monthly total. Controllers cannot answer simple questions without a reconciliation exercise: which department drove the increase in salary cost, which employees are still owed money, which bank account a payment actually left from, and who approved a change to someone's salary three months ago
Real HR and payroll integration means that the people side and the money side share one record. In Arfinex the ledger is the reference system: every balance change is an event with a balanced double entry, and mistakes are corrected with reversing entries rather than by editing or deleting history. Payroll is simply one more source of events that obeys the same rules, next to treasury, contracts, sales and reporting
- One employee record feeds contracts, attendance, payroll and access rights
- Salary cost is visible by department and company without a separate allocation spreadsheet
- Every payroll figure carries a source and a time, so an auditor can follow it from payslip to ledger
- Missing inputs, such as an unapproved overtime sheet, stay marked unknown instead of silently becoming zero
The employee file and the employment contract
Workforce operations start with a single employee file: identity details, role, department, cost centre, company, start date, documents and history. Everything else, from leave balances to payroll postings, refers back to this record, so it is worth getting its structure right before the first payroll run
Contracts signed with evidence
The employment contract should be created from an approved template, pass an internal approval path and then be signed by the employee. Signing evidence such as time, device and the document's digital fingerprint is recorded, the final version is locked, and later changes happen only through a separate amendment. Where a signature needs a specific legal effect under local law, signing is configured on a licensed provider in a supported jurisdiction, as described in evidence-based contracts and electronic signature
Confidential files with role-based access
Salary history, medical notes and disciplinary records do not belong in a shared folder. The confidential part of the employee file opens only for authorized roles, and every access is logged. Separation of customer data and access is specified and verified in each deployment plan, a topic covered in more depth in secure multi-tenant architecture and data isolation
Attendance, leave and salary structures
Attendance and leave feed payroll directly, so they need policies rather than ad hoc edits. Each company in a group can have its own working calendar, leave types and accrual rules, and leave balances are calculated from approved requests rather than typed in by hand
Salary structures in multiple currencies
A salary structure describes the components of pay: base salary, allowances, overtime, bonuses and deductions. Structures are assigned per employee and can be denominated in different currencies, which matters for a group that employs people in more than one country or pays some staff in a currency other than the company's functional currency. The rate used to convert a salary into the reporting currency is stored with its source and time, and changing it after the fact requires approval from a second person
Any change to a salary structure or to an individual assignment goes through an approval path. One person records the change and another approves it, so no salary increase reaches a payroll run on the strength of a single login
The payroll run: approval, accrual entry and payment entry
A controlled payroll run follows the same sequence every period. The calculation itself runs on deterministic, testable code; an AI assistant may explain a variance against last month, but its output is labelled as a proposal and never changes a figure on its own
- Lock attendance, leave and approved salary changes for the period
- Calculate the draft payroll register from salary structures and inputs
- Review variances against the previous period and resolve missing inputs
- Approve the run, with the approver separate from the person who prepared it
- Post the accrual entry for salary expense and salary payable
- Pay from a specific bank or payment account and post the payment entry
A payroll journal entry walk-through
Take a generic example: a company with two departments, operations and sales, whose approved gross salaries for the month are 30,000 and 18,000 in the company's currency. The payroll journal entry at approval debits salary expense for operations by 30,000 and for sales by 18,000, and credits salary payable by 48,000. If local rules require withholdings or employer contributions, they are credited to their own liability accounts as configured with your accountant, so the entry stays balanced
When the salaries are paid, a second entry debits salary payable and credits the bank or payment account the money actually left from. Because both entries reference the same approved run, anyone with the right role can trace a single payslip to the expense line, the liability and the outgoing payment. If a payment is wrong, it is corrected with a reversing entry and a new posting, never by editing the original
This is the core of payroll accounting done well: an accrual that shows the obligation when it arises and a payment that shows how and from where it was settled. The HR and payroll service posts both entries as soon as the run is approved and paid
Payroll cost by department and liabilities to employees
Because every accrual carries a department and a company, payroll cost reporting comes straight from the ledger. Finance can compare salary cost by department, by company and by currency over time, and see it beside budget without a separate allocation file
Liabilities to employees deserve the same attention as liabilities to suppliers. Unpaid salary, unreimbursed expenses, approved but unpaid bonuses and final settlements for leavers all sit on the balance sheet. Tracking them per employee, with age and owner, prevents the uncomfortable discovery that someone who left months ago is still owed money
Bonuses, commissions and performance evidence
Variable pay is where payroll most often loses its audit trail. Commissions should be calculated from confirmed revenue under versioned rules, as explained in CRM, sales commissions and revenue operations, and bonuses should rest on evidence of work rather than on a count of closed tasks. With performance assessment on real work evidence, department cost is viewed beside output, and an approved bonus flows into payroll as expense and payable like any other component
Onboarding and offboarding with access cut the same day
Joiners and leavers are both HR events and security events. An onboarding checklist creates the employee file, collects the signed contract, assigns a salary structure and grants the access the role needs, and nothing more. An offboarding checklist calculates the final settlement, records any remaining liabilities, retrieves equipment and cuts all access on the day the person leaves
- Access is granted by role, not copied from a colleague's account
- The final settlement is approved like any other payroll item and posted to the ledger
- System access, shared credentials and signing authority are revoked on the leaving date
- The confidential file is retained under the customer's own retention policy
Local labour law, payroll tax and insurance
Payroll rules differ from one jurisdiction to another, and they change. Arfinex is not a tax adviser, a law firm or a payroll bureau. Tax brackets, social insurance contributions, statutory leave and termination rules are configured from rules that the customer's accountant or local adviser confirms, and those rules are versioned so that a past payroll can always be explained under the rules that applied at the time
Payments themselves, like other regulated services, are made only through licensed providers or banks in supported jurisdictions. The system prepares, approves and records the payroll; the licensed partner moves the money
Implementation checklist and common pitfalls
Delivery follows the same path as the rest of the platform: an introduction and scope review, corporate identity verification and screening before contract, design and build in a sandbox with synthetic or anonymized data, a parallel run alongside your current payroll method, and go-live only with your approval
Checklist before the first live payroll
- Agree the chart of accounts for salary expense, salary payable and each withholding liability
- Map every employee to a company, department and cost centre
- Load salary structures and confirm currencies and rate sources
- Have your accountant or local adviser confirm tax, insurance and leave rules in writing
- Define who prepares and who approves payroll runs and salary changes
- Run at least one parallel payroll and reconcile it line by line against the current method
- Test offboarding end to end, including same-day access removal
Pitfalls to avoid
- Posting one lump sum per month, which hides department cost and employee liabilities
- Letting the person who prepares payroll also approve it
- Editing a posted payroll instead of reversing and reposting it
- Treating missing attendance or rate data as zero
- Keeping confidential files in shared drives outside role-based access
- Relying on software for tax interpretations that belong to your adviser
Make payroll part of the financial core
When HR and payroll post to the same ledger, workforce operations stop being a monthly handover and become a traceable flow from contract to payment. Department cost, employee liabilities and approvals are visible every day, and payroll accounting becomes as auditable as the rest of your books
