Which reports should you pull first?
Start with closed repair orders at invoice and line level, a payment export and a technician-hours report for the same location and period. Request a field key where the system uses short codes or labels whose meaning changed during a migration.
A monthly summary may tell you that average repair order increased while car count fell. Ask how the software counted a second invoice for the same vehicle, a warranty return after the original ticket closed and a multi-vehicle fleet invoice. Each affects the denominator differently. Write down whether a vehicle can appear more than once per visit and whether the dashboard uses an order, a vehicle or a customer as its unit.
When you export line items, carry the original ticket ID into every row. A job containing labor, parts and shop fees can produce several rows that all belong to one invoice. Count distinct included tickets when calculating average ticket size. Count line rows only when the question concerns line items.
Which definitions belong on the report request?
The first section, Set the export definitions, gives you these prompts and room to document your evidence.
- Choose the revenue date. Use invoice-close or posting date consistently and record the location, time zone, reporting period and whether tax and shop fees are included.
- Count tickets and cars. Export closed order IDs and anonymized vehicle IDs. Split sublets, inspections, zero-dollar returns and reopened tickets before interpreting car count.
- Calculate ARO. Divide comparable net repair sales by included orders. Run the figure again without fleet work and explain the tickets removed.
- Separate labor and parts. Pull sold hours, gross labor dollars, parts sales, credits and parts cost. Note discounts and whether technician wages are posted to cost of sales.
SMS report request checklist preview| Section | Topics covered |
|---|
| Set the export definitions | Choose the revenue date · Count tickets and cars · Calculate ARO · Separate labor and parts |
| Reconcile and reproduce | Trace tech hours · Identify warranty returns · Bridge to the books · Deliver reusable files |
|---|
How do you avoid mixing booked sales and cash?
Use invoice dates to measure earned repair sales under your chosen accounting basis and payment data to examine cash collection. Document the bridge between them rather than treating a difference as an error by default.
If you’re selling, preserve the reports in their raw format along with a screenshot of filters, date fields and location selections. Create a different working copy for redaction and reconciliation. If you’re buying, ask for an export that covers the weeks around your sample so you can match unusually large deposits or fleet receipts that straddle month-end.
Sort refund and credit rows separately. Some systems reverse part of an invoice and leave the original order count unchanged. Others create a negative ticket. Work through one actual example with the service writer, then document how you handled similar rows. Ask whether the accounting export books tax, supplies and sublets to different ledger accounts.
Why can a simple ARO calculation change?
Illustrative composite — not a real client.
Suppose an export contains $60,000 of included repair sales and 200 closed orders. Using those definitions gives $300 per order. Now suppose 20 of those orders are zero-dollar warranty visits and the question concerns paying repair orders. The same $60,000 divided by 180 paying orders yields about $333.33. Both calculations can be reproduced. Use the definition that matches the question and disclose the excluded visits; the warranty work still used technician capacity.
What exactly do you ask the service manager to export?
Sit with the person who normally closes repair orders. Ask them to show the difference between the appointment date, date opened, invoice date, close date and payment date on one completed job. Vendors and shops can use different names for the same event. Under Choose the revenue date, write the actual field label used in this installation, the first and last included dates and whether the report includes reopened orders. Save a picture of the filter settings alongside the export. Someone with ordinary reporting access should be able to repeat the pull when another month closes.
Request a row-level export with the order ID, store ID where applicable, status, selected reporting date and the sales components you intend to compare. If a report contains line-level labor and parts, ask how many rows one ticket can create. A vehicle description may help the service manager verify a sample internally. A buyer who is reviewing monthly totals can generally use stable anonymous identifiers. Have the shop keep its crosswalk to customer names and vehicle information under its own access controls. Record the person authorized to answer exceptions in the checklist’s Owner field.
How can one ticket change the numerator and denominator together?
Illustrative composite — not a real client. Suppose your June export shows 200 completed customer-pay orders and $126,000 of sales before tax on those orders. The average repair order is $630 under that definition. If one $2,100 fleet order was inadvertently joined to three individual payment records, an expanded detail file can show the same total three times. Adding all rows gives $130,200, and counting rows gives 202. Both figures are wrong for the stated definition. Return to the original order ID, inspect how the detail was joined, and reproduce the original 200 orders and $126,000 before you interpret any average.
Now consider a June 30 invoice paid by a fleet office on July 19. The shop might include the sale in its June closed-order report and the cash in its July receipts. Write both dates in the reconciliation note and keep the accounts receivable posting as the link. If the invoice was voided and reissued in July, ask for both transaction references and find how the software handles their original dates. Moving a deposit into June simply to make the reports agree obscures the reason for the difference and can distort the next month’s check.
How do you verify labor and parts before using the sales mix?
Pick a repair order that includes technician labor, installed parts, shop supplies and an outside alignment. Print the internal invoice detail and trace each component to the relevant export column. A shop can group the alignment under a sublet category while another report includes it in a broader sales total. On Separate labor and parts, write where that shop’s export puts the amount and how you handle it in your analysis. Keep the tax calculation outside your defined pretax sales numerator. Identify a discount separately if it is applied to the entire invoice rather than to one line.
For Trace tech hours, compare a specific billed operation with the technician’s job clock. If two technicians worked on it, learn whether both the operation and the billed hours get repeated when the report is grouped by technician. Ask how rounding, unassigned hours and work stopped overnight are shown. You can accept different totals from reports designed to answer different questions when you can explain each difference. A manager who needs a weekly staffing view may need a different grouping from the accountant reconciling closed orders to monthly labor sales.
How do you test the package on someone who did not create it?
Give a second authorized reviewer the exported files, saved filter settings, field definitions and the date the files were generated. Ask that person to regenerate one week of closed orders, calculate its average repair order and trace two invoices into the general ledger. Have them explain any differences without asking the original operator to recreate their steps from memory. If the reviewer picks a different date field, revise the instruction with the exact on-screen label and rerun the week before requesting a longer history.
Keep one version as originally exported and a separate working file that records exclusions or mapping adjustments. Note a reporting-system conversion, location merger or price-book change at the first affected period. Under Evidence or next action, record the reconciled period, the amount still unexplained, the person checking it and a date for their response. This gives a buyer, finance reviewer or incoming manager a reproducible answer when the next question concerns gross profit, missing technician hours or why a reported deposit arrived the following month.
What makes an export reproducible for the next reviewer?
Ask your reviewer to trace technician hours, warranty returns and booked sales from a saved export into the supporting records.
- Trace tech hours. Export technician ID, sold hours, job-clock hours and attendance hours by pay period. Confirm how shared tickets and owner hours are split.
- Identify warranty returns. Use linked original order, reason code, uncompensated hours and parts cost. Review ambiguous callbacks with your service writer.
- Bridge to the books. Reconcile invoiced net sales by month to GL revenue. Explain timing, cash receipts, fleet receivables, refunds, sales tax and merchant deductions separately.
- Deliver reusable files. Save the raw export, field definitions, filter screenshot and extraction date. Keep customer details out of the working copy shared for preliminary review.
What should the final report package contain?
Give the reviewer raw files, definitions, filter settings and a reconciliation with unresolved differences. Your reviewer should be able to regenerate the same numbers even if the dashboard labels change.
Try your reconciled car count and average repair order in the shop earnings builder. Use the technician roster for the separate task of comparing job hours, paid attendance and billed production. Avoid dividing revenue from a fleet-heavy period by technician hours from a pay period with different dates.
Keep the export owner and creation timestamp in the file description. Mark whether an export changes if a closed invoice is reopened. Where you have two versions of a reporting period, explain why both exist and which one supports the transaction materials. A few lines of context can save both sides from repeating days of reconciliation.