HaloPSA manages every client contract — retainers, block hours, subscriptions, and SLA targets — and drives your billing automatically from the moment a contract is set up. No manual intervention, no missed renewals.
Talk to an Expert
Build once, apply in seconds — templates for every MSP contract type.
Retainers, milestones, and usage charges invoiced automatically — no manual triggers.
Every ticket measured against the right client SLA, automatically.
Upcoming renewals flagged across your entire client base before they lapse.
HaloPSA supports every way MSPs charge for their services. Each model is configured independently per client — and each drives invoicing automatically, without manual reconciliation at month end.
Every billable action logged by a technician against a ticket is captured and flows directly to an invoice. Time entries attach to the ticket, the system identifies the client's billing rate, and charges are generated automatically. Nothing falls through the cracks.
A fixed monthly fee covers an agreed scope of support. Billing rules define which ticket types and charge types are included — all matching labour entries flow to the contract, not to a separate invoice. Work outside scope remains PAYG or can be excluded entirely.
Clients purchase a bank of hours upfront. As work is completed, hours are drawn down from the prepaid balance. HaloPSA tracks remaining hours in real time and alerts you when balances run low — so you can top up before a client hits zero.
Recurring invoices can be priced dynamically from a live count of users or devices — pulled directly from your RMM (e.g. NinjaOne), your Microsoft CSP integration, or Entra ID. As client headcount grows or shrinks, the invoice quantity adjusts automatically. No spreadsheet reconciliation at month end.
Billing rules tell HaloPSA how to handle every time entry a technician logs. They run in sequence — as soon as an entry matches a rule, that outcome applies. The right structure is always the same: exceptions first, catch-all last.
Rules are configured once in a billing template and applied to your entire client base in a single click. When your pricing changes, update the template — not each customer record individually.
Implementation tip: Use separate out-of-hours charge rates rather than time multipliers. Multipliers applied to retrospectively-logged time produce confusing invoice numbers — separate rates give clients a clear, predictable bill.
Example: Platinum Managed Services template
On-site support (any ticket type)
Out-of-scope — always charged separately
→ PAYG invoiceOut-of-hours remote support
Premium rate — billed at out-of-hours charge rate
→ PAYG invoice (out-of-hours rate)Remote support on Incidents
Fully managed — covered by the MSA
→ Captured to contractEverything else
Catch-all — anything not matched above
→ PAYG invoiceDefine billing rules once — what goes to contract, what stays PAYG, what's excluded for each service tier.
Assign the template and HaloPSA creates the contract agreement automatically. No separate step, no risk of admin error.
Change what's included in your managed service, hit Update Customers, and HaloPSA pushes the change across your entire client base instantly.
Most PSA tools require you to configure billing rules customer by customer. HaloPSA uses billing templates — a single configuration that deploys across all clients simultaneously.
When you onboard a new client, their contract is up and running the moment you assign the template. When your pricing changes, one update pushes to everyone. No manual work, no inconsistency across your client base.
You can maintain multiple templates — Platinum, Gold, Silver, PAYG — each with its own billing rules. A client's active agreements determine which rules apply, so the same template serves all tiers without separate configuration per customer.
HaloPSA tracks contract and recurring invoice line end dates across your entire client base and fires automated tasks before anything lapses — to the right person, with the right checklist, at the right time.
The automation is a ticket template with a to-do list — exactly the right structure for a renewal workflow. Configure it to fire 90 days out, 30 days out, or both. Set different rules per contract type so managed service renewals trigger a different workflow to block-hour top-ups.
The same mechanism covers recurring invoice line end dates — so if a subscription line stops generating, you know in advance. You're not left paying for something a client is no longer being charged for.
Triggered: 90 days before Acorn Construction MSA expiry
Renew: Acorn Construction — Platinum MSA (expires 31 Jan)
HaloPSA tracks agent costs against each contract — so you can compare what you're charging against what it's actually costing you to deliver. Most MSPs find at least one client that's been under-priced for months.
Client A
Platinum MSA
Cost ratio: 67% — margin: 33%
Client B
Gold MSA
Cost ratio: 90% — margin: 10%
Client C
Silver MSA
Cost ratio: 120% — losing £190/month
Data shown is illustrative. HaloPSA agent cost tracking compares real labour cost against contract revenue, per client.
Connects to
HaloPSA contracts — answered directly.
Also in HaloPSA
Every module included. One licence.
Allied ESM maps your existing agreements into HaloPSA and configures automation from day one. Fixed price, clear timeline.
Talk to an Expert