Service Work, Tracked and Billed
A ticket per job, with the time that went into it, the rate it was worth and the invoice it turned into. Technicians punch against the ticket, the customer sees the time you billed, and the office keeps the record of what actually happened.
How a ticket runs
- Open a ticket for the customer, the site, or the specific piece of equipment.
- Technicians punch against it from the time clock, and their hours attach with the rate that applied that day.
- Close the ticket, and any support hours the customer has prepaid are consumed oldest first.
- Generate one invoice, built from the ticket rows rather than a summary of them.
What you can manage
Punch Against a Ticket
Technicians pick the ticket at clock in. Their time lands on the job without a second timesheet.
Rate Snapshots
The rate is captured when the hours are logged, so a later price change never rewrites old work.
Billed and Actual
What happened and what you charged are separate figures. Adjusting the bill needs a reason and never edits the truth.
Customer Print
The customer sees billed time and the work performed, never raw punches or internal notes.
Generate an Invoice
One invoice per ticket, ever, built from the actual lines with tax as its own visible row.
Support Hours
Prepaid blocks belong to a customer, draw down at close, and overflow prices at each row’s own rate.