Most billing teams track one moment closely: the invoice went out. Far fewer track what happens next.
Was it received? Did your customer’s system accept it? Is it sitting in an approval queue? Did it bounce for a missing field and quietly disappear? Is it disputed?
An invoice can be technically submitted and functionally invisible at the same time. That gap, between “sent” and “known to be accepted,” is one of the most common and least discussed breakdowns in order-to-cash. However, most finance teams have no reliable way to tell the difference until a customer is already well past due.
Why this breaks order-to-cash
Once an invoice leaves your accounting system, whether by email, EDI, or a customer AP portal, it enters a black box.
Your customers’ accounts payable (AP) systems process, route, approve, and sometimes reject invoices. They rarely tell the sender consistently. Some portals show a rejection at once and clearly. Others fail quietly, or send the notice to a generic inbox nobody checks.
Definition
The status vacuum
The stretch of time between submitting an invoice and learning what your customer’s system did with it. During the vacuum, your customer’s system may have approved it, queued it, rejected it, or lost it. From your side, all four look the same.
The result is a status vacuum. As a result, AR teams usually find out something is wrong in one of three ways:
- The invoice goes well past due, and someone finally investigates
- A customer reaches out first, which is rare
- A collector calls about payment and hears, for the first time, that the invoice never arrived or bounced weeks ago
By then, you have lost real time, and you rarely get it back. Days sales outstanding (DSO) clocks do not pause for the days an invoice sits in a rejected state without your knowledge.
The status that matters most: approved
Not all invoice statuses carry the same weight. One gets far less attention than it deserves.
When your customer’s AP system marks an invoice approved, that invoice has cleared every gate between you and payment. First, your customer received it. Then it matched whatever their system checks. Finally, someone with authority signed off.
Approved invoices rarely, if ever, go unpaid. The timing still aligns with your customer’s payment deadlines, but you no longer have to wonder about the outcome as you do with a pending, disputed, or rejected invoice.
Most AR teams treat approved the same as sent. It deserves its own tier. An approved invoice carries far less risk than one still sitting in a review queue, so putting the two side by side in the same collection process spends effort on invoices your customer has already cleared.
This sits in front of your aging buckets rather than replacing them. Age-based escalation is the right way to work receivables you know are real, and our guide to accounts receivable KPIs covers how to run those buckets properly. In other words, status is the filter you apply first, because an invoice your customer never accepted is not yet a collections problem.
Key takeaway
Confirm status before you sort by age. An outstanding invoice at 45 days, your customer has already approved, needs a payment date. An invoice at 15 days with no confirmation needs an investigation, not a reminder. Aging alone cannot tell them apart, so status decides which invoices belong in the buckets at all.
What it looks like in practice
A supplier correctly submits an invoice to a customer’s AP portal. The customer’s system flags it for a missing cost centre code, a requirement nobody had mentioned. Meanwhile, the rejection notice is sent to an email alias that nobody checks daily.
Three weeks pass. Then a collector calls about payment and, for the first time, hears that the invoice never entered the customer’s payment queue. The supplier resubmits, so the approval clock restarts at zero. As a result, a 30-day term becomes 50-plus days, and neither side’s collections efforts caused it.
Nobody in that story did anything wrong. That is what makes it expensive.
The business impact
- Inflated DSO is not a payment problem. Slow payment and an unknown rejection look identical on an AR aging report, and they need opposite fixes. A single DSO figure hides which one you have.
- Wasted collections effort. Collectors chase invoices that could never have been paid on time.
- Strained customer relationships. Repeated “why haven’t you paid this” calls about invoices your customer never received read as sloppy rather than diligent.
- Cash arrives late across the portfolio. A few blind days per invoice, across hundreds or thousands of invoice payments a month, drags real cash.
Those costs are measurable. BLEND, a global localization platform, cut invoice rejections 70% and collections days 47% once its AR team could see invoice status across every portal instead of investigating one at a time.
Reading the status field
Treat status as information, not a label. Five states, five different next moves.
When pending approval is the real problem
One row deserves a closer look. An invoice pending approval has already passed all technical checks, so the approval process is the only thing left between you and payment. An invoice stuck in approval is not a formatting failure.
So treat an approval delay differently from a rejection. For example, an invoice that’s been awaiting approval for three weeks needs a person, not a resubmission, and the person you need is whoever asked for what you sold, not the accounts payable team.
How long is too long?
Ardent Partners’ 2025 accounts payable benchmarks show the average invoice takes 9.2 days to process, with 14% hitting an exception along the way and only 32.6% clearing without a human touch. So, around 1 in 7 invoices run into trouble on your customer’s side, and 2 in 3 pass through somebody’s hands before they clear.
That gives you a benchmark instead of a guess. In practice, an invoice showing no movement three weeks after submission is not working its way through a normal queue.
Meanwhile, checking every portal by hand does not scale, which is why tracking status beats any single follow-up call. A rejection you find on day 2 costs you almost nothing. The same rejection on day 21 costs you three weeks.
Where this flows next: collections
Status problems do not stay inside billing. They reach collections, where teams work the phones without knowing whether your customer can even pay an invoice yet, or whether they have already approved it and it sits safely off the list.
Automating invoice approvals inside your customer’s system is not something you control. Seeing where each invoice stands is. Work an approved invoice and an unconfirmed one from the same script, and a good collector ends up looking careless.
Status also changes how you ask. Invoice escalation works when you can specify the invoice number, submission date, and the person holding it. Without those three, you are asking your customer to do your research for you. Instead, knowing how to ask for payment professionally starts with knowing what you are actually asking for.
Customer story: 11 billers and a spreadsheet
The Imagine Group, a print and marketing production company, invoices thousands of customer accounts across Ariba, Coupa, and 8 or 9 other portals. Eleven billers each owned their own customers. Each one logged into that customer’s portal and entered every invoice by hand.
The blind spot turned up exactly as described above. “We were dealing with a few missed delivery invoices to the portals and also a lot of rejections,” says Yenny Garcia, Manager, Billing. “It was a manual process.” Rejections lived on a spreadsheet, which made a rejection only as visible as whoever last updated the file.
With Monto, 95% of executions now run zero-touch. Total DSO fell by 34%, from 44 days to 29 days. The team recovered more than 8,700 hours.
Customer story
“Monto is great. It gives us the ability to monitor where we couldn’t do that before. There would be no way I would be checking every portal by hand.”
Chelsea Shepherd, Director, Credit, Collections and Billing, The Imagine Group
How Monto closes the status gap
The core issue is not that customers reject invoices, or that some invoices clear approval faster than others. Both are normal parts of AP processing. Instead, the issue is that suppliers have no reliable, real-time way to know which is which.
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 hundreds of others, then carries every invoice from your accounting system all the way through to payment.
Monto tracks invoices across 500+ customer AP portals, from submission through approval. It applies rules and behaviors learned across 20,000+ customer relationships to surface rejections, approvals, and other status changes as they happen, not weeks later.
The bottom line
An invoice you cannot see is not a payment problem. It is an information problem, and the two need opposite responses.
Slow payment calls for a conversation about terms. An unknown rejection requires resubmission today. So until you can tell which one you have, every collection hour is a coin flip, and your aging report keeps reporting a cash problem you may not have.
A rejection you find on day 2 costs you nothing. The same one found on day 21 costs three weeks of DSO.
See invoice status across every portal →FAQ
Does sent mean my invoice was received?
No. Sent confirms your accounting system has released the invoice. It says nothing about whether your customer’s AP system took it, routed it, or rejected it. So treat it as the start of the process, not the end of your job.
How do I know if my customer rejected an invoice?
Check the portal yourself instead of waiting for a notice. Rejection notices vary by portal, and many land in a shared alias rather than reaching the person who submitted the invoice. If a portal shows no movement and no approver several days after submission, assume a quiet failure and investigate.
What is the difference between approved and paid?
Approved means your customer authorized the invoice for payment, so the outcome is settled. Paid means the money moved. An approved invoice is waiting on a payment run, which makes it a scheduling question rather than a collections question.
Why does a rejection restart the payment clock?
Most customers base payment terms on a valid, accepted invoice, not on your first attempt. Resubmit on day 21; the terms often reset then. That is how a 30-day term quietly becomes 50-plus.
Should approved invoices stay on a collections worklist?
No. An approved invoice cleared every gate that decides whether it gets paid. Instead, spend the effort on invoices where the outcome is still open: unconfirmed, pending with no activity, rejected, or disputed.
How do I follow up on an unpaid invoice when I cannot see its status?
Confirm receipt before you ask for payment. An overdue invoice your customer never received needs a resubmission, not a reminder, and chasing payment on an invoice that never arrived costs you credibility you will want later. So check the portal, get the status, then write.
How do I collect an overdue invoice that my customer rejected weeks ago?
Fix the named field, resubmit the same day, and propose a payment date in the same message, rather than letting the terms run again from scratch. When an invoice goes unpaid, what to do next depends on whether your customer ever accepted it, which is why status matters more than age.