Receivables Analytics
Interpret collection performance, aging movement, and payment speed with the correct period, denominator, and currency limits.
Receivables Analytics is the deeper collection-performance view behind the Receivables overview. It separates effectiveness signals from aging and payment-speed signals. You can then diagnose why cash arrives earlier or later.
Before You Start
- Confirm that you selected the correct team.
- Correct invoice issue, due, sent, paid, and status dates before you read the speed metrics.
- Record payments and customer links consistently.
- Choose one reporting period for the review.
- Reconcile multi-currency balances outside the dashboard before you use the results for financial reporting.
Open Receivables Analytics
- Open Receivables.
- Select Analytics.
- Choose a reporting period or Custom range.
- Review Collections performance first.
- Continue to Aging & payment timing.
Collections Performance
Collection Curve
Collection Curve shows the cumulative percentage of receivables collected as the number of days since invoice issue increases. The headline is the final collected percentage represented by the returned series.
Use it to compare collection speed, not only the final rate. A curve that rises later shows slower cash conversion even when it reaches a similar percentage at the end.
Collection Effectiveness
Collection Effectiveness is the all-time share of invoice records that Eigenn marks paid now:
paid invoice count ÷ total invoice record count
The total includes paid, unpaid, overdue, draft, scheduled, and canceled invoices. This card does not follow the selected period and is not amount-weighted.
Collection Effectiveness Index
Collection Effectiveness Index (CEI) compares receivables collected with receivables available to collect during the selected period. The card shows it as a collected-versus-outstanding share.
Use CEI with the collection curve. CEI summarizes the period. The curve shows how collection accumulates over time.
Recovery Rate
Recovery Rate shows the recovered percentage for aging buckets in the selected period. The headline is the average of the bucket rates shown, not a single dollar-weighted recovery calculation.
Examine the bucket bars before you use the average. A strong newer bucket can hide weak recovery in older balances.
Aging and Payment Timing
Aging Movement
Aging Movement shows how receivables shifted across aging buckets during the selected period. The headline is the total charted movement magnitude.
Use it to find exposure that moves into older buckets. It is different from AR Aging, which is the current as-of-today balance by bucket.
Payment Lag
Payment Lag measures days between invoice due date and payment for the selected period. It shows:
- Average days late
- Median, or 50th percentile
- 90th-percentile lag
A small number of very late payments can distort the average. Compare it with the median and the 90th percentile before you decide that the usual customer changed behavior.
Days Sales Outstanding
Days Sales Outstanding (period) estimates the average days that receivables stay outstanding during the selected period. Lower values usually show faster collection. Interpret the number with invoice volume, terms, and customer mix.
Days to Pay
Days to Pay (DSO) is the all-time average number of days from issue date to paid date across paid invoices. The line below it shows the number of paid invoices that Eigenn used.
Despite the similar names, Days Sales Outstanding (period) and Days to Pay (DSO) do not use the same cohort or time behavior.
Period Behavior Reference
| Metric | Uses selected period | Uses currency selection when available |
|---|---|---|
| Collection Curve | Yes | No currency input |
| Collection Effectiveness | No, all time | No |
| Collection Effectiveness Index | Yes | Yes |
| Recovery Rate | Yes | Yes |
| Aging Movement | Yes | No currency input |
| Payment Lag | Yes | No currency input |
| Days Sales Outstanding (period) | Yes | Yes |
| Days to Pay (DSO) | No, all time | No |
When you change the period and compare a period metric with an all-time metric, you can see an apparent contradiction. It is only a cohort difference.
Recommended Review Sequence
- Select the period and record DSO, CEI, payment lag, and the final collection-curve percentage.
- Compare all-time Collection Effectiveness and Days to Pay only as long-run baselines.
- Examine recovery by aging bucket instead of its average alone.
- Find movement into the oldest aging buckets.
- Return to Receivables → Overview.
- Examine current AR Aging and Do next.
- Open Invoices and confirm the records that drive the change.
Read Common Patterns
DSO rose but Days to Pay did not
DSO follows the selected period. Days to Pay is all-time. A recent collection slowdown can move DSO before it changes the all-time average by much.
CEI is weak but Collection Effectiveness looks acceptable
CEI evaluates the collectible receivables of the selected period. Collection Effectiveness counts all invoice records ever recorded, with drafts, scheduled, and canceled records. Investigate the open balances of the period and the all-time status mix separately.
The average payment lag is much higher than the median
A smaller group of very late payments pulls the average upward. Use the 90th percentile and the invoice list to find the tail. Do not change policy for every customer.
Recovery rate is strong overall but old AR increases
Examine each recovery bucket. Newer balances can recover while 61–90 or 90+ day balances continue to age.
Data and Currency Limits
- Many analytics cards can return an empty state for a new team or a period with no records that qualify.
- A zero with no population behind it is not proof of good performance.
- Cards without a currency input can aggregate values without a user-selected currency filter.
- Current invoice aggregates can combine raw amounts from many currencies under one displayed currency.
- Customer, invoice, and payment dates set the metrics. A bank transaction alone does not repair a missing paid date or status.
- Analytics are operational indicators, not GAAP, tax, or statutory reports.
- The page does not give confidence intervals or statistical significance tests.
Verification Checklist
Before you report a metric, confirm these points:
- The selected period and currency are visible and are the ones that you want.
- The source invoice count is non-zero.
- Paid invoices have both the correct status and the correct paid date.
- Issue and due dates are usable.
- You use the same currency or a reconciled conversion method.
- Recent corrections had time to appear.
- You know whether the card is current, period-based, or all-time.
Troubleshoot
A card shows no data
Expand the period. Then confirm the necessary invoice dates and statuses. New teams and periods with no payments that qualify can correctly return an empty result.
DSO shows zero on a new team
Check for paid and outstanding invoices with valid dates. Treat the value as no data until an invoice population exists behind it.
The same period produces different totals across cards
The cards measure different populations. Some are all-time or current, not period-based. Use the period reference table and the label below each card.
A multi-currency total looks too high
Separate invoices by currency in the invoice workspace. Reconcile them with an approved rate. Do not assume that every receivables card does the conversion.
A recent payment has not changed the chart
Confirm the invoice and the payment record. Then refresh. If the source record is correct, give the analytical aggregation time to update before you change it again.