These 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.
- HRMS with AI Chatbot
- Features
- Payroll and tax
Payroll and tax
Prepare a dated payroll run and preserve employee statements and tax records.
OverviewPayroll approval queue×
HRMS with AI Chatbot · Payroll and tax
New
Payroll approval queue
Approval waits for the payroll admin
| Run number | Calendar | Period start | Period end | Pay date | Gross total | |
|---|---|---|---|---|---|---|
| PR-89961 | PC-1791 | 03 Oct | 07 Oct | 10 Oct | 770 | |
| PR-13543 | PC-5846 | 22 Oct | 25 Oct | 30 Oct | 280 | |
| PR-46998 | PC-9688 | 13 Oct | 17 Oct | 20 Oct | 690 | |
| PR-26711 | PC-1821 | 05 Oct | 09 Oct | 16 Oct | 190 | |
| PR-63687 | PC-2602 | 16 Oct | 24 Oct | 26 Oct | 220 |
6 of 6 records
PC-1791Payroll runs · PR-89961
Pending approvalPeriod start03 Oct
Period end07 Oct
Pay date10 Oct
Gross total770
Net total900
What you can do
Make the pay period explicit
Payroll runs identifies a calendar, period start, period end, pay date and run type. Its status shows preparation, calculation, approval, posting, payment and closure as distinct steps. Payroll Admin manages runs and the related pay records. A named approving employee can be recorded before the run moves forward. The calendar ties frequency, entity, country, currency and cutoff days to the workers assigned to it.
Pay statements hold the employee-level result for a run, including period, currency, gross pay, deductions, net pay and payment method. Pay statement lines shows the earning, deduction, tax or employer components. Tax filings can connect a filing to its jurisdiction and run, with due date, amount and filing state. These links let Payroll Admin inspect an aggregate run without losing the employee and jurisdiction detail.
How the work is organized
- Schedule. payroll calendars sets the pay frequency and entity context for each run.
- Calculation. payroll runs and pay statements show the run state and individual results.
- Detail and filing. pay statement lines, tax jurisdictions and tax filings retain components and tax follow-up.
What to agree during setup
Assign workers to the correct calendar and confirm their currency, entity, country and pay grade. Decide who may approve a run, how an off-cycle or correction run is identified and when a run can be posted. Define the source and review of benefit contributions, approved overtime and paid leave. Separate the team’s local Paid status from the evidence received from a bank or other payment provider.
Payroll Admin controls payroll and tax records. Employee has read-only access to their pay statements. CHRO / VP People can review the payroll population. HR Business Partner can see pay statements but does not manage runs. Test these paths with a representative employee and a payroll operator before the first live pay date.
Check the handoff on an actual case
For a monthly calendar, Payroll Admin confirms the period and pay date, checks the assigned employees and creates the draft run. One employee has a new benefit enrollment and approved overtime. Payroll Admin examines the enrollment and approved timesheet total; Admin checks the overtime entry detail. Payroll Admin then reviews the employee’s gross and net statement before requesting approval. The approving employee reviews the run total, employee count and sampled statement lines. Once approved, Payroll Admin moves the run through posting, payment and close with the posted time and tax follow-up retained.
A correction should be visible as its own run type. The team should be able to explain which pay period it adjusts and which statements changed. For each filing, record the jurisdiction, amount, due date and confirmation reference when one is received. That keeps a filing marked Filed distinct from one merely drafted for review.
What your team sees
- Payroll approval queue — Runs awaiting the named approving employee’s decision.
- Payroll run board — A status view across preparation, approval, posting and payment.
- Active employee register — The worker and assignment context used before a run is calculated.
Follow the work through
See onboarding to first pay for worker setup and payroll run to close for the run decision.
What it keeps track of
Data model- Payroll calendars
- Named pay schedules per legal entity, country and currency.
- Payroll runs
- A scheduled execution of payroll for a calendar and period.
- Pay statements
- Per-employee pay statement for a given payroll run.
- Pay statement lines
- Earnings, benefit deductions, taxes and garnishments on a pay statement.
- Tax jurisdictions
- Tax-authority records driving withholding and filings.
- Tax filings
- Payroll tax filings produced from a run and remitted to an authority.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
- Benefit enrollments
- Per-employee enrollment in a benefit plan with dependents and dates.
- Timesheets
- Weekly timesheet header per employee.
Who uses it
Permissions- Payroll Admin
- Prepares and maintains pay and tax records.
- CHRO / VP People
- Reviews aggregate work.
- Employee
- Views their pay statement.
- HR Business Partner
- Checks employee context.
- Admin
- Maintains configuration and corrections.
Set up HRMS with AI Chatbot your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.