QuickBooks: employee reimbursement after an expense is recorded

When an employee expense is already recorded in QuickBooks Online US, a later bank reimbursement must be checked against that original accounting trail. If the reimbursement payment itself is already recorded, match the downloaded bank movement to that payment rather than categorize it as another expense.

First establish whether you have an expense, a liability and an actual reimbursement record. A bank outflow alone cannot tell you which of those has been entered. For PDF evidence, LocalExtract can prepare transaction rows; it does not choose employee accounting treatment.

Find the original expense and the later payment separately

Intuit’s employee reimbursement guide distinguishes paying now from recording an expense for payment later. Its later-payment route uses an expense and employee liability, followed by a check or expense when reimbursement occurs.

Inspect the records actually present in your company. Retain the employee reference, purchase support, original entry and payment reference. Do not copy a contractor or owner-equity procedure into an employee reimbursement merely because all involve personal spending.

The existence of an original expense does not prove that the reimbursement payment has already been entered. If that payment record is absent, the bookkeeper must determine and record the appropriate transaction using the applicable Intuit route; there is nothing yet for the downloaded bank movement to match on that basis.

Match only the existing payment you can identify

Intuit’s matching instructions distinguish Match, which links an existing record, from Categorize, which creates a new record.

1. Open All apps → Accounting → Bank transactions and select the paying bank account.
2. Review the suggested record in Categorize or Match and expand its details.
3. Compare the payee, amount, dates and reimbursement evidence with the actual payment record.
4. Use Find other match if the suggestion is wrong. Post a match only after verifying the payment and record.

Do not match a merchant purchase to the employee repayment simply because the amounts agree. The purchase and the employee payment are different events, even when the liability links them.

Check the expense total and remaining liability

In an invented USD case, an employee purchase creates a 78.00 USD expense and 78.00 USD liability. A later 78.00 USD payment settles that liability. Recording the downloaded outflow as the same expense again would produce 156.00 USD of expense instead of 78.00 USD.

The synthetic reimbursement trail preserves those distinct records. Python verifies only the doubled-expense arithmetic, not a journal, payroll payment or bank match.

For outstanding reimbursements, Intuit describes Reports → Standard reports → Transaction Detail by Account, customized by Employee and the relevant liability account. Compare the actual remaining balance and original records; a partial reimbursement need not equal the original expense.

If the original treatment is uncertain, give the trail to the responsible accountant before adding another entry. The bookkeeping handoff guide covers keeping that evidence together.

LocalExtract handles one PDF locally into date,description,amount CSV. It neither creates reimbursement accounting nor initiates employee payments. Download for PDF review.

Official Intuit US instructions checked October 16, 2026.