Stuut Insights

Leave the AP portals to Stuut

Ben Winter

COO

November 12, 2026

See Stuut in action

Get a personalized demo of Stuut and see how it can help with AR automation.

Get started

The order shipped, the invoice went out, and the buyer has every reason to pay. Three weeks later, the cash still hasn't shown up, so someone on your team logs into Coupa to find out why. The invoice was rejected on day two because the PO was closed, and nobody saw it.

Every big buyer runs its own AP portal, with its own fields, its own rules, and its own login. Most tools built for this treat it as a delivery job: get the invoice uploaded and move on. Getting it uploaded is the easy part. What decides when you get paid is whether the portal accepts the invoice, and how fast someone fixes it when it doesn't.

So we built AP portals in Stuut around one idea: a portal rejection is a collections problem that shows up early.

Stuut checks the PO before the portal does

Look at why invoices get rejected and you usually find the PO. It's closed, it's over budget, the quantity or price doesn't match, or the invoice is a duplicate. None of those get fixed by a faster upload.

Before Stuut submits anything, it checks the invoice against the PO. When everything matches, Stuut fills the portal form and submits it on its own. When something looks off, it sends the invoice to your team first. Every submission is saved with a screenshot of exactly what went in.

When a PO doesn’t match, Stuut drafts an email to the buyer contact on the PO asking them to fix it. Your team reviews it and hits send.

Every status, on the customer's record

Stuut checks each portal several times a day and brings every status back to the customer in Stuut: submitted, approved, rejected, or on hold. When a buyer rejects an invoice, you see their reason and a task right away. Nobody has to log in to find out, and access never depends on one person's password, because Stuut works each portal from its own account on your domain.

From the portal to your books

Portal status tells you more than where an invoice sits. It tells you whether the payment clock has started. An invoice the portal accepted is one the Collections Agent should follow up on. An invoice the portal rejected is one nobody should chase until it's fixed.

Stuut acts on that difference. Accepted invoices go to the Collections Agent with the full history. If the buyer pushes back on what they owe, the Disputes & Deductions Agent picks it up. When the payment lands, the Cash Application Agent matches it. It's one record, from the portal to your books.

“Stuut reviews our invoice, pulls up the PO in the portal, and checks that everything matches. If it does, Stuut submits it into Ariba for us. Nobody on the team must log in to do it.”

Scott Johnson, Corporate Credit & Collections Manager at Bishop Lifting

Scott JohnsonCorporate Credit & Collections Manager @ Bishop Lifting

Get started

If your buyer has a portal, Stuut can work it. That’s 250+ AP portals and counting, including Coupa, Ariba, and Taulia. Stuut logs in, submits, and brings back every status.

We're turning it on account by account. Already a Stuut customer? Reach out to your CSM to get started. Not yet? Book a demo and we'll show it on your own portals.

Your team took this job to get cash in the door. Chasing invoices that never made it into a portal was never part of it.

Ben Winter

COO

Ben brings over a decade of go-to-market and operations expertise to building AR automation that actually works. He was VP Marketing at Fairmarkit (where he met Tarek) and GTM executive at Waldo before co-founding Stuut. He focuses on operations, product, and marketing—ensuring the platform integrates seamlessly with existing ERP systems and delivers results in days rather than months.

How to Calculate DSO: Step-by-Step Formula with Real Examples

Tarek Alaruri

Mar 10, 2026