To record employee expense reimbursements, code each item on the employee's expense report to its own expense account, then match the bank payment that repaid the employee against those items. The payment itself is not an expense category. Keep the receipts, the approval and the report together so every reimbursement line in the books has its support attached.
Why code the expense rather than the reimbursement payment?
The reimbursement payment is only the settlement. The business costs happened earlier, when the employee bought the train ticket or paid for a client lunch. Coding the bank line to one account, such as "Employee reimbursements," hides what the money was spent on and lumps travel, meals and equipment together on the profit and loss.
A single reimbursement account causes three practical problems:
- Reports lose detail. Travel or meals totals for the year are understated by everything that went through reimbursements.
- Tax treatment blurs. Meals and travel can be treated differently from supplies at tax time, and the CPA has to pull every expense report apart to find them.
- Equipment hides in expenses. A monitor or laptop bought by an employee may belong on the balance sheet, not in a catch-all expense line.
The fix is to code from the expense report, item by item, and use the bank line only to prove payment.
What paperwork should back each employee reimbursement?
Each reimbursement needs three things: a receipt for every item, an expense report listing the items with their business purpose, and an approval from someone other than the employee. Together they show the cost was real, was for the business and was authorized. Without them the books record a payment with no evidence behind it.
There is also a tax reason to keep the paperwork tight. The IRS describes an "accountable plan" in Publication 463 on travel, gift and car expenses: expenses must have a business connection, the employee must adequately account for them within a reasonable period, and any excess reimbursement must be returned within a reasonable period. When those rules are met, the publication says the employer should not include the reimbursements in the employee's wages on Form W-2. Publication 463 also gives safe-harbor time limits, such as accounting for expenses within 60 days after they were paid or incurred and returning any excess within 120 days.
Mileage and other claims without a receipt
Some claims have no receipt by nature. An employee who drives a personal car for work is usually repaid at a set rate per mile, so the support is a mileage log instead: the date, the start and end points, the business purpose and the miles driven. Code the total to a vehicle or travel account, never to fuel, because the business did not buy the fuel. Fixed allowances paid without any accounting from the employee deserve a question to the CPA before you code them, since they may not meet the accountable plan rules.
Whether a client's arrangement qualifies is a question for the client and the CPA. The bookkeeper's part is practical: file each report with its receipts and approval, note the date it was submitted, and flag reports that arrive months late or cover items with no receipt.
A worked employee expense report paid from the bank
A worked expense report shows how the items and the payment connect. The example below uses made-up figures for a fictional employee, paid back by bank transfer.
| Item | Amount | Account |
|---|---|---|
| Train ticket to client site | 300.20 | Travel |
| Lunch with client, purpose noted | 86.40 | Meals |
| Parking at client site | 24.00 | Travel |
| Project management software, one month | 54.00 | Software subscriptions |
| Monitor for home office | 147.80 | Office equipment or supplies, per policy |
| Report total | 612.40 |
Two steps produce the entries.
When the report is approved, record a bill or journal entry: debit each expense account for its item and credit an "Employee reimbursements payable" liability for 612.40. Use the approval date, or the dates of the items if the client wants expenses in the month they happened.
When the bank pays the employee, the bank statement shows a transfer of 612.40 to the employee. Code it as a debit to reimbursements payable and a credit to checking. The liability returns to zero.
Small clients often skip the payable and code the bank line straight to the five accounts as a split transaction. That works when the payment follows the report within the same month. The liability step earns its keep when reports and payments cross month end or when several reports are paid together.
Two items that need a second look
The software line belongs with the client's other subscriptions. If the employee keeps paying for it every month, it is better moved to a company card. The guide to categorizing software subscriptions covers how to group those charges so they are easy to review.
The monitor raises the capitalization question. Whether a purchase goes to an asset or an expense depends on the client's written policy and the amount. The post on whether to capitalize or expense a purchase walks through that choice.
Reimbursement payments that bundle reports or run through payroll
One reimbursement payment often covers more than one expense report. An employee who submits weekly reports may be paid once a month, and a business with several employees may pay everyone's reimbursements in one batch. Match the bank line to the total of the reports it settles, and keep a list of which reports each payment cleared.
The liability account makes this matching easy. Each approved report adds to reimbursements payable under the employee's name. Each payment reduces it. At month end, the balance per employee equals reports approved but not yet paid. A balance that never clears points to a report paid twice or a payment coded somewhere else.
Some businesses pay reimbursements through payroll, adding them to the paycheck. The payroll register should show them as a separate non-taxable line when the arrangement is treated as accountable. In the payroll entry, debit reimbursements payable (or the expense accounts) for that line, and leave it out of wages. If the register lumps reimbursements into gross pay, ask the payroll provider before posting, because the books would then show them as wages.
Partial payments happen too. If one item is disputed and the rest are paid, record the payment against the approved items and leave the disputed item on the report until it is approved or withdrawn.
Employee reimbursement errors that distort the books
Employee reimbursement errors usually show up months later as wrong expense totals, a liability that will not clear or reimbursements counted as wages. Most come from coding the bank line before the expense report arrives, or from coding both the report and the payment as expenses.
Watch for these:
- Double counting. The report is posted to expenses, then the bank payment is coded to expenses again. Expenses rise by the full reimbursement.
- The payment coded to wages. A transfer to an employee looks like pay, so a rule tags it as payroll. The expenses vanish and wages are overstated.
- Personal items reimbursed. A receipt that mixes personal and business items, such as a hotel bill with a family dinner, needs the personal part removed before approval, or the business pays for it.
- Card purchases reimbursed. An employee buys on the company card, then also submits the receipt for reimbursement. Compare reports against company card statements for the same period.
- No receipt, no report. A transfer to an employee labelled "reimb" with nothing behind it should not be coded at all until the report turns up.
Transfers to staff are worth holding rather than coding on sight. AutoBankConvert works from each client's own rules and coding history, and a transfer it cannot place waits in review instead of getting a category by default, which gives the expense report time to arrive.
Employee reimbursements between related companies
Employee reimbursements cross company lines when one entity employs the person but the expense served a related entity. A shared manager might travel for a sister company, or one company might pay reimbursements for staff who work across a group. The expense then belongs to the entity that benefited, and the payment creates an amount owed between the two companies.
Record it in two sets of books:
- In the paying company, debit "Due from" the related company and credit checking when the employee is repaid.
- In the company that benefited, debit the expense accounts and credit "Due to" the paying company.
- Settle the balance when the companies move money between them, and confirm both sides show the same figure each month end.
Keep the expense report and receipts in the file of the company that records the expense, with a copy or a note in the paying company's file. The guide to bookkeeping for multi-entity clients covers how to keep due-to and due-from balances in step across a group, which matters well beyond reimbursements.
When the cross-charges become routine, ask the client to give employees a card or approval route in the entity that should carry the cost. Fewer cross-company reimbursements mean fewer balances to agree at month end.