Which source is supposed to prove which claim?
Use shop data for operating activity, the general ledger for booked financial results and settlement records for cash movement. Ask the seller for the claim in writing before choosing the verification method.
A seller may say the shop sees 400 cars per month and averages $475 per repair order. Multiplying those figures implies $190,000 monthly sales only if “cars” and “repair orders” represent the same included population. One vehicle can return several times, one visit can produce two invoices and one fleet summary can combine several vehicles. Define the unit before you challenge a difference. A discrepancy in the denominator can survive even when every dollar of revenue is recorded correctly.
Ask whether the figures cover one location, all stores, retail customers only or every line of work. Note invoice date, completion date, posting date, payment date and settlement date. A dashboard can legitimately use a different date from the month-end income statement. Use a consistent lookback period and save the extraction time so a corrected or reopened ticket can be traced later. The SMS report request checklist gives the seller a precise list of fields to produce.
How do you verify that each repair order counts once?
Build a distinct order key from the location and order identifier, then compare counts before and after every join. An invoice export may repeat its total on each labor, parts or fee line.
Start with a copy of the raw export. Identify the columns that describe one invoice, one job and one line. Summarize included sales at the line level and aggregate to one row per order. Check for blank or reused identifiers, especially where software migrated or separate stores used overlapping sequences. Match a few actual invoices to the summarized table and confirm that each printed total can be reconstructed.
Review negative tickets, reopened orders, internal repairs and warranty lines as separate groups. Ask the service writer to walk through the system’s handling of each. Tekmetric describes operating reports for its own shop system; verify the behavior of the seller’s actual system and version. If the dashboard applies an undocumented filter, keep your independently calculated count and explain the difference instead of forcing the two counts to agree.
A buyer who wants customer retention should also request stable anonymous customer or vehicle keys. Distinct orders answer the ticket-size question. Distinct customers returning over time answer a different question.
What is the right denominator for ARO?
Divide matching net sales by the included count of completed repair orders. Label paying retail ARO, fleet ARO and whole-shop ARO separately where service mix makes the differences material.
Tests for common numerator and denominator mismatches| Possible mismatch | Test | Likely consequence |
|---|
| Payroll periods compared with invoice months | Re-export both sources over the same dates | Apparent movement in labor revenue per hour |
| Tax included in ARO sales | Compare pre-tax line totals with invoice amount due | Higher ticket size than reported net revenue supports |
| Fleet statement counted as one vehicle | Trace statement to underlying repair orders | Inflated average ticket and understated volume |
| Internal and no-charge tickets excluded selectively | Run paying and all-visit definitions side by side | Misleading comparisons between shops or periods |
Look at the distribution as well as the average. A handful of engine replacements can raise ARO while most customers spend the same amount. Ask whether the hours and specialist skills supporting those large jobs will remain after closing. If the seller personally closed the work, tie the relevant order IDs to your staffing diligence.
How do you reconcile a full month to the bank?
Separate earned sales from cash received, then account for processor deductions, deposits crossing the cutoff and nonsales cash flows. Use dates and references that an independent reviewer can follow.
Illustrative composite — not a real client. Suppose the export contains 240 paying orders with $120,000 net repair sales. ARO is $500. Add $5,400 tax billed, subtract $16,000 of new unpaid fleet invoices and add $9,500 collected on older invoices. Expected customer receipts are $118,900. If $2,200 of card fees are withheld and $3,100 settles after month-end, while $1,400 from the prior month settles now, expected matching bank deposits are $115,000.
Assume the bank activity you initially marked as sales totals $118,000. A $3,000 owner cash transfer into the business account could explain the gap if its source and accounting entry confirm it. Exclude the transfer from customer receipts and retain the source evidence. The tax return does not become more reliable simply because bank deposits are larger. Use the Repair Order to Bank Bridge and track all unresolved differences with your accountant.
How does the annual tax return fit into the test?
Reconcile the ledger’s annual revenue to the relevant filed return and ask your CPA to explain reporting differences. The return supports a broader financial check, while your invoice and cash tests support more granular operating claims.
Identify the tax entity, fiscal year and accounting basis. A return can include more than one shop or other activities. The buyer may be acquiring only one location or a subset of assets. Ask for a location bridge using consistent account codes and source records. If the books are accrual basis and the return uses cash basis, timing differences can be legitimate. Have your accountant specify the adjustment rather than accepting an unexplained “tax difference.”
IRS Publication 583 describes the role of underlying records. Test that reported sales are supported by invoices, cash records and bank activity appropriate to the business. Do not add unreported or undocumented revenue to a price just because someone describes the shop as cash heavy. Ask what compliant records support the claim and how they reconcile with filed reporting. Unresolved assertions belong in the exceptions log, outside your verified base case.
Which samples deserve more attention than a random ticket?
Select ordinary, high-value and unusual transactions so your review tests both normal volume and exceptions that can change the result. A sample of easy retail card payments may miss the very fleet or warranty issues driving value.
- Pick one ordinary retail order. Trace estimate, customer authorization, closed invoice, payment and processor settlement through the ledger.
- Pick one large specialty job. Review labor, sublet, parts and warranty exposure, then identify the person and equipment needed to repeat it.
- Pick a fleet invoice that crosses month-end. Match the individual vehicle work, approved rates, aging and eventual receipt.
- Pick a void, refund or comeback. Find the original transaction and confirm which period carries the adjustment, whether sales tax changed and what happens to the order count.
- Pick a ticket issued close to a cutoff or migration. Verify whether posting or reopening changed a historical report after you first received it.
Review customer-level records only through authorized access and preserve confidentiality. The FTC’s information-protection guidance supports limiting personal detail to people who need it. State rules vary; California BAR’s guidance illustrates the authorization and invoice records that may exist within an underlying repair file.
What should you do with a residual discrepancy?
Quantify its magnitude, recurrence and possible effect on your purchase. A one-day settlement timing issue differs from recurring revenue that your team cannot tie to either invoices or receipts.
Assemble the seller’s explanation and the evidence supporting it. If the reconciliation works for one month, repeat it for another period with different fleet, holiday or seasonal activity. If the same unresolved amount recurs, check whether the mapping excludes a channel or duplicates a transfer. If the seller cannot support the amount, rebuild earnings without it and discuss the implications with counsel and the lender before closing.
Run the shop earnings builder with your verified count, ARO and margins. Reconcile its implied revenue against the actual source period. The buying hub addresses the surrounding staffing, equipment and financing checks. Keep the raw files, adjusted analysis, date, reviewer and unresolved exceptions together so another lender analyst or partner can reproduce your conclusion.
How do you test that repeat visits really belong to the same business?
Check whether the customer and vehicle keys are stable and whether the file includes another location, a predecessor owner or a migrated system. A clean-looking trend can combine unlike populations if the identifiers or location boundaries changed.
Choose a small set of returning records and ask the seller to verify the linkage under the agreed access process. One household may bring several vehicles. A fleet account can contain many drivers and many vehicles under one billing key. A vehicle that changes owners may remain under its original record. Each of those cases requires a stated definition before you use repeat rates to support a premium.
Run a sensitivity with retail customers only, leaving fleet recurrence in its own account analysis. Report the denominator, lookback window and number of records you excluded for missing keys. If anonymization changed between exports, ask for a consistent replacement file and keep the previous version for audit. The user reading your diligence memo should be able to repeat the match without needing to know individual customer names.
Can the team retain historical production? Map the verified hours to staff and owner roles in the technician roster. Historical invoices alone cannot establish future capacity.
How should disputed income affect financing? Run the DSCR calculator with the lower supported earnings case and ask the lender to apply its actual underwriting treatment before you decide what to offer.