Payroll

Payroll credibility comes from two things: a calculation you can inspect and an approval you can enforce. continON structures both. The schema is the inspectable part — income items, deduction items, and withholdings are defined per schema with formulas you can test against sample values in a built-in calculator before anything runs. Tax tables are records you maintain: country-wide and state-level structures with progressive brackets, applied by the engine during calculation.

The run is the enforceable part. Payroll generates per period from a pay calendar — separate schedules for exempt and non-exempt staff, or a custom date range — producing calculated lines per employee from the schema, the employment assignment’s wage data, and recorded advances and reimbursements. Reviewers can adjust values and recalculate before saving. Approval is a separate permission from payroll editing: an approver stamps the period, and only then are payslips generated from the report template the schema names, and results published to each employee’s read-only view in My continON.

The module also states its boundaries plainly. Payroll maps items to general-ledger accounts and builds a ledger preview for Finance — it does not post automatically. There is no bank disbursement from the system, and no benefits-plan enrollment module. What is claimed here is what the screens do.