What's New at EnKash: April 2026

Multi-level approval escalation, MCC-based wallet restrictions, duplicate invoice detection, and Video KYC for prepaid onboarding.

Finance teams depend on workflows that hold up under real operating conditions — where approvers go inactive, petty cash drifts outside its intended purpose, bill exceptions go unnoticed, and card onboarding creates delays.

This month's updates address each of these directly, adding structured automation and control across the expense, petty cash, bill payments, and prepaid modules.

Multi-level approval chains break when an approver is unavailable or no longer active in the system. Requests stall, employees wait, and finance teams intervene manually to unblock workflows. The problem is most acute when an approver has left the organisation entirely and the chain has no fallback.

EnKash now automatically escalates requests to the next approver level when the current approver is inactive or absent. The escalation logic handles departures and inactive accounts, not just scheduled leave. Advance and expense requests continue moving through the approval hierarchy without manual override.

• Multi-level approval chains remain functional when approvers leave the organisation
• No manual intervention required to unblock stalled requests
• Reimbursement timelines stay consistent regardless of team changes

• Fewer escalations reaching finance teams for manual resolution
• Advance and expense workflows run without dependency on specific individuals
• Audit trails remain intact through automated escalation, not ad hoc workarounds

Give employees full visibility across the expense lifecycle

Employees receive approval notifications but have no system signal for when their approved expense is actually settled and reimbursed. This gap generates a consistent volume of follow-up queries to finance teams and reduces trust in the process.

Send automated email notifications at settlement, confirming that the reimbursement has been processed and credited. The notification is triggered at the point of actual settlement, separate from the approval notification, completing the visibility loop from submission through to reimbursement.

For approvers, automated periodic digests summarise pending requests, total amounts awaiting action, and aging — delivered on a configured daily or weekly cadence. Approvers stay informed about their queue without logging into the platform.

• Employees receive confirmation upon approval and again upon settlement
• Approvers get a structured view of pending requests on a scheduled cadence
• Finance teams field fewer inbound status queries

• Reduced back-and-forth between employees and finance on reimbursement status
• Approval queues are cleared faster with proactive approver visibility
• No request is delayed simply because it was not visible to the approver

Block duplicate invoice submissions before they reach the approval queue

Duplicate expense claims, whether submitted accidentally or otherwise, create financial leakage and reconciliation overhead. Without an automated detection layer, duplicates reach approvers who may not have the context to identify them, and correcting an approved duplicate reimbursement requires significant manual effort.

Run an automated duplicate check at the point of submission. If an invoice matches a previously submitted claim, the system flags it immediately and blocks the submission before it enters the approval workflow. The employee is notified at submission, and the approver queue remains clean.

• Detect and block duplicate invoices at submission not during review
• Get alerted before wasting time on an invalid claim
• Approvers only see verified, non-duplicate submissions

• Financial leakage from duplicate reimbursements is structurally prevented
• Approval review time is spent on valid claims only
• Cleaner submission records improve audit readiness

Capture receipts at the point of transaction, not after

Receipt documentation compliance degrades the further in time an employee gets from a transaction. Reminder-based approaches and post-hoc collection workflows produce poor attachment rates, creating gaps in expense records and slowing down approvals.

EnKash now prompts users to upload and link a receipt directly from the transaction confirmation screen, immediately after a card or petty cash transaction completes. The receipt is attached to the correct transaction in the moment, before context fades, and is immediately available in the approval workflow.

• Enjoy higher receipt attachment rates without additional follow-up steps
• Documentation is captured and linked at source, reducing gaps in expense records
• Audit-ready receipts are available by default, not assembled retroactively

Restrict petty cash wallets to approved merchant categories

Petty cash accounts are typically issued for specific purposes — meals, fuel, office supplies — but without a transaction-level enforcement mechanism, employees can spend at any merchant. Policy violations surface only during reconciliation, after the spend has already occurred.

Configure your petty cash wallet with Merchant Category Code (MCC) restrictions. Your Admins define which merchant categories are permitted for each wallet. Example: A wallet configured for fuel cannot be used at a restaurant or entertainment venue. A stationery wallet stays within its designated category. The restriction is applied at the transaction layer, before payment is processed.

What this does for you

• MCC-level restrictions enforce the spend policy at the point of transaction
• Admins configure permitted categories per wallet from the admin panel
• Wallet spend data is pre-categorised by merchant type for reporting

Business Impact

• Policy violations are prevented at transaction time, not identified in reconciliation
• Purpose-specific wallets operate within their defined scope without manual oversight
• Finance teams get cleaner, pre-categorised petty cash spend data

Companies issuing petty cash for specific operational purposes — meals, fuel, field expenses — can now enforce that intent directly at the merchant level, without relying on post-spend audits or employee compliance.

Proactive exception handling and an expanded network for business bill payments

Teams managing business utility and recurring business bill payments across multiple locations face a consistent set of failure modes: failed bill copies, bills stuck in processing, and due dates that pass without action. These exceptions are typically discovered late, after a penalty has been incurred or a service has been disrupted.

Now you can generate automated alerts for failed bill copies, pending bills, and bills stuck in processing states. Overdue bill tracking ensures that exceptions are surfaced proactively, giving teams the lead time to act before consequences materialise. Integration with an expanded payment network improves transaction success rates for utility payments processed at volume, reducing failed transactions that require manual retry.

What this does for you

• Automated alerts for failed bill copies, stuck bills, and overdue items
• Overdue tracking across all bill payment queues
• Expanded payment network coverage for higher utility payment success rates

Business Impact

• Finance teams are notified of exceptions before they escalate to penalties or disruptions
• Fewer failed transactions require manual retry and investigation
• High-volume bill payment operations run with fewer unplanned interruptions

Video KYC for prepaid card activation

Remote KYC has been around long enough that the bar isn't whether you offer it. It's whether it actually completes. Drop-offs mid-session, incomplete data, activation held up waiting on manual review — that's where time was getting lost.

The flow we run today is tighter. Employees verify on mobile, guided step by step, with no ambiguity about what's needed. Sessions complete. Data comes out audit-ready. Cards activate without a queue of exceptions waiting on someone to sort them out.

• KYC completed remotely via a guided mobile video session
• No drop-offs, no incomplete fields, no manual cleanup after the fact
• Structured verification flow produces complete, audit-ready KYC data

Business Impact

• Cards activate faster, without exceptions piling up in a queue
• HR and finance teams stop fielding KYC queries and follow-ups
• The same process that works for ten employees works for a thousand

What these updates change for our customers

• Expense approval chains stay intact when approvers are inactive or have left the organisation
• Employees have visibility from claim submission through to settlement confirmation
• Duplicate invoices are blocked at submission before reaching approval queues
• Receipt documentation is captured at the point of transaction
• Petty cash wallets enforce MCC-level spend restrictions automatically
• Bill payment exceptions are surfaced proactively, with expanded network coverage for higher success rates
• Prepaid card KYC is completed remotely, with no physical documentation required

What we're building towards next

We continue to strengthen the automation, alerting, and control layers across EnKash's expense, petty cash, and payments workflows. The focus remains on reducing the manual effort that accumulates at the edges of financial operations, so teams can manage at scale without absorbing the operational cost of every exception.

Get started with these updates on EnKash

These updates are now live on the EnKash platform. For existing customers, reach out through the support form for help with configuration or access — requests are routed to the right team for quicker assistance.