What it does
A screening engine for an Indian pharma company with about 500 field sales staff. Every claim-day is checked against that person's doctor-visit records and a route fare chart. Claims that match are cleared. The rest land in a review sheet with the amount, the reason and what the admin team should do next.
The problem
The company pays out around ₹50 lakh a month in field expense claims. An admin team checked them by hand, which took 15 to 20 person-days every month, and the result depended on who did the checking.
Approach
I wrote the admin team's own checks down as 25 rules, each measured by a script that can be re-run on any month. Claims are joined to visit records and the fare chart, places are matched carefully, and anything unclear goes to a person instead of being deducted automatically. Careful matching mattered: naive place matching would have produced ₹8.5 lakh of false deductions.
- Input
- Rules or code
- Person decides
- Result
Screens
Swipe sideways to see the whole screen.
Client work is shown under confidentiality agreements: no client names, and screens are recreated with sample data.
Stack
- Python
- BigQuery
- Cloud Storage
- Rule engine
