Registry first — then the job

Article Vendors & commercial discipline ~8 minutes

A project desperately needs a specialist subcontractor. Someone creates a company name in a spreadsheet, emails a purchase order, and promises “we’ll tidy the registry later.” Later rarely arrives. Six months on, compliance papers and payment disputes still argue about whether that company formally exists in your system — and under which spelling.

Urgency is real. Shadow companies are how urgency becomes commercial fog. The registry is not bureaucracy for its own sake. It is the durable identity that projects borrow, rather than invent.

This is the first working habit behind Your contractors are part of your record: company truth first, then assignment to the job.

What good practice looks like

Mature enterprises keep a company registry separate from project assignment.

In practice:

• The registry creates the durable company record — names, contacts, identifiers, compliance home.
• Projects onboard vendors afterward — they do not invent shadow companies that only live in one package inbox.
• Approval of requests from the field is an accountable step, not a bypass dressed as mobilisation speed.
• Compliance documents attach to the company where they belong, then ride with onboarding onto jobs.
• The same vendor can serve multiple projects without five conflicting profiles and five conflicting ABN stories.
• Payment entity and contract entity are reconciled deliberately when they differ — not discovered in a claims workshop.

Procurement frameworks call this master data and due diligence. Site translation: if two packages disagree about who “that steel company” is, you do not have a supplier relationship — you have competing rumours with invoices attached.

Good practice still allows fast paths for genuine emergencies. Those paths still invent a controlled request into the registry, not a permanent shadow that never graduates.

Ownership of the registry must be real. If every package admin can create forever and nobody merges duplicates, master data rots in public. A small steward team with authority to refuse lookalike names usually saves more programme time than it costs in week one friction.

Bank and legal identifiers matter when they exist in your jurisdiction. Matching on trading name alone is how “ABC Steel” becomes three payment destinations and one confused insurer.

Where projects slip

• Shadow vendors living only in a job’s inbox or whiteboard.
• Duplicate companies with near-identical names — the classic commercial archaeology starter kit.
• Compliance captured on the wrong project and lost at rollover.
• Payment entities that do not match contract entities, discovered when money moves.
• Field teams creating “just for now” entries that become the unofficial system.
• Procurement cleaning the registry once a year while projects keep creating exceptions every week.

The cost is not a tidy database fantasy. The cost is late arguments about identity that starve time from the real commercial questions: entitlement, performance, and risk.

How Cynilo supports the practice

Cynilo separates the enterprise vendor registry from project vendor assignment. The project works with companies that already have a place in the principal’s record — or with a controlled request that can be approved into that record.

Help How-tos cover request and approve. Learn’s reminder for leaders: speed that skips the registry is how commercial fog begins. The product does not decide who you may use. It stops “who” from being renegotiated every time a new package admin opens a blank row.

What good looks like in a week

On an organisation that keeps registry first:

• New company creation is rare relative to onboarding known companies to new jobs.
• Request queues from the field are short, visible, and owned.
• Duplicate hunts happen before award, not after the first payment mismatch.
• Compliance packs attach once at company level and remain findable when the next package starts.
• Package PMs stop treating “add a company locally” as a clever shortcut.

The weekly test: pick three vendors mobilised in the last fortnight. Do they each resolve to one durable company record that other packages would also use? If not, later is already here.

Onboarding should feel ordinary. When adding a known company to a new package is harder than inventing a local row, people invent local rows. Make the honest path the easy path.

A short story from a regional civils programme

A regional programme onboarded the same electrical specialist onto four packages in nine months. Package one used a spreadsheet name. Package two used a slightly different trading name from a quote header. Package three created a third entry because “we couldn’t find them.” Package four inherited chaos when insurance expiry and a variation argument needed one legal entity.

Nobody intended to invent three companies. Urgency invented them. The programme’s fix was blunt: no purchase order without a registry company; package lists only onboard; duplicates merged with an owner who could say no to new shadow names. The first month felt slower for site admins. Claims season felt shorter for commercial. Identity stopped being a subplot.

Closing

Registry discipline is the quiet spine of vendor memory. Contracts, compliance, and performance all hang off a company that actually exists once in your world — not five times in five lists.

Previous: Your contractors are part of your record