Cutting DSO in Half — How Elate Did It With AR Automation

TL;DR: Days Sales Outstanding is the number of days, on average, it takes a business to turn an invoice into cash. When it climbs, the cause is rarely one slow customer. It's usually a stack of small delays: invoices that go out late or wrong, follow-up that depends on who has time that week, and deals that close in the CRM but take a while to reach billing. This piece walks through where those days come from in a contract-based business, and looks at how one software company, Elate, cut its DSO nearly in half shortly after moving billing and collections onto Monk.

Sponsored Listing by Monk

Key takeaways

• DSO is a lagging number. It tells you cash is slow, not why. The reasons sit upstream, in how invoices are created, sent and followed up.

• Complex contracts are a DSO problem before they are a collections problem. Mid-term upsells, early renewals and custom terms make invoices easy to get wrong, and a wrong invoice is one the customer questions rather than pays.

• Consistent follow-up beats occasional heroics. An invoice that gets the right reminder at the right time is paid sooner than one that waits for the finance team to clear its backlog.

• Elate is a concrete example. After Monk took over contract-driven billing and collections, Elate's DSO fell to nearly half of where it had been, and monthly collections more than doubled in its first full month. That is one company's result, not an average.

• The fix covered the whole path from deal to cash, from closed-won deals in HubSpot through to reconciliation in QuickBooks, rather than a reminder tool bolted onto the end.

What DSO actually measures, and why it creeps up

DSO takes what customers owe you and expresses it in days of sales. The usual calculation divides accounts receivable by credit sales for a period, then multiplies by the number of days in that period. The result is a single figure for how long, on average, your revenue sits as an invoice before it turns into money in the bank.

It's a useful number because it compresses a lot of activity into one line on a dashboard. It's also a frustrating one, because it moves slowly and doesn't explain itself. A finance team often notices DSO rising well after the habits that caused it have set in.

And it tends to drift the wrong way. The average company's Days Sales Outstanding rose to 59 days in 2023, according to Allianz Research. That kind of drift rarely comes from customers deciding to pay later. More often, the invoices themselves are taking longer to become payable.

Where the days actually come from

In a business that sells on contracts, and especially one with a subscription portfolio, the days that add up to a high DSO tend to come from a handful of places:

• Invoices that start late. A deal closes in the CRM, but nobody in finance sees it straight away. The first invoice goes out after the contract was signed, sometimes well after, and the payment clock only starts when it lands.

• Invoices that are wrong. Every customer signed slightly different terms. An upsell lands halfway through a contract. A customer renews early. Each of those changes what should be billed and when, and an invoice that doesn't match what the customer agreed to is one they'll query before they pay.

• Follow-up that runs on one schedule. Different accounts have different payment windows. A single reminder cadence nags some customers too early and reaches others too late, and a team doing it by hand tends to chase whoever is loudest rather than whoever is due.

• No clear line between routine and judgment. When every overdue invoice looks the same, the finance team spends its time chasing all of them equally, instead of stepping in on the few accounts that actually need a conversation.

• Records that disagree. If billing, the CRM and the accounting system each hold a slightly different version of the truth, someone has to reconcile them by hand before anyone can say what is really outstanding.

None of these is dramatic on its own. Together, they add days to every invoice, and DSO is the sum of those days.

The Elate case study

Elate is an AI-native strategy execution platform that helps Chiefs of Staff, COOs and corporate strategists turn plans into results. It sells B2B to nonprofits, education institutions, credit unions and industrial organizations, and as it grew, its subscription portfolio became more and more nuanced.

According to Monk's published case study, the complexity came from exactly the places listed above: varied contract structures, mid-term upsells, early renewals and account-specific billing terms, with precision needed at every step from invoice creation through collections follow-up. The finance team also wanted clearer visibility into where it should step in to escalate or negotiate, instead of chasing every invoice equally. The case study is explicit that the team did not simply need more reminders to customers. It needed a process that could reflect the complexity of Elate's contracts.

Elate chose Monk because it combined contract-aware billing, automated collections, accounting integration and CRM visibility in a single workflow. In practice that meant four things:

• Contract-driven billing. Monk ingested Elate's full contract history, including original agreements, renewals, upsells and amendments, and generated billing schedules across the whole customer base. Invoices are generated from the underlying contract terms, which cuts out manual calculation.

• Automated collections. Monk's AI agent handles outreach on outstanding invoices, keeping follow-up consistent with the right tone and timing for each account. The finance team can see every active conversation and step in at any point, particularly for accounts that need escalation or a more hands-on approach.

• QuickBooks integration. Monk syncs directly with Elate's QuickBooks instance, keeping the general ledger current and removing double entry. Payment reconciliation flows from Monk through to QuickBooks.

• HubSpot deal queue. Closed-won deals from HubSpot show up directly in Monk, so new customers are invoiced promptly instead of waiting for someone in finance to notice them.

The results, as the case study reports them:

Kyle Frederick, Elate's VP of Finance, put it this way: "We expected to improve this over time through better process, discipline, and automation. Our billing operation is complex, and we knew there was a meaningful opportunity to create a more consistent, scalable process. What we didn't expect was how quickly the results would show up. DSO is nearly half of where it was historically, monthly collections more than doubled in our first month, and outstanding A/R is at its lowest point since 2023."

These are Elate's numbers, from Elate's own starting point. They describe one company's experience rather than a typical result.

Why this worked where more reminders wouldn't have

The useful part of the Elate example is where the work sat. Much of what changed happened before a customer was ever chased. Invoices came from the contract, so they matched what each customer had agreed to. New deals reached billing from HubSpot without waiting on a handoff. The ledger stayed in sync, so the finance team was looking at a current picture rather than one it had to rebuild at month end.

Collections then had cleaner material to work with. An invoice that is correct and on time is easier to collect, and follow-up that matches each account's terms arrives when the customer is actually ready to pay. The finance team's time went to the accounts that needed a person, which is the visibility Elate said it had been missing.

That's the general lesson for anyone trying to bring DSO down. The days are rarely lost in the last step. They're lost across the whole path from signed contract to cleared payment.

What to look for if you're trying to cut DSO

If your DSO is higher than it should be and your contracts are anything other than simple, the questions worth asking of any AR tool are fairly specific:

• Does it bill from the contract? Can it take in amendments, upsells and early renewals and produce the right invoice, or does someone still work those out by hand?

• Does it see new deals as they close? If your CRM and your billing don't talk to each other, the first invoice on every new account starts late.

• Does follow-up vary by account? Payment windows and relationships differ from customer to customer. Reminders should too.

• Does it tell you which accounts need a person? A good system handles the routine follow-up and makes the exceptions obvious, rather than handing you a longer list.

• Does it keep your accounting system current? If reconciliation still happens by hand at month end, your view of what's outstanding is always out of date.

On the collections side, Monk's own figure for its collections agent is that Julia reaches customers with a 24% higher response rate than standard dunning. If you want to see what it would take to cut DSO in half with AR automation in your own business, Monk's platform page covers how it runs everything from collections through to cash application, how it handles contract addendums, payment portals and PO mismatches, and when it escalates an invoice to your team.

Who this fits

This kind of change matters most for a business whose revenue runs on contracts that aren't all the same. A company with a handful of customers on identical terms can keep billing and follow-up in a spreadsheet and lose very little. A large enterprise may already have a team whose whole job is this. The gap is in the middle: a growing company, often selling subscriptions, where every new deal adds a slightly different set of terms and the finance team is small enough that billing and collections compete with everything else on its plate.

That describes Elate. It also describes a lot of B2B software companies once their sales-led revenue starts to outgrow their self-serve billing. If that's your situation, our guide to AR for AI-native SaaS covers how net terms and usage billing change collections, and our piece on cash application automation covers what happens once payments start landing and need to be matched back to the right invoices.

Frequently asked questions

What does it mean to cut DSO in half?

It means the average time between issuing an invoice and collecting the cash falls to roughly half of what it was. Elate's case study describes its DSO as cut nearly in half shortly after implementation, or in Kyle Frederick's words, "nearly half of where it was historically."

Is cutting DSO in half a typical result?

Not necessarily. Elate's result reflects its own starting point and the specific problems it had, many of which were about billing accuracy rather than chasing. Across its customers, Monk reports a 40% average reduction in DSO. How far any one business moves depends on where its days are actually being lost.

Can't we just send more reminders?

Elate's finance team concluded that more reminders weren't the answer. If invoices go out late or don't match the contract, extra reminders mostly produce extra questions. Getting the invoice right first, and then following up consistently, is what moves the number.

How long does it take to see a change?

Elate's monthly collections more than doubled in its first full month on Monk, and its DSO fell shortly after implementation. Monk's own figure is: onboard in less than one week, see results in your first month. In practice the pace also depends on how quickly you can connect your billing, CRM and accounting systems and hand over your contract history.

Does this replace the finance team?

No. Elate's finance team kept full visibility into every collections conversation and could step in at any point. What changed was where its time went: less on routine follow-up and manual entry, more on the accounts that genuinely needed a person.

The bottom line

DSO comes down when invoices are right, on time and followed up consistently, and it rarely comes down just because a team chases harder. Elate's experience is one concrete example. With billing driven by its contracts, new deals flowing in from HubSpot, collections automated and QuickBooks kept in sync, its DSO fell to nearly half of where it had been and monthly collections more than doubled in its first full month. If you want to see how that would work against your own contracts, bring your most complicated customer agreement, the one with the mid-term upsell and the custom payment terms, and book a Monk demo to walk through it live.