Work
Bookings, services, jobs, attendance, and assignments
Use case · operational and booking-driven pay
When pay depends on what happened, the Canvas makes the logic visible.
PayCanvas receives operational inputs, normalizes them into a consistent payroll structure, and runs the rules exactly as they are written in the Canvas. Every result remains reviewable, traceable, and explainable.
Operational inputs→Normalized data→Canvas rules→Payroll-ready results
THE INPUT PROBLEM
Your systems record activity. They do not agree on payroll.
Bookings, jobs, time records, sales, tips, and custom fields each describe part of what happened. PayCanvas turns those fragments into the consistent concepts the engine needs.
People
Employees, roles, teams, eligibility, and locations
Money
Sales, tips, pools, commissions, rates, and adjustments
Context
Dates, status, custom fields, approvals, and exceptions
NORMALIZATION
The same person, work event, and dollar only need one meaning.
PayCanvas maps source-specific fields into a stable payroll model. This is what lets one Canvas run consistently even when upstream systems label the same concept differently.
Names, IDs, and assignments→People and roles
Bookings, shifts, jobs, and services→Work events
Sales, tips, rates, and adjustments→Earning inputs
Missing or conflicting evidence→Review questions
THE CANVAS
The Canvas holds the rules the engine must follow.
It defines eligibility, rates, pools, commissions, exceptions, and review requirements in plain, inspectable logic.
SERVICE PAY
Set a rate by service, role, passenger count, unit, or completed event.
ROLE ELIGIBILITY
Only pay people whose normalized work record satisfies the written role requirements.
LOCATION RULE
Apply different rates, pools, or eligibility when operating context changes.
TIP OR GRATUITY POOL
Group money at the right level, then allocate it using the approved weighting.
COMMISSION
Create earnings from eligible sales without confusing revenue with payroll.
EXCEPTION
Hold incomplete or contradictory inputs for review instead of silently choosing an answer.
THE ENGINE
From operational activity to payroll-ready output.
The engine applies the reviewed Canvas to normalized inputs. Reviewers can follow a result backward through every stage.
Connected data, exports, and approved adjustments
Names and events become one consistent structure
The engine applies the reviewed payroll logic
Totals, evidence, and questions stay together
Approved numbers move to downstream payroll work
GENERIC EXAMPLE
A multi-location operator with role pay, pools, and commissions.
The example is intentionally generic. It shows how common operational facts map through a Canvas without implying a required source system or a specific customer’s policy.
| What happened | Normalized input | Canvas rule | Result |
|---|---|---|---|
| Completed service | Service event + assigned lead | Lead rate by completed event | Role pay line |
| Supporting crew | Eligible work assignment | Crew rate for the same service | Crew pay line |
| Shared gratuities | Pool grouped by date and location | Weighted role split | Tip allocation |
| Eligible package sale | Sale linked to completed work | Commission percentage | Commission line |
| Missing assignment | Revenue exists without a person | Assignment evidence required | Exception for review |
WHY PAY CHANGED
The answer is more useful than “the formula changed.”
PayCanvas keeps the source row, normalized meaning, Canvas rule, human decision, and resulting amount in one explanation path.
INPUTCompleted service + assigned lead
NORMALIZED ASEligible work event
CANVAS RULELead rate by completed event
RESULT$84.00 role pay line
PRACTICAL BOUNDARIES
Booking-driven payroll questions, answered plainly.
What PayCanvas replaces, what it does not replace, and how it handles incomplete operational data.
Does PayCanvas replace my source systems?
No. PayCanvas receives configured inputs from the systems and reports you already use. It normalizes those inputs, runs the rules written in your Canvas, and produces results that can be reviewed and explained.
Does PayCanvas file payroll taxes?
No. PayCanvas is not positioned as a payroll tax filing or benefits provider. It helps calculate, explain, review, and prepare payroll-ready outputs for downstream payroll workflows.
Can PayCanvas handle per-unit or per-service pay?
Yes. A Canvas can model rates by role, service, passenger count, quantity, location, eligibility, or another reviewed operational measure.
Can PayCanvas help with tips and gratuity pools?
Yes. PayCanvas can model and review pools by date, work event, location, role eligibility, weighting, approved corrections, and the audit trail behind each allocation.
What kinds of inputs can PayCanvas use?
A Canvas can be configured around available work activity, manifests, time records, sales, tips, commissions, roles, locations, custom fields, and approved corrections. Exact availability depends on the reviewed setup.
What happens when data is missing or contradictory?
PayCanvas keeps the question visible for review. Missing assignments, conflicting roles, incomplete source records, or undocumented corrections can stop the affected result before payroll is finalized.
PayCanvas
YOUR OPERATING MODEL
See how your inputs and pay rules would map into a Canvas.
Bring the systems, exports, rules, exceptions, and payout questions your team works with today. No polished process map required.
Request a setup review