See what expense management changes at your institution
Before vs. after adding expense management to iVake
Where you are today
Holding you back
Paper claims with bills stapled on
Forms travel between offices for signatures, and a claim or its bills go missing on the way.
Pain point
Policy breaches found weeks later
Finance spots an over-limit hotel or a missing bill only at manual review, then chases it over several emails.
Pain point
Claims stuck when an approver is away
When the head of department is on leave, claims wait unsigned because nobody else is authorised to approve them.
Pain point
Project funds checked by hand
Claims against a sponsored research project are checked against a separate spreadsheet of allowed heads and balances.
Pain point
- 3+Signatures chased per claim
- 2+Times each claim is written up
- WeeksBefore a claim is reimbursed
Your institution, transformed
Everything connected
Claimed from a phone
Staff photograph the bill, fill in a short form and submit, and the claim is on the record from that moment.
Solved
Limits checked before submitting
Daily allowances and category limits are checked as the claim is filled in, with the allowed amount shown.
Solved
Approvals that do not wait
A named deputy approves while the approver is on leave, and a claim that sits too long moves up the chain.
Solved
Budget heads checked on entry
Claims charged to a project or budget head are checked against its allowed categories and remaining balance.
Solved
- 1Record per claim, from bill to payment
- 0Paper forms in the internal post
- Same dayView of spending for finance
Ready to make the switch? See how it works for your institution.
From a receipt in a pocket to a submitted claim
When the bill is photographed where it is paid and the policy is checked before anyone presses submit, the paper chase between offices stops.
- Receipt photos attached to the claim, with vendor, date and amount read from the image for staff to confirm
- Daily allowance and category limits checked on entry, with the allowed amount shown
- Local travel claimed by distance, at the rate your policy sets for each kind of vehicle
Approval chains that match your authority levels
When the route a claim takes mirrors who is actually allowed to sign, and a deputy covers anyone on leave, claims stop sitting on an empty desk.
- Routes set by amount, category, department and budget head, with the project office added in parallel where needed
- Deputies approve automatically while the assigned approver is on recorded leave
- A claim waiting past the time you set moves to the next level, and both people are told
Budget heads and project funds without the side spreadsheet
When every claim charged to a project or budget head is checked against what that head allows, and balances update as claims are approved, nobody needs to keep a parallel sheet.
- Each project or budget head carries its allowed categories and balance, and stops what it does not allow
- Spending by department, category, head and month, down to the individual claim
- Advances for travel or fieldwork settled against the claims filed, showing what is owed either way
Expense management features
Everything you need to manage expense claims effectively
Mobile claims
Claims submitted and tracked from the staff app, with the receipt photo attached.
Receipt reading
Vendor, date and amount read from the receipt image, for staff to check and confirm.
Emailed receipts
Bills received by email forwarded into a draft claim, rather than printed and scanned.
Card & bank statements
Institution card and bank statement lines matched to the claims that explain them.
Spending reports
Spend by department, category, budget head and month, with the claims behind each figure.
Approval rules
Routes by amount, category and budget head, with deputies and escalation.
Audit trail
Every submission, approval, change and payment logged with who made it and the previous value.
Rollout support
Policy limits, approval chains and budget heads configured, with a written rollout plan.
Frequently asked questions
Get answers to common questions about expense management
How are daily allowances handled when they differ by city and change each year?
Allowances are kept in a rate table by city class or zone, with separate limits for food and stay and the date each rate takes effect. When your governing body revises them, the table is updated once and every later claim is checked against the new figures. A claim above the limit is flagged as it is filled in, and needs either a lower amount or a written reason for the approver.
Can one expense be split between a project and a department budget?
Yes. A claim line can be divided by percentage or amount across more than one budget head, for example part to a sponsored research project and part to the department’s travel budget. Each share is checked against its own head’s rules and balance, and posts to its own account.
What happens when a claim breaks the expense policy?
Your finance office decides which rules stop a claim and which only warn. A hard stop, such as a hotel above the cap without prior approval, cannot be submitted, and the claimant sees the rule and who can grant an exception. A warning lets the claim through with a written reason that every approver in the chain can read.
Can we match institution card or bank statement lines to claims?
Yes. Statement lines are imported and wait against the cardholder until each is matched to a claim with a receipt and a reason. Lines left unexplained beyond the period you set are flagged to the cardholder and their approver. Tell us your bank and statement format and we will confirm how it comes in.
How does this help with audits of project and grant spending?
Each project record holds its funding body, sanction reference, period, allowed heads and balance. Every claim against it keeps the full chain: who submitted it, the receipt, each approval with its time, and the payment. For an audit or a utilisation certificate, the claims behind any figure come from the record rather than from files.
Do reimbursements reach our accounting software?
Approved claims post to the books in iVake, and the day book and ledgers export to Tally or Zoho Books in their own format. Reimbursements are paid by bank transfer or added to the next salary run in payroll, as your policy decides.
How long does it take to go live?
Expense claims go live with the rest of iVake: roughly four weeks for a school, six to eight for a university or a group with several campuses. Discovery writes down your policy limits, approval chains and budget heads, open advances come across in migration, and staff are trained on their own screens.
Built for your institution type
See how this feature works for your specific institution
CBSE, ICSE & state-board schoolsTrip, event and sports spending claimed against a budget
UniversitiesProject and department budgets across campuses
Degree collegesSeminar and conference claims routed by amount
ITIs, polytechnics & skill centresTrainer travel and workshop costs claimed per batch
Playschools & pre-primarySmall day-to-day purchases claimed with the bill attached
Professional collegesSponsored research claims split across project and department
Integrations, comparisons & tools
Extend expense management with integrations, see how iVake compares, and run the numbers
More in finance & administration
Explore other features in this category
Ready to transform your expense management?
See how iVake takes expense claims off paper, so finance sees spending while it can still be managed.
Try it free for 30 days. No credit card required.