PSA Software: The 2026 Guide for a Quebec MSP

PSA software (professional services automation) is the management tool of a service business: it keeps tickets, contracts, time worked and invoicing in a single database. For a managed service provider, it is what ties the client’s request to the invoice at the end of the month, with nothing retyped in between.

This guide is for people who run an IT services company in Quebec: do you need PSA software, which products should you look at, and how do you switch without breaking service? Our team built OKTO PSA for its own needs and uses it every day, so near the end we also say where it fits and what it does not do.

What is PSA software?

PSA software is management software designed for companies that sell time and services instead of products. The acronym stands for professional services automation. It puts client requests, contracts, hours worked, projects and invoices in the same place.

At a managed service provider (MSP), PSA software is the backbone of operations. The RMM watches the workstations, email receives the requests and accounting keeps the books, but the PSA is the one that knows three things at once: what was promised to the client, what was done for them and what they were billed.

A practical note if you search the web: “PSA” on its own also refers to a blood test in medicine. Type “PSA software” or “PSA for MSP”, or half your results will be about something else.

PSA or RMM: what is the difference?

The RMM looks after the machines, PSA software looks after the business. The first monitors workstations and servers, pushes patches and gives remote access. The second manages clients, tickets, contracts, time and invoices. An MSP needs both, and they have to talk to each other.

The lines move from one vendor to the next. What matters is that an RMM alert becomes a ticket without a human copying it, and that the PSA invoice reaches accounting without being typed again. If your company is not in IT and you are looking for a general management tool, our guide on choosing an ERP for a Quebec small business covers that ground. And if sales is what keeps you up, we priced out what a CRM costs a small business separately.

At what size does an MSP need PSA software?

Headcount is the wrong yardstick. An IT service provider needs PSA software as soon as it sells recurring contracts or prepaid hour blocks and a second person handles client requests. From that point on, the shared mailbox and the spreadsheet let unbilled time slip through.

Alone, with ten or so clients, you can get by with email, a calendar and invoicing software. With a second technician, it no longer holds. The signs:

• a request went unanswered because each person thought the other had it;
• monthly invoicing takes more than a day and means digging through emails;
• nobody can say how many hours are left in a client’s block without opening a spreadsheet;
• a contract was renewed at the same price while the client uses twice the planned hours;
• a client asks for the history of their interventions and it takes an hour to rebuild.

One of these signs can be lived with. Three at the same time, and PSA software pays for itself within months through the hours it stops you from losing.

The features that matter, by the problem they solve

Seven features separate useful PSA software from a big notebook: tickets, SLAs in business hours, contracts and hour blocks, time entry, recurring invoicing, assets and the client portal. Each one exists to solve a specific problem.

Tickets: nothing gets lost

A request that comes in by email, by phone or through the portal becomes a ticket with an owner, a priority and a history. The problem solved is simple: knowing who is handling what without asking out loud across the office. We go through what to expect from IT ticketing software on its own page.

SLAs in business hours: promises you can measure

An SLA is a promised delay: first response within one hour, resolution within eight, for example. The trap is in the math. If your contract covers Monday to Friday, 8 a.m. to 5 p.m., a ticket opened on Friday at 4:45 p.m. should not be late on Saturday morning. The clock has to follow the client’s calendar and Quebec statutory holidays, and stop while you wait for the client to answer. Software that counts clock hours shows delays that are not delays, and the team quickly stops looking at the indicator.

Contracts and hour blocks: knowing what is covered

Per-workstation plan, prepaid hour block, hourly rate: every client has its own agreement, and the technician does not know it by heart. PSA software ties the ticket to the right contract and draws down the block with each time entry. The problem solved is the surprise.

Time entry: the hour logged in the right place

Time is logged on the ticket, when the work happens, not in a timesheet filled from memory on Friday. Check that it takes two gestures. If it is slow, nobody will do it.

Recurring invoicing: month-end in an hour

Monthly plans, resold licences and block overages go out in one batch, from the contracts and the time already entered. The problem solved: the day lost building invoices by hand, with the omissions that come with it. In Quebec the taxes also have to be right; we come back to that below, and our page on invoicing software with GST and QST goes into detail.

Assets: knowing which machine we are talking about

The client’s fleet (workstations, servers, network gear) is attached to its record and its sites. When the ticket names the machine, the technician sees its history before taking the call. Ideally the inventory comes from the RMM, so nobody keeps it by hand.

The client portal: fewer “where is my ticket” calls

The client opens a request, follows its tickets and looks up its invoices without writing to you.

How much does PSA software cost in 2026?

It depends on the vendor, and several do not publish a price. On the sites read on October 2, 2026, HaloPSA lists CA$129 per agent per month for 10 agents, billed annually, when Canada is selected on its pricing page. ConnectWise and Autotask send you to a quote request. OKTO PSA lists CA$300 to CA$700 per month depending on the user tier, before taxes.

Sources: HaloPSA pricing page, ConnectWise pricing page, Autotask PSA page at Datto, read on October 2, 2026. OKTO PSA prices come from our own grid, in Canadian dollars, before taxes. “Not published” means we did not read it on the vendor’s site, nothing more.

A per-agent price and a per-tier price do not compare line by line. Run the numbers for the team you have today, then for the one you expect in two years, in the currency you will be billed in. Also ask who counts as a paying user: technicians only, or the person doing the invoicing and the one in sales as well?

To go further on each vendor, we have one comparison page each, built the same way: OKTO PSA next to HaloPSA, next to ConnectWise and next to Autotask PSA. Each one names the cases where the other product remains the better choice. The overview is on the page about US PSA products compared with one made here.

What does Quebec change when choosing PSA software?

Four things: personal information protection, language, taxes and currency. PSA software designed elsewhere can work perfectly well in Quebec, but each of these four points calls for a check before you sign.

Law 25 and where the data sleeps

Your PSA software holds names, emails, phone numbers and sometimes details about the workstations of your clients’ employees. That is personal information. Quebec’s Act respecting the protection of personal information in the private sector, commonly called Law 25 since its reform, sets a few obligations that bear directly on a software choice:

• section 3.1 makes the business responsible for the information it holds and requires publishing the title and contact information of the person in charge of protecting it;
• section 3.3 requires a privacy impact assessment for any project to acquire an information system that handles personal information, which buying PSA software is;
• section 17 requires that assessment before communicating personal information outside Quebec, taking into account, among other things, the legal framework of the place it would be sent to;
• section 3.5 requires notifying the Commission d’accès à l’information and the persons concerned when a confidentiality incident presents a risk of serious injury;
• section 91 provides, for a business, fines of $15,000 to $25,000,000, or 4% of worldwide turnover if that amount is greater.

We reread these sections on October 2, 2026 in the official French version published on LégisQuébec, updated to August 12, 2026; the wording above is our own summary. This is not legal advice. The main thing to remember is that no software makes a business compliant: the law targets whoever holds the information. Hosting in Quebec limits what leaves the province, but also check where the backups go and which subprocessors are involved. So put the question to each vendor in writing: in which region is the database hosted, and who has access to it? Our page on Law 25 and the software that holds your clients has the full list of questions.

French, for the team and for the clients

There are two kinds of French to check. The interface your technicians read eight hours a day, and the documents that leave the software: ticket emails, quotes, invoices, the portal. Ask to see the email templates and a sample invoice in French before you commit.

GST and QST

Your invoices carry two taxes, with your registration numbers, and some clients are exempt. Software designed for another market often handles a single sales tax, or asks you to set up the second one by hand. Run the test during the demo: an invoice with a taxable client, an exempt client and an amount that forces rounding. Then check how those amounts land in your accounting software.

Currency

A subscription billed in pounds sterling or US dollars moves with the exchange rate, and your budget moves with it. Ask whether a Canadian dollar price exists and whether it is fixed for the length of the contract.

How to choose PSA software in 7 steps

The right PSA software is the one that solves your three biggest operating problems, at a price you can forecast over two years, and that your team will actually use. The method below takes a few weeks.

1. Name your three problems. Unbilled time, lost tickets, an endless month-end: write them down, with what they cost you. That is your grid. A feature that solves none of the three carries no weight in the decision.
2. Draw the path of a request. From the client’s email to the paid invoice, note every tool touched and every retyping. PSA software should remove steps, not add some.
3. List the tools to connect. Your RMM, your accounting software, your directory. If the connection to one of them does not exist, find out before you sign, not after.
4. Shortlist three candidates and ask for the full price. Licences, startup fees, training, migration, currency, commitment length. A price without those six items is not a price.
5. Test with your cases, not the vendor’s. A ticket opened on a Friday at 4:45 p.m., an hour block that ran over, an invoice for a tax-exempt client. If the demo skips them, ask for another one.
6. Ask the awkward questions. Where is the data? How do you get it back if you leave, and in what format? Who answers support, in which language and during which hours?
7. Have the people who will use it try it. A technician and the person who invoices. If they find time entry painful, the nicest dashboard in the world will stay empty.

How do you migrate to new PSA software without stopping service?

You migrate without stopping service by keeping the old system running until the cutover. The new software is set up in parallel, the data is brought over and validated, then you switch on a chosen date, with a final import of that day’s data. Nobody works in a void between the two.

1. Pull an export of everything. Clients, sites, contacts, tickets, contracts, invoices, assets. Looking at the export is how you see what carries over well, what carries over badly and what is not worth carrying over.
2. Decide what follows you. Active contracts and the hours left in the blocks, always. Tickets closed years ago, not necessarily. Deciding early shortens everything else.
3. Set up the new software in parallel. The old one keeps running. Meanwhile, taxes, SLA calendars, and email and invoice templates get configured.
4. Validate the data before talking about a date. Take ten clients you know by heart and check their contracts, hour balances and latest invoices. A mistake found here costs nothing.
5. Train the team on its real tickets. An hour in the new software, with data it recognizes, is worth more than a day of generic training.
6. Pick the cutover date. The start of a week, far from monthly invoicing. The day before, the last day’s data is brought over.
7. Keep the old system readable for a while. To settle a doubt without panic. And plan for close support during the first weeks.

Ask each vendor who does this work. Some hand you an import template and leave you to it; others do it for you, by the hour or for a fixed fee. With us, our team does it, for a fixed fee quoted after a look at your data; the page on how we bring your data over explains what gets carried.

Common mistakes to avoid

The mistakes that cost the most when choosing PSA software are not technical. They come from how the purchase is made: choosing on the demo, underestimating the migration, paying for features that will never be used, forgetting the exit.

• Buying the feature list. The more the software does, the longer it takes to configure. A small team that buys a tool sized for a hundred technicians spends its first months filling in settings.
• Forgetting startup fees. Onboarding package, training, migration: they can weigh as much as the first year of licences. Get them in writing.
• Configuring everything before starting. Better to start with tickets, time and contracts, then add the rest. Software used halfway is worth more than perfect software nobody has opened yet.
• Neglecting the link to accounting. If invoices have to be retyped in the accounting software, you moved the problem, you did not solve it.
• Not asking how you leave. The export of your data, its format and its price are negotiated on the way in. On the way out, it is too late.

Where OKTO PSA fits, and what it does not do

OKTO PSA is PSA software designed and hosted in Quebec, in French by default, sold by user tier: $300 per month up to 10 people, $550 from 11 to 20, $700 from 21 to 30, in Canadian dollars before taxes. It suits a small or mid-sized MSP from here. It does not suit everyone.

What it does: tickets with SLAs calculated in business hours on the client’s calendar, contracts and hour blocks, time, recurring invoices with GST and QST calculated per line, the asset inventory and a client portal. The CRM and HR are included in every tier. Each client has its own database, hosted in Quebec. Seven connections are shipped: QuickBooks, Stripe, OKTO RMM, NinjaOne, Tactical RMM, Microsoft Entra ID and Google Workspace. Details are on the page about PSA software for Quebec MSPs, and the pricing grid by tier fits in four lines.

What it does not do, and we would sooner say it before you find out:

• it has no public API and no webhooks, so no in-house automations that read and write in the software;
• it does not offer SAML sign-in;
• it has no knowledge base;
• its reports are limited to a fixed dashboard and five CSV exports;
• custom fields, multi-currency and the mobile app are not shipped.

It does not replace your accounting software or your payroll service either. And the seven-day trial is requested from the team, not self-serve; meanwhile, an interactive demo with sample data opens in your browser.

If your operations rest on scripts that talk to your PSA all day, or if you need dozens of integrations, look first at the vendors in the table above. If what you are after is a tool in French, hosting in Quebec, correct taxes and an invoice that does not move with every hire, we should talk. The security and hosting page answers the questions your privacy officer will ask.