Answer

Client wants me to use their vendor portal: what to do

Vendor portals are designed for the buyer, not the seller. Sometimes you have no choice. Often you have more room to push back than it seems. Here is how to evaluate the request, when to comply, when to negotiate, and how to keep your own records intact either way.

Keep your own invoice record Back to all answers →

When a client wants you to use their vendor portal, the question is not really "do I have to," it is "what does this actually cost me, and is the engagement worth that cost." Vendor portals (Ariba, Coupa, Tipalti, Bill.com, an in-house tool, or a generic Microsoft Forms page) shift work onto the seller in exchange for AP efficiency on the buyer side. The work shifted is real: setting up the portal account, entering invoices into a system you do not control, reconciling between the portal and your own records, often a hold on payment until the portal validates the submission. Sometimes the engagement is worth that overhead. Sometimes you can push back and keep emailing the invoice directly. Sometimes the portal is genuinely optional and your contact did not know.

First, find out if the portal is actually required

A surprising number of vendor-portal requests turn out to be soft. Three quick checks:

Ask "is this a hard requirement, or your team's preference?" If the answer is "preference," you have room to negotiate. If the answer is "hard, AP will not process without it," you do not.
Ask the procurement contact directly, not your day-to-day contact. Operations contacts often default to "use the portal" because that is what their finance team told them. The procurement or AP contact knows whether there is an exception path for small vendors.
Ask what happens if you email the invoice anyway. "It will be rejected" is different from "it will be processed but slowly." The second is workable; the first is not.

When to comply

✓The engagement is large or ongoing. An hour of portal setup for a multi-month contract is fine. For a one-time $500 invoice, the overhead is disproportionate.
✓The portal is free for vendors. Most are, but not all. Some (notably Ariba's Standard Account is free, but Enterprise tiers charge transaction fees) push the cost onto you. If the portal charges fees, factor that into the engagement price before agreeing.
✓The client has signaled flexibility on terms. A client willing to pay net-15 to offset the portal overhead is a different proposition from one demanding net-60 plus portal submission.
✓You expect more clients with the same portal. Enterprise buyers cluster around a handful of portals (Ariba, Coupa, Bill.com). If your client base is moving that direction, the first setup is an investment, not a sunk cost.

When to negotiate or decline

×One small invoice, no future work expected. The portal setup time exceeds the value of the engagement. Ask if you can email this one to AP directly, with the understanding that future invoices will go through the portal.
×The portal charges meaningful transaction fees. Fee + the time cost can exceed your margin. Either negotiate a price increase to absorb the fee or explore the "free for small vendors" tier if the portal offers one.
×The portal locks you into a payment system you do not want. Some portals route payment through their own rails (with delays, currency conversions, or holds). If you bank somewhere specific or need fast payment, the portal can be a deal-breaker.
×The portal requires data you are not willing to provide. Some require W-9 or full banking info before any invoice is allowed. For one small engagement, decide whether the information transfer is worth it.

How to keep your own records intact either way

Whatever you do for the portal, also do for yourself. The portal is the client's system of record, not yours.

→Create the invoice in your own tool first. Generate the invoice number, dates, and PDF in your invoicing system, then copy the details into the portal. Your records stay coherent.
→Keep the original PDF in your accounting records. The portal may not give you a downloadable copy of the submitted version, or may store it in a format your accountant cannot use.
→Log the portal submission date separately. "Submitted to Ariba on May 27" is the start of the payment clock from the client's side. Track it; AP will reference it if you have to follow up.
→Reconcile the portal status against your own records monthly. Status mismatches (you have it as paid, the portal still says pending) are common and worth catching.

Working with vendor portals

Can I refuse to use a vendor portal?

Yes, but understand what you are refusing. For one-off engagements with small dollar values, declining is often reasonable and the client may accept email submission. For ongoing engagements with enterprise buyers, refusing the portal usually means losing the engagement. Treat it as a commercial decision, not a process objection.

Should I increase my prices to cover the portal overhead?

For meaningful engagements, yes, especially if the portal charges fees that come out of your invoice. A 2-5 percent uplift on enterprise work is normal and offsets the administrative cost. Bring it up before agreeing terms, not after.

What is the typical setup time for a vendor portal?

For Ariba Standard Account, Coupa, or Bill.com, expect 30 to 90 minutes for first-time setup, including any tax forms and bank details. For in-house portals or older enterprise tools, it can be longer. Set aside dedicated time; do not try to set up the portal in the middle of trying to submit an invoice.

Do I still send an invoice email if the client requires the portal?

Usually no. The portal is the client's preferred channel; emailing in addition can confuse AP. Confirm with your contact whether they want a heads-up email when an invoice is submitted to the portal (some do, for visibility) or whether portal alone is enough.

What happens if the portal says my invoice is rejected?

Find out the specific reason. Common rejections are missing PO, wrong tax format, missing fields the portal requires that are not on standard invoices, or a duplicate-detection false positive. Fix the specific issue and resubmit. Email your contact if the portal does not give a clear reason; they can usually see the AP-side notes that you cannot.

Keep your own clean invoice record

Whatever portal your client uses, JupiterInvoice keeps a clean, branded copy of every invoice you sent, with view history, version trail, and downloadable PDF. Submit to the portal, but keep your own canonical record. Free, no signup.

Create your first invoice

No signup required. Build now, save later.

How to forward an invoice to accounts payable

How to forward a vendor's invoice to your AP team without losing the original, and what senders can do to make AP forwar...

Client wants to add a PO number after the invoice is sent

When a client asks you to add a PO number after sending an invoice, you do not have to reissue. Here is how to handle it...

Client says they never got the invoice: how to handle it

When a client says they never received your invoice, it is rarely a lie. Spam, wrong contact, or corporate email strippi...