Finance shouldn't discover a ₹40,000 hotel bill during the audit.
OneFinOps enforces your spend policies the moment an expense is submitted, not weeks later. Role-based limits, city-tier caps, multi-level approval chains, and exception workflows are all configurable without writing a single line of code. Policy violations are flagged inline before they reach any approver.
Three Layers of Spend Control
Spend policies, approval routing, and exception management work together to give finance full control without creating friction for employees.
Role-Based Spend Limits Without Code
Build your expense policy in the OneFinOps policy editor. Set spend limits per category (meals, hotel, flights, transport) and per role (IC, Manager, Director, VP, C-suite). Apply city-tier modifiers, a hotel cap in Mumbai is different from Tier-2. Policies are version-controlled and effective-dated, so changes apply to new expenses without affecting in-flight claims.
- Per-category limits by role: IC → Manager → Director → C-suite
- City-tier modifiers: Metro / Tier-1 / Tier-2 / International
- Department overrides for sales, engineering, field operations
- Version-controlled policies with effective dates
- Policy preview: employees see limits before they book
Multi-Level Approval Chains by Amount
Configure approval routing based on expense amount, category, and submitter's role. A ₹500 meal claim goes directly to the line manager. A ₹50,000 travel expense routes to manager → finance controller → CFO. Approvers get mobile push notifications with full context (receipt image, category, policy status) and approve or reject in one tap.
- Amount-based escalation: single → multi-level based on thresholds
- Category-specific routing (e.g., all IT expenses to IT finance)
- Delegation rules for when approver is OOO
- SLA enforcement: auto-escalate if not approved in 24h
- Mobile-first approval with receipt view and reject reason
Out-of-Policy Exceptions with Justification Flow
Not every policy breach is fraud, sometimes a business dinner runs over budget or the only available flight is above the cap. OneFinOps allows employees to submit out-of-policy expenses with a mandatory business justification. These are automatically routed to a higher approval level (e.g., CFO or department head) rather than being blocked entirely.
- Inline policy flag with overage amount clearly shown
- Mandatory justification field for out-of-policy submissions
- Auto-escalation to senior approver for exceptions
- Exception register for monthly finance review
- Recurring exception patterns flagged for policy review
From Expense Submitted to Reimbursed: In Five Steps
Every expense follows a policy-checked, approval-gated path that keeps finance in control
Submit
Employee snaps a receipt or logs an expense. OCR pre-fills the fields. The employee selects a category, project code, and adds a description. One tap to submit. The expense is now in the system with a full receipt image attached.
Policy Check
Immediately after submission, OneFinOps runs the expense against the employee's applicable policy profile. Amount vs category limit, city tier, and receipt requirement are all validated. Within-policy expenses proceed to approval. Out-of-policy expenses are flagged with the specific violation and the employee is asked to justify or edit.
Route to Approver
The expense is routed to the correct approver based on amount, category, and submitter role. The approver receives a push notification with the expense summary, receipt image, and policy status. For multi-level chains, each level is notified in sequence. SLA timers start immediately, inactivity triggers an escalation reminder after 24 hours.
Approve or Reject
Approvers review the expense in the OneFinOps mobile or web app. Approve with one tap, or reject with a mandatory rejection reason (which is shared with the employee). For exceptions, the approver can approve with a note that is recorded in the exception register for finance review.
Queue for Reimbursement
Fully approved expenses are automatically added to the next reimbursement batch. Finance confirms the batch and initiates NEFT. The employee receives a notification when the payment is credited. The expense record is closed with the UTR number, approval chain, and receipt archived for audit.
Common Questions About Approval Policies
Control Spend at Submission, Not at Audit
Set up your company's spend policies in minutes. Role-based limits, multi-level approvals, and exception workflows that give finance full control without slowing your team down.