MSP PSA software: key features explained
What MSP PSA software does, the features that connect service delivery with billing, which platforms to shortlist, and how to test the whole service-to-cash workflow before you choose.
Updated November 11, 2026
MSP PSA software connects the business side of managed IT services: support tickets, technician time, projects, contracts, billing and reporting. Rather than treating each as a separate job, professional services automation brings them into one workflow. This guide explains the core features and gives you practical ways to test whether they fit your service business. (source)
What is MSP PSA software, and how does it work?
MSP PSA is professional services automation software used by a managed service provider. It organises service delivery and links the work technicians do to client agreements, schedules and financial records. Its central purpose is to make every piece of service work traceable, from the first request through to completion and billing. (source)
Take a typical support request. A client reports an issue, a ticket captures the details, and a technician records the work. Set up properly, the PSA connects that work to the client’s agreement and billing, instead of needing separate records at every stage. (source)
PSA and remote monitoring and management (RMM) do different jobs. RMM looks after endpoints and technical operations; PSA manages the service workflow around that work. Integrating the two turns monitoring alerts into tickets linked to the right devices and agreements. (source) The PSA and RMM guide covers that in depth.
Key features that connect service delivery and business operations
When comparing PSA tools, look at how the features work together rather than counting modules. Use a realistic client request to test the hand-offs between dispatch, technical work, approvals and finance. A polished dashboard matters less than whether your team can finish that workflow without typing the same thing twice.
Service desk ticketing and SLA management
Ticketing gives each support request a trackable record, and service-level agreement (SLA) management helps the team keep response and resolution commitments. Good platforms combine ticket intake, routing, client communication and deadline alerts for a more consistent service. (source)
In a demo, ask to see an urgent request arrive outside business hours. Check how the system identifies the client, sets the priority, picks the queue and calculates the deadline, and what happens when the technician is unavailable or the ticket needs escalating. Then reassign it: the next technician should have enough context to carry on without asking the client to start again.
- Ownership: can anyone see who is responsible for the next action?
- SLA rules: can it represent your real support hours and commitments?
- Client visibility: can clients follow progress without seeing internal notes?
- Ticket quality: can you require the essential details without making submission a chore?
Time tracking and resource scheduling
PSA time tracking ties technician effort to tickets, projects and client agreements, and scheduling views help match people to incoming work. Together they give a clear record of where service effort goes. (source)
Test time entry with the people who will use it every day: record a short support call, switch between tasks, and correct an entry. Include internal admin and work covered by a recurring agreement, not only separately billable labour. For scheduling, try booking an onsite visit while keeping support covered, without your dispatcher needing a second calendar, and check that the dispatcher can tell real capacity apart from someone who simply has an empty calendar but not the skills the job needs. Fast, accurate time capture is a usability requirement, not just a report.
Contract management and billing
Contract management defines how services and labour are charged: recurring services, time and materials, fixed-price projects or prepaid hours, depending on the platform. Autotask’s documentation, for example, describes several contract types and billing tied to contacts or devices. (source)
Ask the vendor to reproduce your real agreements, not a simple sample invoice. Include covered support, excluded work, an add-on service and a change in the client’s quantities, then trace each charge back to its contract or source record.
Test a recurring agreement that includes support but excludes project work: show how the excluded task reaches invoice review, and how a mid-cycle change to the agreement is handled. For profitability reports, ask what revenue and cost figures sit underneath them; a polished dashboard isn’t enough. (source)
Check the review process as carefully as invoice creation. Who approves time, resolves exceptions and confirms changes before charges reach accounting? Make those responsibilities explicit, so automation supports your billing controls instead of bypassing them.
Payments and reconciliation
Billing doesn’t end when the invoice is sent. Online payments, and the reconciliation that follows, decide whether the PSA, your accounting system and your bank agree on what was actually collected. Test that separately: ask to see a partial payment, a credit, a failed collection and a refund, not just a successful card payment, and check that each one lands correctly in the invoice’s balance and in your accounting system. Ask for the security documentation for any payment integration, and be clear which responsibilities for payment data stay with your team. Installing an integration isn’t evidence that every security or compliance obligation is covered.
Project management
Project features organise work into tasks, schedules, budgets and assignments, with progress and capacity visible alongside day-to-day support. That matters most when the same technicians handle both support tickets and planned work. (source)
Use a client onboarding or a network upgrade as your test project: break it into preparation, implementation, validation and handover, assign owners and estimates, and see what happens when an urgent ticket interrupts the schedule. Don’t pay for sophisticated planning features unless someone will keep the information they need up to date.
Reporting and operational visibility
PSA reporting can bring together service performance, technician activity, costs and revenue. Dashboards and financial views vary by product, so check for the reports you need rather than assuming every platform measures things the same way. (source)
- Service backlog: which open requests need attention, and who owns them?
- SLA performance: where are commitments being missed, and why?
- Client effort: which clients use a lot of technician time relative to their agreements?
- Billing readiness: what finished work still needs review before invoicing?
For each report, ask for the definitions and the records behind it. Agree what counts as a response, a resolution, a billable hour and labour cost before judging performance by a dashboard. A few trusted numbers beat a big report library nobody maintains.
Integrations and workflow automation
Integrations connect service delivery with monitoring, accounting, documentation and other systems, and workflow rules can automate steps such as ticket assignment or billing updates. What’s available, and how deep it goes, depends on the product and configuration. (source)
Judge integrations at the level of fields and workflows. An RMM connection might create tickets while an accounting connection updates invoice and payment status: different jobs, so an integration logo alone doesn’t tell you what your team can automate. (source) For each connection, establish:
- Data ownership: which system controls client details, contracts, invoices and payment records.
- Sync behaviour: which fields move, in which direction, and how often.
- Failure handling: how staff find out a sync failed, and retry it without creating duplicates.
- Access controls: what the integration’s account can read or change, before you grant it.
Test a duplicate alert, an unavailable connection and a client record changed in two places, and ask for a clear recovery process rather than accepting “it integrates” as proof. Ask to see permissions, sign-in options and audit records too, and confirm which responsibilities stay with your team.
Which PSA tools should MSPs evaluate?
Start by comparing dedicated PSA platforms with combined PSA-and-RMM suites. Capabilities and package inclusions differ, even within one vendor’s range, so confirm what’s in the subscription you’re actually being offered. (source) These are starting points, not a ranking:
- ConnectWise PSA: broad service delivery, project, time, finance and reporting capabilities; check package inclusions against your needs. (source)
- HaloPSA: worth a look when configurable workflows, contracts, billing rules, portals and reporting are central to your evaluation. (source)
- Atera: a combined RMM, PSA and remote-access suite if consolidating your stack is the priority. (source)
- Syncro: integrated RMM and PSA, including ticketing, automated invoicing, workflows and reporting. (source)
- SuperOps: a PSA with AI assistance such as ticket summaries, worklogs and suggested responses. (source)
For a small team, weigh how maintainable each one is alongside what it can do: who will configure workflows, keep contracts accurate and train new staff? For larger or more complex operations, test approval paths, permissions and reporting across teams before committing. Opcrunch’s own comparison pages set it side by side with ConnectWise, Autotask, HaloPSA and Syncro, with sources.
Test a complete service-to-cash workflow
Before choosing, run one complete piece of work through each shortlisted PSA using representative sample data, with your technicians, dispatcher and whoever does billing each handling their own step:
- Receive and assign: submit a request and check the client details, owner, priority and SLA.
- Deliver and document: record time, hand the ticket to someone else, and check the history they see.
- Apply the agreement: check included services, exclusions, recurring charges and invoice adjustments.
- Collect and reconcile: follow the invoice through payment and confirm the PSA and your accounting system agree.
- Inspect the results: review service performance, recorded effort and the inputs behind profitability figures.
Test AI features separately. Several PSAs now offer AI ticket summaries, categorisation, triage or suggested replies. (source) Run them on your own representative tickets, check how staff review or override the output, and tell genuine AI assistance apart from fixed rules and scheduled tasks.
For pricing, ask for a written total covering subscriptions, implementation, migration, training, integrations and optional features, and which charges grow with users, endpoints or usage. Compare that with the admin work the trial actually removed, not with promised savings.
How to choose the best PSA software for an MSP
Evaluate candidates against your workflows, billing arrangements, integrations and how much admin your team can carry. Define those requirements before watching demos, and use the same test scenarios with every vendor so the decision reflects fit rather than presentation.
- Name your main friction points, such as unreviewed time entries or unclear ticket ownership.
- Separate requirements from preferences: essential contract rules versus nice-to-have interface touches.
- Run the service-to-cash test above with every shortlisted vendor, using the same scenario.
- Assess the full commitment: licensing, implementation, migration, training, integrations, support and how you would leave.
- Include everyday users: have technicians, dispatchers and whoever does billing test their own tasks.
When reading reviews, look for context rather than the overall score: the review date, team size, service model and the specific workflow being discussed. Turn relevant praise or criticism into something you can check during a trial.
What should a small MSP prioritise?
For a small MSP, prioritise the essential workflows, easy daily use and an admin load your team can sustain. Test ticket handling, time capture, contract billing and the hand-off to accounting first, and add complexity only where it solves a defined problem.
Before committing, decide who will own configuration and upkeep, and ask them to estimate the work of managing queues, templates, permissions, billing rules and reports. Count that workload alongside the subscription price. Then run a small pilot with representative clients and agreements, agree what success looks like (for example, an invoice review with no parallel spreadsheet), and expand only once the team handles routine exceptions confidently.
Where Opcrunch fits
Opcrunch is a PSA built for small MSPs, around exactly these workflows: tickets with SLAs, agreement billing (recurring services, fixed fees, prepaid blocks and included hours), time that flows from approval onto the invoice, quotes, projects and a client portal. It connects to QuickBooks Online or Xero, takes card and ACH payments through your own Stripe account, and turns alerts from NinjaOne, Datto RMM, N-able and Syncro into tickets. Its optional AI assist summarises tickets, drafts replies and tidies notes, and a person always reviews before anything is sent. Its daily revenue check compares each agreement with Microsoft 365 and RMM counts and lists approved time that never reached an invoice, which covers the billing-readiness check above. It’s $49 per technician, month to month, and migration is free, so you can run the pilot with your own data.
Choose connected workflows over a longer feature list
Choosing a PSA is a workflow decision, not a feature-count contest. Shortlist against your real service and billing requirements, test the hand-offs that matter most, and choose the platform your team can run consistently, with clear ownership for keeping it useful.
Guides in this series
- PSA and RMM for MSPs: how they work together: What PSA and RMM each do, how an RMM alert should become a ticket and then an invoice, which platforms to shortlist, and how to test an integration before you commit.
- Microsoft 365 license reconciliation for MSPs: How to compare the Microsoft 365 licenses each client actually has with what their agreement bills, how often to do it, and how to fix the gaps without surprising the client.
- Finding and fixing unbilled time at an MSP: Where billable hours go missing between the ticket and the invoice, the four places to look each month, and the habits that stop it happening again.
- PSA software: benefits for businesses: the wider view of professional services automation beyond MSPs.
- Compare PSAs for MSPs: Opcrunch next to ConnectWise, Autotask, HaloPSA and Syncro, with sources.