Rahul
Patwekari

In over 15 years of working in finance, I've reviewed hundreds of dashboards, sat through countless executive reviews, and debated dozens of KPIs. But when it comes to Accounts Receivable, one metric always rises to the top: Days Sales Outstanding (DSO).

DSO measures the average number of days it takes your organisation to collect payment after a sale. At its simplest: DSO = (Accounts Receivable ÷ Total Credit Sales) × Number of Days. But its simplicity is deceptive. DSO is a window into the health of your entire business — your sales terms, your invoicing accuracy, your customer relationships, and your collections discipline.

Why DSO Matters More Than You Think

A high DSO means cash is tied up in receivables rather than being available for operations or investment. Even a profitable business can face a liquidity crisis if DSO is poorly managed. I've seen businesses report strong revenue while quietly building dangerous levels of aged debt. Conversely, a low DSO signals operational efficiency — clean billing, satisfied customers, and a proactive collections team.

The Real Drivers of High DSO

High DSO rarely has a single cause. The most common contributors I've encountered: invoicing errors that give customers a reason to delay; unclear payment terms that create ambiguity; weak collections follow-up without a structured escalation cadence; unresolved disputes sitting in inboxes for weeks; and missed early warning signs of customer financial stress.

How to Systematically Reduce DSO

1. Fix the invoice at source. Send correct invoices the first time. Build a pre-billing checklist validating PO numbers, pricing, tax codes, and supporting documents.

2. Standardise your collections cadence. A reminder 5 days before due date, a follow-up on the due date, an escalation 7 days overdue. Automate where possible. Consistency is everything.

3. Segment your receivables. Use aging buckets (0–30, 31–60, 61–90, 90+) to prioritise effort on the highest-risk, highest-value accounts first.

4. Involve sales. A call from the account manager alongside the AR team is far more effective than a collections email alone for strategic accounts.

5. Build a real-time DSO dashboard. When I implemented Zoho-integrated dashboards at Searce, visibility alone changed team behaviour. You can't improve what you can't see.

Final Thought

DSO is a lagging indicator — by the time it rises, the problem has already happened. The best AR leaders treat DSO as a symptom and spend most of their energy fixing the upstream processes that drive it. Watch it weekly, understand its drivers, and build a culture where early escalation is celebrated, not avoided.

When I started my career in finance, automation meant building a better Excel macro. Today, it means designing end-to-end digital workflows that eliminate manual touchpoints entirely. The journey from one to the other is one I've lived firsthand across multiple organisations and roles.

Start With Kaizen: The Philosophy Before the Technology

Before you automate anything, you need to understand it deeply. During my time at Flex, I pursued Kaizen certification to bring structured improvement methodology to our AR and inventory accounting processes. The core discipline is simple: map the current state, identify waste, design the future state, implement incrementally, measure the result. Automation applied to a broken process just speeds up the production of errors. Fix the process first.

The Automation Maturity Ladder

Level 1 — Standardisation: Document processes, create SOPs, eliminate variation. Level 2 — Templates & Tools: Excel templates, pivot tables, standardised report formats. Level 3 — Macro & Script Automation: VBA, Power Query, Python. Level 4 — RPA: Software bots that mimic human actions across systems. Level 5 — Intelligent Automation: RPA combined with AI for exception handling and prediction. Most finance teams jump to Level 4 and wonder why adoption fails. Levels 1–3 must be solid first.

My RPA Experience: Sales Order Creation at Flex

One of the most impactful automation projects I led was the RPA implementation for sales order creation at Flex — logging into SAP, extracting data from multiple source files, validating fields, creating orders, and confirming back to the business. After a Kaizen exercise to eliminate unnecessary steps, we deployed a bot for the full workflow. Processing time dropped by over 70%, error rates fell to near zero, and the team was freed to focus on exception handling that genuinely required human judgment.

Dashboard Automation at Searce

At Searce, the challenge was reporting. Multi-entity AR data in disconnected systems, with leadership needing a consolidated real-time view. We built automated Zoho dashboards pulling from multiple sources, applying business logic, and delivering executive-ready views updated in real time — without a single manual export. What once took half a day to compile weekly became available to every stakeholder at any moment.

What Finance Leaders Get Wrong

The biggest mistake: treating automation as an IT project. It's not. Finance professionals understand the process, the exceptions, the risks, and the business logic. IT provides the tooling. When those roles get reversed, you get technically correct solutions that don't reflect operational reality. The second mistake: automating for automation's sake. Every initiative should start with a clear problem — what is this manual effort costing us in time, errors, or both?

Where to Start

Identify your top 3 most repetitive, high-volume manual processes. Map each end-to-end. Apply Kaizen to eliminate waste. Start with the simplest version of automation. Measure the before and after. Then scale what works. Automation is not a destination — it's a practice.

I've built, reviewed, and presented MIS reports across six organisations and four continents. And I've noticed a consistent pattern: the reports that get used look almost nothing like the reports that get sent. The average MIS package is a 40-slide deck compiled over two days — and gets skimmed in four minutes. The executive extracts one or two numbers and moves on. The rest is noise. This is a failure of design, not data.

Understand What Executives Actually Need

Before you build a single report, ask: what decision does this need to support? Executives don't read reports for information — they read them to make decisions or confirm that no decision is needed. Every piece of content should either flag an issue requiring a decision or confirm a metric is on track. If it does neither, it doesn't belong.

The Three-Layer Framework

Layer 1 — The Headline View (1 page): 5–7 critical metrics with traffic-light indicators (RAG). No explanations — just status. This is what a CEO looks at in the first 30 seconds.

Layer 2 — The Analysis View (3–5 pages): For each red or amber metric: what happened, why it happened, what action is being taken. One chart per page. Clear ownership and timelines.

Layer 3 — The Detail View (Appendix): Full data for the finance team and anyone who wants to drill down. Most executives never open it — and that's fine.

Common Mistakes That Kill MIS Reports

Reporting the past without the forward view. "Revenue was ₹12Cr in March" is information. "Revenue was 8% below forecast due to a delayed payment now collected — full-year outlook unchanged" is insight. Too many metrics. When everything is highlighted, nothing is. Pick 5–7 KPIs and report them consistently. Inconsistent formats. Standardise ruthlessly — same layout, same order, same colour codes every period. Late delivery. A perfect report delivered after the executive meeting is worthless. Timeliness is a feature.

Lessons From the Field

At Capgemini, I found that format preferences mattered far less than consistency and reliability of data. Build trust in your numbers first, then worry about presentation. At Razor Group, managing 200+ accounts across four continents, the solution was tiered dashboards — a global view for the CFO, regional views for directors, account-level detail for the AR team. Same data, different lenses. Every stakeholder saw exactly what they needed and nothing more.

The One Rule That Changes Everything

Write the conclusion first. Before you build a single chart, write the three sentences you want the executive to walk away with. Then build the report to support those sentences. This forces clarity and prevents the common trap of building a data dump and hoping the reader finds the insight. Executives are decision-makers, not analysts. Your job is to make their decisions easier — not to demonstrate how much data you have access to.