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.
- Gig Workers HRMS
- Features
- Payroll and tax
Payroll and tax
Prepare pay periods, examine employee statements and track the related filing record.
OverviewPayroll approval queue×
Gig Workers HRMS · Payroll and tax
New
Payroll approval queue
Approval waits for the employee
| Run number | Calendar | Period start | Period end | Pay date | Gross total | |
|---|---|---|---|---|---|---|
| PR-15212 | PC-7983 | 13 Oct | 16 Oct | 24 Oct | 560 | |
| PR-72386 | PC-1803 | 17 Oct | 26 Oct | 04 Nov | 280 | |
| PR-58593 | PC-5791 | 17 Oct | 22 Oct | 29 Oct | 140 | |
| PR-73404 | PC-9519 | 05 Oct | 14 Oct | 21 Oct | 770 | |
| PR-70601 | PC-4421 | 12 Oct | 15 Oct | 19 Oct | 350 |
6 of 6 records
PC-7983Payroll runs · PR-15212
Pending approvalPeriod start13 Oct
Period end16 Oct
Pay date24 Oct
Gross total560
Net total750
What you can do
Make the pay period reviewable
Payroll Admin creates a payroll run for a calendar and period, with a pay date and run type. The calendar identifies frequency, entity, country, currency and cutoff days. A run carries its status, employee count, gross total and net total. The team can review those values before approval, then retain the posted and paid states as the pay process progresses.
Each employee pay statement links to a run and period. The statement records gross pay, deductions, net pay, currency and payment method. Its lines distinguish earnings, pretax items, post-tax deductions, tax and employer amounts by category and code. A tax line may point to a tax jurisdiction. This structure lets Payroll Admin inspect the detail behind a total rather than relying on a run-level amount alone.
How the work is organized
- Calendars and runs. A legal entity’s pay schedule determines the relevant period and cutoff.
- Statements and lines. Each employee’s pay outcome is supported by categorized amounts.
- Filings. Jurisdiction and due date connect payroll runs to tax filing records.
What to agree during setup
Confirm the calendar and currency for every employee before the first payroll rehearsal. Decide which run types the team will use for corrections, bonuses and off-cycle pay. Review the tax jurisdictions assigned to locations and statement lines. The company remains responsible for its tax rules, filing procedures and banking arrangements; connect its specialist systems and payment provider as part of implementation.
Assign a reviewer for the run totals and pay statements. The person preparing a run should know what evidence the approver expects: included employees, approved hours, deductions, benefit enrollments and material changes in gross or net pay. Agree how the team records a cancelled pre-posted run and how it handles a correction after posting.
Check the handoff on an actual case
Use one pay period that includes an employee with regular hours and a contractor with approved weekly time. Verify that each employee is tied to the intended payroll calendar and that the statement period matches the run. Open the statement lines and compare earning, deduction and tax amounts with the statement totals. Check the run’s gross and net totals before recording its approval.
Then follow the same run through posting and payment, recording the pay date and posted time. For a tax filing, attach the applicable jurisdiction and run, enter the filing period, due date and amount, and update its status only when the filing step occurs. A filing marked paid should have its actual confirmation reference when one is available. Keep the finance owner in the review loop for remittance outside the HRMS.
What your team sees
- Payroll approval queue — Pay periods with totals awaiting a decision.
- Statements awaiting release — Employee statements grouped by preparation state.
- Contractor workforce — Contractor employees and their assigned payroll calendars.
Follow the work through
Follow the employee time to pay process. Plan banking and tax connections in integrations and review rollout steps in implementation.
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 filings
- Payroll tax filings produced from a run and remitted to an authority.
- Tax jurisdictions
- Tax-authority records driving withholding and filings.
- 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.
Who uses it
Permissions- Payroll Admin
- Prepares and records runs, statements and filings.
- Admin
- Reviews approval and controls access.
- CHRO / VP People
- Sees the payroll picture.
- Employee
- Sees their own pay statement under the configured permission model.
Set up Gig Workers HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.