Claim capture
- Claims
- Lines
- Receipts
- Receipt waivers
재무 및 매출
비용
Expense management for claims, receipts, approvals, reimbursements, corporate cards, OCR, and accounting handoffs.
구현됨
Evidence-first module page
Primary users
Employee
Line manager
Finance reviewer
Card administrator
App-derived visual
Expense operations workspace
Claims
Workflow gated
Receipts
OCR aware
Cards
Match controlled
| 영역 | 상태 | 증거 |
|---|---|---|
| Claims | Approval tracked | Decision history |
| Receipts | Verified | OCR proof |
| Handoffs | Accounting ready | Export run |
핵심 워크플로
What the module helps operators complete.
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Step 1
Submit claims with receipt evidence and policy checks
Step 2
Approve, reject, return, or reimburse expense claims
Step 3
Match corporate card transactions and receipt evidence
Step 4
Post approved handoffs to accounting with export evidence
Feature checklist
Capabilities grouped the way operators look for them.
Approval and payment
- Approval workflow
- Reimbursement
- Corporate cards
- Exception review
Evidence and handoff
- OCR results
- Accounting handoff
- Export runs
- Audit trail
Connected module map
How this module exchanges business context with the rest of ERPStack.
| Module | 관계 |
|---|---|
| 회계 | Approved claims and reimbursement journal handoff |
| 문서 | Receipt evidence and export artifacts |
| HR / Payroll | Employee identity and manager approval context |
| BI | Spend, reimbursement, policy, and card analytics |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
거버넌스
- Receipt waiver controls
- Approval workflow audit
- Corporate card match evidence
- Export run checksums
보고서
- Claim status
- Reimbursement queue
- Card matches
- Spend analysis
AI coverage policy
What ERPStack can honestly claim for this module today.
AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.
AI L2 ready| Coverage claim | Current AI coverage: Expenses L2/L2 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 2 registered tools, 2 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: not in the current proactive-agent monitor wave. |
| L4/L5 boundary | Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable. |
Evidence-first standard
Module pages explain value, workflow, control, and proof in one place.
This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.
Feature clarity
Buyers can see concrete function groups instead of vague capability claims.
Operational fit
Workflows, users, and connected modules show where the module belongs.
Governance proof
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Review path
Public pages link back to app routes so reviewers can compare page claims to product surfaces.