Why Supplier Onboarding Decides When You Get Paid

The contract is signed, and everyone has moved on to the next deal, but your new customer pays through Coupa and hasn’t set you up inside it yet, so your first invoice has nowhere to go. Nobody has rejected it, and nobody has disputed it. As far as their system is concerned, you don’t exist.

Most finance teams never give this gap a name, so nobody manages it. It surfaces a quarter later as a customer who was meant to start paying in January, and starts paying in March.

What does supplier onboarding involve?

Supplier onboarding is how your customer turns your company into an approved, payable vendor inside their procurement system, and the contract you just signed doesn’t do it. A different team owns that work on a different clock, with its own queue and priorities.

The key steps rarely change from one customer to the next. Their procurement team sends you a registration invitation, you build a company profile with your vendor data, and you enter the legal entity name, remittance address, and contact information exactly as they’ll appear everywhere else. Then you upload compliance documents, usually a W-9 or the local tax equivalent, often alongside business licenses, insurance certificates, and your banking details.

What you sell decides the rest. If you supply goods, you may need to load a catalog, and if you supply services, you’ll probably need to agree to a service entry process before anyone can approve a payment against it.

Then the compliance checks start. Someone in their accounts payable or vendor master team runs a risk assessment on your record and verifies your bank account, often by calling a number they look up themselves, rather than the one printed on your letterhead. It’s sound fraud control, and it’s also slow, because it depends on two people being at their desks at the same time.

Once they approve the record, your customer can raise purchase orders against you, and only then can you send an invoice.

Why does the vendor onboarding process take weeks and not days?

Because the key steps run in sequence rather than in parallel, each one belongs to a different team. Procurement owns the invitation, your controller owns the tax forms and banking details, and their vendor master team owns the compliance checks. Nobody owns the whole chain, which is why nobody chases it.

That sequencing is also why small errors cost so much. Miss one field, and the packet doesn’t pick up where it left off; it rejoins the back of the queue behind everything that arrived while you were fixing it. A record can bounce because the legal entity name on your tax form doesn’t match the one on your bank letter, down to the punctuation.

Then there’s the part that surprises finance leaders more the second time than the first: every customer runs its own version of this. A different portal, different required fields, and a different definition of a complete record mean that what your team learned onboarding one customer only partly transfers to the next. The directory of portals your customers use shows how many versions are in circulation, and the setup guide covers what a typical registration asks for.

What does the delay cost you?

Cash is the obvious answer. You’ve booked the revenue, and none of it has moved, and your payment terms started running at signature while their clock started weeks later.

The less obvious cost is that your reporting can’t see any of it. Days sales outstanding (DSO) counts from the invoice date forward, and supplier onboarding happens before an invoice exists, so every week that it sits outside the number your board reviews. You can post your best DSO of the year while a customer who signed in January still hasn’t paid you anything.

Your first invoice also carries more risk than any invoice you’ll send that customer later. It goes against a brand new record with fields nobody has tested, so it comes back more often, and a rejection at that stage is the easiest one all year to miss, because submitted isn’t the same as accepted, and nobody is watching an account that hasn’t paid yet.

What about network fees?

Some networks also charge you to participate, and the amount you pay scales with how much you transact through them. SAP publishes its supplier pricing tiers publicly, so if you’re budgeting for Ariba supplier fees, start there rather than with a number someone half-remembers from a previous job.

Ariba network fees are the ones finance teams ask about most often. SAP Ariba supplier fees combine a subscription level with your document volume and transaction value, which means your cost moves with your revenue, so it’s worth understanding the structure before your first invoice rather than after it.

What can you do before the contract closes?

Most of this work can happen earlier than it currently does, and the cheapest place to start is your sales handoff. Add one question to it: which system does this customer pay through, Coupa, Ariba, Tungsten, Tipalti, or something built in-house? Your account executive can ask it on a call they’re already having, weeks before you need the answer.

Ask for two names while you’re there. You want the person who sends the registration invitation and a contact in accounts payable, because chasing a shared inbox after signature costs you days you won’t get back.

Keep a ready pack in one folder so you’re never assembling it under pressure: current tax forms, a signed bank verification letter, insurance certificates, business licenses, remittance instructions, and your legal entity details. Most onboarding delays come down to one missing document, repeated across customers, and the folder saves time on every new account after this one.

Give onboarding a single owner, because split across three people, it becomes nobody’s deadline. Log what each portal asks for as you go, since the second customer on the same procurement system should move faster than the first, and it will only if somebody writes it down. That habit reduces risk later too, and it’s the same discipline that keeps invoices from stalling later in the cycle.

How Monto handles a new customer’s portal

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.

For a new customer, that means an agent learns the portal’s compliance requirements once and applies them from the very first invoice, so your first submission behaves like your hundredth. It works within the wider order to cash process rather than sitting alongside it as another system to check.

FAQ

How long does supplier onboarding take?

It varies by customer and by portal, so any single number would mislead you. What sets the length is how many approvals sit in sequence on their side and how complete your compliance documents are when you submit them, which is the part you can actually control.

Can we invoice before the supplier onboarding process finishes?

Almost never. Most enterprise customers won’t process an invoice from a vendor record nobody has approved, and sending one outside the portal usually adds a step rather than saving one, since someone still has to key it in once you’re set up.

Why does each customer ask for different information?

Each company configures its own portal and sets its own compliance requirements, so two customers running identical software can still ask you for different things. The software may be the same, but the rules layered on top of it aren’t.

Does onboarding delay appear in DSO?

No, and that’s what makes it easy to miss. DSO measures from the invoice date, so the time you spend waiting to become payable falls entirely outside it, and the only way to see the full gap is to measure from contract signature through to the first payment received.