A busy multi-brand workshop is a factory that never gets treated like one. Work arrives without appointments, gets promised without checking the bays, moves through the floor on verbal updates, and gets billed from a pad at six o'clock by whoever remembers what was done. The owner knows the day was full; nobody can say whether it was profitable. Car service management software exists to run that floor the way a factory runs a line, and xMatix does it around one organising object: the job card — the single record that carries the vehicle, the approved work, the parts, the technician hours and the money, from the first health check to the settled invoice. This page is written for the independent and multi-brand operator; the franchised dealership's version of the same engines lives on the dealer workshop page.
The job card is the unit of work
Everything in the workshop hangs off the job card. The health check at reception turns findings into recommended jobs; the estimate carries them with parts, labour and tax; and the customer's approval or decline stamps the estimate and every line before work starts — so the six-o'clock billing argument is settled at nine in the morning. Declined items don't vanish: they stay on the vehicle's record as follow-up opportunities for the next visit. As the day runs, the card accumulates reality — technician timesheets, usage readings, photos from the floor, the parts actually consumed — which means the invoice at the end is not a reconstruction of the day but a by-product of it. A workshop that has only ever known billing software discovers the difference the first time a customer disputes a repair and the card answers with the checklist, the photos and the signature.
Bays and technicians are capacity, not a queue
Most workshops schedule by shouting. On xMatix, service bays are bookable resources with types — mechanical, denting, washing — and jobs book them the way appointments book a calendar: type matched, capacity checked, the day visible as a plan. Technicians are allocated by skill and existing load, so the one tech certified for the German brands gets the German brands and nobody carries three simultaneous jobs. The floor runs from a console with three views — board for who-does-what, timeline for when, map for the pickup fleet — and when reality edits the day (a part doesn't arrive, a customer walks in bleeding coolant), the dispatcher drags the plan around it instead of re-shouting the afternoon. A week ahead, the same capacity model answers the question walk-in-only workshops cannot: how much work can we actually promise for Tuesday? The walk-in trade still fits — a workshop is not an airline — but it fits into visible slack instead of silently displacing the booked customer whose car was promised by five.
Parts consumed on the job, priced at the counter
The parts counter is where workshop margin quietly leaks — parts fitted but never billed, stock counts that drift, the fast-mover that stocks out on a Saturday. Because parts issue to the job card as they are consumed, the card and the stock ledger agree by construction: what left the shelf is what appears on the invoice, priced by the price list with GST treated correctly as goods, separate from the labour lines' service treatment. Replenishment projects from actual consumption, so the counter reorders from evidence; and a part that strands a vehicle mid-job raises its urgency from the job itself rather than from a phone call. The full counter-level story — stock, purchase, day-end cash — is on the garage management page.
Service contracts that generate their own jobs
The most valuable customer a workshop has is the one who comes back without being chased — and the AMC is the machine that manufactures that customer. Contracts on xMatix meter themselves — by time or usage, with entitlements that burn down visibly — and their preventive schedules generate jobs before due dates, so the calendar fills from the contract book rather than from hope. Reminder engines work the non-contract base the same way: every vehicle's history implies its next due date, and due dates become leads, calls and booked appointments. The mechanics of that funnel are on the service reminders page; the effect is a workshop whose Mondays are planned by its own records.
Billed compliantly, posted automatically
The job card ends as a GST-correct invoice — labour and parts each taxed as what they are — with e-invoicing where turnover requires it, and the collection captured against the invoice it settles, cash and UPI included. Every document posts to real double-entry books as it happens, so the month-end is a review rather than an archaeology dig, and the accountant stops re-entering the workshop's month from a folder of counterfoils.
The billing model stretches to the customers who matter most: fleet accounts — the cab operator, the school buses, the courier franchise — run on credit terms with limits enforced at job creation, monthly statements generated from the same invoices, and ageing that is a fact rather than a feeling. Insurance and accident work follows its own payer lane on the same job card, so a visit that mixes insurer-paid panel work with customer-paid servicing bills each party exactly its own lines. The workshop stops subsidising its biggest customers by accident.
What the multi-brand operator sees across branches
Run three branches on memory and you run three different businesses that share a name. Run them on one platform and the questions become answerable: bay utilisation and technician productivity per branch, average job value, parts margin, AMC attach and renewal rates, declined-work conversion — computed from the same job cards that ran the floor, not from month-end returns each branch manager assembles in self-defence. Branch stock transfers keep identity and cost intact, customers and their vehicles are one record wherever they show up, and the operator planning a fourth branch is planning from evidence. The questions between the reports get answered too: Sense, the AI assistant, answers in plain language from the operator's own records under their own permissions — "which AMCs lapse next month?", "compare bay utilisation across branches this quarter" — with the working shown, so the numbers meeting stops waiting for someone to build the query. The offline-first mobile app extends the same records to pickup drivers and roadside jobs — because a workshop's work does not all happen inside the workshop.
Common questions
How does a job card differ from an invoice?
The invoice is the last page of the story; the job card is the story. It carries the approved estimate, the technician hours, the parts consumed, readings, photos and checklists — accumulated while the work happens. The invoice is generated from it, which is why the two can never disagree and why a disputed repair has evidence instead of an argument.
Can bay and technician capacity be planned a week ahead?
Yes — bays are bookable resources with types and capacity, technicians have skills and availability calendars, and appointment slots draw from both. The week's promise-making runs against real capacity, and the dispatch console re-plans the day by drag when reality intervenes.
How are spare parts consumed and billed on a job?
Parts issue from stock to the job card as they are fitted, so the stock ledger and the card agree by construction. At billing they carry their own GST treatment as goods, separate from labour, and consumption feeds replenishment so the counter reorders from what jobs actually used.
Does car service management software work for a multi-branch, multi-brand operator?
That is the operator it is built for: branches share one customer and vehicle master, one parts ledger with identity-preserving transfers, and one set of books — while bay plans, pricing and performance are visible per branch. Multi-brand is the default, since the vehicle model is configurable rather than tied to one OEM's structure.