Account for money already issued to employees, verify unused funds returned, and close each advance without paying the same expenses twice.
An employee submits a trip report and sends back some unused cash. The manager approves the report, but finance still sees an outstanding advance. Neither the approval email nor the employee’s transfer screenshot proves that the advance has been settled.
Employee cash advance reconciliation links the original disbursement to approved expense applications, confirmed repayments and any balance still requiring action. Its output is an advance-specific settlement record, not simply an approved expense report. Use the process below for business-expense advances already paid to employees, not payroll loans, supplier prepayments or cash withdrawn on company cards.
Separate expense approval from advance settlement
Expense approval answers whether a cost is supported and permitted. Advance settlement answers how much of the money already issued has been accounted for. A claim can pass the first test while the second remains incomplete.
Oracle’s PeopleSoft reconciliation documentation explains that applying an advance to an expense report affects the reimbursement calculation. It also tracks remaining balances and associated expense reports. That is a software-specific illustration of why advance application must be checked before another payment is released.
For your operating design, distinguish these states: Paid → Evidence submitted → Validated → Settlement approved → Applied/returned → Reconciled → Closed. Missing support or cash sends the case to an owned exception, not directly to closure. These are suggested workflow states, not prescribed accounting-system labels.
Build one settlement record per paid advance
The expense administrator starts the record when the trip or activity ends, is cancelled, or reaches the review date set in company policy. Carry forward the original advance ID rather than identifying the case only by the employee’s name.
- Original issue: employee, legal entity, business purpose, advance ID, amount and currency, payment date, bank/payment reference and accounting reference.
- Expense applications: report ID, approved lines, amount actually applied, application date and posting/reference evidence. Link each line to the correct advance.
- Returns: repayment amount and currency, receipt reference, receiving account confirmation and accounting application. Distinguish a promised return from a confirmed receipt.
- Open balance: amount, reason, responsible person, next action and policy-based due date.
- Review: preparer, settlement approver, posting owner, final reviewer and dated closure evidence.
Keep receipt files in the approved expense system or restricted record location. Link the evidence rather than copying personal banking details into a widely shared tracker.
Use a bridge, not a balancing plug
For a simple single-currency advance, use: outstanding advance = paid advance − approved expenses actually applied − confirmed returns actually applied. Keep the amounts on the same measurement basis. Do not subtract a submitted but rejected expense, a pending bank transfer or an unrelated repayment merely to make the balance zero.
Where multiple reports use one advance, track each application separately and check cumulative use. Where one report uses several advances, preserve each allocation. For foreign currency, retain original amounts and the approved conversion basis; have accounting separately identify exchange differences and fees rather than hiding them in the expense total.
Control each handoff with evidence
This matrix is a suggested internal control design. Assign named people to the roles and align approval limits, due dates and exception treatment with your organization’s policies.
| Trigger and owner | Evidence and control | Financial state and next step | Exception path |
|---|---|---|---|
| Activity ends: employee submits | Advance ID, expense report, receipts and proposed unused amount; administrator checks completeness | Cash issued remains open pending validation | Missing documents return to employee with a reason and due date |
| Complete packet: manager and expense reviewer validate | Confirm purpose, policy eligibility and no duplicate company-paid costs; approve eligible lines | Approved expenses become eligible for application, not a second full reimbursement | Disallowed or disputed lines remain separately owned; designated reviewer decides treatment |
| Approved settlement: expense/accounting owner applies | Advance-to-report allocation and saved application reference; check cumulative amounts | Applied expenses reduce the open advance in the system of record | Wrong advance or changed report requires reversal/correction and reapproval before recalculation |
| Unused cash due: employee returns; cash owner confirms | Approved return instructions, confirmed receipt and correct advance/account reference | Only the confirmed, recorded return reduces the remaining balance | Partial, missing or unidentified receipt stays open with a tracing owner |
| Balances agree: independent reviewer signs off | Issue, applications, receipts, postings and remaining balance agree; review any additional reimbursement separately | Reconciled; close the advance only after the supported disposition is recorded | Unexplained residual is carried as an exception, not written off by the preparer |
North Carolina’s NCFS guide for closing unapplied employee advances illustrates the distinction between depositing the returned funds and completing the approved accounting and expense-system steps. Its account codes and navigation are specific to that system; use your own accounting procedure.
Work through a partial return before closing
Illustrative example: an employee receives a $1,200 business advance. Finance validates $930 of eligible expenses and confirms that the expense system has applied that amount to the advance. The employee says the remaining $270 has been returned, but the receiving record supports only $200.
- The administrator links the $1,200 disbursement to the advance ID and the $930 application to the approved report.
- The cash owner confirms the $200 receipt and accounting links its application to the same advance.
- The settlement bridge shows $1,200 − $930 − $200 = $70 outstanding. The employee owns the repayment query; the cash owner checks whether a second receipt is unmatched.
- No new reimbursement is due for the $930 already funded by the advance. The record remains open for $70, with a next action and date.
- A later $70 receipt is confirmed and applied. The reviewer verifies the zero balance against the expense and accounting records before closure.
A transfer screenshot alone does not complete step five. Conversely, cash received but not correctly applied can leave the advance open even though the money is back.
When expenses exceed the advance
In a separate example, $1,350 of approved eligible expenses are fully supported and $1,200 is applied from the advance. The additional reimbursement is $150, not $1,350. Confirm both the advance application and the separate reimbursement authorization before payment. The expense reimbursement approval workflow covers claim validation; this settlement record prevents that valid claim from being funded twice.
Keep exceptions visible through month-end
Cancelled trips and missing receipts
If the trip is cancelled, request the return of unused funds and validate any unavoidable business costs separately. Do not invent an expense to clear the advance. A missing receipt goes through the organization’s alternative-evidence policy, if one exists; without an approved resolution, it is not an applied expense.
Changed reports and overdue repayments
If an approved expense report is reduced after application, preserve the old reference, obtain the corrected approval and have the authorized system owner correct the application. Recalculate the advance and any additional reimbursement. A prior signoff is not permission to leave the changed balance unexplained.
At close, the administrator supplies an aging list of open advances with employee, amount, reason, next action and owner. Accounting determines the appropriate balance classification and any required adjustment. Do not assume every old balance can be expensed, forgiven or deducted from wages.
Set reconciliation and escalation dates in the applicable policy. Do not treat an example deadline from another organization as a universal rule. Tax consequences, collection rights and payroll deductions require the relevant jurisdictional rules and authorized specialist review.
Where Workhint fits
The coordination problem is getting the employee’s evidence, manager’s decision, cash confirmation and accounting reference into a reviewable handoff. Workhint’s Workflow Engine describes required details and files before progression, with approvals routed to managers, finance or other defined roles. Those are relevant building blocks for the submission and review stages.
Its Workflow Automation Software solution describes configured forms, review stages, owners and approval outcomes. A proposed advance workflow could coordinate those decisions while the expense system, bank and accounting system remain authoritative for applications, receipts and balances. The cited pages do not establish native cash-advance reconciliation, bank imports, repayment collection, payroll deductions or ledger posting; verify implementation details rather than assuming them.
Frequently asked questions
Does an approved expense report close the advance?
Not by itself. Confirm the approved amount was applied to the correct advance, verify any required return and reconcile the remaining balance in the system of record.
Can finance close a partially returned advance?
Not merely because some cash arrived. Keep the unexplained amount open until it is returned or has an authorized, recorded disposition. Separately document any policy-approved accounting treatment and outstanding recovery action.
Who should approve closure?
Assign a reviewer with authority under your policy, separate from the employee and, where practical, from preparation. The reviewer needs the issue, applications, return receipts, accounting references and final balance—not just a completed task status.

Leave a Reply