The updates and functionalities listed below are scheduled by next week of this month (January 2026).
This release introduces a dedicated Pocket MIS for on-the-go visibility into payments and outstanding, major usability improvements in Multi-Level Approvals, and greater configurability in customer pricing display and scheme calculations to better support diverse B2B selling models.
This release does not require any mandatory action from the customers’ end.
1. New Pocket MIS Report for Payments
We’ve added a new Payments Outstanding, Overdue & Ageing Report under Pocket MIS to give teams stronger visibility into collections and ageing reports for all outstanding, leading to better collection planning, faster recovery, and reduced overdue risk.
What this report includes:
Outstanding amount summarized at team level
Customer-level breakup of outstanding dues
Clear visibility of outstanding vs Overdue amounts
Ageing wise bucketed visibility of Outstanding to prioritise follow-ups
2. Improved Approvals Setup Across All Workflows
The Approval Module has received several key enhancements to give companies finer control over complex hierarchies:
Multiple designations at the same approval level can now be configured within an approval hierarchy
User-based trigger conditions are now supported which means Approval flows can vary based on who performs the action, even when all other conditions remain the same
Example: Order approvals can follow different hierarchies depending on the designation of the user collecting the order
Clearer approval actions in the mobile app:
Final approvers will now see only Approve and Reject options
Intermediate approvers (with final-approval rights) can still approve or forward requests further up the hierarchy
3. Enhanced Pricing Visibility & Scheme Calculation for Multiple B2B Selling Scenarios
BeatRoute now supports comprehensive customer pricing visibility to cater to different B2B selling models. These enhancements ensure pricing, margin clarity, and scheme benefits are aligned with how selling actually happens on the ground across different industries & geographies.
Admins can configure whether sales teams see PTR with tax, PTR without tax, or MRP + Customer Margin during order capture
Scheme calculations can now be based on MRP (in addition to the existing PTR-based logic)
4. Miscellaneous Improvements
Customer list pages grouped by Subtype now support direct search by customer name. Search will work across both Subtype name and Customer name.
In the Activity Download file, the AD column name has been updated. The column has been renamed from “Distance Travelled (in meters)” to “Distance Away from Customer (in meters)” for more clarity on what this column actually means.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article