Systems and records
Supplier onboarding evidence dataset: existing is not approved
By SourceX Editorial · Updated
9 sections
Short answer
A supplier that exists in the vendor master is not necessarily approved. Approval means every required onboarding gate, such as identity, tax ID, bank verification, screening, category scope and quality sign-off, has dated evidence from an authorized person that still holds on the purchase date and covers the item being bought. A supplier onboarding evidence dataset records those gates per purchase, so the verdict can be checked rather than assumed.
Provenance trail
Supplier onboarding evidence
Key takeaways
- A vendor master record proves the supplier can be selected, not that onboarding was completed for this category, site or specification.
- Status flags differ by system: Oracle separates prospective from spend authorized suppliers, while Business Central and ERPNext use blocks and holds that can allow purchasing but stop payments.
- Judge approval per purchase: each gate needs evidence, a decision owner, a scope that covers the line and a date that is still valid.
- Pending bank changes, expired documents and approvals tied to an older specification revision are the most common reasons an active supplier is not approved.
- Build the task from as-of snapshots and audit history, and label it with what actually happened after the order, not with the current status.
How do you tell an existing supplier from an approved one?
Check four things for the specific purchase: the supplier's status flags on the order date, the evidence behind each onboarding gate, whether the approval covers this category, site and specification revision, and whether any document has expired. Existence answers only the first question, and only partly.
A purchasing agent who sees a familiar name in the supplier lookup is looking at a master record. That record may have been created by a registration workflow, a data migration, a one-time vendor setup in accounts payable or an acquisition. None of those routes proves that the tax, bank, screening and quality steps were finished for the work now being ordered.
The practical rule is simple to state and hard to apply from memory: approved means approved for this purchase, by someone with authority, on evidence that is still current. Everything else is a supplier that exists.
Why does the vendor master record prove so little?
Because each ERP encodes approval differently, and most encode it as a coarse flag rather than as a list of cleared gates. Reading one flag as the whole answer is the commonest mistake an agent or a new buyer makes.
Oracle Fusion Procurement is explicit. Its supplier model separates prospective suppliers, which can take part in sourcing negotiations and supplier qualification but are not available for ordering and invoicing, from spend authorized suppliers. Oracle's documentation says spend authorization needs a more complete level of supplier information and is subject to approval by the supplier manager.
Dynamics 365 Supply Chain Management runs onboarding as a vendor request that moves from draft through review and pending approval to approved or rejected. Microsoft's documentation says the vendor account is created when the request is approved, and a rejection must carry a reason. Vendors created directly in the vendor master, outside that workflow, never pass through those statuses.
Business Central and ERPNext lean on blocks instead. In Business Central the Blocked field is blank, Payment or All, and a Payment block still lets people use the vendor on purchase documents. ERPNext has a Block Supplier switch with a hold type of All, Invoices or Payments and an optional release date, plus separate Prevent POs, Warn POs, Disabled and Is Frozen settings. An unblocked supplier in either system is simply one nobody has stopped.
| System | What the record shows | What it does not show |
|---|---|---|
| Oracle Fusion Procurement | Business relationship: prospective or spend authorized, with a spend authorization request status | Which documents were reviewed, or whether a category or site approval exists |
| Dynamics 365 Supply Chain Management | Vendor request status from draft to approved or rejected, with a rejection reason | Approval status for vendors created outside the request workflow |
| Business Central | Blocked field: blank, Payment or All | Why the vendor is unblocked or whether onboarding finished |
| ERPNext | Block Supplier with hold type and release date; Prevent POs and Warn POs flags; Disabled; Is Frozen | Evidence behind the flags or their scope by item or site |
The documentation and approval completeness task
The asset below is a gate list. For each purchase in the dataset, every gate gets one of four states: complete, missing, expired or out of scope, plus a pointer to the evidence. A supplier is approved for the purchase only when every gate required for that category is complete.
Two gates deserve emphasis because the evidence is easy to misread. Tax identity matters because the IRS requester instructions for Form W-9 describe backup withholding when a payee has not provided a taxpayer identification number or has provided an incorrect one, and the IRS sends a notice when the name and number on an information return do not match its records. Bank details matter because Dynamics 365 can be set to require approval for every new vendor bank account, including ones imported through a data entity, and for changes to selected fields: a pending change is an open gate, not a formality.
Which gates apply varies by company and category. Keep the list in the task as a configuration per category, so a cleaning supplies vendor is not marked unapproved for lacking a quality audit it never needed.
| Gate | Evidence record | Usual home | Complete when | Common failure |
|---|---|---|---|---|
| Legal identity | Registration request with legal name and registration number | Supplier portal or vendor request | Name and number match the master record | Trade name in the master, legal name elsewhere |
| Tax identity | Signed tax form and a name and number match result | AP document store | Form on file, signed, no open mismatch notice | Form missing for vendors created by migration |
| Bank account | Bank details plus an approved change record | AP bank account workflow | Approved, and verified through contact details on file | Change pending, or verified only by email reply |
| Restricted-party screen | Screening result with list version and date | Compliance tool log | Screened before first order and on the company's rescreen schedule | Screen predates a name or ownership change |
| Category scope | Approved procurement categories | Vendor request or supplier profile | Category of the order line is in the approved set | Approved for packaging, ordered for machined parts |
| Technical or quality approval | First article, audit or qualification record tied to a specification revision | Quality system | Approval revision equals the revision on the order line | Approval tied to an older revision |
| Contract and terms | Signed master agreement or accepted standard terms | Contract repository | In force on the order date and covers the category | Expired agreement, orders continued |
| Insurance and certificates | Certificates with expiry dates | Supplier portal | Unexpired on the order date | Certificate lapsed between orders |
| Risk questionnaire | Questionnaire responses and reviewer sign-off | Vendor request questionnaires | Reviewed by a named role | Submitted but never reviewed |
| Final approval | Approval action with approver role and timestamp | Workflow history | Approver held the authority for this category and risk level | Approved by the requester themself |
What goes into one task instance, and how is it graded?
One instance is one order line, frozen at the moment the order was placed. The model or the trainee sees what a buyer could have seen then, and answers whether the supplier was approved for that line and why.
At a glance
What goes into one task instance, and how is it graded
Grading uses the evidence, not the final status. An answer that says approved is wrong if any required gate was open on the order date, even if the gate was closed a week later and the current master looks clean.
- Inputs: the order line (category, item, specification revision, site, quantity, date), a vendor master snapshot as of that date, the onboarding request history, an index of onboarding documents with dates and expiries, and any customer or program constraint on approved sources.
- Question: was this supplier approved for this line on this date, and if not, which gates were open and who could have authorized an exception?
- Verdict labels: approved; approved under a documented exception; not approved, gate open; not approved, out of scope.
- Required reasoning: each open gate named with its evidence pointer, and the authority needed to close or waive it.
- Outcome fields, hidden from the solver: receipt result, invoice hold or release, payment block events, returns and any later corrective action against the supplier.
- Grading: verdict correct; every open gate found; no gate invented; authority named at the right level; evidence pointers resolve to real records.
Which constraint makes the obvious supplier the wrong one?
The obvious choice fails when a constraint sits outside the vendor master: a scope limit, a pending change, a revision mismatch or a customer rule. The table lists the six that most often turn an active, familiar supplier into an unapproved one.
Bank changes deserve their own warning. The FBI's Internet Crime Complaint Center advises verifying vendor payment detail changes through contact information already on file rather than through details in the requesting email. A dataset that treats an emailed bank update as complete teaches exactly the behavior fraudsters exploit.
| Constraint | How it shows up | Evidence that settles it | Correct verdict |
|---|---|---|---|
| Category scope | Supplier approved for one category, line is in another | Approved category list against the line's category | Not approved, out of scope |
| Specification revision | Engineering change after the supplier's approval | Change notice date and the approval's revision | Not approved until requalified |
| Customer approved source list | Program requires sources the customer approved | Customer constraint record for the program | Not approved for that program, even if approved generally |
| Pending bank change | New bank details awaiting approval | Change proposal status and verification record | Purchase may proceed; payment gate open |
| Expired document | Insurance or certificate lapsed | Expiry date against order date | Not approved, gate expired |
| Hold type | Payment-only block or warning flag | Hold type, release date, flag history | Depends on gate: purchasing allowed, payment not |
Worked case (illustrative): an active vendor with one gate open
This case is invented to show the method; the counts and durations are illustrative. A buyer raises an order line for a machined bracket at specification revision C. The supplier has been active for 14 months, has 37 prior receipts, carries no block and is the fastest quote.
The document index shows legal identity, tax form, bank account, screening, contract and insurance all complete and in date. The quality approval, however, is a first article inspection against revision B. Engineering released revision C 21 days before the order, with a tighter tolerance on one hole position. The approval gate is therefore out of scope for this line.
Correct answer: not approved for this line. The open gate is technical approval at revision C; closing it needs a new first article or a documented waiver from the quality owner. The hidden outcome confirms the reasoning: receiving inspection rejected 3 of the first 40 parts on the changed dimension.
Exception variant: the same facts, plus a signed deviation from the quality manager allowing revision B parts for one lot while requalification runs. The verdict becomes approved under a documented exception, and the answer must cite the deviation, its lot limit and its expiry.
Counterexample: the same supplier, an order for a bracket still at revision B. Every gate is complete, so the correct answer is approved, and an answer that flags the revision C change is wrong because that change does not touch this item.
Reconstructing approval as it stood on the order date
Build every instance from history, not from today's master. Approval state changes: blocks are lifted, certificates lapse, bank details change and categories are added. A label taken from the current record will be wrong for many older orders.
Use the workflow and change history to rebuild each gate as of the order timestamp. Where the history is missing, mark the gate unknown and keep the instance out of the graded set rather than guessing.
- Pull order lines with their creation timestamps, categories, items, revisions and sites.
- Join the vendor request or registration history, keeping every status change with its timestamp and actor role.
- Join the document index with issue and expiry dates; join change notices for the items ordered.
- Rebuild block and hold flags from change logs where the system keeps them; otherwise record them as unknown.
- Attach outcomes after the order: receipt and inspection results, invoice holds, payment blocks, returns, corrective actions.
- Sample on purpose: include approved lines, exceptions and not-approved lines, and keep counterexamples where the obvious flag would mislead.
When the verdict needs a procurement or compliance specialist
Stop and route to a specialist when the answer depends on judgment the records cannot carry. A possible restricted-party match, a tax mismatch notice, a regulated category such as medical devices or defense, or an approval whose delegated authority is unclear all need a person who owns that decision.
For the dataset, these cases are still valuable. Label them as escalate, record who resolved them and how, and do not convert a specialist's judgment into a rule the model is expected to apply on its own.
Licensing onboarding history without leaking supplier secrets
Onboarding records are among the most sensitive files a procurement team holds. Bank details, tax identifiers, questionnaire answers and insurance documents belong to suppliers or describe them, and many supplier agreements limit how that information is shared. Having access to these records is not the same as holding the rights to license them, and removing names does not create those rights.
The task needs gate states, dates, scopes and evidence pointers, not the documents themselves. Replace document contents with typed metadata, never export bank or tax numbers, pseudonymize supplier and approver identities, and have counsel review supplier contract terms before any onboarding history is offered.
For procurement teams that clear those reviews, SourceX takes selected operational records through rights review, preparation and delivery as licensed AI datasets, with the company approving scope and signing before any onboarding history is handed over. It opens with a short company assessment that needs no upload.
Frequently asked questions
Is a supplier with no block in the ERP an approved supplier?
No. A missing block means nobody stopped the supplier, not that onboarding was completed. Approval needs evidence for each required gate, covering the category and specification on the order, and still valid on the order date.
What is the difference between a prospective and a spend authorized supplier?
In Oracle Fusion Procurement, a prospective supplier can take part in sourcing and qualification but is not available for ordering and invoicing. A spend authorized supplier has been approved by a supplier manager after more complete information was collected, and can be used for orders.
Can a supplier be approved for one purchase and not another?
Yes. Approval is usually scoped by category, site or specification revision. A supplier approved to make a part at one revision is not automatically approved after an engineering change, and a supplier approved for packaging is not approved for machined parts.
Why should the dataset use as-of snapshots instead of the current vendor record?
Because the current record reflects changes made after the order. A certificate renewed later or a block lifted later would make an unapproved purchase look approved, and the labels would teach the wrong answer.
Should onboarding documents be included in a licensed dataset?
Usually not. The task works with gate states, dates and evidence pointers. Bank details, tax numbers and questionnaire answers stay out, and supplier agreements need a contract review before any onboarding history is shared.
Sources
- Oracle's supplier model separates prospective suppliers, which are not available for ordering and invoicing, from spend authorized suppliers approved by a supplier manager. Source
- Dynamics 365 vendor requests move from draft to approved or rejected; the vendor account is created on approval and rejections need a reason. Source
- Dynamics 365 can require approval for new vendor bank accounts, including imported ones, and for changes to selected bank account fields. Source
- Business Central's vendor Blocked field allows all transactions when blank, blocks new payments with Payment and blocks all transactions with All. Source
- ERPNext suppliers carry a Block Supplier switch with hold types All, Invoices or Payments and a release date, plus Prevent POs, Warn POs, Disabled and Is Frozen settings. Source
- The IRS requester instructions for Form W-9 describe backup withholding when a payee's TIN is missing or incorrect, and notices for name and TIN mismatches. Source
- The FBI's IC3 advises verifying vendor payment detail changes through contact information on file rather than details in the requesting email. Source
See if your company qualifies
A short company assessment. No data uploads are needed.