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 + Payroll for SMB
- Features
- Tax and reporting
Tax and reporting
Keep jurisdiction, filing and pay detail records available for period review.
OverviewPayroll approval inbox×
HRMS + Payroll for SMB · Tax and reporting
New
Payroll approval inbox
Approval waits for the payroll admin
| Run number | Calendar | Period start | Period end | Pay date | Gross total | |
|---|---|---|---|---|---|---|
| PR-96613 | PC-2509 | 13 Oct | 20 Oct | 29 Oct | 300 | |
| PR-85930 | PC-2628 | 24 Oct | 02 Nov | 05 Nov | 470 | |
| PR-84647 | PC-6364 | 14 Oct | 20 Oct | 24 Oct | 770 | |
| PR-81535 | PC-1170 | 20 Oct | 24 Oct | 29 Oct | 490 | |
| PR-32450 | PC-4094 | 03 Oct | 07 Oct | 10 Oct | 870 |
6 of 6 records
PC-2509Payroll runs · PR-96613
Pending approvalPeriod start13 Oct
Period end20 Oct
Pay date29 Oct
Gross total300
Net total510
What you can do
From pay detail to a filing record
Tax jurisdictions identify the country, region, authority and filing frequency used for payroll tax records. A location can point to a tax jurisdiction, and a pay statement line can point to one as well. This gives Payroll Admin a way to inspect the tax category and amount in the employee detail before preparing a filing. A tax filing records record connects a jurisdiction and a payroll run to the filing period, type, amount, due date and status.
The filing status distinguishes Draft, Filed, Paid, Late and Disputed. Payroll Admin can record a filing date and confirmation reference as the work moves forward. The record is an operational log of what was prepared and recorded for a pay period. The actual authority submission and funds transfer need an agreed external process and evidence. A reviewer should check the authority and period before marking a record Filed.
How the work is organized
- Jurisdiction. Country, region, authority name and frequency define the destination for tax work.
- Pay detail. Tax lines under employee statements carry the amount and a jurisdiction reference.
- Filing. The filing connects a run to an authority, due date, amount and recorded outcome.
What to agree during setup
Confirm the country and jurisdiction for each work location, including remote workers. Decide whether a filing frequency should be Monthly, Quarterly or Annual for each authority. Map the filing type names used in the relevant countries. Set a naming convention for confirmation references so the Payroll Admin can find the external receipt. Exchange rates is a read-only effective-rate table; agree how rates are supplied if payroll reporting crosses currencies. The app’s filing amount should be compared with the relevant run and statement lines before a status changes.
For a payroll run that spans an end-of-quarter date, review the employee tax lines for the jurisdiction and sum the amount in the filing record. Check that its period, due date and filing type match the authority’s schedule. Record the actual filing date and confirmation reference when the external submission is complete. If the amount is disputed, keep the status and evidence distinct from Paid so the reviewer knows a follow-up remains.
Check the handoff on an actual case
Select a Paid payroll run and an employee statement with a Tax line. Open the line to confirm the jurisdiction and amount. Compare the jurisdiction’s country and filing frequency with the location and filing period. Review the associated filing record’s amount, due date, status and confirmation reference. Ask Payroll Admin to explain how the external submission receipt will be kept. Then check the pay run summary so the tax review is tied to the correct calendar and dates.
What your team sees
- Filings due — Draft or late items with authority, period, due date and amount.
- Tax filing calendar — Filing status and dates grouped by jurisdiction.
- Payroll period summary — Run totals that give a period anchor for tax review.
Follow the work through
Begin at payroll cycle, then use implementation to agree the external filing handoff.
What it keeps track of
Data model- Tax jurisdictions
- Tax-authority records driving withholding and filings.
- Tax filings
- Payroll tax filings produced from a run and remitted to an authority.
- Pay statement lines
- Earnings, benefit deductions, taxes and garnishments on a pay statement.
- Pay statements
- Per-employee pay statement for a given payroll run.
- Payroll runs
- A scheduled execution of payroll for a calendar and period.
- Locations
- Physical and remote locations where employees work.
- Exchange rates
- Read-only effective exchange rates for this app.
Who uses it
Permissions- Payroll Admin
- Maintains jurisdictions and filing records.
- CHRO / VP People
- Reviews payroll context.
- Admin
- Manages reference data and access.
Set up HRMS + Payroll for SMB your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.