ID734 - Accounts Receivable (Power BI) Overview & Sample:

ID734 is a Power BI report that presents your entire accounts receivable position in one place: executive exposure, collector worklists, aging detail, billing accuracy, payment portal performance and customer-level deep dives. Optional write-back and reminder-email actions directly from the report.

Jump to a specific section by clicking a link

Overview | Samples | Variables | Alert Functionality | Power BI Reporting | Related Alerts | Webinar

Click to Subscribe and Download Template

Overview

Overview

ID734 is a Power BI report that provides accounts receivable data points so you can easily analyze your AR. You have the option to add-on a Power Platform feature that allows you to trigger a reminder email to your customers, and write back options into EA, all from inside this AR Power BI report. No per-user Power Apps or Power Automate licenses are needed, only a Power Automate Premium license for the CEOJuice account in your tenant.

If you use a combination of ID437 to email invoices to customers as they are created, ID800 to chase when invoices are past due, and ID669 online payment links that allows your customers to pay you online (you recover credit card fees), and this Power BI report, it will automate the majority of your AR processes.

Type of Output: On Demand Power BI Report

*  *  *

Sample

Sample

The Landing Page below is the entry point to the report. Each of the nine sections links straight to its pages, and the revision log on the left records what changed in the current release.

00 – Landing Page

01 – Executive A/R Scorecard

05 – Open Aged A/R

04 – Collector Worklist

Every page in the report is shown and documented individually in the Power BI Reporting section below.

*  *  *

Variables

Variables

Variables are set on the CEO Juice website subscription page for ID734.

*  *  *

Alert Functionality

Alert Functionality

-See here for getting Power BI in place.

-Click here to download the file

For ECi Hosted clients: We are working with ECi to open up our access so we can set an ODBC connection for you. If you are interested, then please provide us the public static IP address for your company network so that ECi can whitelist it to allow us access.

Data refresh and scope

• Every page header reports the Last Refresh timestamp and states in plain English which filters are currently applied and which are not, so a screenshot is never ambiguous about its own scope.
• Aging is always calculated as of the last refresh and ignores the date slicer. Only period measures — DSO, revenue, payments, billing accuracy and the rolling averages — respond to the date slicer.
• Total Due = Due less Unapplied cash. This is stated in the header of every page where it applies.
• Invoices dated after today are excluded from the aging pages.

A/R Email Actions & Write-Back

The A/R Email Actions panel appears on the drill-through pages and on the exception pages that support outbound contact — Missing A/R Contact / Contact Info, the Accounts with Unapplied Credit Memos drill-through, Open Invoices, Invoice Details and the BillTo Profile.

The panel shows how many rows and what value are currently in scope, and offers three independent recipient toggles — AR Rep, AR Contact and Decision — each set to Yes or No. A deliberate "Unlock to send" control has to be released before anything is sent, which prevents accidental triggering while you are still filtering.

This is the CEO Juice custom visual introduced in the current revision. It provides the reminder-email and e-automate write-back functionality using a Power Automate flow behind the scenes, so report users don't need their own Power Apps or Power Automate licenses, only a Power Automate Premium license for the CEOJuice account in your tenant. To use it, set the Power Platform variable to Yes.

Notes

• The CEOJuice assigned O365 account must have 'Send As' access to the AR Email specified in the ID734 Variables on the CEO Juice site.
• If ALL of the recipient toggles are set to "No", the email will send to the current user instead of the customer.
• Use the back arrow to reset send protection and avoid accidental triggers.

*  *  *

Power BI Reporting

Power BI Reporting

This section documents every page in the report in the order it appears on the Landing Page. For each page you will find its Purpose, Expected Outcome and How to Read This Page content — the same text that appears in the report's own on-page documentation — together with a screenshot and any controls or measures specific to that page.

How Every Page Works

Every page in ID734 follows the same two conventions. They are shown here once using the Executive A/R Scorecard as the example, and they behave identically on every other page in the report.

1. The Filter Panel

Click the filter icon in the top-right corner of any page to slide out the full filter panel. Filters are grouped by the level they act on, so you always know what a selection is actually filtering:

• CUSTOMER LEVEL FILTERS – Customer Branch, AR Rep, Sold To Contact, Customer Status, Customer Type, a Search Customers box and a Customer picker.
• BILL-TO LEVEL FILTERS – BillTo Branch, Bill To On Hold?, Bill-To Status, Bill-To Type, a Search Bill-To Customers box and a Bill To Customer picker.
• INVOICE FILTERS – Branch, Manager / Sales Rep, Transaction Type, Order Type, Module and Creator.

Filter panel – slide-out from the icon in the top-right of any page

In addition to the panel, each page carries Quick Access Filters in the header bar that are relevant to that page only — for example Aging Basis and Aging Period on the aging pages, DSO Target on the KPI pages, and Rolling Months on the trend pages.

The header of every page also reports the Last Refresh timestamp and a plain-English statement of which filters are currently applied, so a screenshot is never ambiguous about its own scope.

2. On-Page Documentation

Click the "?" icon in the top-right corner of any page to slide out that page's own documentation. Every page carries the same three sections, written for that page specifically:

• Purpose – what the page is for, in one or two sentences.
• Expected Outcome – what a reader should be able to do or decide after reading the page.
• How to Read This Page – the interpretation rules, caveats and traps specific to that page.

On-page documentation – slide-out from the "?" icon in the top-right of any page

Some pages carry additional blocks. The Executive A/R Scorecard adds a TAKE AWAYS section that reads the current numbers back in narrative form, and the Collector Worklist adds a "How Suggested Action decides" block that documents the decision rules behind its Suggested Action column.

The Purpose, Expected Outcome and How to Read content for every page is reproduced in the Power BI Reporting section below, so this document and the report itself always say the same thing.

00 – Landing Page

The Landing Page is the navigation hub for the whole report. It carries the report ID and revision, the Last Refresh timestamp, a Documentation / Webinar button, and a colour-coded revision log so you can see at a glance what is new, what was rebuilt and what is unchanged in the current revision. Report pages are grouped into nine themed sections:

EXECUTIVE – Leadership view of exposure, risk and direction of travel — no invoice detail required.

• Executive A/R Scorecard
• Historical Open A/R
• A/R Risk & Concentration

OPEN AGED A/R – Where the balance sits today, who to work first, cash not yet applied, and outbound statement runs.

• Collector Worklist
• Open Aged A/R
• Open Aged A/R Invoices
• Unapplied Payments (ID717)
• Accounts with Unapplied Credit Memos

SUMMARIES – Invoice statistics and what is coming due, for a quick read on volume and near-term cash.

• A/R Invoice Statistics (ID504)
• Invoices Coming Due (ID477)

BILLING ACCURACY – How often invoices go out correctly — overall, by admin agent, and by transaction type.

• Billing Accuracy Summary
• Billing Accuracy by Admin Agent

EXCEPTION REPORTS – Accounts and invoices that need a human: missing data, missing follow-up, unusual behaviour.

• Missing A/R Contact / Contact Info
• A/R Past Due Customers without selected A/R Activities Tasks
• Voided Invoices missing A/R Tasks / Notes
• A/R Past Due More Than Usual

A/R REVENUE BREAKDOWN – Revenue trends across the book, by Bill To customer and by Ship To location.

• Revenue Summary & Trends
• Revenue :: BillTo Customers
• Revenue :: ShipTo Locations

PAYMENTS PORTAL – Payment volume by customer and method, and what the portal is costing in fees.

• Payments Summary
• Payments by Bill To & Method
• Processor Fees Overview

PERFORMANCE BILLING KPIS – DSO, days-to-pay trajectory, AR Rep performance and how collections workload is distributed.

• Days Sales Outstanding (DSO)
• Rolling Averages Due / Bill Days to Pay
• Rolling Averages Due / Bill Days to Pay Trends
• Rolling Averages by Transaction Type
• Collections Workload by Assignee
• A/R Rep Performance

CUSTOMER DEEP DIVE – One account at a time — full profile, plus notes and tasks across every active customer.

• BillTo Profile

00 – Landing Page

Revision log – what changed in rev. 2026.09.25

The Landing Page colour-codes each page link: green for new this revision, blue for rebuilt this revision, and black for no change this revision.

• Report remodeled & revamped
• Added Executive Section (Executive A/R Scorecard, Historical Open A/R, A/R Risk & Concentration)
• Added Collectors Worklist under the Open Aged A/R section
• Added Custom Visual developed by CEO Juice for write-back functionality, which eliminated the need for a Power Apps license
• Added missing filters
• Added Quick Access Filters relevant to page context
• Bug-fix on the Open Invoices dataset for related ARAPReceivablePayables not tied to ARInvoices
• Added On-Page documentation

Jump to a report page

00 – Landing Page

Executive: 01 – Executive A/R Scorecard  |  02 – Historical Open A/R  |  03 – A/R Risk & Concentration

Open Aged A/R: 04 – Collector Worklist  |  05 – Open Aged A/R  |  06 – Open Aged A/R Invoices  |  07 – Unapplied Payments (ID717)  |  08 – Accounts with Unapplied Credit Memos

Summaries: 09 – A/R Invoice Statistics (ID504)  |  10 – Invoices Coming Due (ID477)

Billing Accuracy: 11 – Billing Accuracy Summary  |  12 – Billing Accuracy by Admin Agent

Exception Reports: 13 – Missing A/R Contact / Contact Info  |  14 – A/R Past Due Customers without selected A/R Activities Tasks  |  15 – Voided Invoices missing A/R Tasks / Notes  |  16 – A/R Past Due More Than Usual

A/R Revenue Breakdown: 17 – Revenue Summary & Trends  |  18 – Revenue :: BillTo Customers  |  19 – Revenue :: ShipTo Locations

Payments Portal: 20 – Payments Summary  |  21 – Payments by Bill To & Method  |  22 – Processor Fees Overview

Performance Billing KPIs: 23 – Days Sales Outstanding (DSO)  |  24 – Rolling Averages Due / Bill Days to Pay  |  25 – Rolling Averages Due / Bill Days to Pay Trends  |  26 – Rolling Averages by Transaction Type  |  27 – Collections Workload by Assignee  |  28 – A/R Rep Performance

Customer Deep Dive: 29 – BillTo Profile

Drill-Through Pages: A/R Notes  |  A/R Tasks  |  Bill To Tasks  |  Open Invoices  |  Invoice Details

Executive

01 – Executive A/R Scorecard
What we are owed, how risky it is, and which way it is moving

Purpose
Give the CFO and CEO a single-glance read on what the business is owed, how risky that balance is, and which way it is moving — without exposing invoice detail.

Expected Outcome
A leadership reader can answer four questions in under a minute: how much are we owed, how much of it is late, how fast are we collecting against target, and how exposed are we to any one customer. They should leave knowing whether A/R needs attention this quarter, not which invoice to chase.

How to read this page

• Read the five cards left to right — how much, how overdue, how slow, how concentrated, how much we billed. The sequence is deliberate: each one qualifies the one before it.
• Card colour is the alert, not the value. Orange is the primary figure, green is inside tolerance, amber is watch, red is outside tolerance.
• Every card carries a prior-year comparison. Read the delta before the level — a large balance that is falling is a different situation to a small one that is rising.
• The trend chart shows level and direction. The bullet shows position against target. Neither means much alone.
• Aging figures ignore the date slicer by design. Only DSO and revenue respond to it, because only they are period measures.
• There are deliberately no drill buttons. If leadership can reach invoice detail from here they will read the report as an operational tool and the framing collapses.

TAKE AWAYS

This page carries an additional TAKE AWAYS block in its on-page documentation, which reads the current figures back as narrative — open A/R and past-due share, DSO against target and the working capital that closing the gap would release, top-5 concentration and the concentration index, customers whose exposure ratio exceeds their trailing revenue, the aged share over 90 days on a like-for-like basis, and the value of receipts still sitting unapplied.

01 – Executive A/R Scorecard

02 – Historical Open A/R
Open receivables reconstructed at any point in the last 24 months

Purpose
Show what the business was owed at any month end over the last two years, reconstructed from invoices less applied cash rather than from a stored snapshot.

Expected Outcome
A reader can separate seasonality from deterioration, see whether the current balance is normal for the time of year, and judge whether the book is structurally growing or simply oscillating.

How to read this page

• Compare the two lines before reading either. A balance above last year in every month is growth; above in some and below in others is seasonality.
• Read level and DSO together. Balance up with DSO flat is growth; balance up with DSO up is slippage.
• The reconciliation card is on the page deliberately. If it drifts below about 95%, stop trusting the history until the variance is explained.
• Snapshots are month end. Anything intra-month will not appear — use Open Aged A/R for today.

On the page

Cards cover Total Open A/R, Peak Exposure and Trough Exposure within the 24-month window, the Aged > 90 share now against last year, and a Reconciliation percentage with its variance against live aging. The Watchlist table lists the top 10 largest exposures with Total Due, reconstructed Open A/R, reconciliation percentage and peak / trough exposure per customer.

02 – Historical Open A/R

03 – A/R Risk & Concentration
Which customers could hurt us, and how much of the book they represent

Purpose
Rank customers by the risk they represent rather than by the size of their balance, and quantify how exposed the business is to losing any one relationship.

Expected Outcome
A reader can name the accounts that warrant credit review, state what proportion of revenue would disappear if the largest relationship ended, and see which customers are paying materially slower than their own history.

How to read this page

• Sort by exposure ratio, never by balance. A $245K balance on a $149K customer matters far more than a $554K balance on a $5.3M customer.
• Read the trajectory column beside the ratio. A high ratio that is improving is a known slow payer being worked; a high ratio deteriorating is an emerging loss.
• Apply the minimum balance slicer.
• The concentration curve answers a different question to the table, not who is risky, but how few customers the business depends on.
• Right-click any row to open that customer's Bill To Profile.

Key measure

Exposure Ratio = Total Due ÷ trailing 12-month revenue. Above 1.00 the customer owes more than they buy in a year. The page also carries a Herfindahl index with a plain-English interpretation, a Top N Customers selector, a DSO Target control, and a Balance Without Pending Task card that sizes the book nobody is working.

03 – A/R Risk & Concentration

Open Aged A/R

04 – Collector Worklist
What to work today, ranked by a priority score rather than by balance

Purpose
Turn the open ledger into a ranked list of what to work today, using a composite score rather than balance alone.

Expected Outcome
A collector opens the page and works top down without having to reconcile five columns in their head. They finish the day having touched the highest-risk accounts, not simply the largest.

How to read this page

• Work top down. The score already weighs balance at risk, age, exposure, deterioration and silence together.
• Use Days Since Last Contact as the tie-break. Two accounts with the same score but one showing blank is not a close call — blank means never contacted.
• Suggested actions derive from the same measures, so they will be wrong on accounts with context the model cannot see. Treat them as a starting point.
• Filter by AR Rep to run this as an individual queue rather than a team list.

How Suggested Action decides

First match wins, in this order: (1) No A/R contact → Establish contact. (2) Exposure ≥ 1.0 → Credit hold review. (3) Never contacted and no task → Escalate to manager. (4) No task → Assign owner. (5) Unapplied cash > $1,000 → Apply unapplied cash. (6) Trajectory ≥ +100 days → Call – deteriorating. (7) Oldest invoice ≥ 360 days → Payment plan. (8) Silent > 30 days → Follow up. (9) Otherwise → Monitor. Priority Score itself blends balance at risk, days overdue, exposure ratio, days-to-pay deterioration and days since last contact.

04 – Collector Worklist

05 – Open Aged A/R
Where the open balance sits today – by aging bucket and by BillTo Customer

Purpose
Show where the open balance sits today by aging bucket and by customer, on a user-selectable aging basis.

Expected Outcome
A collector can see total exposure, how it is distributed across buckets, which customers carry it, and whether anyone is already working each account — then move straight to that customer's invoices or notes.

How to read this page

• Read the cards left to right for exposure then distribution. Shape matters more than any single figure — a book weighted to Current is healthy regardless of size.
• Check the aging basis caption before drawing conclusions. Due Date and Invoice Date produce the same total but very different distributions.
• Sort the table by a specific bucket column rather than Total Due to build a worklist for one bucket. Over 360 surfaces write-off candidates; 61 to 90 surfaces what is about to become serious.
• Check A/R Tasks before working an account. A large aged balance with no pending task is an account nobody owns.
• Read Unapplied before escalating. A customer with past-due balance and a large unapplied credit may not owe what the aging implies.
• The Invoice Customers column shows fan-out. Anything above 1 means the Bill To is a lease company or collective and the end customer is someone else.

Drill-through buttons

A/R Notes, A/R Tasks, BillTo Tasks, Unapplied Payments, Open Invoices and BillTo Profile. The Aging Buckets slicer filters to BillTo Customers with open amounts in the selected buckets without excluding their other open invoices in non-selected buckets. Total Due = Due less Unapplied cash.

05 – Open Aged A/R

06 – Open Aged A/R Invoices
Every open invoice behind the aging, at transaction level

Purpose
Show where the open balance sits today by aging bucket and by customer, on a user-selectable aging basis — at individual invoice grain rather than customer grain.

Expected Outcome
A collector can see total exposure, how it is distributed across buckets, which customers carry it, and whether anyone is already working each account — then move straight to that customer's invoices or notes.

How to read this page

• Read the cards left to right for exposure then distribution. Shape matters more than any single figure — a book weighted to Current is healthy regardless of size.
• Check the aging basis caption before drawing conclusions. Due Date and Invoice Date produce the same total but very different distributions.
• Sort the table by a specific bucket column rather than Total Due to build a worklist for one bucket. Over 360 surfaces write-off candidates; 61 to 90 surfaces what is about to become serious.
• Check A/R Tasks before working an account. A large aged balance with no pending task is an account nobody owns.
• Read Unapplied before escalating. A customer with past-due balance and a large unapplied credit may not owe what the aging implies.
• The Invoice Customers column shows fan-out. Anything above 1 means the Bill To is a lease company or collective and the end customer is someone else.

On the page

The detail table carries Invoice Customer, Bill To, Billed Elsewhere, Invoice #, Invoice Total, Amount Due, Invoice Date, Due Date, Aging Period, Transaction Type, Creator, Remarks and A/R Tasks. The header caption quantifies how many open invoices bill to a different entity than the invoice customer. An Invoice Details drill-through is available from any selected row.

06 – Open Aged A/R Invoices

07 – Unapplied Payments (ID717)
Cash received that has not yet been matched to an invoice

Purpose
Surface cash received but not yet matched to an invoice, so it is cleared before anyone chases the customer.

Expected Outcome
The team clears held cash before running collection calls, and can tell a matching-rule failure from a keying delay.

How to read this page

• Clear this page before running collection calls. Chasing a customer who has already paid is the fastest way to lose credibility.
• Sort by days held, not by amount. A small receipt held 88 days is a process failure; a large one held 3 days is normal.
• EFT and ACH should auto-apply. Anything unapplied on those methods points at a matching-rule problem, not a person.
• Repeat names in the Creator column indicate a training issue rather than isolated mistakes.

On the page

Cards age the held cash across the same buckets used elsewhere, each showing receipt count and Bill To count. The detail table is sorted oldest first and carries Customer, Bill To, Receipt #, Unapplied, Days Held, Receipt Date, Check / Method, Method and Creator. Companion visuals break unapplied cash down by method and by age band. A Method quick filter sits in the header.

07 – Unapplied Payments (ID717)

08 – Accounts with Unapplied Credit Memos
Customers holding credits that have not been offset against open invoices

Purpose
Identify customers holding credits that have not been offset against open invoices.

Expected Outcome
Month-end reported A/R is reduced without any cash moving, and customers in net credit stop appearing on collection queues.

How to read this page

• Use this before month end. Applying credits is the cheapest way to reduce reported A/R.
• A negative Total Due means the customer is in credit overall — those accounts should never appear on a collection list.
• Read Credit Memos as a component of Due, not as an extra deduction. Subtracting it again double-counts.

On the page

The header quantifies the total credit value, how many accounts hold it, and how many of those are in net credit and owe nothing. The aging table carries a Credit Memos column alongside the standard buckets. Selecting a row enables the "Open Invoices / Notify Customer: Unapplied Credit Memos" drill-through, shown below.

08 – Accounts with Unapplied Credit Memos

Drill-through from Accounts with Unapplied Credit Memos – open invoices for the selected Bill To, with AR Rep, AR Contact and Decision Contact details and the A/R Email Actions panel

Summaries

09 – A/R Invoice Statistics (ID504)
How long invoices actually take to pay, invoice by invoice

Purpose
Show how long invoices actually take to pay, at invoice grain, with a KPI layer the original page lacked entirely.

Expected Outcome
A reader can tell whether the payment problem is broad or concentrated in a minority of very late invoices, and which transaction type is responsible.

How to read this page

• Read the distribution before the average. Most invoices are fine; a minority are badly late, and the mean hides that.
• Compare median against mean. A wide gap confirms the average is being dragged by a tail.
• Use the transaction-type chart to decide where process change would pay.
• Days Late is only populated where an invoice was paid after its due date. Blank means paid on or before term.

Key measure

Bill Days to Pay = Due Days to Pay + Term Days. Cards cover invoice count and value, % Paid On Time, Avg Due Days, Avg Bill Days, Avg Days Late and the count and value of invoices more than 60 days late. The detail table gives one row per invoice with First Pay Date, Pay Full Date, Due Days, Bill Days, Term Days and Days Late.

09 – A/R Invoice Statistics (ID504)

10 – Invoices Coming Due (ID477)
Expected cash and what may not arrive

Purpose
Forecast cash over the next 30 days and flag how much of it is likely to slip.

Expected Outcome
Treasury can plan against a realistic number rather than a gross one, and collections can contact at-risk customers before the due date.

How to read this page

• Use the weighted forecast for cash planning and the gross figure for exposure. The gap is what history says will slip.
• Filter to customers below 50% on-time to build a pre-emptive call list. Contacting before the due date is far more effective than chasing after it.
• Adjust Coming Due Days to match your cash cycle — 30 is the default but weekly planning wants 7.

On the page

The forecast is weighted by each customer's historic on-time rate; the unweighted total is the maximum, not the expectation. Cards break the window into next 7 days, 8 to 14 days and 15 to 30 days, and count At Risk Customers with an on-time rate below 50%. A cash-expected-by-week visual shows gross against weighted, and a transaction-type table gives on-time rate, invoice count, amount due and weighted forecast per type.

10 – Invoices Coming Due (ID477)

Billing Accuracy

11 – Billing Accuracy Summary
How often invoices are issued correctly the first time

Purpose
Compare accuracy and void behaviour across every transaction type.

Expected Outcome
A reader can name the transaction type responsible for most of the void volume and argue for a process fix at invoicing.

How to read this page

• Start with the transaction-type table — it explains most of the variation the trend charts show.
• Compare void percentage against volume before concluding a type is problematic; low-volume types swing wildly.

Key measure

Billing Accuracy = 1 − (Voided Invoices ÷ Invoices). Voids include legitimate rebills, so read the figure as churn rather than pure error. Cards name the best and worst transaction type with their accuracy. Three trend charts cover accuracy, invoice volume and void volume against a configurable Billing Accuracy Target.

11 – Billing Accuracy Summary

12 – Billing Accuracy by Admin Agent
Who is generating voids, weighted by how much they actually bill

Purpose
Identify who generates voids, weighted by how much they actually bill.

Expected Outcome
A manager leaves with a remediation list ordered by impact rather than by percentage, and does not waste effort on agents with trivial volume.

How to read this page

• Rank by impact, not by percentage. Fixing the largest contributor removes thousands of voids; fixing the worst percentage removes dozens.
• Use the accuracy column to diagnose and the void-share column to prioritise. They rarely agree.
• Check the excluded panel before assuming an agent is missing — low-volume agents are held out deliberately.

On the page

A Minimum Invoices floor excludes low-volume agents from the ranking and shows them in a separate Excluded panel — a 100% score on one invoice is not a result. The ranked table carries Billing Accuracy, # Invoices, # Voided, Void Rate, Voids Share and an Impact Rank with a Priority / Review flag.

12 – Billing Accuracy by Admin Agent

Exception Reports

13 – Missing A/R Contact / Contact Info
Accounts we cannot chase because we have nobody to chase

Purpose
Surface accounts that cannot be chased because there is no usable contact.

Expected Outcome
The data gap gets closed in priority order, and the statement campaign stops being blocked on the same accounts every run.

How to read this page

• Work from the top. The full list is a cleanup project; the accounts with past-due balance and no contact are today's job.
• Distinguish Missing Contact from Missing Email — the first needs a call, the second needs a field completed.
• Accounts with no balance can wait. They cost nothing until they are invoiced.

On the page

Missing A/R Contact? and Has balance Due? quick filters sit above the table, with an AR Rep selector that also displays that rep's own email and work phone in the header. The table is sorted by amount due descending and carries Contact Number, Contact, Contact Email, Contact Phone1 and Phone2, Branch, Total Due, Past Due Amount, # Invoices in period and Invoiced Amount in period. An A/R Email Actions panel sits below the table with a row count and an Unlock to send control.

13 – Missing A/R Contact / Contact Info

14 – A/R Past Due Customers without selected A/R Activities Tasks
Past due balance that nobody has worked

Purpose
Find past-due balance nobody has worked — accounts with none of the selected A/R activities completed, old enough and large enough to matter.

Expected Outcome
A ranked list of accounts to assign. Every row needs a task created or an owner named. Worked weekly, the list should shrink.

How to read this page

• Set the Activity slicer first — it defines what "worked" means.
• The thresholds narrow the list hard. Lower the amount to widen it.
• A/R Tasks of 1 or 2 isn't a contradiction — that column counts all tasks, the filter only counts the selected types.
• Sort by a bucket column to work one aging band.
• Check Unapplied before calling. Cash may already be sitting there.
• Invoice Customers above 1 means a lease company — the end customer may need involving too.

Controls

An Activity multi-select defines the activities that count as "worked" (A/R Notes, Collection Notes, Credit On Account, Spoke with, and others). A Days Threshold sets the minimum age for those activities and an Amount Threshold sets the minimum Open A/R for the Bill To customer. Aging Basis, Aging Bucket and DSO Target controls sit alongside.

14 – A/R Past Due Customers without selected A/R Activities Tasks

15 – Voided Invoices missing A/R Tasks / Notes
Voids with no explanatory note – an audit and training gap

Purpose
Expose voids with no explanatory note — an audit and training gap rather than a collections one.

Expected Outcome
Void documentation coverage improves, and repeat offenders are identified for coaching.

How to read this page

• Use for audit readiness, not daily work.
• Filter by Creator to turn it into a coaching list — the same names appear on Billing Accuracy by Admin Agent.
• Filter out zero-value voids before drawing conclusions about volume.

On the page

Every void should carry a task or note explaining why; these do not. Three visuals break the population down by Transaction Type Mix, Creator Mix and month-on-month trend. The detail table carries Customer, Bill To, Creator, Invoice Date, Due Date, Invoice Number, Invoice Total, Transaction Type, Module, VoidID and Remarks.

15 – Voided Invoices missing A/R Tasks / Notes

16 – A/R Past Due More Than Usual
Invoices aging beyond what this customer normally does

Purpose
Flag invoices aging beyond what that specific customer normally does.

Expected Outcome
Collections get an early-warning list of behaviour change, months before absolute aging would surface the same accounts.

How to read this page

• This is the most predictive page in the report. Absolute aging tells you who is late; this tells you who has changed.
• Read deviation before aging days. A 28-day invoice at 2.2× a six-day baseline is a bigger signal than a 90-day invoice from a customer who always pays at 90.
• Use the four rolling windows to check whether the baseline itself is moving. If all four are rising the customer is deteriorating generally.

Controls and measures

The page compares each open invoice's current age against that customer's own payment baseline — behaviour change, not absolute age. A Severe Threshold multiple, a Compare to selector (for example Avg. Due Days To Pay 3M), a Min. Amount Due floor and an Aging Basis control sit in the header. Cards cover invoices above baseline, severe cases at 3× baseline, worst deviation, median deviation and the value newly flagged against last month.

16 – A/R Past Due More Than Usual

A/R Revenue Breakdown

17 – Revenue Summary & Trends
Invoiced revenue, its direction and how it converts to cash

Purpose
Show invoiced revenue, its direction, and how much of it has converted to cash.

Expected Outcome
A reader knows whether growth is real, broad-based, and collecting — or whether it is consuming working capital.

How to read this page

• Read revenue beside the conversion bar. Growth that is not converting to cash is working capital consumption, not performance.
• Use the cumulative chart for the annual position and the monthly chart for momentum.
• Check the transaction-type table before celebrating growth. Even growth across types means volume; concentrated growth means mix change.

Definition

This is invoice billing, not GL revenue — SUM of Invoice Total on invoice date, excluding voids. There is no GL feed in the model. The Revenue to Cash Conversion visual walks Gross billed → Voided → Net billed → Collected → Still open.

17 – Revenue Summary & Trends

18 – Revenue :: BillTo Customers
Which customers are growing, which are shrinking, and who we depend on

Purpose
Show which customers are growing, which are shrinking, and how dependent the business is on the largest.

Expected Outcome
Sales and finance can see growth and dependency in one view, and spot customers whose balance is growing faster than their revenue.

How to read this page

• Read the cumulative share column to find where the dependency line sits.
• Compare Revenue vs PY against Open A/R. A customer growing fast while their balance grows faster is a credit decision, not a sales win.
• Very high growth percentages on small bases are usually new contracts, not expansion. Check absolute value.

On the page

Cards cover Revenue against prior year, Cash Collected with a conversion percentage, and invoice count with average invoice value. The table gives Revenue, Revenue PY, vs PY and vs PY % per Bill To customer, alongside period-over-period and running-total trend charts.

18 – Revenue :: BillTo Customers

19 – Revenue :: ShipTo Locations
Where the equipment actually sits, and how those locations perform

Purpose
Show where equipment sits and how those locations perform, separately from who pays.

Expected Outcome
Territory and service planning can use location performance without confusing it with billing relationships.

How to read this page

• Use Ship To when the paying entity differs from the serviced site — multi-site accounts hide performance at Bill To level.
• A decline across one site of seven reads very differently to a decline across all seven.
• State-level revenue is useful for territory planning but is not profitability.

On the page

Cards cover Revenue, Ship To Locations with an average per Bill To, States Covered with the top state, Multi Site Accounts with their share of revenue, and the largest Ship To decline. Two tables give Revenue vs Prior Year by Bill To customer (with site counts) and by Ship To customer, alongside a ranked state table.

19 – Revenue :: ShipTo Locations

Payments Portal

20 – Payments Summary
Cash received, how it arrives, and what the portal is worth

Purpose
Show cash received, how it arrives, and what the payment portal is worth.

Expected Outcome
A reader knows portal penetration against target and what a percentage point of migration is worth in recovered fees.

How to read this page

• Read % Portal Payments against a target, not in isolation.
• Recovered fees are measured against portal payments only — the rate applies to portal volume, not to all cash.
• Use the method table to find the migration target. Cheque and EFT volume is where portal growth has to come from.
• Check the date range before comparing to Processor Fees; the two pages default to different windows.

On the page

Figures are based on receipt date. Cards cover Paid Amount, Paid through portal, % Portal Payments against a configurable Portal Utilization Target, Recovered fees and % Recovered fees. Four month-on-month trend charts and a payment method mix table (CH, EFT, ACH, CC, CA) sit below, with an opportunity panel that sizes what moving portal share to target would add in recovered fees.

20 – Payments Summary

21 – Payments by Bill To & Method
Who pays, how they pay, and who has not adopted the payment portal

Purpose
Show who pays, how they pay, and who has not adopted the portal.

Expected Outcome
A portal migration campaign can be built from the non-adopter list, sized by recovered-fee opportunity.

How to read this page

• Use this page to build a migration campaign, not to review collections.
• A 0.00% portal figure on a large customer is a sales opportunity worth roughly the recovered-fee rate on their volume.
• On Account customers are the easiest to convert — they already have a billing relationship set up.

On the page

Blank portal columns indicate customers who have never used the portal. Cards cover Paid Amount, Portal Adopters against the paying customer base, Non-adopters above $100K with their volume, On Account Customers with their value, and % Recovered fees with its range. A Largest non-adopters visual ranks the migration targets.

21 – Payments by Bill To & Method

22 – Processor Fees Overview
What the payment processors charge, and what we recover

Purpose
Show what the processors charge against what is recovered from customers.

Expected Outcome
Once the feed is reconciled, a reader can state the net margin per portal dollar. Until then the page exists to make the data gap visible.

How to read this page

• Treat every figure as provisional until the fee feed is reconciled against processor statements.
• Compare recorded fees to the volume they sit against before drawing any conclusion about portal profitability.
• The useful metric once reconciled is net margin per portal dollar: recovered fees less processor fees.

Data quality

The page raises an explicit data quality warning when recorded processor fees are implausibly low for card processing, and shows the expected fee figure beside the recorded one. Fees are broken down by processor, with a Fees vs recovery panel that spells out the implied rate, the realistic rate, and why the page should be labelled provisional and excluded from the executive layer until reconciled.

22 – Processor Fees Overview

Performance Billing KPIs

23 – Days Sales Outstanding (DSO)
How long it takes to convert a sale into cash

Purpose
Show how long it takes to convert a sale into cash, corrected for the two defects in the original measure, grouped by AR Rep.

Expected Outcome
A reader trusts the number, can see it against a target they control, and knows what closing the gap is worth in cash.

How to read this page

• Use the corrected figure. The old measure filtered aging by the date slicer and used a denominator that included voided invoices.
• Total Due is static as of the last refresh and uses a denominator that responds only to credit sales.
• Read DSO beside credit sales. A high DSO on a small account is noise; a high DSO on a large account is cash.
• Check the excluded panel before assuming an account is missing. Small and negative denominators are held out deliberately.
• Group by AR Rep for accountability and by Bill To for diagnosis.

On the page

A Grouping selector (Bill To / AR Rep), a Min. Credit Sales floor and a DSO Target control sit in the header. A "What is driving the gap" panel attributes the variance - accounts above 90 days DSO, the contribution of unapplied cash, slow transaction types, and the working capital that closing the gap would release. Excluded accounts and the reasons for exclusion are shown in their own panels.

23 – Days Sales Outstanding (DSO)

24 – Rolling Averages Due / Bill Days to Pay
Payment speed by customer, with the trajectory made explicit

Purpose
Show payment speed by customer with the direction of travel made explicit rather than left to mental arithmetic.

Expected Outcome
A collector can sort the whole book by deterioration and get a worklist of customers whose behaviour has changed.

How to read this page

• Sort by the 3M versus 12M column, not by absolute days. A customer who always pays at 90 is a terms problem; one who moved from 20 to 90 is a credit problem.
• Read the four windows left to right as a slope. 12M > 9M > 6M > 3M means speeding up.
• Use the Trend chip for triage and the numbers for the conversation.
• The minimum-invoice filter matters — a customer with three invoices can swing hundreds of days on one late payment.

On the page

3M vs 12M is the signal: a customer whose recent behaviour diverges from their own baseline is changing, regardless of absolute level. A Distribution of change visual bands the book into Improving fast, Improving, Stable, Watch and Severe. A Min Invoices 12M floor keeps low-volume customers out of the ranking. Drill-through to BillTo Profile and KPI Trends.

24 – Rolling Averages Due / Bill Days to Pay

25 – Rolling Averages Due / Bill Days to Pay Trends
How payment speed has changed across the whole book

Purpose
Show how payment speed has moved across the whole book.

Expected Outcome
A reader can tell whether the portfolio is speeding up or slowing, and whether the change comes from behaviour or from terms.

How to read this page

• Watch the gap between the 12M and 3M lines. When the short window crosses below the long one the book has turned.
• Read Due Days for terms compliance and Bill Days for total cash cycle. The difference is average terms.
• Portfolio averages can improve while significant accounts deteriorate. Do not read this page alone.

On the page

Portfolio-level rolling averages: shorter windows react faster, and divergence between them is the early signal. Four cards cover Avg Due Days to Pay at 12M and 3M and Avg Bill Days to Pay at 12M and 3M, each against the start-of-period value. An "All four windows side by side" table adds an Implied average terms row and a Direction flag.

25 – Rolling Averages Due / Bill Days to Pay Trends

26 – Rolling Averages by Transaction Type
Which invoices get paid and which get ignored

Purpose
Show which kinds of invoice get paid and which get ignored.

Expected Outcome
A reader can make the case for a process change at invoicing rather than more collections effort.

How to read this page

• Compare Due Days and Bill Days within each row. Where they are equal the type carries no terms.
• Contract and sales invoices are the volume drivers — small changes there move the portfolio average more than large changes on misc. charge.

On the page

Cards name the slowest and fastest transaction type with their 12M due days, the spread across types, and the portfolio due days. A "Why Misc. Charge Invoice is different" panel works through cause, effect, type and fix — typically zero term days meaning the invoice is due on issue, customers treating the type as disputable rather than payable, and the fix being standard terms plus a clear description.

26 – Rolling Averages by Transaction Type

27 – Collections Workload by Assignee
Who owns what, how fast they clear it, and how much is owned by nobody

Purpose
Show who owns what, how fast they clear it, and how much work has no owner at all.

Expected Outcome
A manager can rebalance load, identify unowned work, and see whether high throughput is coming at the cost of quality.

How to read this page

• Read the coverage donut first. Until assignment coverage improves, every other number on the page describes a fraction of the work.
• Treat the <n/a> row as a queue, not a person.
• Read Balance Under Management beside Open Items. Two people with five items each are not equally loaded if one carries six times the balance.
• Late completion rate is the quality measure. High throughput with a high late rate means work is being closed, not done.

On the page

Cards cover Unassigned Activities with coverage percentage, Open Items split assigned and unassigned, Completed Activities split on-schedule and late, % Completed Late and Avg Days To Complete. An Open queue detail table lists Bill To, Activity, Created, Scheduled, Balance, Assignee and Activity Notes. An Activity mix visual shows what collections work actually consists of.

27 – Collections Workload by Assignee

28 – A/R Rep Performance
Measure portfolio, payment behaviour and task discipline by relationship owner.

Purpose
Measure portfolio, payment behaviour and task discipline by relationship owner.

Expected Outcome
A manager can compare reps on a like-for-like basis and see which portfolios are improving.

How to read this page

• Read clients and invoices together with balance. A rep with many small clients and one with few large ones need different comparisons.
• Use L12 versus L3 as the performance signal, not the absolute level, which is mostly determined by inherited customers.
• On-time % is the discipline measure; past due tasks is the workload measure.
• Assign the clients with no AR Rep before treating any comparison as fair.

28 – A/R Rep Performance

Customer Deep Dive

29 – BillTo Profile
One account at a time – full profile, notes and tasks

Purpose
Bring everything the report knows about a single Bill To customer onto one page: position, behaviour, aging shape, value and rank within the portfolio, and the risk flags that follow from them.

Expected Outcome
A collector or credit manager can prepare for a conversation with one customer without touching any other page, and can act on that customer from the same screen.

How to read this page

• Select the customer from the Select a Bill To Customer picker, or arrive here by drill-through from any page that offers a BillTo Profile button.
• Read the six cards first — Total Due, % Past Due, Exposure Ratio, DSO 12M, Oldest Open Invoice and Days Last Contact — each shown against the portfolio equivalent so the customer is always read in context.
• Use the Aging profile to see the shape of the balance and the Payment behaviour table to see the 12M / 9M / 6M / 3M trajectory.
• Value & Rank places the customer in the book: revenue, revenue vs PY, share of total revenue, revenue rank and open A/R rank.
• Risk Flags summarise Position, Behaviour, Aging, Value and Engagement as CRITICAL or CLEAR, each with the reason stated.
• The lower section carries Revenue vs Prior Year by transaction type, a period-over-period trend, the customer's open invoice detail, contact cards and the A/R Email Actions panel.

BillTo Profile – top section

BillTo Profile – bottom section: revenue vs prior year by transaction type, period-over-period trend, open invoice details, AR Rep / AR Contact / Decision Contact cards and A/R Email Actions

Drill-Through Pages

Drill-through pages are reached by selecting a row in a table and clicking one of the drill-through buttons that become enabled above it, or by right-clicking a row. They open in the context of the selection and always show which Bill To customer or invoice they are scoped to, immediately under the page title.

Every drill-through repeats the aging cards for the selected context so you never lose sight of the balance you are working, carries a back arrow in the top-left to return to the page you came from, and honours the same Aging Basis and Aging Period controls as the rest of the report.

Drill-Through – A/R Notes

Opens in the context of the selected Bill To customer and shows every A/R invoice note against that customer's invoices.

The aging cards and the Open Invoice Details table give the balance context, and the A/R Invoice Notes panel below lists each note with its invoice number, creator, date, note type and full text. System Event entries — for example invoice renumbering — appear alongside user-entered notes.

A Note Type filter narrows the list, the record count tells you how many invoices are in context, and a New Note button lets you add a note without leaving the report. Each row carries an edit control.

Drill-Through – A/R Notes

Drill-Through – A/R Tasks

Opens in the context of the selected Bill To customer and shows every A/R activity recorded against that customer's invoices.

The Invoice A/R Activities panel lists Invoice #, Activity, Type, Status, Creator, Created date, Scheduled date and Notes. An Activity Status filter narrows to open or completed work, and the record count confirms how many invoices are in context.

A New Activity button creates a task directly from the report, and each row carries an edit control for updating an existing one.

Drill-Through – A/R Tasks

Drill-Through – Bill To Tasks

Opens in the context of the selected Bill To customer and shows activities recorded at customer level rather than against a specific invoice.

The Bill-To A/R Activities panel lists Activity, Type, Status, Creator, Created date, Scheduled date and the full note text — which on long-standing accounts gives you the complete collection history in one scrollable list.

An Activity Status filter and a New Activity button work exactly as they do on the A/R Tasks drill-through.

Drill-Through – Bill To Tasks

Drill-Through – Open Invoices

Opens in the context of the selected Bill To customer and lists every open invoice for that customer, with the full set of aging cards recalculated for that customer alone.

The header quantifies how many of the customer's open invoices bill to a different entity than the invoice customer, which matters on lease-company and collective accounts.

Three contact cards sit below the table — AR Rep, AR Contact and Decision Contact — each with email and phone details, followed by the A/R Email Actions panel described below.

Drill-Through – Open Invoices

Drill-Through – Invoice Details

Opens in the context of a single selected invoice and is the lowest grain in the report.

The header row gives Invoice Customer, Bill To, Invoice Total, Amount Due, Invoice Date, Due Date, Aging Period, Transaction Type, Creator, Invoice Description, Remarks and the Invoice URL.

Below it sit the same three contact cards and the A/R Email Actions panel, together with the Invoice A/R Activities and A/R Invoice Notes panels scoped to that one invoice — so a single invoice query can be answered, noted and actioned without leaving the page.

Drill-Through – Invoice Details

*  *  *

Related Alerts

Related Alerts

The alerts below work alongside ID734. Used together they automate the majority of the A/R process — invoice delivery, past-due follow-up, online payment and the analysis that ties them together.

ID437 - Emails invoices to customers as they are created, so the customer receives the invoice the day it is raised rather than on a statement run.

ID800 - Chases invoices once they are past due. Used with ID734 it automates the follow-up that this report identifies.

ID669 - Online payment links that allow your customers to pay you online, with credit card fee recovery. Portal adoption is measured on the Payments Summary and Payments by Bill To & Method pages of this report.

ID717 - Unapplied Payments. Surfaced as a dedicated page inside this report.

ID504 - A/R Invoice Statistics. Surfaced as a dedicated page inside this report.

ID477 - Invoices Coming Due. Surfaced as a dedicated page inside this report.

See full list of all Power BI reports that we currently have available

https://support.ceojuice.com/hc/en-us/sections/360011259132-Power-BI-Reports

*  *  *

Webinar

Webinar

Webinar Recorded March 30, 2025

Automated AR overview