|
Monthly Product Release · November 18, 2026
This release includes six updates:
■ New feature
Margin Insight, now available to all customers
Available in: Web portal (Financial Snapshot) · Margin Insight workspace · All customers
Release summary
Affected modules
Customer action required
Overview
Who benefits most: Account managers who need to know which accounts are losing margin, schedulers who need to catch overtime and hours paid but not billed while shifts can still be re-covered, and finance leads who want a view of pay and bill before payroll and invoicing close.
What drove the change: Pay is only final after the payroll run, and revenue only after invoicing, so most of a period goes by without a reliable view of margin. Margin Insight ran as a limited release with a small group of customers. General availability adds features built in response to their feedback.
What's new
What it does
Margin Insight shows each snapshot in two views:
- Spreadsheet: a sortable table of hours, overtime, pay, bill, margin and direct labour %, grouped by Site, Contract, Employee, Calendar Day or Rate Type. Expand a row to see what’s behind it.
- Graphics: period burn, a ranked worklist, rate-type mix, a heat matrix and an exposure plot, with an adjustable threshold for the measure you pick.
- Non-billable overtime: an estimate (paid overtime with no matching billed overtime), marked ≈ wherever it appears.
- Read-only: running a snapshot doesn’t change schedules, shifts or any other portal data.
How they work together
- One permission controls access. Users need View Labor Budget P&L, under Scheduling, on their Admin Portal role. The Administrator role always has access.
- Regions still apply. Users see data only for the regions they have access to.
- It shows amounts. The permission shows pay, bill and margin even without Payroll or Billing permissions, and it lets users create, edit and run Financial Snapshot templates. Give it only to roles that should see those amounts.
Why it matters
By the time payroll and invoicing close, the overtime and coverage gaps behind a bad period can no longer be fixed. Margin Insight shows them while there’s still time to change upcoming shifts, and you can rerun the snapshot to see the effect.
How to access it
Web portal: Settings > View All > Financial Snapshot > [template] > Results
Direct: office.tracktik.app, signed in with your TrackTik portal account
Screenshot
The Results button sits next to Requests on each Financial Snapshot template.
Screenshot
The View Labor Budget P&L permission, under Scheduling, controls who can open Margin Insight.
Rollout and upgrade
Rollout method
Customer action required
Yes. To start using Margin Insight:
- Ask your Customer Success Manager to turn on Margin Insight for your portal.
- Give the permission to the roles that should see it: Settings > Roles & Security > Roles/Permissions > [select role] > Permission > Scheduling > View Labor Budget P&L.
- Create a template: Settings > View All > Financial Snapshot > Create Template. Choose the frequency, reference date, scope (Bill, Pay or Bill & Pay) and the regions or sites to include.
- Select Requests to run the template for a period. When the run shows Completed, select Results.
Documentation
■ New feature
OBBB qualified overtime in payroll
Available in: Web portal · Prepare Payrun · Data Lab · US payroll regions
Release summary
Affected modules
Customer action required
Overview
Who benefits most: Payroll admins who process and reconcile payruns for US-based hourly employees, and admins who set up payroll by region.
What drove the change: Overtime in a payrun can mix federal weekly overtime, state daily overtime and contractual premiums, and only part of it qualifies under OBBB. Employers report the qualifying amount separately on W-2 forms starting with 2026, so payroll teams were working it out by hand.
What's new
What it does
A processed payrun gets a new tab and a new dataset:
- OBBB Overtime tab: one row per employee per workweek, with Workweek, Overtime Hours, OT Non-FLSA Hours, Qualified OT Rate, Qualified OT Amount and YTD Amount.
- The calculation: Qualified OT Amount = Overtime Hours × 0.5 × Qualified OT Rate. For example, 45 hours at $20.00 an hour gives 5 × 0.5 × $20.00 = $50.00. The full overtime pay for those 5 hours is still $150; only the $50 premium is qualified overtime.
- Data Lab: the obbb_overtimes dataset totals qualified overtime by employee. Run a query, export it or save it as a widget.
How they work together
- Weekly, not daily. Only hours beyond 40 in the workweek count. State daily overtime doesn’t qualify unless the week also goes over 40.
- Worked hours only. Paid time off, holiday hours that weren’t worked and unpaid leave don’t count toward the 40.
- Each workweek stands alone. Hours are never averaged across weeks, and hours from every site in the workweek are added together.
- Premium only. Hours over 40 paid at double time still qualify, but only the half-time portion counts.
Why it matters
Payroll teams get the qualifying amount for each employee without working it out by hand, ready for year-end reporting.
How to access it
HR & Payroll > Prepare Payrun > [payrun] > OBBB Overtime
Screenshot
The OBBB Overtime tab in a processed payrun.
Screenshot
A Data Lab query on the obbb_overtimes dataset.
Screenshot
The region setting in BackOffice Default.
Rollout and upgrade
Rollout method
Customer action required
Yes. To turn it on:
- Contact your Customer Success Manager to enable the functionality.
- Turn it on for each US region: [Region] > Settings > BackOffice Default > Payroll / Other Settings > Calculate OBBB Qualified Overtime.
- On the same page, check Overtime Start Day of Week and Default Overtime Rule.
- Process a payrun, then open HR & Payroll > Prepare Payrun > [payrun] > OBBB Overtime.
Turn it on only for regions that pay US-based, non-exempt hourly employees: TrackTik doesn’t check the country. Amounts appear in Prepare Payrun and Data Lab and aren’t sent to your payroll provider in this release. This isn’t tax advice: check tax treatment with your payroll provider or tax advisor.
■ New feature
PEPPOL e-invoice export for Belgium
Available in: Web portal · Billing · Belgium only · Paid add-on
Release summary
Affected modules
Customer action required
Overview
Who benefits most: Billing admins who invoice Belgian business clients.
What drove the change: Belgium requires structured e-invoices sent over the PEPPOL network for business-to-business invoices from January 1, 2026. A PDF sent by email doesn’t meet that requirement.
What's new
What it does
Approved invoices get a Send to PEPPOL action:
- Checks first: TrackTik checks the seller and buyer details. If something is missing, an error names it, and no file is generated until it’s fixed.
- A ZIP of XML files: one XML file per invoice.
- Audit history: every export is logged in Settings > Audit History > Peppol Export.
How they work together
- Belgium only, in this release. Commercial invoices only (no credit memos), with one VAT rate per invoice.
- Approved invoices only. Invoices must be in Approved or Approved & Distributed status.
- Roles: admins set up PEPPOL Settings. Admin and Manager roles can complete site buyer details and export invoices.
Why it matters
Billing teams can meet Belgium’s e-invoicing requirement from the invoices they already create in TrackTik, without retyping them in another system.
How to access it
All sites: Billing > View All Invoices > Send to PEPPOL
One site: [Site] > Billing > Invoices > Send to PEPPOL
Screenshot
Select approved invoices, then click Send to PEPPOL.
Screenshot
The pop-up confirms the export.
Screenshot
Seller config in PEPPOL Settings.
Screenshot
The PEPPOL section in a site’s billing settings.
Rollout and upgrade
Rollout method
Customer action required
Yes. To start exporting:
- Contact your Customer Success Manager to turn on the add-on, then log out and back in to see PEPPOL Settings.
- Complete Settings > BackOffice Configurations > PEPPOL Settings: fill in Seller config, then map each tax class in Tax class mapping.
- For each site invoiced through PEPPOL, add the client’s VAT number, endpoint ID and scheme in [Site] > Billing > Billing Settings & Preferences > PEPPOL.
- Filter the invoice list to Approved, select the invoices, click Send to PEPPOL and open the ZIP. For a single invoice, use the Send to PEPPOL button on its row.
Submit the XML files through your own PEPPOL access point.
■ Enhancement
Premium pay detail in the payrun
Available in: Web portal · Prepare Payrun · All customers
Release summary
Affected modules
Customer action required
Overview
Who benefits most: Payroll admins and finance reviewers who check payruns before approving them.
What drove the change: A line could show a $20.00 base rate but a $186.00 total for 8.5 hours, with nothing to explain the difference. Raw Items lines had a pay code, quantity, rate and total but no date, so they couldn’t be tied to a day.
What's new
What it does
Two additions in Prepare Payrun:
- Base Rate Hours and Premium Rate Hours: new columns in the Summary tab. Together they add up to the hours on the line (Reg plus OT). For example, a $20.00 base rate, a $22.00 premium rate and 8.5 hours show as 0.5 Base Rate Hours and 8 Premium Rate Hours: 0.5 × $20.00 + 8 × $22.00 = $186.00.
- Expense Date: a new column in Raw Items, next to Employee Name, so every line shows the date it belongs to. The rest of Raw Items is unchanged.
Why it matters
Reviewers can see why a line’s total is higher than its base rate suggests, and tie every Raw Items line to a day, without opening the shifts behind it.
How to access it
HR & Payroll > Prepare Payrun > [payrun] > Summary
HR & Payroll > Prepare Payrun > [payrun] > Raw Items
Screenshot
Base Rate Hours and Premium Rate Hours in the Summary tab.
Screenshot
Expense Date in the Raw Items tab.
Rollout and upgrade
Rollout method
Customer action required
■ Enhancement
Client notes on dispatch requests
Available in: Client portal · Admin portal (setup) · Opt-in
Release summary
Affected modules
Customer action required
Overview
Who benefits most: Client portal users who raise dispatch requests and need to add context or updates, and the dispatchers and operators who handle those requests.
What drove the change: Built in response to customer feedback. Clients could see the note field on their dispatch requests but couldn’t use it, so they had no way to add context or updates to a request inside the portal.
What's new
What it does
Once their role has the permission, client portal users add a note like this:
- Under Security Operation, select Dispatch / Requests.
- Select the request. Its details open on the right, under Ticket Meta Information.
- Type the note in Add comments or notes.
- Click Add Note.
The note shows as the request’s Last Comment, and dispatchers see it on the same request in the admin portal.
How they work together
- Permission off: client users with that role can’t add notes.
- Admin and staff portals don’t change. The same release toggle option already controls adding notes there, and it works as before.
Why it matters
Clients can add context or updates straight onto the request they raised, so dispatchers see it on the request instead of the client hitting an error.
How to access it
Admin setup: Settings > Roles & Security > Roles/Permissions > Client Portal Roles > [select role] > Permission > Mobileplus > Can add comments to dispatch tasks on mobile
Client portal: Security Operation > Dispatch / Requests > [select request] > Add Note
Screenshot
The Can add comments to dispatch tasks on mobile permission, in the Mobileplus folder of a Client Portal Role.
Screenshot
A note added from the client portal, shown as the request’s Last Comment.
Rollout and upgrade
Rollout method
Customer action required
Yes. To let client users add notes:
- Contact your Customer Success Manager to enable the functionality.
- Go to Settings > Roles & Security > Roles/Permissions.
- Under Client Portal Roles, select the role your client users have.
- On the Permission tab, open the Mobileplus folder and check Can add comments to dispatch tasks on mobile.
To stop a role adding notes, uncheck the permission again.
■ Enhancement
Typed time in Time Picker and Date Time Picker
Available in: Web portal · Report templates and other web portal screens that use the time picker · All customers
Release summary
Affected modules
The mobile apps aren’t affected.
Customer action required
Overview
Who benefits most: Anyone filling in reports in the web portal (dispatchers, supervisors and account admins), especially when they already know the exact time they need to enter, like the time of an incident or an arrival.
What drove the change: Built in response to customer feedback. Setting a time meant clicking through the clock dial, one hour and one minute at a time. That’s slow when you already know the time you want to enter.
What's new
What it does
Same two fields, same names. Only how they open and take input has changed:
- Time Picker: the clock dial is gone. The picker opens with an hour field and a minute field. Type the value, press Tab to move to the minutes, and select OK. Or use the up and down arrows.
- Date Time Picker: pick the date on the calendar tab as before, then set the time on the clock tab the same way.
- Keyboard only: tab into the field, type the hour, press Tab, type the minutes. No mouse needed.
Why it matters
Entering a known time takes a couple of keystrokes instead of several clicks on a dial, so reports get filled in faster and with fewer mis-clicked times.
How to access it
Fill in a report: New Report > Choose Form and Account > Report Details, then click into the Time Picker or Date Time Picker field
Add the fields to a template: Settings > Report Templates > Custom Report Forms > [template] > Field Setup
Screenshot
Before: you dragged the hand around the clock dial.
Screenshot
Now: type the hour and minutes, or use the arrows.
Screenshot
Date Time Picker: pick the date on the calendar tab.
Screenshot
Then type the time on the clock tab.
Screenshot
The filled-in fields. Dates and times display in each user’s own date and time format settings.
Rollout and upgrade
Rollout method
Customer action required