A specialized consulting firm in South Korea completed a market entry research engagement for a procurement team at a large consumer goods manufacturer. The final report was delivered on schedule. The invoice followed the same day. What came next was not fast: the invoice sat in exception routing for 31 days before payment was dispatched.
The delay was not caused by a missing approval or a disputed invoice amount. It was caused by the standard vendor onboarding process. The consulting firm was not in the vendor master. Before AP could schedule a payment, someone had to create a record, and creating that record meant six sequential handoffs across four teams.
What Standard Vendor Onboarding Actually Involves
When an enterprise AP team receives an invoice from a supplier with no existing vendor record, the process that follows is more complex than it looks from the outside. In the case we observed, it went like this.
First, procurement submitted a new vendor request, including the supplier's legal name, country of registration, and banking details. That request entered a compliance review queue managed by the legal team. Legal ran a Know-Your-Business check: verifying the entity's registration, checking ownership structure, and screening against relevant sanctions lists. That step took about a week, including queue time.
Next, the AP team sent a tax form request to the supplier. Because this was a South Korean entity receiving payment for services from a US company, the applicable form was a W-8BEN-E. The supplier's finance contact was not familiar with the form and needed two rounds of follow-up to complete it correctly. That exchange added another five to seven business days.
Treasury reviewed the banking details to verify the SWIFT code and account information matched the entity on the invoice. That was a half-day step once someone got to it in the queue. Finally, AP entered the vendor record manually into the ERP, routing it for a manager approval to confirm the new entry was correct before any payment could be scheduled.
Total calendar time from invoice receipt to first payment: 31 days. The supplier's project had been completed. The work was done. The only thing outstanding was the administrative record creation.
Why the Process Exists
It would be easy to describe this as bureaucratic friction and stop there. That would miss the point. Each step in the process exists because there is a real risk it is designed to address.
KYB review protects against payments to sanctioned entities or fraudulent suppliers. Tax form collection establishes the correct withholding treatment before funds leave the account. Banking detail verification prevents wire fraud, which is a real and frequent attack vector for enterprise AP operations. ERP record entry ensures the payment has an audit trail and cannot be made again without a deliberate second authorization.
These are legitimate requirements. The problem in this case was not that the requirements were wrong. The problem was that all of them were designed around the assumption that a vendor record takes six weeks because the vendor will be paid hundreds of times over the next three years. For a one-time international engagement, that assumption does not hold.
The Decision to Find a Different Path
After the South Korea situation, the procurement director we worked with went back through the prior 12 months of payment records. She found 19 first-time international supplier payments during that period. The average time from invoice to payment was 28 days. The shortest was 14 days. The longest was 47 days.
In aggregate, those 19 payments had held up project deliverables, strained new supplier relationships at the point of first impression, and consumed an estimated 85 hours of AP, legal, and treasury staff time on record creation work that would never be reused: 14 of the 19 suppliers had been paid exactly once and had no subsequent engagement.
The team's question was not how to speed up vendor onboarding. It was whether one-time international payments needed to go through vendor onboarding at all.
What Changed
The team piloted a different path for their next one-off international payment: a freelance data visualization specialist in Germany, engaged for a single six-week project. Rather than opening a new vendor record, they submitted a payment request through a third-party payment intermediary that handled the compliance layer directly.
The intermediary sent a guided form completion request to the German supplier. The W-8BEN was completed within two hours. KYB verification ran against EU business registries and sanctions lists. Withholding was assessed: services income from a German individual providing work performed outside the US, with a completed W-8BEN claiming treaty benefits under the US-Germany agreement, resulted in zero withholding obligation. The payment was dispatched the same day.
The team received a structured CSV record with all transaction details, tax form references, and verification outcomes for import into their ERP. The audit trail was complete. The compliance steps had all run. The time from request submission to payment confirmation: under four hours.
What the AP Team Did Differently
From the AP team's perspective, the submission process was a single form: supplier name, invoice amount, country, and payment purpose. No email thread with legal. No chasing the supplier for forms. No ERP entry before payment could be made.
The ERP entry happened after the fact, using the structured record from the intermediary. For audit purposes, this approach is actually cleaner: the record contains the verification outcomes, form references, and withholding calculation alongside the payment details, rather than having those scattered across separate systems and email threads.
Over the next six months, the team routed 11 first-time international payments through this approach. Average time to payment: under six hours. No compliance exceptions. No delayed project deliverables. No frustrated suppliers.
Where This Approach Has Limits
We want to be direct about what this case study does not mean. The approach described here is not a substitute for the vendor master on repeat supplier relationships. If a supplier is going to receive 20 payments over the next two years, the investment in a thorough vendor onboarding process is entirely justified. The verification work amortizes across those payments, and having the supplier in your ERP with approved payment terms and verified banking details creates real operational value.
The case for routing around standard vendor onboarding applies specifically to one-off and first-time international payments where the onboarding process is structurally disproportionate to the relationship. A six-week record creation process for a payment that will never be made again is not caution. It is a workflow design choice that was never updated to account for the modern procurement reality where one-off international engagements are common.
The compliance requirements do not change. Supplier identity verification, tax form collection, withholding calculation, and sanctions screening all need to happen before the payment leaves the account. The question is only where those steps happen and who is equipped to run them efficiently.