ERP for IT Service Providers
Project management, time tracking and controlling, tailored to IT projects and agile teams.
In Numbers
What the switch means day to day
What consultancies and IT service providers measure with QUANTICAL.ERP day to day.
What project time tracking has to do for IT service providers
An IT service provider rarely has one project. It has ten, on different contracts: fixed price for the migration, an hours quota for support, time and material for the development team at the client. Add developers who work on three of them in a single day, and clients who want to see the record for every invoice in their own ticketing system.
Time tracking has to carry that variety without someone stitching spreadsheets together at month end. Hours belong on the right project at the right rate, quotas have to shrink visibly, and the invoice has to come out the way each contract prescribes.
QUANTICAL.ERP sets these rules on the project and runs booking, record and invoice along them. To connect your own tooling there is a REST API with API keys, and sign-in via Microsoft Entra ID.
How IT service providers work with QUANTICAL.ERP
Several projects per developer, one rate per project
Only people assigned to a project can book on it, and each assignment carries its own hourly rate with a validity period. A senior developer books on the migration project at a different rate than in support. Several bookings for one day are entered in one pass and saved together.
Quotas as budgets with a term
An hours quota or a fixed price is stored on the project as a budget with an amount and a validity period, so a maintenance contract becomes a sequence of quarterly budgets. In controlling you see continuously how much is used and when the quota runs out at the current booking rate.
Records in the client's format
Per project you define whether the client requires a record of hours, whether it is uploaded in QUANTICAL.ERP or submitted in the client's portal, and whether it arrives in one file with the invoice or separately. The month-end closing shows each developer which projects still lack a record.
Invoice run by contract type
Single invoice per project, grouped invoice across all projects of a client, or credit note procedure, with the payment terms written in the contract. The monthly invoice run follows these rules automatically and locks the billed hours. Intercompany billing between your own legal entities runs in the same step.
Team utilization and capacity
Weekly hours, vacation and sickness produce the target per developer, and bookings run against it. Planned hours per project and period show who is still free in the coming weeks before you commit to a new project.
API and single sign-on
Through the REST API with API keys you read and write data from your own systems. Sign-in can run via Microsoft Entra ID, so your team needs no additional credentials and colleagues who leave lose access to the platform together with their company account.
Where ticketing-system time and Excel fail IT service providers
Many IT service providers track time in the ticketing system because the team works there anyway. But the ticketing system knows no hourly rate, no quota and no invoice. At month end someone exports the times, maps them to contracts and types totals into an invoicing program.
That handover is where the errors the client finds come from: hours on the wrong contract, a quota silently exceeded, a support rate on development work. Each of these costs a corrected invoice and a piece of trust.
What is missing is the view ahead. Whether the team can carry another project next quarter is written in no ticketing system. Only capacity planning that puts target, bookings and planned hours side by side answers that question.
Frequently asked questions from IT service providers
Can a developer book on several projects in one day?
Yes. Several bookings are entered in one pass, each with project, hours and description. The calendar shows progress against the daily target for each day.
How do we model hours quotas and maintenance contracts?
As a budget with an amount and a validity period on the project. A maintenance contract becomes a sequence of budgets, for example per quarter. Consumption comes from bookings times rate and is shown in controlling against the budget and the projection.
Is there an API?
Yes, a REST API with API keys that you create in the administration area. Use it to connect your own systems instead of transferring data by hand.
Do you support single sign-on?
Yes, via Microsoft Entra ID. Your team signs in with the company account, and permissions end with the account.
We have several legal entities billing each other for services. Is that possible?
Yes. Employees belong to a legal entity, and billing targets can be set between entities. The invoice run produces the intercompany invoices with their own numbering in the same step as the client invoices.
What does QUANTICAL.ERP cost for an IT service provider?
12.90 euros per user per month, cancellable monthly, all features included, API and SSO among them. Before that, 90 days free with the full feature set and no payment details required.