PSA, ticketing system, or accounting system?
A ticketing system knows who asked and what was done. It does not know what the work was worth.
A CRM manages the business up until the deal is closed. Everything that happens after the contract is signed is outside its scope.
An accounting system receives the billing data but does not create it. The data has to come from somewhere, and in many MSPs, that means a spreadsheet and a long afternoon at the end of the month.
An ITSM system solves the same thing for an internal IT department, but without contracts, pricing, and billing – because the recipient is a colleague, not a customer.
A PSA covers the distance between a sold contract and a sent invoice. It is on that stretch that the margin is either found or lost.
The contract model is the difficult part
Most people who switch PSA systems think they are doing it for the sake of ticketing. In practice, it is the contract model that determines whether the system will work.
Fixed-price agreements, time and materials, hour banks, block agreements, license rebilling, and recurring services must coexist in the same structure, often for the same customer. If the system can only handle one of these models, the rest will be managed on the side, and what is managed on the side is rarely billed on time.
Map out your actual contract types before you look at a single feature list, exceptions included. That exercise is what separates a successful PSA implementation from an expensive one.
Where margins leak
Time that is never recorded. The half-hour squeezed in between two meetings doesn't show up in any report, but it remains in your payroll costs.
Work outside of agreements. Tasks performed out of habit, even though they fall outside what the customer is paying for. Without an agreement linked to the ticket, it goes unnoticed.
Licenses renewed unnoticed. A renewal that goes through automatically for a customer who stopped using the service last spring.
Invisible profitability. You know which customers pay the most. Without tracking per customer, you don't know which ones are actually profitable.
Three questions that determine your choice
Who will manage the configuration? Some platforms are configured by your own staff, while others require consulting hours for every new field. This determines what the system costs over five years.
Which accounting system does it need to talk to? Fortnox, Visma, and Pyramid are recurring requirements in the Nordics, and something international providers rarely have a good answer for. Verify that the integration is ready to use, not just that an API exists.
How is the monitoring connected? Alerts from your RMM system that don't automatically become tickets with the correct customer and agreement create double work every single day.
Migration from an existing PSA
Customers, contacts, agreements, price lists, assets, and ticket history all need to be moved. The mapping takes the longest time; the actual migration is fast. We perform test migrations and verification together with you before the live cutover, and if necessary, run them in parallel for a period so that no billing falls through the cracks.
The system is visible in the service desk
A PSA is the backbone of the business, but what the customer encounters is the service desk. The configuration of queues, priorities, and SLAs determines how the delivery is perceived – and consequently, whether the contract is renewed.
We run our own business in a PSA
MSP Nordics runs its entire operation in HaloPSA – service desk, contracts, time tracking, and billing. We have therefore encountered the same things you will encounter: where the contract model clashes with reality, which configurations hold up as the customer base grows, and which automations actually save time.
