Your order-to-cash metrics indicate that the days sales outstanding (DSO) is 52 days. They do not tell you where those 52 days went.
That is the problem with most order-to-cash metric lists: they stop at DSO, the collection effectiveness index, and aging buckets. Each of those describes a finished cycle rather than the stages inside it. Useful in a board pack. Close to useless on a Monday morning. Someone on your accounts receivable (AR) team needs to know which outstanding invoices to work on first, and no one can tell them.
The gap widens once your customers pay through their own accounts payable (AP) portals. An invoice leaves your ERP and waits in a customer’s portal for acceptance. It comes back rejected for a missing purchase order line, then waits again until someone spots it. None of that surfaces as a stage in your reporting. It lands later instead, as a bigger number and a longer average number of days to collect.
This piece is the measurement companion to how order to cash automation works when your customers use AP portals. That post makes the case that portal submission is an unowned stage. This one answers the question that follows: what belongs on the dashboard.
Definition
Order to cash metrics
Order-to-cash metrics measure how long each stage of the order-to-cash cycle takes and how often a stage is repeated. Outcome metrics, such as DSO, report what the cycle produced. Process metrics point to where it slowed down. A working dashboard carries both.
Why can’t DSO tell you where the days went?
DSO averages the entire order to cash process. It runs from the moment a customer places an order to the moment cash hits your bank account. Averaging makes the number readable but also useless for diagnosis. A quiet month with long payment terms reads almost the same as a bad one. Both look the same, even though a third of your invoices came back rejected and were sent twice.
DSO also lags. By the time it moves, the invoicing process behind it has already run for 6 to 8 weeks. You can explain the number without changing it.
We covered the root causes separately in why your DSO is too high. The short version: most payment delays are not customers deciding to pay late. There are days your invoices spend in a state nobody monitors. Good order to cash metrics make those days visible.
In what order are cash metrics worth measuring, stage by stage?
Break the cycle into the stages your team actually touches, then measure two things in each one: elapsed time, and how often the work gets repeated.
One word needs to be defined first, because the whole portal stage hangs on it. The customer’s AP portal accepts an invoice after validating the data and moving it into their approval queue. Acceptance is not approval, and approval is not payment processing. Acceptance means the invoice finally exists in your customer’s system. Until that happens, no payment clock runs anywhere.
Time alone hides the story, so the second column of order-to-cash metrics matters as much as the first. A stage that runs 4 days on the first attempt and 4 more on the second reads as an 8-day stage. The fix for a genuinely slow stage looks nothing like the fix for a stage that keeps getting repeated.
Most finance teams already track the top and bottom rows of that table. The middle row usually has no owner and no number. So the rest of this post covers those three order to cash metrics and how to calculate them. They are also where most order to cash bottlenecks sit.
What is the submission-to-acceptance time, and why has nobody calculated it?
Submission to acceptance time measures the gap between the invoice date in your ERP and the date the customer’s AP portal marks the invoice as accepted.
Most teams have never calculated it. The two dates live in separate systems, and neither system treats the gap as its business. Your ERP closes the job at invoice creation. The portal opens the job upon acceptance. The days in between belong to nobody, so they accumulate quietly.
This is also the only segment of the cycle your billing team can move without calling a single customer. Payment terms sit in a contract. Customer approval speed is part of somebody else’s workflow. Getting an invoice accepted the first time correctly rests entirely on your side of the line. That makes it your fastest route to improved cash flow.
Why it matters
Say submission-to-acceptance runs 5 days on average across 400 monthly invoices. Those 5 days are applied to every invoice before the payment clock even starts. They never appear as their own line on a standard AR report. PYMNTS, reporting the June 2026 Growth Corporates Working Capital Index, has growth corporates losing roughly 4.1% of revenue chasing overdue B2B payments. Part of that chase starts with an invoice the customer had not accepted yet.
Why is the first-time acceptance rate only useful per portal?
First-time acceptance rate measures the share of invoices a portal accepts without requiring a correction or resubmission. As a one company-wide number, it tells you almost nothing. Split by customer portal, it tells you exactly where to spend the week.
Here is how the average hides things. Say you run at 92% overall. That sounds healthy until you split it. Nine customers sit at 99%, and one large customer sits at 61%, because that customer’s portal requires a purchase order line reference that your ERP never populates. The average buried your single highest value fix.
Rejection reasons also cluster tightly. Across our customer base, roughly 2 out of 3 rejections trace back to the same 3 causes. So, a per-portal view usually surfaces a handful of field-level fixes rather than a sprawling project. Our own customers run first-time invoice acceptance rates above 99% once each portal’s requirements are handled automatically.
How long does a rejected invoice sit before anyone notices?
Rejection-to-resubmission time is the third metric, and it turns a month-end shock into a backlog you can manage.
Portal rejections stay quiet. No phone call arrives. Often, no email reaches the right person, either, because the notification goes to whoever set up the portal account 2 years ago. Teams that manually work on portals usually discover a rejection on day 30 or later. An aging report raises the question, and only then does anyone notice the invoice was never accepted at all.
Measure the gap between the rejection timestamp and the resubmission timestamp. That gives you a number you can set a target against. Under 1 day is achievable. Over 2 weeks means nobody watches the portal. The aging report becomes your only alarm.
How do you build the view when the data sits in your ERP and in every customer’s portal?
For most teams, the honest answer starts with a weekly export and a spreadsheet, and that is a reasonable place to begin.
Pull invoice number, invoice date, and amount from your ERP. Log in to each customer portal, export the invoice status list, then match by invoice number. Add a column for the accepted date and a column for the rejection reason. You now hold the submission-to-acceptance time and first-time acceptance rate for one week per portal. That is more than most AR teams have ever had.
The catch: it stays manual. Portals change their fields and layouts without notice. A spreadsheet built in March quietly breaks in June. At that point, the measurement must come from the same source as the submission.
How Monto gives you the portal numbers without the spreadsheet
Monto is the autonomous co-worker that gets you paid by your enterprise customers, end-to-end. It puts a self-learning AI agent on every customer relationship. Each agent learns the exact workflows of the AP portals your customers use, Coupa, Ariba, Tungsten, Tipalti, and 600+ others. Then it carries every invoice from your ERP all the way through to payment.
Because the agent handles the submission itself, the timestamps exist where the work happens. You are no longer reassembling them from two systems that each treat the gap as the other’s business. Monto also gives you a single dashboard that covers invoices, purchase orders, and payments across every portal your customers use, so the raw material for these metrics is in one place. The same data feeds automated payment reconciliation from portals at the other end of the cycle. Receiving payment and clearing it against the correct invoice no longer requires two separate hunts.
What should you review weekly, and what belongs in the monthly pack?
Sort your order-to-cash metrics by what you can act on within 7 days. That split is the single best order-to-cash reporting habit to build. It turns a metrics list into an order-to-cash efficiency you can measure.
Weekly, for the team doing the work: first-time acceptance rate by portal, open rejections and their age, invoices submitted but not yet accepted past 3 days, and rejection to resubmission time.
Monthly, for the finance leadership pack: DSO, submission to acceptance time as a trend, the collection effectiveness index, aging distribution, unapplied cash, and whatever your revenue recognition close depends on. Together, these show whether the weekly work compounds. That is what turns into faster customer payments and better financial health.
You may already track accounts receivable metrics at the department level, in an accounts receivable KPIs scorecard, or a monthly review. The portal metrics sit underneath those as the diagnostic layer rather than replacing them. Among order-to-cash best practices, layering matters more than the exact list you pick.
Key takeaway
Outcome metrics tell you what happened last quarter. Process metrics tell you what to fix this week. A working order-to-cash dashboard carries both, and most carry only the first.
FAQ
What are the most important order to cash metrics and KPIs?
DSO, the collection effectiveness index, aging distribution, invoice accuracy, and cash application time make up the standard set. Teams whose customers pay through AP portals should add three more metrics: submission-to-acceptance time, first-time acceptance rate per portal, and rejection-to-resubmission time. The standard set does not measure the portal stage at all.
How do you calculate order to cash cycle time?
Measure the days from order receipt to cash applied. Then break that total into stage durations: order to invoice, invoice to acceptance, acceptance to approval, approval to payment, and payment to cash application. The total is your headline. The stage durations are what you act on.
What is a good first-time acceptance rate?
Track it per the customer portal rather than against a universal benchmark. Any portal sitting well below your others is where the days you can win back are hiding. A single field-mapping fix often moves one portal from the 60s to the 90s.
How is order to cash reporting different from AR reporting?
AR reporting starts at the invoice. Order to cash reporting covers the full cycle from order through cash application. So it shows whether a delay started in order entry, in portal submission, or in collections.
Why is our DSO high when customers say they paid on time?
Usually, because the portal never accepted the invoice, even though your team assumed it had. A rejected invoice that nobody noticed is not overdue in the customer’s system. It simply does not exist there yet. So the delay lands in your DSO rather than in a rejection report.
See what submission-to-acceptance time and portal acceptance rates look like across your own customers.
Book a demo →