Expense Claim
Expense Claim reimburses employees for approved business expenses. Claims include expense lines by Expense Claim Type, taxes, approvals, and optional Employee Advance settlement. Submitted claims may generate payable entries for accounts.
Help URL: https://smoothhiring.com/help/hrms/expenses/expense-claim
Table of contents
- Overview
- Desk paths
- Creating a claim
- Advance settlement
- Approval workflow
- Accounting
- Who uses Expense Claim
- Common mistakes
- Troubleshooting
Overview
| Area | Detail |
|---|---|
| Employee | Claim owner; company from employee |
| Expense table | Type, amount, description, receipt |
| Taxes | As configured |
| Advances | Link Employee Advance for settlement |
| Approval | Expense Approver on Employee |
Smooth HR runs on Frappe v16. Module sidebars (People, Recruitment, Expenses, Performance, Tenure, NextAI) appear after login. DocType lists use /app/{slug}; workspace homes use /desk/{module}.
Desk paths
| Action | Path |
|---|---|
| Expense Claim list | /app/expense-claim |
| Expense Claim Type | /app/expense-claim-type |
| Expenses workspace | /desk/expenses |
Creating a claim
- Employee or HR opens Expense Claim → Add.
- Select Employee (defaults to self if ESS).
- Add rows: Expense Claim Type, amount, description, attach receipt.
- If advance exists, add Advances section rows to settle.
- Save → Submit for approval.
Advance settlement
ERPNext HRMS pattern:
- Employee received Employee Advance (paid).
- On Expense Claim, table Advances lists open advances.
- Enter Allocated Amount up to advance balance.
- Remaining claim amount is reimbursement due to employee.
Unsettled advance balances appear on employee account until cleared.
Approval workflow
Expense Approver on Employee must approve. HR Settings → Prevent Self Expense Approval blocks self-approval. After approval, accounts creates Payment Entry to pay employee bank account.
Accounting
Expense Claim Type maps to default accounts. Company must have books set up. Reports: Unpaid Expense Claim in Expenses sidebar.
Who uses Expense Claim
| Role | Typical use |
|---|---|
| HR Manager | Full create/submit/cancel; setup masters; reports |
| HR User | Day-to-day transactions; may need approval rules |
| Employee | Self-service where enabled |
| System Manager | Site-wide configuration, integrations, NextAI keys |
Common mistakes
| Mistake | Fix |
|---|---|
| No approver on employee | Set Expense Approver |
| Double settlement | One allocation per advance per claim |
| Wrong company | Employee company drives claim |
| Missing tax template | Configure on expense type |
Troubleshooting
| Issue | Fix |
|---|---|
| Submit blocked | Mandatory fields; approver |
| Advance not listed | Advance must be paid/unsettled |
| Unpaid report stale | Refresh after payment entry |
Receipts and audit
Attach clear receipt images. Auditors trace Payment Entry back to claim lines.
Use naming and posting date discipline for month-end close.
Frequently asked questions
Can manager submit for employee?
Yes if HR User role and permissions allow.
Partial advance settlement?
Allocate partial; remainder stays on advance.
Related guides
Additional operational detail
Smooth HR v16 organizes HR into module workspaces accessible from the desktop app switcher. Each module sidebar mirrors production fixtures in the HRMS app: People at /desk/people, Recruitment at /desk/recruitment, Expenses at /desk/expenses, Performance at /desk/performance, Tenure at /desk/tenure, and NextAI at /desk/nextai. DocType routes follow /app/{slug} where slug is the lowercased DocType with spaces replaced by hyphens.
HR Managers configure masters and approvals; HR Users run daily transactions; Employees interact through self-service when User records link to Employee and roles permit; System Managers own site configuration including NextAI API credentials. Before go-live, validate Role Permissions Manager entries for each DocType mentioned in this guide.
When migrating from spreadsheets, import Company and Department before Employee, then recruitment and expense histories. Use Data Import templates and fix validation errors row-by-row rather than bulk-deleting partial loads. Clear desk cache after fixture updates so sidebars reflect the latest Smooth HR layout.
For payroll-adjacent HR data, keep Employee company and department aligned with cost centers. For recruitment, remember Job Applicant documents use email as the primary key. For expenses, settle Employee Advance balances on Expense Claim submission. For performance, run Appraisal Cycle to batch-create Appraisal records. For tenure, complete Employee Separation projects before deactivating employees. For NextAI, store Gemini or OpenAI keys only in NextAI Settings and review usage logs before retention cleanup runs.
Additional operational detail
Smooth HR v16 organizes HR into module workspaces accessible from the desktop app switcher. Each module sidebar mirrors production fixtures in the HRMS app: People at /desk/people, Recruitment at /desk/recruitment, Expenses at /desk/expenses, Performance at /desk/performance, Tenure at /desk/tenure, and NextAI at /desk/nextai. DocType routes follow /app/{slug} where slug is the lowercased DocType with spaces replaced by hyphens.
HR Managers configure masters and approvals; HR Users run daily transactions; Employees interact through self-service when User records link to Employee and roles permit; System Managers own site configuration including NextAI API credentials. Before go-live, validate Role Permissions Manager entries for each DocType mentioned in this guide.
When migrating from spreadsheets, import Company and Department before Employee, then recruitment and expense histories. Use Data Import templates and fix validation errors row-by-row rather than bulk-deleting partial loads. Clear desk cache after fixture updates so sidebars reflect the latest Smooth HR layout.
For payroll-adjacent HR data, keep Employee company and department aligned with cost centers. For recruitment, remember Job Applicant documents use email as the primary key. For expenses, settle Employee Advance balances on Expense Claim submission. For performance, run Appraisal Cycle to batch-create Appraisal records. For tenure, complete Employee Separation projects before deactivating employees. For NextAI, store Gemini or OpenAI keys only in NextAI Settings and review usage logs before retention cleanup runs.
Last updated: May 2026
Additional operational detail
Smooth HR v16 organizes HR into module workspaces accessible from the desktop app switcher. Each module sidebar mirrors production fixtures in the HRMS app: People at /desk/people, Recruitment at /desk/recruitment, Expenses at /desk/expenses, Performance at /desk/performance, Tenure at /desk/tenure, and NextAI at /desk/nextai. DocType routes follow /app/{slug} where slug is the lowercased DocType with spaces replaced by hyphens.
HR Managers configure masters and approvals; HR Users run daily transactions; Employees interact through self-service when User records link to Employee and roles permit; System Managers own site configuration including NextAI API credentials. Before go-live, validate Role Permissions Manager entries for each DocType mentioned in this guide.
When migrating from spreadsheets, import Company and Department before Employee, then recruitment and expense histories. Use Data Import templates and fix validation errors row-by-row rather than bulk-deleting partial loads. Clear desk cache after fixture updates so sidebars reflect the latest Smooth HR layout.
For payroll-adjacent HR data, keep Employee company and department aligned with cost centers. For recruitment, remember Job Applicant documents use email as the primary key. For expenses, settle Employee Advance balances on Expense Claim submission. For performance, run Appraisal Cycle to batch-create Appraisal records. For tenure, complete Employee Separation projects before deactivating employees. For NextAI, store Gemini or OpenAI keys only in NextAI Settings and review usage logs before retention cleanup runs.