Every procurement workflow category assumes that the supplier it is processing has been paid before. The purchase order workflow assumes an approved vendor with negotiated terms in the ERP. The invoice receipt workflow assumes a three-way match against a PO and a goods receipt record. The payment processing workflow assumes a vendor record with verified banking details. The tax compliance workflow assumes a W-8 or W-9 form on file with a confirmed TIN.
The first payment to a new supplier violates every one of these assumptions simultaneously. The vendor record does not exist yet. The banking details have not been verified. The tax form has not been collected. The supplier may not be in any compliance-reviewed database. The result is an exception-handling cascade that touches every part of the AP and procurement operation.
Understanding exactly where the workflow breaks, and why it breaks there, is the first step toward designing a better path.
Where the Purchase Order Workflow Breaks First
Most organizations require a purchase order before AP will process an invoice. The PO creates the financial commitment, establishes the terms, and provides the basis for three-way match. For this to work, the supplier must be in the ERP with an approved vendor record before the PO is issued.
For a new supplier, this means the PO cannot be issued until onboarding is complete. The business unit that needs the work done cannot make a formal commitment until procurement has built a vendor record. In practice, this plays out in one of two ways. The business unit waits, and the project start is delayed by the length of the onboarding process. Or the work starts on an informal basis, the PO is issued retroactively when the vendor record is ready, and the organization has created a commitment that was never properly authorized at the time it was made.
Neither outcome is what the PO process was designed to produce. The PO workflow works well for planned procurement with established suppliers. It creates significant friction for unplanned engagements with new suppliers, particularly when the need is urgent.
Where the Invoice Matching Workflow Breaks
Assuming the vendor record is eventually created and the PO issued, the invoice arrives and enters the matching workflow. Three-way match requires the invoice to match a PO and a goods receipt. For services, the equivalent is a confirmed service receipt or statement of work milestone completion.
For a new international supplier, the invoice may also arrive in a different format than expected. The currency may require conversion. The tax treatment may need clarification. The invoice may reference a contract that is stored in a different system from the PO. Each of these issues generates a manual exception that someone must resolve before the invoice can be approved for payment.
The cumulative effect is that a new international supplier's first invoice will almost always be processed as an exception rather than through the standard workflow. This is expected and unavoidable to some degree, but it means that every first-payment vendor consumes disproportionate AP staff time regardless of the dollar amount.
Where the Compliance Workflow Creates the Longest Delay
The compliance steps for a new foreign supplier are not optional and they are not fast under a standard workflow. KYB entity verification confirms that the supplier's legal entity exists and is in good standing in its home jurisdiction. Sanctions screening checks the entity against OFAC's Specially Designated Nationals list and any additional applicable sanctions databases. Tax form collection gathers the appropriate W-8 form, reviews it for completeness, identifies and resolves errors, and retains the form as part of the payment record.
Each of these steps requires either internal expertise or access to third-party databases that most AP teams do not have direct access to. The compliance review is typically routed through a legal or risk team that has its own queue and its own priorities. When that queue is backed up, the compliance review for a new supplier sits and waits.
An international supplier engaged for a two-week project may wait four weeks after delivering their work before their first payment is processed. The work was good. The relationship was positive. The experience of waiting four weeks to be paid after completing the engagement is not the first impression the procurement team intended to create.
Where the Banking Verification Workflow Adds Unexpected Friction
International banking details require additional verification that domestic bank accounts do not. SWIFT codes, IBAN formatting, correspondent bank relationships, and intermediary bank requirements vary by country and institution. Banking information received via email from a new supplier is unverified until it is matched against an independent source or confirmed through a callback or identity verification process.
This verification step exists to prevent payment fraud, and it is a legitimate and necessary step. The challenge is that it typically cannot start until the vendor record creation process has begun and the banking details have been provided. For a new international supplier who is not familiar with the verification process, the request for additional banking information after they have already provided it can seem like unnecessary friction rather than a reasonable fraud prevention step.
The Common Thread: Everything Is Designed for Repeat Transactions
The common element across all of these breakpoints is the same: the procurement workflow was designed assuming that the relationship with a supplier begins before the payment conversation does. The vendor record is created as part of a relationship-building process, not as a last-minute prerequisite to payment. The compliance review happens in advance because the relationship justifies the investment. The banking details are verified because they will be used many times.
For a supplier who will be paid once, this architecture creates process overhead that does not serve any ongoing purpose. The vendor record that takes four weeks to create will never be used again after the single payment is made. The compliance review that consumed three weeks of calendar time produced documentation for a relationship that does not continue.
The solution is not to reduce the rigor of compliance or verification for one-off payments. The KYB check and sanctions screening need to happen regardless of whether the relationship is ongoing. The W-8 form needs to be collected and reviewed. The banking details need to be verified. What can change is the architecture: rather than building a supplier relationship as a prerequisite to payment, run the compliance and verification steps as part of the payment process itself. The end result is the same compliance documentation and audit trail. The timeline is hours rather than weeks.
This is a workflow design problem that the procurement industry has understood for a long time and not adequately solved. The vendor record architecture is deeply embedded in ERP systems that were not designed with one-off international payments in mind. Solving it requires either a significant change to ERP workflow configuration or a separate payment path for first-time international suppliers that handles compliance at the payment level rather than the relationship level.
Both approaches are available. The organizations that have made the most progress on first-payment vendor processing are the ones that chose one and implemented it, rather than continuing to treat every first-payment vendor as an exception to be handled case by case.