Holidays and employee costs: where the numbers come from

Which holidays sync from Autotask vs. get added by hand (ConnectWise, HaloPSA, Syncro, Rev.io and SuperOps workspaces add holidays by hand), what the holiday calendar now drives on your dashboards and your PSA date pushes, and where employee cost rates come from.

Updated Oct 10, 20263 min read

On this page · 3 sections

Holidays: one calendar per tenant, two ways to fill it
Employee cost: per-person, from two sources, admin-only
What holidays and costs are each used for

Two numbers quietly shape a lot of what Current shows you: the company holiday calendar (which drives every schedule), and each employee's internal hourly cost (which drives every margin figure). Both can come from two places (synced from your PSA, or entered by hand in Current), and it matters which one applies where. Holidays sync from Autotask only; cost rates sync from Autotask, ConnectWise and HaloPSA, and on a Syncro workspace you set them in Current. Here's exactly how each works, verified against the code, not guessed.

Note

On ConnectWise and HaloPSA, holidays are the manual part. Cost rates are not

Cost rates sync on three of the six PSAs: Autotask reads the Internal Cost (Burden Rate) on the resource's HR tab, ConnectWise reads hourlyCost on the member, and HaloPSA reads costprice on the agent. Syncro, Rev.io and SuperOps do not publish an internal cost rate through their APIs, so on a Syncro, Rev.io or SuperOps workspace you set rates in Current and a sync never overwrites them. That includes technicians who have no Current login. Their rate is mirrored too, and prices their hours in the renewal dossier's account profitability section. The holiday calendar is the piece that is still Autotask-only: a ConnectWise, HaloPSA, Syncro, Rev.io or SuperOps workspace adds its holidays by hand, a few minutes once a year, and they drive scheduling identically.

Holidays: one calendar per tenant, two ways to fill it

Current keeps a single company-wide holiday calendar shared by every project. This is what "weekends + holidays skipped" on the Timeline actually skips. It's filled two ways, and both can be in play at once:

Synced from Autotask. Current's regular sync pulls Autotask's company holiday set and adds those dates automatically. These rows are tagged as coming from Autotask. (Autotask workspaces only.)
Added manually. A Tenant Admin can add a one-off holiday (a date plus an optional name) directly in Current, for anything your PSA doesn't have, or, on ConnectWise, for the whole calendar.

1
Open the Holidays page
Admin-only page. It shows a running count, e.g. "14 holidays, 10 synced from Autotask, 4 added here."
2
Review each entry
A synced holiday shows an Autotask badge (hover it: "reappears on next sync if deleted here"). A manual one shows a pen icon instead.
3
Add a manual holiday
Pick a date, optionally name it, and save. It applies to every project in the tenant immediately.
4
Delete carefully
Deleting a synced holiday works, but it comes back on the next Autotask sync, delete it in Autotask instead if you want it gone for good.

Heads up

A synced holiday will reappear

If a holiday is tagged as coming from Autotask, deleting it in Current is temporary, the next sync re-adds it. Remove it in Autotask if you want it gone permanently.

Note

This list also shapes your response times now

If your workspace measures average first response and average resolution time on your desk's working hours (a tenant-admin setting in Settings › General › Region and words), the days on this calendar are left out of those two numbers, exactly as the Timeline leaves them out of a schedule. One list, so scheduling and your service desk numbers can never disagree about a day off. Adding a holiday therefore makes those two averages read slightly smaller for any period that contains it. On the round the clock setting, which is where every workspace starts, this calendar has no effect on those numbers at all.

Employee cost: per-person, from two sources, admin-only

Every person can have an internal hourly cost, what they actually cost the business per hour, as opposed to what you bill a partner. Current uses it in two places: the Profitability report under Reports, and the cost-to-serve math behind the renewal dossier's private profitability section. The rate itself never appears anywhere a project manager, engineer, account executive, or partner viewer can see.

Synced from your PSA. If a person is linked to a PSA resource, their cost is pulled in automatically on every people sync: Autotask's Internal Cost (Burden Rate), ConnectWise's member hourlyCost, HaloPSA's agent costprice. Current shows this as the source and won't let you hand-edit it here, because the next sync would just overwrite your edit. Settings → Cost rates is the one place an override sticks. Note that Autotask only sends across resources marked Active, so a technician who has left stops being refreshed.
Entered manually. For anyone your PSA holds no cost for, a Tenant Admin can enter a rate by hand, and no sync overwrites it.
Mirrored but not listed. Technicians with no Current login never appear in this list, because it is built from your Current people. Their PSA rate is still mirrored, admin-only, and it prices their hours in the renewal dossier's account profitability section.

What holidays and costs are each used for

Data	Drives	Doesn't drive
Holiday calendar	Task scheduling and critical-path dates on the Timeline, Dependency map, What-if, and the Schedule grid. Recognizing an Autotask date that rolled forward off a holiday, so Current adopts Autotask's stored date instead of logging a conflict. Also, on a workspace measuring response times on working hours, the average first response and average resolution time on your dashboards: a holiday is not a working day, so it is left out of both	Cost, margin, or budget figures. Nor SLA compliance, which is your PSA's own verdict against its own due times and its own calendar
Employee hourly cost	The Profitability / Margin lens on Reports (revenue minus internal labor cost, by project), and the cost to serve behind the renewal dossier's account profitability section	Scheduling, capacity, or the standard project budget/burn view. Those use billable rate and hours, not cost

Note

Cost rates are Tenant Admin only, with one named exception for margin

Cost rates themselves (this list, and every per-person figure built on it) are Tenant Admins and super admins only. Project Managers, Engineers and Account Executives never see them, and neither does a partner viewer. Margin follows the same rule everywhere except one place: since August 2026, the renewal dossier's private profitability section shows account-level gross margin, cost to serve and hours for a single company to sales leadership and to Account Executives who can view that company. Even there the breakdown by technician stays admin-only. If margin numbers look incomplete, it's because some people don't have a cost rate on file yet. Current never leaves those hours out and never treats them as free: the dashboard margin tiles report them as unpriced hours, and the renewal dossier prices them at your team's median rate and marks them estimated.

See "PTO and availability-aware scheduling in the Timeline" for how the holiday calendar interacts with individual PTO, and see "Roles & permissions: who sees what" for the full admin-only visibility list.

Was this helpful?

← Previous

PTO and availability-aware scheduling in the Timeline

What-if scenarios: preview a schedule slip before it happens