Understand DSO
Interpret countback DSO over complete months and connect changes to receivables and billed revenue.
Updated
In short
DSO estimates how many days of revenue cover end-of-month receivables. Billabex uses countback, walking backward through billed months while excluding the incomplete current month and partial release month. Movements are converted into analytics currency with historical rates; compare only points calculated on equivalent windows.
Expected result
You understand each point period and investigate change through corresponding receivables and revenue.
Before you start
- Wait for at least one complete month after analytics availability.
- Check base currency and displayed range.
Procedure
- Open Management > DSO and read first available date.
- Identify months omitted because partial or still in progress.
- Compare several complete months rather than one point.
- For an increase, inspect month-end receivables and earlier billed revenue.
- Cross-check collections and aged balance before attributing a cause.
What Billabex does
Calculation rebuilds receivables at each month end from opening balance and signed movements, then counts revenue backward. One unresolved conversion stops the complete result.
If the result is not what you expected
- Current month is never a final DSO point.
- A recently activated organization has no reconstructed earlier history.
- A DSO decline alone does not identify which action produced collections.