Expense Claims, Employee Reimbursement, and Employee Loans

When employees spend personal money on behalf of the company, those obligations need to be tracked and settled accurately. ERPNext handles this through two related but distinct mechanisms: Expense Claims for reimbursable spending and Employee Loans for cash advances that are repaid over time. Both flow through the HR module and connect directly to the general ledger, ensuring the balance sheet reflects outstanding obligations to employees at all times.

Expense Claims

An Expense Claim documents a request for reimbursement when an employee has personally paid for a business expense. Common examples include travel costs, meals during client visits, and office supplies purchased when the company's procurement process is impractical. The claim can be submitted by the employee directly or entered by the HR or accounting team on their behalf.

Each claim identifies the expense type, amount, date, and any supporting documentation. ERPNext can route submitted claims through an approval workflow before they are ready for payment, allowing a manager or supervisor to review and authorize each request. This workflow step provides internal control without requiring the accounting team to validate every submission individually.

When an approved Expense Claim is submitted in ERPNext, the system creates the following general ledger entry:

The Employee Payable account is a current liability that accumulates all approved but unpaid reimbursements. Mapping each expense type to the correct GL account in the Expense Claim Type configuration is important—incorrect mapping can silently post expenses to the wrong account for extended periods before the error surfaces in financial reporting. Configuring Expense Claim Types at setup time and restricting edits to that configuration limits this risk.

Expense Claim Types and Policy Enforcement

Expense Claim Types are the primary mechanism for enforcing company policy on reimbursable expenses. Each type maps to a specific expense account and carries a description that can communicate policy to employees—for example, what documentation is required, what spending limits apply, or what circumstances justify the expense.

Organizations typically create Expense Claim Types that align with their chart of accounts and travel policy. Common examples include:

• Travel - Airfare mapped to a travel expense account, with policy notes about booking class restrictions
• Travel - Lodging mapped to the same or a separate travel account, with notes about nightly rate caps
• Meals - Business Development mapped to a meals and entertainment account
• Office Supplies mapped to a supplies expense account
• Professional Development mapped to a training expense account

By limiting which Expense Claim Types are available, an organization controls where expense dollars can be allocated without requiring manual review of every claim. The approval workflow then provides a second layer of control for amounts or circumstances that warrant human judgment.

Per Diem Allowances

Per diem—a fixed daily allowance for meals and incidental expenses during travel—simplifies employee reporting by paying a flat rate per day rather than requiring receipts for every meal. ERPNext does not calculate per diem amounts automatically; organizations implement it by creating an Expense Claim Type with policy documentation specifying the daily rate. Per diem rates often vary by destination and are subject to regulatory limits (for example, GSA rates in the United States), so documenting the applicable rate in the Expense Claim Type description keeps employees and approvers aligned on current policy.

Mileage Reimbursement

When employees use personal vehicles for business travel, mileage reimbursement compensates them for fuel, wear, and depreciation. ERPNext does not have built-in mileage rate calculations—organizations implement mileage reimbursement the same way as per diem, by creating an Expense Claim Type with policy documentation specifying the rate per mile or kilometer. Employees calculate the reimbursement amount manually and submit the claim. As with per diem, mileage rates are often subject to regulatory limits (for example, the IRS standard mileage rate in the United States), and documenting the applicable rate in the Expense Claim Type description keeps employees and approvers aligned on current policy.

Employee Advances

An Employee Advance is a cash disbursement made to an employee before expenses are incurred. This is common for business travel where the organization provides funds upfront rather than expecting the employee to float significant expenses.

The Employee Advance account is a current asset—the company has given cash to the employee and expects either documented expenses or a return of unused funds. The Employee Advance DocType tracks the advance amount, the amount claimed against it, and the amount returned.

When an employee submits an Expense Claim, they can link one or more Employee Advances in the Advances section. The Expense Claim total is first applied against any linked advances before creating additional Employee Payable liability. If the employee's expenses exceed the advance, the difference becomes payable to the employee. If expenses are less than the advance, the remaining balance can be returned via payroll deduction (if the "Repay Unclaimed Amount from Salary" option is enabled) or through a separate return transaction.

In this example, the employee received a $1,000 advance and incurred $850 in documented expenses. The remaining $150 would be returned or deducted from salary, clearing the Employee Advance balance.

Employee Reimbursement

Reimbursement is the act of paying out the approved Expense Claim. ERPNext provides a Make → Payment Entry action on the approved Expense Claim that generates the Payment Entry directly from the claim. This links the payment to the originating claim, clears the Employee Payable balance, and maintains full traceability between the original expense and the disbursement.

The Payment Entry uses the Employee as the party type, which ensures the payable is tracked and cleared at the individual level rather than in a pooled liability account:

Some organizations create standalone Payment Entries to reimburse employees directly, bypassing the Expense Claim module. While this clears the bank account correctly, it breaks the audit trail: there is no connection between the payment and the approved expense, no record of what the payment was for, and no way to report on outstanding reimbursements by employee.

Periodic reconciliation of the Employee Payable account surfaces approved claims that have not yet been paid. Unpaid approved claims are a common failure point in reimbursement processes—claims are approved and then forgotten before payment is issued, and the liability sits on the balance sheet without visibility until a reconciliation is run.

Employee Purchases of Inventory Items

Occasionally employees purchase inventory items directly rather than going through the normal procurement workflow. A standard Expense Claim debits an expense account, but inventory purchases should appear on the balance sheet as assets. Handling this correctly requires coordinating the Expense Claim with a Stock Entry that records the items.

Both workflows below use a clearing account to connect the Expense Claim to the Stock Entry. Create a current liability account (for example, Employee Purchase Clearing) with root type Liability and no special account type. Do not use the "Stock Received But Not Billed" account type—that type is reserved for the company's default SRBNB account used by Purchase Receipt, and mixing employee purchase entries into that account complicates reconciliation and may affect reports. A dedicated clearing account with a generic type keeps these transactions cleanly separated. Create an Expense Claim Type that maps to the clearing account.

This workflow should be considered exceptional. While the accounting ties out correctly, purchasing data and controls are absent. Neither the Expense Claim nor the Stock Entry captures formal supplier information, so there is no record of which vendors supplied which items, no purchase order to enforce pricing or quantity controls, and no three-way matching. A single Expense Claim or Stock Entry may cover purchases from multiple suppliers across multiple transactions. Organizations should limit this workflow to urgent situations and ensure that standard procurement remains the default path for inventory acquisition.

Partial Consumption On-Site

An employee purchases $100 of supplies at a hardware store during an on-site job. Some items are consumed immediately; the remainder returns to the warehouse. The employee submits an Expense Claim for the full $100:

The inventory team creates a Stock Entry of type Material Receipt for ALL items purchased—both the items that return to the warehouse and the items that were consumed on-site. Each item row has an Expense Account field; set this to the same clearing account. This receives the full $100 into inventory and clears the liability:

At this point the clearing account nets to zero. A separate Stock Entry of type Material Issue records the consumption of items used on the job. The Expense Account on these rows is set to the job expense account:

The net effect: $60 expense (consumed), $40 inventory (retained), $100 reimbursed to the employee. The stock ledger shows a complete record of all items received and a clear record of which items were consumed on which job. This separation also divides responsibilities appropriately: the employee submits the claim with documentation of what was purchased, the inventory team receives items into stock, and the job supervisor or project manager authorizes the Material Issue against the job.

Online Purchase for Inventory

An employee orders $500 of specialty ingredients online using a personal card to meet a shipping deadline. All items will go into inventory—nothing is consumed immediately. This scenario follows the same clearing account pattern.

When the items arrive, the inventory team creates a Stock Entry of type Material Receipt with the Expense Account set to Employee Purchase Clearing:

The employee submits an Expense Claim using an Expense Claim Type mapped to the same clearing account:

The clearing account nets to zero. When the employee is reimbursed:

The net effect: Inventory on Hand increases by $500, Bank decreases by $500, and no expense is recognized—the cost is capitalized into inventory as it should be.

If a Material Request was involved and is now partially fulfilled through procurement and partially through the employee purchase, amend the Material Request to remove the employee-purchased items rather than attempting to close them out through a fake supplier flow, which would double-count the cost.

Employee Loans

An Employee Loan differs from an expense reimbursement in an important accounting respect: it is an asset to the company, not an expense. When a company lends money to an employee, the cash leaves the bank and a receivable appears on the balance sheet. The disbursement does not create an expense; the obligation to return the funds is the employee's, and only if the loan is later forgiven does it convert to an expense.

Loan requests in ERPNext originate in the HR module and can be initiated by the employee or by HR. Once approved, the disbursement is processed through a Payment Entry:

Repayment typically occurs through payroll deductions in installments. When ERPNext processes payroll, it reduces the Employee Loan balance against the employee's Salary Payable:

If the employee repays outside of payroll—by cash or bank transfer—the repayment needs to be linked to the loan record so the balance remains accurate. Unlinked payments create phantom balances in the Employee Loan account that complicate reconciliation and final settlement calculations.

Interest-bearing loans require selecting the correct loan type prior to approval. ERPNext calculates and accrues interest automatically for qualifying loans, keeping both principal and interest balances visible in the loan record. Failing to select the interest-bearing type at the outset means interest would need to be tracked and accrued outside the system.

When an employee separates from the company, any outstanding loan balance is included in the final settlement calculation. ERPNext's loan reports make it straightforward to identify employees with open balances, but this step is a deliberate check during offboarding—outstanding loan balances do not automatically appear in the standard offboarding workflow and can be missed if the process is not explicitly designed to surface them.