Choose an entity
Save your recovery codes
Each code signs you in once if you lose your phone. Keep them somewhere safe, such as a password manager. They are shown only now.
Payroll quality
How the payroll is going: delivered on time, without errors, and how quickly new hires and changes are handled.
On time and accuracy, by month
Percentage of months delivered by the internal cut-off, and of payslips without errors on our side.
Errors found, by cause
Unique errors found by the verification each month (employee + check), by who caused them.
Errors in the period, by type and by who caused them
Documented errors only. Use them to agree fixes with your managers, HR and the payroll vendor.
| Entity | Payrolls | Payslips | On time | Accuracy | Errors | Rework | Inputs | New hires & changes | Status |
|---|
Monthly payroll
Load the entity's inputs and the payroll GTN, review the verification, document every issue, close the version and download the output GTN.
A · Entity inputs
One row per employee and one column per item (overtime, bonus, allowances…).
B · Payroll GTN
The gross-to-net report from the payroll system. The table is found automatically, even if it is rotated.
Inputs from managers
Inputs your managers sent for this pay period. Approve them as they are, change and approve, or reject them with the reason; an approved input goes into the open version as a manual input (the manager, the approver and the documents stay in its record) and the verification runs again.
| Employee | Input | Value | Why | Documents | Sent by | Status |
|---|
Manual inputs
A last-minute input (for example a bonus approved after the file was loaded) is added to this version without loading another file. The verification runs again. Who added it and when is kept; removing it brings back the value it replaced. Loading a new inputs file replaces the manual inputs it covers.
| Employee | Input | Value | Before | Why | Added | Status |
|---|
| Level | Row | Column | Value | Problem |
|---|
First rows of the file
| Version | Data | Loaded | By | Employees | Values | Note |
|---|
Original files
The entity inputs and payroll GTN files of the selected version, kept exactly as uploaded. Their SHA-256 fingerprint is printed in the monthly report, so anyone can confirm a downloaded file is the one that was checked.
| Data | File | Loaded | By | SHA-256 |
|---|
Sign-off
| Type | Employee | Item | Expected | Actual | Difference | Status | Documentation |
|---|
Employees
The employees of the entity with the data the payroll validation uses: job and contract, pay, time off and history, each with its effective date.
| Employee | Job title | Department | Manager | Work centre | Hire date | Status |
|---|
Key facts
Time off
Latest pay
Team
Recent and upcoming
Other employee data
Additional dated data used by formulas or loaded from files (for example a pay group).
| Field | Value | Since |
|---|
Fixed pay
| Item | Periodicity | Amount | Annual | Since |
|---|
Pay changes
| Effective | Item | Value | Comment |
|---|
Garnishments
Total to deduct and what the payroll GTN has deducted so far (last version of each month). A garnishment is completed automatically with the payroll that reaches the total; complete or cancel it by hand if it is paid in advance or lifted. Every verification checks the month's deduction.
| Garnishment | Since | Total | Deducted | Remaining | Status |
|---|
Payslips
From the payroll GTN of the last version of each month. Click a month to see every line.
| Month | Version | Gross | Deductions | Net |
|---|
All items by month
Holiday balance
Absences
| Type | From | To | Days | Status | Notes |
|---|
Documents
| Title | Kind | File | Valid until | Uploaded |
|---|
Change history
Every change to the employee, who made it and when. It cannot be edited or deleted: to change a value, use its tab (Job & contract, Pay, Personal, Time off); a new value with the same effective date is kept as a correction.
| Changed on | By | Area | Field | Effective | Before | After | Note |
|---|
One row per employee: employee ID, effective date (optional), name (optional) and one column per item, e.g. ID | Effective date | Name | Gross annual salary | Car allowance | Pay group. Each column is saved as a fixed pay item (annual or monthly amount; added to the catalogue if new) or as data. Empty cells change nothing; a 0 means the item stops from that date.
Taking over an entity in the middle of its tax year? Load each employee's pay so far as opening year-to-date amounts: one column per wage type, e.g. Basic Salary YTD | Employee National Insurance YTD (columns named after a wage type with “YTD” are recognised automatically). The date says which tax year they belong to; YTD() and YTDG() add them to the months loaded here.
| Column | Saved as | Treatment | Payments / year | Category |
|---|
New hires, terminations and changes
Register every new hire, termination or change the entity reports. Each one creates its legal tasks with their deadline; tick them as they are done.
| # | Type | Employee | Effective | Status | Next task | Due |
|---|
Tasks of the movement
| Task | Due | Done |
|---|
Deadline: effective date + legal term; payroll tasks use the internal cut-off of the month.
Configuration
Tax returns
Each return the entity files, calculated from the payroll GTN of its months. Register what was filed: any box that differs from the calculation is flagged.
| Return | Period | Status |
|---|
Tax returns
Tax returns by country and region, maintained by your vendor after reviewing the legislation. Import the returns of a country, then activate the ones each entity files and choose how often.
| Code | Name | Region | Authority | Frequency | Status |
|---|
Inputs for my team
Send the variable pay of your team (bonuses, overtime, allowances…) for the payroll specialist to review. Attach what supports it. You see whether each one was approved or why it was not.
You have no team assigned yet: ask your client administrator.
Several at once (Excel)
Download your team with one column per input, write the values and why, and upload the file: you see what will be sent before sending it. Each value goes for review on its own, as if sent here one by one.
| Row | Employee | Input | Value | Why |
|---|
What I sent
| Sent | Pay period | Employee | Input | Value | Why | Documents | Status |
|---|
Auditors
Give an auditor read-only access to the closed payroll of an entity, for some months and until a date. They receive an invitation by email, choose their password and set up two-step sign-in. Nothing is sent by email: they download the sealed reports in VeraVia, and every download is recorded here.
Accesses
| Auditor | Entity | Months | Until | Status | Downloads | Given by |
|---|
What auditors downloaded
| When | Auditor | Document | Pay period | Version |
|---|
Audit
The closed payroll you were given access to, with its electronic signatures. Download the sealed monthly report, the verification and the input summary. Every download is recorded.
Your access
Closed payroll
| Entity | Pay period | Version | Prepared and signed | Approved by the client | Documents |
|---|
Original files
The entity inputs and the payroll GTN exactly as they were uploaded. A downloaded file is the one checked if its SHA-256 fingerprint matches the one printed in the sealed monthly report.
| Source | File | Loaded | SHA-256 |
|---|
Calculation rules
How each check computes the expected value and which payroll value it compares it with, followed by the calculations the checks use.
| Rule | What it does | Expected value | Compared with | Tolerance |
|---|
Results of the checks
| Type | Check | Employees | OK | Differences |
|---|
Differences and how they were documented
| Employee ID | Check | Expected | Actual | Difference | Documentation |
|---|
Pending tasks
Cut-offs, tax returns and the legal steps of new hires, terminations and changes, overdue first.
| Entity | Period | Type | What is missing | Deadline | Status | Specialist |
|---|
Users
Who can sign in. Client administrators manage the users of their own client.
| User | Name | Role | Client | Status | Two-step | Last sign-in |
|---|
Sign-in activity
| When | User | What | Address | Detail |
|---|
Integrations
Employee changes sent by your HR system (Workday, SAP, Personio, BambooHR…) through the VeraVia API: new hires, terminations, contract, working time, salary and the rest of the employee record.
When it is off, every change waits here for review. Changes that affect a closed payroll always wait for review.
Incoming changes
| Received | System | Employee | Field | Value | Effective | Status | Detail |
|---|
API keys
| Name | HR system | Key | Created | Last used | Status |
|---|
Field mapping
| HR system | Their field | VeraVia field | Values |
|---|
Catalogue internal
Retire a return when the legislation replaces it: it disappears from every client's library; entities that still file it keep it, marked “retired”, until they deactivate it.
| Code | Name | Region | Base | Entities filing (all clients) | Status |
|---|
Platform catalogues administrators
Everything the platform brings, for every country: returns and their boxes, parameters, tables, shared formulas, standard checks and groups, regions, employee fields, dropdown lists (also the application's), movement tasks, employer identifiers and public holidays, with their source and confidence. Returns added manually (to a country pack or for one client) are included. Read only.
Yearly updates
When each country's values usually change (taken from the dates in its pack), when the next update is due, values that have ended without a new one (the checks would keep using the old value) and who in the team updates the country.
| Country | Values change in | Next update | Values as of | Values ending | Owner |
|---|
Country reviews
The vendor is responsible for the country content. Before a pack (or a new revision of it) goes live, a second person of the team checks it with the review workbook (an outside adviser is optional) and uploads it here. A pack is signed off when every row is OK; a new pack revision needs a new review.
| Country | Revision | Items | Confidence | Review | Reviewer |
|---|
Clients internal
Each client has its own database, separate from the others.
| Code | Name | Entities | Users | Status |
|---|
Backups
Loading…
| Started | Why | Result | Databases | Size | Checked | Off-site copy | File |
|---|
Server health and alerts
Loading…
| Problem | Since (UTC) | Last email | Resolved |
|---|