June 6, 2026 · Job Pilot Team

How to Set Up an Expense Approval Workflow That Your Team Will Actually Use

If your techs are spending company money with no oversight, you need a system. Here is how to implement expense tracking that works for both the field and the office.

The Receipt in the Cup Holder

Somewhere in one of your tech’s trucks right now, there is a crumpled receipt from a supply house sitting in the cup holder. It might be for a $12 box of wire nuts. It might be for a $400 water heater element. Either way, nobody in your office knows about it, it is not attached to a job, and by the time anyone sees it — if they ever do — nobody will remember what it was for.

This is the reality of expense tracking for most field service companies. Your techs are out buying parts, fuel, supplies, and the occasional emergency tool. They are spending real money on behalf of your business, and the tracking system is basically the honor system crossed with a prayer that they remember to hand in a receipt at the end of the week.

If this sounds familiar, you are not alone. And you are almost certainly losing money because of it.

Why Loose Expense Tracking Costs You More Than You Think

The obvious problem with untracked expenses is that you cannot reimburse what you cannot see. But that is actually the smallest issue. The real damage happens in three areas that most owners do not think about until tax season or a bad quarter forces them to look.

Under-Billed Jobs

When a tech buys a part on a job and does not log it, that cost does not make it onto the invoice. You eat the expense and the client gets a discount they never asked for. Over the course of a month, these untracked job expenses can add up to thousands of dollars in revenue you simply forgot to collect.

Inaccurate Job Costing

If you are trying to understand which jobs are profitable and which ones are money pits, you need accurate cost data. When half your material expenses are floating around in cup holders and back pockets, your job cost reports are fiction. You cannot make smart pricing decisions based on incomplete data.

Tax Documentation Gaps

The IRS does not care that your tech “definitely bought it for a job.” Without documented, categorized expenses tied to business activities, you are leaving legitimate deductions on the table and creating audit risk at the same time. Your accountant needs clean records. A shoebox full of faded receipts in April does not qualify.

When you do not know what your team is spending in real time, you cannot forecast cash flow accurately. You might think you had a great week based on revenue, only to discover on Friday that your techs collectively spent $3,000 on parts that have not been logged yet. Surprise expenses are the enemy of healthy cash flow.

What an Expense Approval Workflow Actually Looks Like

An expense approval workflow is simply a structured process for how money gets spent, tracked, and approved in your business. It does not have to be complicated. In fact, the simpler it is, the more likely your team will actually follow it.

Here is a framework that works for field service companies of any size.

Step 1: Capture the Receipt Immediately

The single most important habit to build is this: when a tech buys something, they photograph the receipt right then and there. Not at the end of the day. Not at the end of the week. Right now, in the parking lot of the supply house, before they start the truck.

This is the step where most systems fail because they rely on memory. Your techs are busy. They are thinking about the next job, not about filing paperwork. If your system requires them to remember to do something later, it will not happen consistently.

The solution is to make receipt capture part of the purchase itself. The tech buys a part, pulls out their phone, snaps a photo, and uploads it. Done. The receipt is now in your system, timestamped and permanent, even if the paper version ends up in the washing machine.

Step 2: Link the Expense to a Specific Job

A receipt without context is almost useless. “Home Depot - $87.43” tells you nothing about profitability. But “$87.43 in copper fittings for the Johnson bathroom remodel” tells you everything.

When your tech uploads an expense, they should be required to attach it to the job it belongs to. This accomplishes two things simultaneously. First, it feeds your job costing data so you know the true cost of every project. Second, it ensures you can bill the client for materials if your pricing model includes cost pass-through.

For general business expenses that are not tied to a specific job, like fuel for the truck or a new drill bit, you should have a general category available. But job-linked should be the default.

Step 3: Categorize with Accounting Codes

Your bookkeeper or accountant needs expenses sorted into the right buckets. Materials, tools, fuel, subcontractor payments, permits — these all hit different lines on your P&L statement and have different tax implications.

The trick here is to keep your category list short and obvious. If a tech has to scroll through 40 expense categories to find the right one, they will either pick the wrong one or stop categorizing altogether. Aim for 8 to 12 categories that cover 95 percent of what your team spends money on. You can always add more later if a specific need arises.

Good starter categories for most field service companies include:

Materials and parts
Tools and equipment
Fuel and mileage
Subcontractor costs
Permits and fees
Office supplies
Vehicle maintenance
Meals (if applicable)

Step 4: Manager Approval Before Reimbursement

This is the “approval” part of the approval workflow. Before an expense gets reimbursed or reconciled, someone with authority reviews it. This is not about distrusting your team. It is about having a second set of eyes to catch errors, verify amounts, and confirm that the expense makes sense for the job.

The approval step also creates a clear paper trail. If the IRS ever asks why you deducted $14,000 in materials last quarter, you can show that every expense was submitted by a specific person, attached to a specific job, and approved by a specific manager. That level of documentation is audit-proof.

For small teams, the owner might approve everything. For larger operations, you might delegate approval to a dispatcher or office manager for expenses under a certain threshold and only escalate larger purchases.

Common Pitfalls That Kill Adoption

Building a workflow on paper is easy. Getting your team to actually use it is the hard part. Here are the most common mistakes that turn a good system into shelfware.

Making It Too Complex

If your expense process has more than four steps, it is too complicated. Field techs are not accountants. They are in the middle of a repair, their hands might be dirty, and they have another appointment in 45 minutes. Your system needs to work in under 60 seconds on a phone screen. If it takes longer than that, compliance will crater within the first week.

Every additional field, dropdown, and required note you add to the submission form is another reason for a tech to skip it. Start with the minimum viable process — photo, job, category, amount — and add complexity only after the habit is established.

Making It Too Loose

On the flip side, if your “system” is just telling people to “try to keep their receipts,” you do not have a system. You have a suggestion. And suggestions do not survive contact with a busy Tuesday schedule.

There has to be a clear expectation: every purchase gets logged, every receipt gets photographed, and expenses that are not submitted by a specific deadline do not get reimbursed. That last part sounds harsh, but it is the single most effective policy for driving compliance. When people know that a lost receipt means money out of their own pocket, receipts stop getting lost.

Not Closing the Loop

A tech submits an expense. Then what? If they never hear back, they stop caring. The approval workflow needs to have visible status updates. Submitted. Approved. Reimbursed. When a tech can see that their $87 expense was approved and will be on their next check, they trust the system. When expenses disappear into a black hole, they stop submitting them.

Ignoring the “Why”

Your team will resist any new process unless they understand the reason behind it. “Because I said so” is not a compelling argument for adults. Take five minutes to explain that accurate expense tracking means more accurate job costing, which means better pricing, which means the company makes more money, which means better pay and job security. When people understand that the process exists to help them, not just to create more paperwork, they are far more likely to participate.

Setting Spending Thresholds

One additional layer that larger teams find helpful is pre-purchase approval thresholds. The concept is simple: techs can spend up to a certain amount on a job without asking permission, but anything above that threshold requires a phone call or a message to get approval first.

This is not about micromanaging small purchases. It is about preventing surprises. If a tech is on a job and needs a $15 coupling, they should not have to stop work and wait for approval. But if they are about to buy a $600 compressor, that is a conversation worth having before the purchase happens.

Common thresholds for field service companies are somewhere between $100 and $250 for per-purchase limits, depending on your margins and the type of work you do. The key is to set the number high enough that it does not slow down routine work but low enough that it catches significant unplanned expenses before they happen.

Getting Your Data Into Accounting Software

The final piece of the puzzle is getting your approved expenses out of your field management tool and into your accounting software. If your techs submit expenses in one system and your bookkeeper re-enters them in QuickBooks, you have just doubled the work and introduced a new opportunity for errors.

The ideal setup is a direct sync. When an expense is approved in your field management platform, it should flow into your accounting software automatically, with the correct category, amount, and job reference already attached. Your bookkeeper’s job then becomes review and reconciliation, not data entry.

This sync also eliminates the end-of-month scramble where your office manager is trying to match a stack of receipts to bank statement line items. Every transaction is already documented, categorized, and matched.

Building the Habit

Any new process takes time to become a habit. Expect the first two weeks to require reminders and follow-up. Check daily that your techs are submitting expenses. When someone forgets, do not punish them — just remind them and make it easy. “Hey, I saw you stopped at Ferguson’s today. Can you upload that receipt when you get a minute?”

After about three weeks of consistent use, the behavior starts to stick. After two months, it becomes second nature. The key is consistency from leadership. If you enforce the process for a week and then stop checking, your team will stop submitting.

How Job Pilot Handles Expense Management

If you are looking for a system that makes all of this simple enough for a tech to use between jobs, Job Pilot’s expense management was built specifically for field service teams.

Your techs can snap a photo of a receipt right from their phone and upload it in seconds. Every expense gets linked to a specific job so your job costing stays accurate and you never miss billing a client for materials. Built-in accounting codes keep your bookkeeper happy, and the manager approval workflow ensures that every dollar is reviewed before it hits the books.

Once expenses are approved, they sync directly with QuickBooks, so there is no double entry and no end-of-month reconciliation headaches. Your techs get a simple, fast process they will actually use, and your office gets clean, organized financial data without chasing down paper receipts.

Start your free trial with Job Pilot and take control of your field expenses before another receipt disappears into a cup holder.