Automating Supplier Onboarding Without Losing Control of Business Data

Where company checks fit in supplier creation: register prefill, duplicate detection, review queues and monitoring, while keeping your supplier data clean.

· By the Fuentio team · 7 min read

Share image: "Automating Supplier Onboarding Without Losing Control of Business Data" on Fuentio's paper background, with the Use case label.

Procurement and accounts-payable software lives or dies by its supplier master data. Every supplier record you create is a company you may pay, so a typo in a legal name, a duplicate record or a supplier that quietly closed turns into a failed payment, a confused audit or worse. Automating supplier onboarding helps, as long as the automation makes the data more reliable, not just faster. This guide shows where company checks fit and how to keep control of the result.

What you'll learn

  • The four points in supplier creation where a company check belongs
  • How to prefill supplier records from the register without losing what the supplier told you
  • How official identifiers make duplicate detection reliable
  • How to design review queues and ongoing monitoring that people actually use

Short answer: require the official identifier when a supplier is created, prefill the legal details from the register, key the supplier on that identifier to catch duplicates, route anything that isn't clearly verified to a review queue with the reasons shown, and watch active suppliers so changes reach you instead of waiting for the next manual review.

Where do company checks fit in supplier creation?

A typical supplier creation flow has four moments where the register helps:

  1. Capture: the supplier, or a buyer on its behalf, fills in a form. Ask for the country and the official identifier (SIREN, Registro Mercantil sheet, UK company number), not just the name.
  2. Creation: look the identifier up and prefill the legal details. Run a verification for an outcome you can act on.
  3. Approval: route the record according to the outcome: straight through, to a reviewer, or blocked.
  4. Life of the relationship: watch the supplier's record so you hear about a closure, a procedure or a change of registered office.

The rest of this guide takes them in turn. A version of this flow specific to France and Spain is in a supplier-onboarding check for France and Spain.

Prefill from the register, keep what the supplier said

The register is the authority on a company's legal name, legal form, registered address and identifiers. Prefilling them removes the most common errors in supplier data: misspelled names, a trading name instead of the legal one, an old address.

Keep control by storing both values: what the supplier entered and what the register says, each with its source and date. When they differ, show the difference to a person instead of silently overwriting either. A supplier that trades under a brand isn't lying; a supplier whose "registered office" doesn't match the register at all deserves a question.

Duplicate detection that works

Duplicate suppliers cause duplicate payments and split spend reporting. Names are a poor way to find them, because the same company appears as "ACME SAS", "Acme" and "ACME S.A.S." in three records. Official identifiers fix this:

  • Key suppliers on the company identifier. Two records with the same SIREN or UK company number are the same legal entity.
  • Distinguish the company from its sites. In France one SIREN can have many SIRETs, one per establishment. Several supplier records for different sites of one company may be legitimate, but they belong together.
  • Flag look-alikes, don't merge them. Two records with similar names and different identifiers are probably different companies, often in the same group. That is a question for a reviewer, never an automatic merge.

Review queues people can work through

Automation earns its keep in the cases it doesn't handle. Map verification outcomes to actions:

OutcomeAction
verifiedCreate the supplier; no review needed for the register step
partialReview queue: show the reasons, for example a Spanish company with no stated status
unverifiedBlock creation and tell the requester why, for example ceased or in administration
not found or not coveredAsk the requester for the right identifier or another document

A reviewer should see, on one screen, what was checked, the outcome and its reasons, the source and the date, and the supplier's own data next to the register's. If they have to open the register in another tab to understand the decision, the queue will slow down. The reasoning behind treating "active" with care is in an active company is not always a safe company to onboard.

Ongoing monitoring instead of yearly re-checks

A supplier that was fine at onboarding can close, enter a procedure or move its registered office later. Re-checking every supplier every year is slow and still misses what happens in between. Monitoring turns it around: you watch the suppliers that matter, and changes come to you.

With Fuentio, a watch (POST /v1/watches) sends the changes to a company's official records, signed, to your HTTPS endpoint. The Free plan includes 3 watches and paid plans up to 100, so start with active suppliers you pay regularly. When a change arrives, route it like a new check: a closure or a procedure goes to a person, a routine filing doesn't need to.

Bank detail changes: a moment to re-check

A request to change a supplier's bank details is a classic moment for invoice fraud. A register can't tell you who owns a bank account, but the request is a good trigger to re-run the company check: is the supplier still active, has its registered office or name changed recently? Combine it with your own call-back procedure to a known contact. The register check gives you fewer manual checks to do, not a guarantee.

Keeping control of your supplier data

  • The identifier is the key; names and addresses are attributes with a source and a date.
  • Never overwrite silently: keep the supplier's version and the register's, and log who accepted which.
  • Keep the evidence of each check: the outcome, the source, the date and a reference you can retrieve later.
  • Store no more personal data than you need. Fuentio returns no person's name; if your process needs a contact person, collect it from the supplier directly.
  • Re-check on change, not on a calendar, where you can.

The same principles applied to sellers on a platform are in how marketplaces can check business sellers.

Limits

Frequently asked questions

Which identifier should I require when creating a supplier?

The company's official registration number for its country: the SIREN in France, the Registro Mercantil sheet in Spain, the company number in the UK. Names alone can't be checked reliably.

How do I find duplicate suppliers?

Group supplier records by official identifier. Same identifier, same legal entity; similar names with different identifiers are separate companies to review, not merge.

Should supplier data be overwritten with register data?

Prefill from the register, but keep the supplier's own values alongside, with sources and dates, and show differences to a person.

How often should suppliers be re-checked?

Watching active suppliers for changes is more reliable than periodic re-checks. Re-check on events such as a bank detail change request.

Sources

← All articles · RSS feed