Ask five finance teams to map their order to cash workflow, and you’ll get the same five stages back. A customer places an order, credit reviews it, you fulfill it, you invoice it, then collections chases the payment. That’s the model in every enterprise resource planning (ERP) process map and most consulting decks. It’s also incomplete.
There’s a sixth step, and no diagram shows it. Billing releases the invoice. Collections start chasing. In between, your invoice has to land in your customer’s accounts payable (AP) portal, in that portal’s format. The portal has to accept it. Only then does the payment clock start.
That gap is where many days go.
What is the order to cash process, stage by stage?
The order-to-cash process consists of five stages, from the moment a customer places an order to the moment cash lands in your bank account. Order capture, credit review, fulfillment, invoicing, collections. Each stage has a system, an owner, and a number. Billing owns the invoicing process and watches invoice accuracy. Collections owns collections and watches accounts receivable (AR) aging.
The model holds because every stage runs inside software you control. Your order management system records the order. The credit tool scores the customer, and your billing system issues the invoice. Then the invoice leaves, and your visibility does too.
Definition
The portal submission step
It covers three jobs. You move a finished invoice from your ERP into each customer’s AP portal. You match the exact format that portal requires. Then you confirm the portal accepted it. All of it happens after invoicing and before collections, inside software you don’t own.
Where does the missing step sit?
It sits in the handoff between billing and collections, and both sides look straight past it.
Billing treats the invoice as done once it leaves the ERP. That’s a fair reading of the job. Collections assumes the aging clock started on the invoice date, because that’s what the aging report says. Neither assumption survives contact with a customer AP portal.
Watch a single invoice. You date it the 1st. It reaches the portal on the 4th. The portal rejects it on the 6th over a missing purchase order line. You resubmit on the 9th. It enters your customer’s approval queue on the 10th.
Your aging report has been counting since the 1st. Your customer’s clock started on the 10th. Nine days went by, and no report in your stack caught them.
Customer story
“We didn’t know we had a problem until after the 90 days were up, and it didn’t get paid.”
Mark Sellers, Sales Manager, ES&E
Why does nobody own the portal step?
Because the step crosses a system boundary, and org charts follow systems.
Ownership stops where the software stops. Billing’s tools end at the ERP. The collections team’s tools begin with the aging report. The portal sits between a browser and a password. So the work lands on whoever has room for it. Usually, a billing specialist squeezes submissions around the close. Or a collections specialist finds the rejection three weeks late.
Onguard’s FinTech Barometer 2026 surveyed 336 CFOs and finance and credit professionals in the Netherlands. The survey found 80% report delays caused by internal disagreement over responsibility, and 11% say ownership of days sales outstanding (DSO) sits nowhere at all. DSO is a shared metric with no shared owner, so the steps feeding it go unclaimed, too.
What does the unowned step cost each team?
AR managers and billing specialists
You absorb the work with no line for it anywhere. The close pushes portal submissions to the back of the queue, so they slip in a busy week. When a portal rejects an invoice, you learn about it by logging in. Nobody tells you.
Controllers and VP Finance
Your close rests on data you can’t see. Your ERP marks an invoice as issued, but it may not yet exist on your customer’s side. That difference doesn’t move revenue recognition. It does move every cash forecast you build on top of it.
CFOs
Your DSO number credits the delay to your customer when part of it is due to your own process. Accept that sent isn’t the same as accepted, and a slice of your receivables is aging against a clock that hasn’t started.
Key takeaway
Nobody owns the step between issuing an invoice and getting it accepted in a portal. So that time reads as customer behavior in your DSO. It isn’t. That’s process time, and you can take it back.
How do you measure order to cash cycle time you can’t see?
You compare two dates. The invoice date in your ERP, and the acceptance date in the portal.
Run that comparison across one month of invoices, and you have the size of the gap. Most teams have never run it, because the second date lives in dozens of separate portals. So start narrow. Pick your 10 largest customers by invoice count. Pull the invoice date from the ERP. Pull the accepted date from each portal. Average the difference.
Then track it as its own number. Call it submission-to-acceptance time. It belongs next to DSO on the same dashboard, because it’s a slice of order to cash cycle time you fully control. If your team already watches which invoices can actually be paid now, this completes the picture.
Who should own the portal step in your order to cash workflow?
The team that can fix a rejection should own it. Order to cash roles and responsibilities work best when the owner also holds the fix.
In most mid-market finance teams, that means billing rather than collections. Billing holds the purchase orders, line details, and ERP access to correct and resubmit. A collections specialist can chase a person. They can’t repair a formatting error at 4 pm on a Friday. So write the step into billing’s remit, name it, and give it a number to hit.
Then plan for portal changes. Customers update required fields and approval routing on their own schedule. That’s normal, and it’s their system to run. But nobody sends the supplier a notice.
So most teams learn about a change the same way they learn about everything else in a portal. Someone logs in to one portal at a time and reads the screen. That means they rarely catch the change itself. They catch the rejection it caused, on the next invoice, a week later. Your owner needs a faster route than a manual login round because a single field update can quietly stop a month’s invoices.
How Monto closes the gap between billing and collections
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, and each agent learns the exact workflows of the AP portals your customers use, Coupa, Ariba, Tungsten, Tipalti, and 500+ others, then carries every invoice from your ERP all the way through to payment.
That turns an unowned step into an owned one. The agent submits each invoice in the format required by the portal. It captures the reasons for rejection that would otherwise cost you a week. It reports acceptance back, so your aging report follows your customer’s clock rather than guessing. Your team makes the judgment calls and drops the logins.
ES&E now processes 90% of its invoices with zero-touch. Portal work that took at least 2 hours a day takes up to 2 minutes, and the AR team went back to collections instead of keying. Everything lands in one dashboard across every customer AP portal, which is where submission-to-acceptance stops being a manual audit and becomes a live number, next to cash application and the payment terms you agreed with each customer.
What to do with this next week
Pick your 10 highest-volume customers and measure the gap. Under 2 days means your handoff works, and you can stop reading. At 5 days or more, you’ve found days your DSO has been blaming on your customers. Those days are yours to recover.
Either way, name an owner before the next close. The rest of the order-to-cash automation picture gets easier once this step has a person assigned to it. Order-to-cash optimization usually starts with a stage nobody drew.
FAQ
What is the order to cash process?
The order-to-cash process covers everything from a customer placing an order to you collecting payment. Most models list five stages: order capture, credit review, fulfillment, invoicing, and collections. If your customers use AP portals, add a sixth between invoicing and collections. That’s the submission and acceptance step, and it’s where the payment clock starts.
Is portal submission part of invoicing or part of collections?
Neither, in practice, is the problem. Put it with billing. Billing holds the purchase order detail and the ERP access to fix a rejection and resubmit the same day.
How long should the submission-to-acceptance process take?
Automate the submission, and you can hit the same day. Manual teams often take several days, and a rejection adds more, because the supplier learns about it by logging in rather than by notification.
How do you know when a customer changes their AP portal?
Most suppliers have no alert for it. Someone logs in to each portal and reads the screen, so the change usually appears as a rejected invoice rather than a notice. Assign the portal step to a single owner and review the highest-volume portals on a set schedule.
Does order to cash software cover the portal step?
Most of it doesn’t. Order-to-cash and invoice-to-cash platforms model the business process from your systems outward, so they hand off at the time of invoice delivery. Ask any vendor to show you the accepted date inside your customer’s portal, not the sent date from their own system. It’s one of the order-to-cash challenges that O2C automation vendors rarely name.
Which metric shows payment delays first?
Submission-to-acceptance time. DSO shows the symptom and blames the customer. Submission-to-acceptance time shows how many days you can act on your own before it moves faster.
See it on your own invoices. Find how many days sit between issued and accepted across your customer AP portals.
Book a 20-minute walkthrough →