Is Tekmetric a parts reconciliation tool?

Not in the accounts-payable sense. Tekmetric's accounting integration reconciles your parts activity into QuickBooks at the total and category level, and you validate the batch before you send it. That's accounting reconciliation — making the books agree with the ticket. It is not a line-level audit of each vendor invoice against the order and the packing slip, which is the three-way match that catches an overbill or a missing credit. Tekmetric is the system of record. A reconciliation layer audits the money flowing through it.

How does Tekmetric handle core charges?

Tekmetric tracks core charges and part returns natively. You can add a core to a part, mark it returned, and see the status on the RO, and it does this well. The gap isn't tracking — it's recovery. Tekmetric records the core charge you paid, but it has no view of the vendor credit memo that's supposed to refund it, because that credit lands on a vendor statement, not in Tekmetric. So a core can show as a charge on the ticket and still never come back as cash, and the system of record won't tell you, because the missing half of the deal lives at the parts house.

Can Tekmetric catch a vendor overbilling me on parts?

No, and that's not a knock on Tekmetric — it's a question of what data it holds. Tekmetric captures what you sold and what cost you keyed in. It never receives the vendor invoice, so it has nothing to compare against. If a supplier quotes a part at $84 and bills $97 three days later, Tekmetric shows whatever cost got entered. Catching that $13 means matching the order, the packing slip, and the invoice line by line — a layer that sits between your SMS, your vendors, and QuickBooks.

Why does my Tekmetric parts margin report look healthy when I'm still losing money?

Because reports are downstream of data entry. Tekmetric calculates margin off the cost keyed into the part line. If that cost is understated because an overbill inflated your real landed cost, or the matrix overstates the sell, or a core charge posted and the credit never came back, the report is mathematically correct and economically wrong. A healthy margin means the math on the entered numbers is right. It says nothing about whether the entered numbers match what actually happened at the parts counter.

Does WickedFile replace Tekmetric?

No. WickedFile doesn't run your shop, write ROs, schedule, or dispatch — it does nothing Tekmetric does, and it doesn't replace QuickBooks either. It's the reconciliation layer between your SMS, your vendor invoices, and your accounting. It reads the vendor invoices and credits Tekmetric never sees, audits them against the activity Tekmetric records, and flags the gaps. Tekmetric runs the shop. WickedFile audits the money. You keep both, because they do different jobs.

Does Tekmetric Catch Parts Margin Leaks?

Q: Does Tekmetric catch parts margin leaks?

Tekmetric catches the leaks that live in the data you keyed into it — a low matrix gross profit, a discounted line, a core marked unreturned on the RO. Read the reports and they're right there. What it can't catch is a leak that lives off the ticket: a vendor invoice that overbilled you, a core charge you paid but never recovered, a credit that never posted. The vendor invoice never enters Tekmetric, so Tekmetric has nothing to audit it against. It reports your margin to the decimal, and the decimal can still be wrong.

If your Tekmetric parts margin report has ever looked healthy while your bank account quietly disagreed, congratulations — you’ve met the most polite liar in your back office. (It isn’t lying, exactly. It’s reporting the truth about numbers that weren’t.) If you run on Tekmetric and have never reconciled your vendor invoices against your repair orders, there’s a good chance somewhere between $8,000 and $40,000 a year is leaking out of your parts margin, and your reports show none of it.

That’s not a flaw in Tekmetric. It’s the difference between a system of record and an audit.

This post is for the owner or multi-location operator already running Tekmetric. Not to talk you out of it. To draw a clean line around what the system of record can and can’t see on parts, and to show where a reconciliation layer earns its keep on top of it.

Read it in six minutes. Audit it on your own Tekmetric data this week.

What Tekmetric Does Well

Let’s be honest about the tool first, because the whole argument depends on respecting what it’s good at.

Tekmetric is one of the better shop management systems on the market. On parts specifically, it does things a lot of owners don’t realize they’re getting.

It tracks core charges and part returns natively. You attach a core to a part, mark it returned, and see the status on the RO. That’s more discipline than the clipboard-and-core-bin system most shops actually run.

It gives you parts purchasing and inventory reporting that rolls up what you bought, from whom, and at what cost. Its parts inventory management tracks stock in real time, pulls part-usage and per-job cost data from completed ROs, and shows it across locations.

And its labor and parts matrix engine is genuinely good — it keeps pricing consistent and margins protected by applying your markup automatically, so your counter staff aren’t pricing parts off gut feel.

Put it together and Tekmetric reports your parts gross profit cleanly, by job, by advisor, by period. If you read the reports, you’ll see the low-margin ticket. The reporting is not the problem. The reporting is very good.

Reconciliation Means Two Different Things

Here’s where the word “reconciliation” needs care, because it means two things, and Tekmetric does one of them well.

Tekmetric reconciles your parts activity into your accounting. At close, you review the batch, validate it before you send, and the totals flow to QuickBooks. That’s a real, useful step, and validate-before-send is the right design. It keeps your books in agreement with your tickets.

But notice what that’s doing. It’s reconciling totals — the sum of parts activity recorded in Tekmetric against the entries posted in QuickBooks. It assumes the data already keyed into Tekmetric is correct. It makes the books match the tickets. It does not make the tickets match the parts house.

That distinction is the entire post. Accounting reconciliation answers “do my books agree with my system of record?” An accounts-payable audit answers a different question: “does my system of record agree with what the vendor actually charged me?” Tekmetric was built to nail the first. The second needs data Tekmetric doesn’t hold.

This is the part I’ll say plainly, because it’s the one opinion worth taking away: accounting software doesn’t verify reality — it records what gets entered. Tekmetric is no exception. It faithfully reports the number you fed it. It has no way of knowing the number was wrong before it arrived.

Garbage In Still Reports Clean

Every report Tekmetric produces is downstream of what got keyed in. That’s true of every system of record ever built. A wrong number goes in, a clean report comes out — mathematically correct, economically false.

Let’s do the math, and label all of it illustrative. These are “say you do this volume” figures, not your actuals.

Say you run a busy three-bay shop doing $520,000 in parts purchases a year. Now layer on two things that never touch a Tekmetric report:

Vendor overbilling at a conservative 1.5% of parts spend. Manual invoice processing runs roughly a 2% error rate, so this is defensible. That’s $7,800 in inflated cost — paid, posted, invisible.
Core charge walkaway. Say you do 50 core-eligible jobs a month at a 20% non-recovery rate and an average $70 core. That’s $700 a month, or $8,400 a year, in deposits you paid and never got back.

Add the two pieces Tekmetric structurally cannot see — the overbill and the unreturned cores — and you’re at $16,200 a year, gone before markup, on a single shop. And here’s the part that stings: your Tekmetric parts margin report for that year will look fine. The arithmetic on the entered numbers is correct. The entered numbers just didn’t match reality.

That’s the gap. Not Tekmetric reporting badly. Tekmetric reporting faithfully on data that was already wrong.

What Tekmetric Sees, and What It Misses

Walk through the common parts leaks and it gets clear fast. Some Tekmetric handles. Some it can’t, by design.

Unreturned core charges

This is the one Tekmetric gets the most credit for and still can’t fully close. It tracks the core beautifully — charge on the RO, return status, the whole flow. What it sees: that you charged a core and whether someone marked it returned. What it misses: whether the vendor actually issued the credit and whether that credit matched the charge. The refund lives on a vendor statement or credit memo, outside Tekmetric entirely. So a core can sit on the RO marked returned and still never come back as cash — past the return window, worth nothing — and the system of record will swear everything’s fine. (Cores don’t come back on their own. They’re not homing pigeons.) Full breakdown in our core charges and profit leakage guide, and the related trap of returns marked but never credited in the return-and-forget loophole.

Vendor overbilling

A supplier quotes one price and bills another. What it sees: nothing — the vendor invoice never enters Tekmetric, so there’s nothing to compare the entered cost against. What it misses: the entire discrepancy. The invoice is the truth, and the invoice isn’t in your SMS. That’s the heart of vendor overbilling in auto repair.

Wrong matrix selection

A dealer-sourced part gets billed on the standard matrix instead of the dealer matrix. What it sees: this one it actually can surface — a low gross-profit line shows up if you read the reports, and the matrix engine is built to prevent it in the first place. What it misses: it doesn’t know the cost was right, only that the markup math ran. If the underlying cost was inflated by an overbill, the matrix dutifully marks up a wrong number. See dealer vs. standard vs. list matrix for which part belongs on which.

Service advisor discounting

An advisor knocks a line down to save a sale. What it sees: the discount, clearly, by advisor — this is a real Tekmetric strength, and the reporting hands you the pattern if you look. What it misses: nothing structural. This is the leak the system of record handles well, and the fix is management, not reconciliation. Our service advisor discounting and parts gross profit breakdown covers the coaching side.

The pattern holds: when the proof lives on the ticket, Tekmetric catches it. When the proof lives in a document Tekmetric never receives — the vendor invoice, the credit memo, the core refund — it can’t, and no SMS can.

Why a Missing Credit Is Worse Than a Missing Return

A return slip says a part went back. A credit memo says you got paid for it. Those are not the same thing, and the difference is where the money hides.

One transmission franchise started reconciling its vendor statements and found something nobody expected. An employee at one of their parts vendors had been intentionally withholding credits to dress up his own department’s numbers. Thousands of dollars in credits the shop was owed simply never posted. The owner was furious — he had “Stop the Steal” signs hung around his own shop, because he was so focused on preventing employee theft. The money was leaking somewhere he never thought to look.

The lesson wasn’t that vendors are dishonest. Good vendors make mistakes too. The lesson was that every dollar should be verified no matter where it comes from — and that a return marked complete in your SMS proves nothing about whether the credit actually arrived. Tekmetric will show that core as returned. It cannot show you the credit that never came.

Where a Reconciliation Layer Fits on Top

Here’s the clean division of labor: Tekmetric runs the shop. WickedFile audits the money.

WickedFile reads the documents Tekmetric never sees — the vendor invoices, the credit memos, the core refunds, the bank and card feeds — and reconciles them against the parts activity Tekmetric records and the entries that hit QuickBooks. When the invoice says $97 and your RO was built on $84, it flags the $13. When a core charge posted but no credit ever came back, it flags the open deposit. When the cost keyed to the RO doesn’t match the vendor invoice, it surfaces the real landed cost. It’s the three-way match — order, receipt, invoice — that no SMS runs on parts, explained plainly in what parts reconciliation is and why it’s critical. It’s not just us saying so: CPA Hunt Demarest and WickedFile’s Alex Saladna break down the parts-reconciliation gap costing shops six figures — the same blind spot, from an accountant’s chair.

Now the honest limits, because credibility is the whole game. WickedFile does not process payments. It does not issue corporate cards. It does not do accounts receivable or invoicing. It does not replace Tekmetric, and it does not replace QuickBooks. It finds the money. A human still moves it — you or your AP person calls the rep, requests the credit, short-pays the disputed line, and confirms it posts. WickedFile is the reconciliation layer between your SMS, your vendors, and your books. Nothing more, and nothing Tekmetric already does.

At Eleven Locations, a Rounding Error Becomes a Budget Line

A $15 missed core is a rounding error at one shop. It’s a budget line at eleven.

That’s the whole multi-location case. Take the illustrative single-shop figure above — call the structurally invisible piece roughly $16,000 a year — and across a group it doesn’t add, it compounds. Every location runs its own counter habits, its own mix of parts houses, its own matrix discipline. One store’s parts driver is religious about cores; another’s bin overflows. One advisor discounts to hit a number; another never touches the matrix. The leaks differ store to store, which is exactly why they’re hard to see from the group level. There’s no single pattern, just a hundred small ones.

Tekmetric gives you clean per-location reporting. What it can’t give you is a group-wide audit of the vendor dollars flowing through eleven separate Tekmetric instances, because none of those instances hold the vendor invoices. A reconciliation layer that sits across all of them turns a hundred small, store-specific leaks into one regional report you can act on before it costs you a quarter. For a ten-location group, the structurally invisible piece alone is six figures — and it never once showed up red on a Tekmetric screen.

How to Audit This on Your Own Tekmetric Data This Week

You don’t need software to find out whether this is real in your shop. You need an afternoon and your existing Tekmetric reports.

[ ] Pull the parts purchasing report for the last 90 days for your top two or three parts houses plus your dealer counters.
[ ] Pull the matching vendor invoices for that same window from each of those vendors — statements or the vendor portal.
[ ] Spot-check 25 part lines: does the invoice unit price match the cost that posted to the RO in Tekmetric? Flag anything over a $12 or 5% gap.
[ ] Pull every core charge from the period and check each against a vendor credit memo. No matching credit means an open core. Total those.
[ ] Review the advisor discount and matrix gross-profit reports — Tekmetric hands you these, so use them. This is the leak it does show.
[ ] Total the flagged dollars and multiply by four for an annualized number. At a group, run it at your two highest-volume stores and extrapolate.

If that number is small, your reconciliation is already tight and Tekmetric plus discipline is doing the job. Good — you don’t need us. If it’s four or five figures, you’ve found the gap between what your system of record reports and what actually happened at the parts counter. That’s the gap a reconciliation layer is built to close, and it’s worth booking a demo to see it run against your own invoices.

Running a different system? The same structural gap shows up in Mitchell 1, too.

Tekmetric tells you your parts margin to the decimal. Make sure the decimal is true.