Shop management system (SMS) is the software a repair business uses to organize customer and vehicle records, estimates, authorizations, repair orders, scheduling, invoicing and related operating reports.
What part of the sale does the system help you verify?
It shows how the shop records customers, vehicles, authorized work, labor, invoices and payment activity. It can expose patterns hidden in annual financial statements, as long as you understand what staff actually entered.
A customer may have several vehicles and one vehicle may appear on many repair orders. An estimate can contain work the customer declined. A posted invoice can include sales tax, and a payment can settle to the bank on another date. Treating all these events as sales makes a busy screen look more profitable than the shop. Follow one normal repair from first call through final deposit before interpreting a dashboard.
Tekmetric, Shopmonkey, Mitchell 1 and AutoLeap are examples of shop management systems. Their reports, field names, integrations and user roles differ. Ask the seller which features the team uses, whether the shop changed systems and which measurements come from spreadsheets outside the platform. Your diligence concerns the actual shop, not the list of functions the vendor offers.
Which reports should you request first?
Request a small package that answers one complete operating question, then drill down where the figures disagree. A large export with unclear filters can waste time and expose unnecessary customer information.
- Obtain monthly completed or posted sales, split into parts, labor, sublet, fees, discounts and tax where the system supports those fields.
- Export repair order detail with stable identifiers, status, dates, vehicle and anonymized customer account. Distinguish completed work from estimates, voids and internal jobs.
- Pull technician billed hours, job-clock hours where available and customer or vehicle activity. Identify the owner’s work and overlapping assignments.
- Obtain payment, credit and refund information for a period that can be matched to merchant and accounting reports.
- Record the report name, settings, permissions and extraction date. Keep an unmodified original and document any cleaning or exclusions in your analysis.
The SMS report request checklist gives the buyer and seller a common starting point. Tekmetric’s reporting, customer-history and accounting guides explain where you can look for sales activity, customer records and job costs. Each identifies a different population of records and may use a different event date.
How do you reconcile billed work to cash?
Start with one period and explicitly bridge between invoiced sales, payments collected and dollars settled. The goal is a reconciled difference with explanations that can be tested.
Illustrative composite — not a real client. A shop posts $105,000 of customer invoices, including $5,000 of tax. Pretax sales are $100,000. Suppose $12,000 of the gross invoices remain unpaid at month end and the shop collects $7,000 against invoices from the prior month. Gross receipts are $105,000 minus $12,000 plus $7,000, or $100,000 before credits, fees or other timing items.
Assume all but $8,000 of those receipts come through a card processor. The processor retains $2,100 in fees and has $3,000 of current receipts unsettled at month end. A further $1,500 from the previous month settles now. Expected card deposits are $92,000 minus $2,100 minus $3,000 plus $1,500, or $88,400. Trace the separate $8,000 of other receipts to cash records or other accounts. Matching pretax sales and gross receipts at $100,000 in this example is a coincidence, not a reconciliation shortcut.
Use the shop earnings builder only after establishing the operating sales base. If the average repair order looks unusually high, check whether the numerator includes tax, fleet invoices or sales with no matching completed customer order.
What data errors can mislead a buyer?
Common problems include missing labor assignments, identical customers entered twice, unposted vendor costs and different treatment of reopened tickets. Audit how the team uses the platform under pressure.
A technician working on a job overnight may leave the job clock running. A service adviser might reopen an invoice to correct a price and inadvertently shift the report date. A manager could use a default parts cost until a supplier invoice arrives but never update it. A customer with a new phone number could be recorded as a new account. Each mistake touches a different claim, from efficiency to margin to repeat demand.
Select normal work and exceptions. Rebuild a handful of jobs from estimate, authorization, completion and payment. Include a fleet job, a warranty claim, a returned part, a discount and a job crossing month end. Verify how each appears in the general ledger. If the owner relied on personal spreadsheets to correct gaps, request the spreadsheet and check whether someone else can maintain it after closing.
What must transfer with the system?
Establish the rights, permissions and connections needed to operate after closing. An administrator password alone cannot substitute for vendor approval or a lawful account transfer.
If you’re selling, identify the legal account holder, billing contact, administrative users and any personal email or phone used for recovery. Ask the vendor how ownership and subscriptions can be changed. List connected payment processing, customer texting, accounting, inspection tools and booking services. Each integration may have its own agreement, credentials and verification process.
If you’re buying, use the data-room index to track access rights and transfer steps. Ask for a supervised demonstration and a redacted sample before requesting identifiable records. Plan how you will continue open jobs, preserve warranties, protect customer information and give the seller any limited records required for historical tax or claims matters.
What breaks when the shop changes software in the middle of the year?
Find the last trustworthy period in the old system and the first complete period in the new one. Ask whether the conversion imported historical jobs, open jobs, customer contacts, balances or only selected fields. A shop may retain invoice images for reference without importing the underlying labor-hour detail. Conversely, a migration may copy a customer’s old ticket and then create another order when the vehicle is picked up. A year-to-date export from the new platform can therefore omit history or duplicate it, even though the service counter operates normally.
Take a hypothetical shop that switches in July. The old platform shows 980 posted orders for January through June. The new platform shows 1,070 for the second half, including 30 imported historical orders mistakenly tagged with July posting dates. Eight of the 30 are open jobs actually completed and billed in July. After checking the crosswalk, exclude only the 22 genuine duplicates. The result is 980 plus 1,070 minus 22, or 2,028 distinct posted orders across the year. Automatically discarding all 30 would undercount the eight completed jobs.
Choose several jobs near the switch and follow them by vehicle, invoice total, authorization date, final posted date and payment destination. Preserve the original identifiers from both platforms. A new system may assign an entirely different ticket number to the same vehicle. A matching dollar amount by itself is weak evidence, especially in a shop that sells menu-priced services. Once you have a trustworthy crosswalk, reconcile the dollars separately to the ledger and check transactions that were refunded or reopened after the migration.
Which user actions should the buyer demonstrate before taking control?
Select ordinary tasks that cover the role boundaries in the shop. Ask an authorized incoming service manager to find an existing job, read an attachment available to that role, identify a deferred recommendation and export a report for a closed period. Ask a technician to show that the assigned role can see their own queue and record time. Verify how a permitted manager can revoke access for a departing employee. Use approved test records or a properly supervised demonstration so you preserve confidentiality and avoid sending a customer an unintended message.
A successful owner login on one computer tells you little about the rest of the workflow. The merchant account can have its own legal owner, the customer-messaging number may be administered separately, and the bookkeeping connector may depend on an individual credential. List each dependency and its administrator, approval requirement and expected transfer date. Have the vendor confirm the mechanism for your contract. Credentials that belong to the seller personally should not become the buyer’s informal long-term access plan.
At the completion meeting, ask someone who did not arrange the transition to reproduce one monthly report from the written instructions. Compare the result with the saved control total. If the difference is $900, determine whether it reflects a changed date range, tax setting, refunded invoice or permission level before accepting the transfer. Retain the configuration and version information that produced the original result. Your objective is a reporting and dispatch system that the incoming staff can use and explain on the first normal workday, including the parts that will remain available only through a legacy archive.
How should you record the handoff?
Build a dated access checklist with a named owner for each action. Practice the sequence in a permitted test or supervised setting so closing day does not become the first time anyone asks how the system works.
- Confirm which data can be exported and how long the seller and buyer can retain it.
- Verify the new authorized administrator, separate user roles and recovery methods.
- Check that invoices, messages, payment settlement and accounting integrations reach the correct entities after cutoff.
- Keep a record of completed, open and disputed tickets at the moment control changes.
Schedule an ordinary end-of-day reconciliation under the buyer’s control. Confirm that customers can approve repairs, staff can close jobs and the buyer can see where actual cash settles. Only then has the software handoff become an operating reality.
Before your seller’s administrator signs out, ask your own manager to run the last settled day using your new credentials. Can you explain the difference between the posted repair total and the deposit that reached your bank? Can your service writer find the scanned approval you would need if a customer disputed the job? Save your answers with the report settings so you can repeat both checks after the vendor’s transition team leaves.