Employee Expense Tracking: A Practical Business Guide

Set the policy and roles before collecting claims. Give each report an ID and require date, purpose, amount and private evidence references. Review duplicates and company-paid items, then record the accepted amount separately from the request. Subtract any advance before settlement and preserve negative balances. Reconcile the final payment to the approved report; a submitted or approved claim is not proof of payment.

Set an employee expense tracking policy

Decide what the business needs to see before it can review a claim. Name the person who submits, the reviewer and the person who pays. State how the process handles missing sources, late items and costs paid directly by the business. A template can record those decisions but cannot create the policy by itself.

Keep the request simple enough that employees can supply a complete record. Date, supplier, business purpose, amount and receipt reference form the line detail. The header identifies the claimant, report ID, period and department or project. Ask only for information needed for the task; bank logins and full card details do not belong here.

Separate policy eligibility from tax treatment. A repayment decision can follow the employer's process while a separate tax question still needs review. Avoid writing “deductible” beside every approved line. Approval describes the business's decision, not a universal tax conclusion.

Capture claims and source documents

Use one stable report ID across the claim, receipt index and settlement record. Put it on every line included in the report. A filename alone can change during review, so it should not be the only connection between the evidence and the amount requested.

Keep the claimed amount intact. The reviewer enters the approved amount in another field. If only part is accepted, both figures remain visible with the reason. Overwriting the request erases the distinction between what the employee asked for and what the business decided.

Store receipts privately and use source IDs in the report. Check that intended reviewers can open the documents. A public link can make access easier while exposing private details, so it is not a sound default. Review the permissions of the storage folder as well as the report.

Choose the right report record

The pack's Expense Report tab holds the line details and approval fields. Claim Balance selects a report ID, totals the approved lines and subtracts an entered advance. Word and PDF forms use manual totals. Sheets use begins with a private import of the XLSX, followed by formula and sharing checks.

A status field is a record of the process. It does not verify identity or provide a full audit system. If the business requires stronger controls, choose a workflow that supplies them rather than relying on a typed status or a hidden formula cell.

Review duplicate and company-paid items

Compare report lines to the actual source events. Similar dates and amounts may indicate a duplicate, but they can also be separate purchases. Check supplier, purpose, receipt ID and payment account before deciding. Preserve the reason for a correction so the claimant can understand it.

Look for a cost already paid on a company card. It may belong in the trip review without increasing the amount owed to the employee. Make that distinction visible. A report total that repays every listed cost can overpay when some items were never funded personally.

The original purchase, an employee claim and a later payment are connected records. They are not automatically three operating expenses. Link them by source and report ID, and keep the accounting process clear about which event has already been recorded as the cost.

Handle missing evidence and partial approval

Return the specific line for the missing information. Say whether the problem is purpose, amount, date or source. A broad “rejected” status can conceal what the employee needs to fix. The form should leave enough room for a short question and response reference.

If the business permits an exception, record who decided and why under the actual policy. Do not invent a receipt ID to make the spreadsheet appear complete. The missing document and the approval exception are two facts that can both remain visible.

For partial approval, retain the original requested amount. Add the accepted amount separately. Check the report total after any change. A document total may not update on its own; a spreadsheet total may exclude the line until its status meets the formula criteria.

Calculate the amount left to settle

The fictional example has approved lines of 80 and 100. Approved total is 180. The employee already received an advance of 200. The balance is 180 - 200 = -20, meaning 20 should return to the business under the settlement process.

A negative balance is useful information. Do not clamp it to zero and lose the outstanding return. Likewise, an unknown advance is not a confirmed zero advance. Check the earlier payment record before presenting a final amount due.

When no advance was paid, enter a confirmed zero. Then the approved amount is the amount left to settle, subject to any other documented adjustments in the business's process. Keep those adjustments traceable rather than inserting an unexplained balancing line.

Record reimbursement after payment

Mark payment only after it happens. Keep date, amount and payment reference linked to the report. Approval may occur on one date and settlement on another. Preserving both makes an unpaid approved claim visible instead of suggesting that a status field moved the money.

Check the payment amount against the approved balance. If a payment covers several reports, retain the list of included report IDs and amounts. If one report settles through several payments, keep that allocation clear. A later reviewer should not have to infer it from similar totals.

Avoid asking employees to put payment credentials into a shared workbook. Use the established controlled payment process. The report can hold a settlement reference without carrying sensitive account details into every copy sent for review.

Export and reconcile paid claims

Choose the reporting period according to the question. Claim dates, approval dates and payment dates can differ. State which one the report uses rather than assuming all three fall in the same month. Keep the original event dates in the source detail.

Match the approved report, payment record and underlying purchase. Check that the cost was not added again when the settlement appeared in a bank import. Keep unresolved differences with an owner and next action. A total that adds correctly can still include a duplicate event.

Save a reviewed period copy and the source index. A CSV export transfers selected rows without the workbook's formulas or protection. Open the export and compare report IDs, amounts and dates before passing it to another process. Preserve the evidence of the original approval separately.

Decide when a shared file needs replacement

A file may be enough when claims have clear ownership and limited access needs. It may be a poor fit when each claimant must see only their own records, several approvers need controlled routing or the business requires stronger audit evidence. Filtering and hiding rows do not create privacy boundaries.

List the exact requirement before comparing software. Receipt capture, approval rules, card matching and reimbursement are separate functions with plan limits. Check vendor documentation for the intended region and workflow. Do not assume a receipt-scanning feature supplies the whole claim and payment process.

Use a fictional or copied sample for a trial migration. Check both a normal claim and an exception, including a negative advance balance. Inspect the export so you know what can be recovered if the tool no longer fits. Keep the original reviewed records available until the transfer is checked.

Walk one report through the whole process

Start with a fictional report ID, such as REP001. Add two costs with their own source IDs. Keep the amount requested in the claim field. Ask the reviewer to enter the accepted amount and status in the separate approval fields. Check which lines enter the selected total.

Add a company-paid cost as a review case. It needs a clear payer record so it does not become money owed to the employee. Keep its source in the trip evidence if it belongs there. The person who reviews the report should be able to explain why it is included in one view but excluded from repayment.

Then add an advance. Use the actual known amount in a live report, or a clearly fictional amount in a check copy. Read the result with its sign. The return case matters as much as the usual positive payment case.

Make the payment handoff clear

The person making payment needs the reviewed report ID and final amount. They do not need to recreate the review from a pile of receipts or guess which edited copy is current. Keep the approval source and payment instruction connected through the business's controlled process.

After settlement, add the reference and date. If money is returned instead, keep the return reference. Do not use a generic Paid status to conceal which direction the money moved. An audit trail should make the event easier to read, not force the next person to infer it.

If settlement combines several reports, list the included IDs and amounts. Check that the sum matches the payment. If one report settles in parts, keep the remaining balance visible. A similar grand total is not enough to prove the reports were settled correctly.

Limit access during review

Check which copies exist. A claim may be sent as a document, saved in a shared folder and entered into a workbook. Keep the intended reviewers clear in each place. Do not make a receipt public merely because one reviewer cannot open it.

Use a fictional example to report a workbook fault. Live claims can reveal private purchases, travel and employee details. The formula and a few made-up inputs usually explain an error without sending the whole report outside the normal review process.

Keep a review copy when the report closes. State the report ID and date in its name or cover record. If a late change affects the approved amount, keep the earlier decision and obtain the review your process requires for the new version. A later edit should not silently inherit an earlier approval.

FAQ: employee claims

Is a submitted claim already an expense to repay?

A submitted claim is a request for review. The business still needs to check its evidence, policy and payment source. Keep the requested amount separate from approval. A company-paid cost may belong in the report without creating money owed to the employee. The form records these distinctions rather than deciding them automatically.

How do I avoid duplicate reimbursement?

Use stable report and source IDs, then compare the underlying purchase and payment account. Check previous reports and company-paid items before settlement. Similar amounts are a warning to inspect, not proof of duplication. Keep the final payment reference connected to the approved report so a later reviewer can see what was settled.

What if the advance is larger than approval?

Keep the negative balance. Approved amounts minus the advance show a return amount when the advance is larger. The fictional 180 approval against a 200 advance leaves minus 20. Follow the business's return process and retain its reference. Do not hide the outstanding return by forcing the calculation to zero.

Can a filter keep each employee's claims private?

No. A filter changes what is visible at the moment, not the file's access rights. Someone allowed to open the workbook may be able to see other rows. Use separate controlled files or a suitable system when claimants should not see one another's information. Review receipt-folder permissions too.

Does the template provide verified approval signatures?

No. It records names, statuses and decisions entered through the business's process. Typed fields and sheet protection are not a complete identity or audit system. If policy requires verified signatures or controlled routing, use a workflow that meets those requirements. Keep evidence of the actual decision rather than overstating what the file supplies.

Sources and checks

Checked 15 October 2026. The examples are fictional and the arithmetic is original.

• IRS records: Business recordkeeping and supporting documents.

Related records and guides

• how to keep track of business expenses
• how to make an expense spreadsheet

Verdict on employee expense tracking

Employee expense tracking works when a claim remains traceable through review and settlement. Keep requests, approvals, advances and payments distinct. Resolve the source and payer before deciding what the employee is owed.