Payroll boundaries and role-training guide

1. Establish the payroll-to-accounting boundary

Singapore is absent from the reviewed Odoo 19 native payroll-localization list. Employment Hero administers payroll and Odoo receives draft accounting entries; Central Provident Fund (CPF), Skills Development Levy (SDL) and Foreign Worker Levy (FWL) calculation, payment and filing remain outside any native-Odoo claim. Verify the payroll-localization catalogue, Employment Hero guide and Singapore localization page before design.

• Responsibility: Employee-category and current-rule decisions; Accountable role: Employer, HR/payroll owner and CPF/MOM adviser; Acceptance evidence: Dated category register and source review
• Responsibility: Payroll administration; Accountable role: Employment Hero or another payroll provider; Acceptance evidence: Provider batch, exceptions and support record
• Responsibility: Interface configuration; Accountable role: Odoo administrator and provider owner; Acceptance evidence: Endpoint, permission and credential-custody record
• Responsibility: Accounting acceptance; Accountable role: Accounting reviewer; Acceptance evidence: Source-to-draft reconciliation and posting approval
• Responsibility: Release and revalidation; Accountable role: Release owner and compliance reviewer; Acceptance evidence: Open-issue register and unresolved human review

Synthetic acceptance example: the provider produces a draft payroll result for an invented employee group. HR and the payroll adviser accept employee categories and provider outputs; accounting accepts the Odoo draft entry only after reviewing accounts, dimensions, period and source batch. Nobody treats the draft entry as proof of statutory calculation, payment or filing.

Reviewed 6 November 2026 — research review, not legal signoff. Revalidation owner: Compliance reviewer (CR) with the country owner and named client advisers; unresolved human Singapore regulatory review by a qualified Singapore regulatory reviewer remains mandatory before release.

2. Build the CPF employee-category and current-rule register

Use the Central Provident Fund coverage guidance and contribution guidance to review citizens and Singapore Permanent Residents. The register distinguishes citizen or Singapore Permanent Resident (SPR) status, SPR year, age band, wage components and other current-rule inputs. It does not assign one universal CPF rate to the workforce.

• Register field: Synthetic employee and entity; Purpose: Supports training without exposing real identities; Owner: HR owner
• Register field: Citizen or SPR status and SPR year; Purpose: Selects the applicable employee-category analysis; Owner: HR and CPF adviser
• Register field: Age and wage inputs; Purpose: Supports the current-table row review; Owner: Payroll owner and adviser
• Register field: Current table and effective date; Purpose: Prevents mixed-period calculation; Owner: CPF adviser
• Register field: Provider mapping and evidence; Purpose: Connects the reviewed category to the provider batch; Owner: Provider owner

Keep the CPF tables effective 1 January 2026 separate from changes announced for 1 January 2027. The register records which table applies to which payroll period and never mixes 2026 and forthcoming 2027 rules. No numeric payroll rates are published in this guide.

Synthetic acceptance uses several invented employees with different status, SPR year, age and wage inputs. HR selects the category, the CPF adviser selects and dates the applicable current table, the provider demonstrates mapping, and accounting checks only the resulting draft entry. A changed category triggers review rather than an automatic inherited calculation.

3. Review SDL and FWL as different obligations

The Skills Development Levy guidance requires review across employees, including foreign employees and applicable exemption categories under current rules. The register therefore does not filter SDL by citizenship or assume either a universal charge or a universal exemption.

FWL is assessed only for applicable Work Permit and S Pass populations, not every employee. Use MOM Work Permit levy guidance and S Pass levy and quota guidance. Sector and quota distinctions remain visible and current rules are rechecked.

• Obligation: SDL; Population and current-rule review: All employees reviewed, including foreign employees and applicable exemption categories; Owner: Payroll owner and CPF adviser
• Obligation: Work Permit FWL; Population and current-rule review: Applicable pass, sector, quota context, effective rule and employer evidence; Owner: HR and MOM adviser
• Obligation: S Pass FWL; Population and current-rule review: Applicable pass, sector, quota context, effective rule and employer evidence; Owner: HR and MOM adviser

Fields include employee category, wage-period input, current SDL rule source, exemption-category review where relevant, calculation owner, provider result, reviewer and payment or filing evidence outside Odoo.

Synthetic acceptance includes an SPR employee, a foreign employee for SDL review, an exemption-category case, a Work Permit case and an S Pass case. HR must not apply FWL to the entire set or exclude foreign employees from SDL by assumption. The payroll adviser signs category and current-rule evidence, while the provider and employer sign their respective calculation and payment processes.

4. Control the Employment Hero or provider interface

Document the actual provider tenant, entity mapping, API permission, credential custodian, endpoint, batch schedule, chart and analytic mapping, error route and support responsibility. Store only a secure credential reference in the register, never a secret. The Singapore endpoint or a successful authentication response proves neither employee-category correctness nor statutory filing.

The interface contract states that Employment Hero administers payroll and Odoo receives draft accounting entries.

• Interface field: Provider batch and pay period; Purpose: Connects source payroll to the accounting period; Owner: Payroll provider
• Interface field: Category review version; Purpose: Shows which employee-category evidence was used; Owner: HR and payroll adviser
• Interface field: Source and expected journal lines; Purpose: Defines the accounting control; Owner: Payroll owner
• Interface field: Actual lines and residual; Purpose: Supports reconciliation and exception handling; Owner: Accounting reviewer
• Interface field: Posting approval; Purpose: Keeps draft status until independent review; Owner: Accounting reviewer

Test a normal batch, a rejected batch, a corrected category, a duplicate-delivery prevention case and a period reopening or reversal scenario where applicable. Reconcile provider output to draft entries and then to approved accounting. CPF, SDL and FWL calculation, payment and filing evidence stay with the employer, adviser and provider processes, not with a native-Odoo acceptance label.

5. Write least-privilege task cards for every role

Create English task cards with purpose, permitted screens, prohibited actions, routine procedure, exception lab, evidence to save, escalation owner and practical assessor. English Odoo UI labels and technical tokens remain exact where users need them.

• Role: Cashier; Routine and exception focus: Opening, permitted sales, refunds and close; Acceptance evidence: Register evidence and permission-denied test
• Role: Outlet manager; Routine and exception focus: Offline restrictions, reconnection and outlet close; Acceptance evidence: Incident and recovery signoff
• Role: AP/AR; Routine and exception focus: Source documents, open items and supplier/customer exceptions; Acceptance evidence: Document and allocation evidence
• Role: GST reviewer; Routine and exception focus: Distinct categories, conditional Box 13 and reverse-charge stop rules; Acceptance evidence: Tax review and return workpapers
• Role: Migration lead; Routine and exception focus: External IDs, imports and residuals; Acceptance evidence: Run and residual log
• Role: Payroll reviewer; Routine and exception focus: Employee categories, provider batches and draft entries; Acceptance evidence: Category and batch reconciliation
• Role: HR; Routine and exception focus: CPF/SDL/FWL stop rules and escalation; Acceptance evidence: Current-rule and escalation record
• Role: Treasury/payment operator; Routine and exception focus: PayNow and bank settlement rather than QR acceptance; Acceptance evidence: Bank match and residual evidence
• Role: Administrator; Routine and exception focus: Role design, credential custody and provider configuration; Acceptance evidence: Access and audit evidence

A user who can explain but not perform the exception, or perform but not retain the evidence, receives targeted reassessment rather than an attendance-based pass.

6. Run finance, migration and outlet exception labs

The AP/AR lab uses synthetic standard-rated, qualifying zero-rated, exempt and out-of-scope documents. The learner records actual place/time-of-supply evidence and escalates conditional Box 13 or reverse-charge uncertainty. No automatic tax determination is allowed in the assessment.

• Lab: GST categories; Required action: Classify synthetic documents and escalate uncertain treatment; Assessor evidence: Signed category and source review
• Lab: SGD residual; Required action: Trace source, expected and actual SGD to the import run and owner; Assessor evidence: Resolved or escalated residual
• Lab: Acknowledgement; Required action: Distinguish receipt from buyer acceptance, tax treatment, a GST return or payment; Assessor evidence: Correct status labels and explanation
• Lab: Offline recovery; Required action: Preserve browser data, reconnect, generate delayed invoices and prevent duplicates; Assessor evidence: Order, invoice and reconciliation evidence
• Lab: PayNow settlement; Required action: Match QR references to independent bank evidence; Assessor evidence: Gross, fee, net and bank reference review

The migration lead identifies the source row, exchange-rate evidence, import run and owner, then resolves or escalates the residual without a blanket tolerance.

The cashier and outlet manager compare order counts, references and statuses, generate delayed invoices where required and reconcile duplicates, stock and payments. The assessor retains screenshots and signed results by role.

7. Run payroll, treasury and administrator stop-rule labs

The payroll lab presents invented employees with citizen or SPR status, differing SPR year, age and wage inputs, foreign-employee SDL review, applicable exemption categories, and applicable Work Permit or S Pass cases. HR must stop when the category, exemption review or current table is missing. The payroll reviewer checks that 2026 and 2027 sources are not mixed and that no universal numeric rate has been hardcoded.

• Stop-rule lab: Missing employee category or exemption review; Required response: Stop and escalate to HR and the qualified adviser; Acceptance evidence: Named question and reviewer
• Stop-rule lab: Missing bank settlement; Required response: Keep the PayNow item unmatched; Acceptance evidence: Pending exception and owner
• Stop-rule lab: Failed provider batch; Required response: Preserve the error and prevent duplicate delivery; Acceptance evidence: Provider error and correction record
• Stop-rule lab: Draft accounting entry; Required response: Accept or reject from source evidence, not status alone; Acceptance evidence: Accounting review and posting decision

The treasury lab provides a PayNow QR reference without a bank line, followed by an independent synthetic settlement. The operator marks the first as unmatched and reconciles the second using gross, fee, net and bank reference fields. A bank-feed delay is handled through the pending procedure, not by calling the QR settled.

The administrator lab configures a test provider reference and least-privilege role without exposing secrets. None of these labs permits a learner to claim CPF/SDL/FWL filing, InvoiceNow clearance or bank settlement from an Odoo status alone.

8. Assess evidence, not presentation attendance

Each assessment has role, scenario version, synthetic data set, starting access, expected routine result, expected exception action, actual evidence, assessor, result, coaching note and reassessment date. The rubric distinguishes task completion, control understanding, source evidence, exception escalation and permission boundaries.

• Assessment field: Scenario and access; Purpose: Reproduces the intended role and permission boundary; Owner: Training owner
• Assessment field: Routine and exception results; Purpose: Tests both operation and stop rules; Owner: Role assessor
• Assessment field: Source and output evidence; Purpose: Proves what the user actually completed; Owner: Role assessor
• Assessment field: Coaching and reassessment; Purpose: Records correction and retest; Owner: Champion and role owner

Failed cases remain visible with their correction and retest. Training material is updated when the actual screen, provider behaviour, regulatory source or responsibility changes; an old recording is not accepted as proof of current competence.

The evidence pack includes the signed task card, permission test, source and output samples, exception result and open questions. Personal employee information and live credentials are excluded. Provider, access-point and session-company examples are educational only, never Oakland references, recommendations, Singapore delivery evidence or proof of statutory capability.

9. Hand over champions and exit hypercare on adoption evidence

Nominate champions for outlet operations, finance, migration, payroll/HR, treasury and administration. Hand over current task cards, synthetic labs, assessment rubrics, source register, known limitations, escalation routes and revalidation triggers. Champions accept ongoing material ownership rather than becoming unqualified statutory approvers.

Hypercare reviews whether target work is actually being completed: invoices and open items are processed, residuals are explained, outlets close after reconciliation, PayNow is matched to bank evidence, provider errors are routed and payroll drafts are reviewed. Recurring spreadsheet workarounds and repeated exceptions trigger design, data, provider or training investigation.

Exit requires closed blocking defects, accepted residual owners, demonstrated role competence, working escalation and champion acceptance. It is not based on a generic calendar promise. Later source, employee-category, provider or screen changes enter reassessment and, where necessary, a separately approved optimization scope.

10. Close with cross-guide stop/go evidence and responsibility ownership

The final responsibility matrix shows unresolved employee categories, current CPF/SDL/FWL sources, provider activation, draft-entry residuals, role-access failures, training reassessments and statutory evidence owners. Each blocker identifies employer, HR, adviser, provider, accounting, Oakland or release ownership. The unresolved qualified Singapore regulatory review remains mandatory.

The payroll boundary is an Odoo 19 acceptance scope; later product versions do not change employer, adviser or provider statutory responsibilities. Canonical Singapore PDF and reporting-standard version comparisons belong in the GST and InvoiceNow readiness guide, not in this payroll guide.

Continue with GST and InvoiceNow readiness, SGD migration and reconciliation, and POS go-live and recovery. These guides share evidence and training scenarios but do not transfer acceptance from the named payroll, tax, provider or outlet owner to another guide.