When Your Client's Accounts Payable Portal Is the Bottleneck

You sent the invoice on the first. It went into the client's vendor portal exactly the way their operations manager told you to send it, and the portal gave you a confirmation number. That was five weeks ago. The work is finished, nobody has raised a problem, and the money is still not in your account.

This is a different kind of waiting than a client who simply forgot. When a small client is late, there is a person you can nudge and a decision they can make in ninety seconds. When a larger client routes everything through an accounts payable portal, your invoice is not in anyone's inbox. It is in a queue, behind a step that has not happened yet, and the person you have a relationship with often cannot see that queue either.

This post covers what happens to your invoice inside those systems, the five places it stalls, how to tell whether you are waiting on a human or a calendar, and what useful follow-up looks like when the usual friendly nudge has nowhere to land.

What a vendor portal actually does to your invoice

An accounts payable portal is a submission funnel with a validation layer on top. Coupa, SAP Ariba, Tipalti, Bill.com, and the dozens of homegrown vendor portals in between all work roughly the same way: you upload a document, the system tries to match it against something it already knows about, and only matched invoices move forward to approval and payment.

The important part for you is that matching is automatic and unforgiving. If the portal expects a purchase order number and your invoice has a project name instead, nothing escalates to a human who might use judgment. The invoice simply does not advance, and the status keeps reading something neutral like "submitted" or "in process" for weeks.

This is not the client being difficult. These systems exist because email approvals were losing invoices. The controls work — they just move the cost of a small formatting mistake onto the supplier, and the supplier is you.

The five places a portal invoice actually gets stuck

Almost every stalled portal invoice is stuck in one of five places, and knowing which one changes what you do next.

• A purchase order mismatch. The PO number is missing, expired, closed, or the invoice total exceeds what remains on it. This is the single most common cause, and it is invisible unless you go looking.
• A missing receipt or approval. Many portals need the person who requested your work to confirm it happened. Your contact may not know this is waiting on them.
• An incomplete vendor record. Tax forms, banking details, and insurance certificates all have to be current. An expired certificate can freeze payment on an otherwise perfect invoice.
• The payment run calendar. The invoice is approved and waiting for the next scheduled disbursement. Many organizations pay twice a month; a few pay once.
• The wrong submission channel. You emailed a PDF to your contact because that felt faster, so it never entered the portal at all.

Only two of these are about a person deciding something. The other three are about data being wrong or a date not having arrived. A polite reminder does nothing for any of them, which is why generic follow-up here feels like shouting into a well.

How to tell whether you are waiting on a person or a calendar

You can usually resolve this in one message. "Just checking in on invoice 1042" invites a reply of "let me look into it," which costs you another week. Ask instead for a status and a date:

"Hi Dana — invoice 1042 went into the portal on August 1 and still shows as in process. Is it waiting on an approval step, or is it approved and scheduled for a payment run? If it's scheduled, I just need the run date so I can plan around it."

That phrasing gives the recipient two easy answers instead of an open-ended task. If the reply is "it's in the next run on the 15th," your problem is solved — you are not chasing anything, you are waiting, and you can plan around it.

If the reply is vague or never comes, escalate sideways rather than upward — the accounts payable inbox can usually answer in a minute.

The questions to ask before the first invoice ever goes in

Nearly all of this is preventable at onboarding, when a new client is most willing to answer administrative questions. Before you send invoice number one, get five things in writing:

• The submission channel. Portal, dedicated AP email address, or both — and whether a copy to your contact helps or is ignored.
• Whether a PO is required. If yes, get the number and approved amount before you start work.
• Who approves. Name the person whose confirmation the invoice needs, so you know who to ask later.
• The payment run schedule. "We pay on the 15th and the last business day" turns a mystery into a date.
• What starts the clock. Net 30 from the invoice date and net 30 from the date the invoice is approved in the portal are very different promises. The second can quietly add two weeks.

That last point deserves its own thought. Terms are only as good as the event that triggers them, which is worth deciding deliberately — the difference between net 30 and due on receipt matters less than whether both sides agree on when day one starts.

When the portal says approved and the money still has not moved

This is the most frustrating version and the easiest to handle, because approved means the disagreement is over. Nobody is questioning the work or the amount. What remains is a decision about when cash leaves the building.

Ask for the payment run date and the method. If the date passes, reference it directly: "The portal showed invoice 1042 approved on the 12th and scheduled for the run on the 15th. I don't see it on our end yet — could you confirm it went out and share the reference number?" You are not accusing anyone of anything. You are asking for a fact one person can look up.

Keep a written record of these exchanges. The third time an invoice slips past a stated run date, that pattern is your argument for changing terms at renewal. One late payment is noise; a documented pattern is a negotiating position.

Build a follow-up rhythm that matches their calendar, not your anxiety

The instinct with a slow portal client is either to check obsessively or to give up entirely. A rhythm built around the client's actual schedule beats both, and it usually looks like three touches rather than ten.

• Day 3 after submission. A short confirmation that the invoice landed and shows a valid status. This is where PO mismatches are still cheap to fix.
• Day 10, or two days before the stated payment run. Confirm it is approved and on the run. This is the message that actually moves money.
• Three business days after a missed run. Reference the specific date and ask for the payment reference. Escalate to the AP inbox if your contact cannot answer.

Three messages per invoice sounds like a lot until you count the hours your current approach costs across every client. Scheduling those touches in advance — in a calendar, a spreadsheet, or a tool like DueDrop that sends the follow-up messages for you — turns an anxious background process into something that runs whether or not you remember it on a busy Tuesday.

Cutting a week off your average wait across every client reshapes a month more than a rate increase does — the same math behind how reliable follow-ups reshape your monthly cash flow.

When the portal is the wrong battle to fight

Sometimes the honest answer is that the client's process is slower than your business can absorb, and no amount of skillful follow-up will fix that. A ninety-day cycle at a company with a rigid approval chain is a structural fact, not a communication problem.

The pressure is real and it is widespread: the QuickBooks 2026 Small Business Late Payments Report found that nearly three in five small businesses now have invoices more than thirty days overdue, up sharply from the year before.

If a portal client is otherwise good work, the fix is commercial rather than conversational: a deposit up front, progress billing at shorter intervals, or a late fee that gives the payment run a reason to include you. If the client is not otherwise good work, the portal is only the most visible symptom, and the decision in front of you is about the relationship, not the software.

Frequently Asked Questions

How long should I wait before following up on an invoice in a client's portal?

Check the status around day three to confirm the invoice was accepted and matched, then follow up again a few days before the client's stated payment run. Waiting the full thirty days before the first check-in is the most common mistake, because a formatting or purchase order problem discovered on day three costs you nothing, while the same problem discovered on day thirty costs you an entire cycle.

Who should I contact when an invoice is stuck — my project contact or accounts payable?

Start with your project contact if the invoice appears to be waiting on an approval or a confirmation that the work happened, since that step is usually theirs. Go directly to the accounts payable inbox if the invoice is already approved and you need a payment date or a reference number. AP teams can look up a specific invoice number quickly and generally prefer a direct question to a forwarded thread.

Is it unprofessional to ask a client for their payment run schedule?

Not at all. It is a routine operational question, and asking it during onboarding signals that you run an organized business. Most accounts payable teams answer it in one line. Knowing the schedule also removes the guesswork that makes follow-up feel confrontational, because you are referencing a date the client gave you rather than a deadline you invented.

Can I invoice outside the portal to get paid faster?

Usually no, and trying often makes things slower. An invoice that arrives by email at a company that requires portal submission tends to be forwarded once and then forgotten, with no audit trail and no status you can check. If your contact suggests emailing a copy as well, treat that as a courtesy copy rather than the actual submission.

Key takeaways

• A portal invoice that is not moving is usually stuck on data or a date, not on someone's goodwill.
• Ask a question with two easy answers: waiting on approval, or scheduled for a payment run?
• Get the submission channel, PO requirement, approver, run schedule, and clock-start rule before the first invoice.
• Approved but unpaid is a timing question — ask for the run date and the reference, not for a favor.
• Three planned touches per invoice beat ten anxious ones, especially when they are scheduled rather than remembered.
• When the client's cycle is structurally too slow for you, change the commercial terms rather than the wording.