Every expense.
Under control.

Employees can create Local and Outstation Tour Plans through the mobile app, for themselves or other employees. Each plan captures the purpose, travel dates, passengers, co-travellers, remarks and supporting documents. Incomplete plans can stay in draft and be edited before submission.

Flight, Train, Car and Hotel booking requests sit under the relevant tour, with multiple bookings supported for one journey. The Admin Department processes these requests against the organisation’s travel policy.

Co-traveller acceptance is a defined step in the workflow. SMS confirmation links are sent to the respective employees, and every co-traveller must accept before the tour moves forward. Manager approval and Admin booking confirmation then provide clear checkpoints for the next responsibility.

Travel-class selections are checked against the employee’s permitted entitlement. An out-of-policy selection follows the exception route to the authorised person before it proceeds to the Admin Department. The exception remains a request for a decision, rather than an undocumented bypass.

After a tour, employees can submit the applicable Travel, Local Conveyance, Hotel or Lodging, Food and Miscellaneous expenses. Additional expenditure can be recorded against the same tour, keeping the claim connected to the journey that created it.

The web portal gives administrators separate views of tour details, passengers, bookings and approval status. Employees and administrators can follow progress through dashboard statuses and notifications at key points, including acceptance, approval, booking confirmation and claim submission.

Reimbursement claims move to Accounts for verification and approval, with the designated users able to approve or reject them. Approval leads into the employee reimbursement process. The payment method, accounting interface and source of settlement confirmation are established for the deployment; an approved claim should remain distinguishable from a completed payment.

Branch Heads can record petty cash expenses in the mobile app against the relevant monthly budget or expense cycle. The dashboard brings the branch budget, recorded expenses and total expenditure into view so users can follow utilisation during the month.

An expense entry captures its date, expense head, amount and remarks. Users can add the relevant expense heads and review individual entries, with editing or deletion available where the workflow permits it.

The monthly view keeps individual entries in the context of the branch’s expenditure. It supports conversations about what has been recorded, what remains pending and how the total relates to the available budget.

Branch expenses follow the applicable amount and budget-category route. Designated reviewers can include the Area Manager, Regional Head, Zonal Business Head and Accounts, according to the configured approval matrix.

Assigned and Escalated tabs separate a reviewer’s pending responsibilities. If the first-level approver does not act within the defined timeline, the expense moves to the next-level escalation bucket. Both the assigned and escalated approvers can act while the item remains pending; once one records an approval or rejection, the expense is removed from the other approver’s corresponding action screen.

Rejection requires a reason of at least 20 characters. This gives the submitting team a usable explanation and makes the decision easier to review. Amount slabs, escalation timelines and permitted actions are agreed around the organisation’s actual operating policy.

Rent Management covers branch and regional-office agreements from the initial requisition through renewal, amendment and termination. A requisition brings together office details, landlord information, KYC, tax and bank-account records, rent and security deposit details, with the supporting documents needed for review.

The approval route can involve Regional Admin, Zonal Admin, Regional Head, Admin Head and other authorised stakeholders. Rent amount slabs and the configured route matrix determine the applicable responsibilities.

Renewal can be initiated 75 days before agreement expiry, with provisions for rent increments and tenure extensions. Dedicated workflows support landlord modification and agreement amendments, including rent increases or decreases, agreement extensions, premises changes and landlord bank-account changes.

Termination handling covers normal cases and cases following a landlord’s death, with the applicable templates, approvals and settlement options. Branch shifting carries the existing branch and rental details into the new-premises process, following the current Rent Route Matrix for approval.

The rent accounts workflow calculates monthly rent-related transactions for each branch, identifies payable and receivable amounts and prepares consolidated monthly statements. These records give Accounts visibility of the amount to pay or receive and the calculation behind the handover.

The supplied interface includes Live Rents, Rent Master, Rent Payment Register, Payable for Accounts, Hold Transaction, Reject Transaction, Completed Transaction and an Export Tally Report option. Report export supports an accounting handover; a direct connection to an accounting system is assessed separately.

Rent and security deposit records retain UTR details alongside the relevant transaction history. Approval, amendment and termination histories help a reviewer follow how an agreement or amount reached its current position.

The rent tracker supports a focused review by region, branch, status, agreement expiry, rent amount and owner, as shown in the supplied screen. Report options include rent, pending approvals, completed or pending approvals, expiry counts, completed rent, tour management, rejected rent and escalation reports.

Push and email notifications support the rent approval stages, alongside document uploads, downloads, verification and approval. The supplied notification and email examples show how the relevant rent or landlord event is brought back to the responsible person.

Start a walkthrough with one real example from each module you need: a tour with a policy exception, a branch expense awaiting escalation or an agreement nearing renewal. We can map the forms, approval limits, role access, notification services, opening records and finance handovers before agreeing the rollout scope.