A contracting-authority identity record is a dated, source-linked account of every organization named as a buyer in one procurement. It stores the published name, normalized legal name, notice-local organization reference, official identifiers with their schemes, jurisdiction, address, buyer scope, joint-procurement and central-purchasing subroles, evidence anchors, contradictions and review state. It records departments, contact points, procurement service providers, eSenders, portal operators, financiers, payers and contract signatories as separate roles. `confirmed_single_buyer` and `confirmed_joint_buyers` mean the current official material identifies the buyer set and the organization evidence is internally consistent. `buyer_confirmed_signatory_unresolved` confirms the buyer while leaving the future buyer-side signatory open. `identity_conflict`, `role_conflict`, `insufficient_public_evidence` and `superseded` keep uncertainty visible. The record identifies who the source says is buying. It does not decide from first principles whether an entity legally falls within a procurement statute or guarantee who will sign an unawarded contract.
A tender page may carry the logo of a shared service, the email of a consultancy and a submission link owned by a software vendor. The documents may use a department name, while the notice names a council or statutory body. Joint buying adds a lead authority and several participating authorities. A central purchasing body may buy for other organizations, and an award-stage record may later name a signatory, financier or payer that did not appear in the same role at tender stage. Choosing the most visible name can send legal review to the wrong entity, corrupt buyer history, miss an eligibility condition tied to the contracting party or cause a supplier to address a bid to the portal operator. A single field called `buyer` hides the mistake instead of resolving it.
Resolve the procurement first, then treat buyer identity as a role assignment backed by organization evidence. The current official notice proves who is assigned the buyer role for that procedure. A public register can corroborate a legal name and durable identifier, but it cannot create the procurement role. A buyer website can connect an operating brand or department to its parent body, but it cannot silently replace the notice. Keep each buyer in a joint set, preserve the stated lead, and scope roles to the procedure, lot or contract that the source covers. Notice-local references such as `ORG-0001` are join keys inside one notice, not permanent identifiers. If the buyer is established but the future signatory is absent, say exactly that. Agents may read and reconcile public evidence; they may not infer legal status, enter a private workspace, contact an organization or make a case-specific legal conclusion without separate authority.
Direct answer
The buyer is the organization assigned the buyer role
The quickest reliable answer starts inside the current official notice. Fix the procedure identifier, notice identifier and version, then locate every organization referenced as a buyer. In current TED eForms, `OPT-300-Procedure-Buyer` points to an organization acting as a buyer. The referenced organization carries a published name through `BT-500` and an organization identifier through `BT-501`. Follow the reference. Do not choose the first organization listed on the page.
The reference matters because procurement records contain organizations with different jobs. TED’s current organization-role codelist distinguishes a buyer, a central purchasing body, a procurement service provider and a TED eSender. The schema adds subroles for the group leader, tender recipient, tender evaluator, contract signatory, financing organization and paying organization. Several roles may point to the same organization, but shared identity does not make the roles interchangeable.
UK rules expose the same problem in plainer terms. Regulation 13 of the Procurement Regulations 2024 requires the name and unique identifier of a single authority or of every authority acting jointly. It separately requires the lead authority, any person carrying out all or part of the procurement on behalf of those authorities, and the notice enquiry contact. A person named in the same notice therefore needs a role before its name answers “who is buying?”
This task assumes that the official procurement and current source have already been resolved. If several websites disagree about which notice controls, return to the source-authority record first. Buyer identity cannot repair a broken procedure join.
| Published object | What it can establish | What it cannot establish alone |
|---|---|---|
| Buyer organization reference | Who the current notice assigns as buyer | Whether the legal classification is correct under every applicable law |
| Department or contact point | Which unit or person handles a function | That the unit is a separate legal buyer |
| Procurement service provider | Who performs stated procurement work | That the provider owns the budget or contract |
| eSender or portal operator | Who transmits data or runs the interface | Who is procuring the goods or services |
| Contract signatory | Who signed on the buyer side when the contract record states it | Who will sign before that evidence exists |
Identity evidence
Keep the notice join key and the legal identifier in different fields
An eForms value such as `ORG-0001` is a technical identifier within a notice. TED uses it to reference one organization from the buyer, service-provider or signatory context without repeating the full organization block. The current eForms FAQ says those values need only be unique inside the notice. Another notice can use `ORG-0001` for a different body. Store it as `notice_organization_id`, qualified by notice ID and version.
A durable organization identifier needs both the value and the issuing scheme. `12345678` is unsafe on its own. `GB-COH:12345678`, a PPON, a national public-body identifier or another named register entry tells a reviewer where to check it. The Open Contracting Data Standard recommends a legal identifier from an official register and models the scheme separately from the ID. It also distinguishes primary legal registers from secondary registrations and third-party databases.
Not every public authority is a company. A missing Companies House record, commercial-register entry or VAT number does not disprove a ministry, municipality or statutory body. Use the identifier named in the notice and the authoritative organization directory appropriate to that entity type. If no suitable public register applies, record `registry_not_applicable` with the basis and preserve the statutory or official establishment source. Do not fabricate a company identifier to make the row look complete.
Keep `published_name`, `legal_name`, `organization_part_name` and `contact_name` separate. The buyer website may state that “Digital Services” is a department of Southmere Borough Council. That evidence can normalize the department label to the council while preserving the original phrase. It cannot override a notice that names a different legal buyer. A discrepancy becomes a review item, not a silent cleanup.
| Field | Required treatment | Failure state |
|---|---|---|
| `published_name` | Copy the current source value | `insufficient_public_evidence` if absent |
| `notice_organization_id` | Qualify by notice and version | Never use as a global key |
| `legal_name` | Link to official identity evidence | `identity_conflict` if incompatible |
| `identifiers[]` | Store scheme, value, source and checked time | Do not compare bare values |
| `organization_part_name` | Retain department or unit separately | Do not create a legal entity by default |
| `address` | Preserve source, date and jurisdiction | Treat mismatch as evidence to review |
| `registry_status` | Confirmed, not applicable, inaccessible or conflicted | Absence is not negative proof |
Joint procurement
A lead authority does not absorb the other buyers
When several organizations buy jointly, return a set. TED eForms requires a group-lead indicator when more than one buyer is present, with one buyer marked as leader. The Procurement Regulations 2024 likewise call for the lead authority and every other authority acting jointly. The lead is a subrole. It is not a rule for deleting the remaining buyers.
Scope each role. One joint procurement may cover every lot in the name of all authorities. Another may place lots 1 and 2 with the lead authority and lot 3 with a participating authority. EU Directive 2014/24 distinguishes a procedure conducted entirely in the name and on behalf of all participating authorities from one where only parts are conducted jointly. The record should follow the current procurement documents and preserve the named scope rather than infer responsibility from the word “lead.”
Central purchasing also needs a subrole. The eForms organization model distinguishes a central purchasing body that acquires supplies or services for other buyers from one that awards contracts or concludes frameworks for them. A procurement service provider is a separate role again. Record what the notice states. Whether a particular arrangement has the claimed legal effect belongs with procurement or legal counsel when the answer affects eligibility, challenge rights or contracting risk.
Framework language can name organizations that are merely eligible to call off later. That future user population is not automatically the buyer set for the framework procurement or for a later call-off. Bind each buyer record to the current procedure and, where the source does so, to the lot or contract. A later call-off gets its own identity decision.
| Situation | Record now | Do not infer |
|---|---|---|
| Joint procedure | Every buyer, lead flag and stated scope | That the lead is the sole buyer |
| Central purchasing body | Buyer role plus acquiring or awarding subrole | That every beneficiary is a buyer in this notice |
| Procurement run on behalf | Principal buyer and separate service-provider role | That the agent owns the procurement |
| Framework user list | Eligibility population as its own object | That every listed user is a current buyer |
| Lot-specific authority | Buyer-to-lot link from the source | One procedure-wide role from visual proximity |
Worked record
A joint tender can name two buyers and three organizations that are not buyers
Consider the fictional UK procurement `ocds-example-southmere-2026-17`, checked on 3 September 2026. Its current tender notice names Southmere Borough Council as lead authority and Fenwick Health Authority as the other joint authority. Each has a distinct example PPON and public address. Northbridge Procurement Services is described as carrying out the procurement on their behalf. CivicNotice Ltd is the eSender, and BidRoom Cloud operates the submission interface. The enquiry contact uses the display name “Southmere Digital Commissioning Team.”
The buyer record contains two organizations. Southmere receives `buyer: true` and `joint_lead: true`; Fenwick receives `buyer: true` and `joint_lead: false`. Both preserve their notice names, example identifiers, source anchors and the all-lots scope stated in the notice. Northbridge gets `procurement_service_provider`, CivicNotice gets `esender`, BidRoom Cloud gets `portal_operator`, and the commissioning team remains a contact point under Southmere. None of those records is discarded, because each explains a visible name. None enters `buyers[]`.
The notice says the two authorities are responsible for the procurement, but it does not name the legal person that will sign each resulting contract. The record therefore ends in `buyer_confirmed_signatory_unresolved`, with `buyer_set_state: confirmed_joint_buyers`. That is a finished answer. The team can qualify the opportunity against both authorities while preserving a separate question for the draft contract or award record.
All names and identifiers in this example are invented. The shape is deliberate: a useful record can be complete about the current buyer role and incomplete about a later contract role. Filling the signatory field with Southmere because it is lead would replace a visible evidence boundary with a guess.
| Organization | Published role | Identity evidence | Scope | Decision |
|---|---|---|---|---|
| Southmere Borough Council | Buyer and joint lead | Example PPON plus notice organization record | All tender lots | Include in `buyers[]` |
| Fenwick Health Authority | Other joint authority | Separate example PPON plus notice record | All tender lots | Include in `buyers[]` |
| Northbridge Procurement Services | Carries out procurement on behalf | Name and example organization identifier | Procedure administration | Keep outside buyer set |
| Southmere Digital Commissioning Team | Notice enquiry contact | Touchpoint linked to Southmere | Enquiries | Do not create a legal entity |
| CivicNotice Ltd and BidRoom Cloud | eSender and portal operator | Service evidence only | Publication and submission interface | Keep outside buyer set |
Decision states
Resolve what the evidence supports and preserve the rest
Use one state for the buyer set and separate qualifiers for later roles. `confirmed_single_buyer` requires one explicit buyer reference joined to a coherent organization record. `confirmed_joint_buyers` requires every stated buyer, the lead indicator and the applicable scope. A buyer can be confirmed even when a registry is not applicable, provided the notice and an authoritative public establishment source identify the body.
Issue `identity_conflict` when the role points to an organization whose legal name or identifier is incompatible with current official identity evidence. Issue `role_conflict` when two current, properly scoped sources assign incompatible procurement roles. `insufficient_public_evidence` covers a missing buyer reference, an unexplained department label or an identifier that cannot be qualified. `superseded` keeps an older decision in history after a correction or reorganization changes the current record.
Do not resolve a mismatch by choosing the source that looks more polished. Preserve the exact values, source functions, checked times and contradiction. A typo in a registry number may need a correction notice or buyer clarification through the designated channel. The identity record can describe the conflict and block dependent automation without deciding its legal effect.
Expiry belongs in the output. Recheck after a notice correction, a new procurement stage, an award or contract notice, a public reorganization, an identifier change, or a stated review date. A cached organization profile does not silently update an older notice. Keep what was published, what is current and how they relate.
| State | Evidence threshold | Permitted downstream use |
|---|---|---|
| `confirmed_single_buyer` | One explicit buyer and coherent identity | Buyer-level research and qualification |
| `confirmed_joint_buyers` | Complete buyer set, lead and scope | Research against the preserved set |
| `buyer_confirmed_signatory_unresolved` | Buyer proven, future signatory absent | Use buyer facts; leave signatory-dependent work open |
| `identity_conflict` | Identifier or legal-name contradiction | Block entity-dependent automation |
| `role_conflict` | Incompatible current role evidence | Block buyer assertion and escalate |
| `insufficient_public_evidence` | Role or identity chain incomplete | Return the missing evidence and next check |
| `superseded` | Later evidence replaces the decision | History only |
Later roles
Buyer, signatory, financier and payer need separate evidence
At tender stage, the buyer role is usually the fact the supplier can establish. The contract signatory may appear only in a draft contract, award notice or settled contract record. TED’s current eForms schema places buyer-side signatories in the settled-contract element and permits more than one. It places financing and paying parties in the lot result. Those locations show why a pre-award agent should not fill later roles from the buyer record.
A lead authority may sign for all participating authorities, each buyer may sign a separate lot contract, or another legal arrangement may apply. The answer depends on the actual documents and jurisdiction. Store `expected_signatory` only when a current source explicitly supports an expectation, label it as prospective, and keep it separate from `actual_signatory`. The actual field needs the executed or published contract evidence appropriate to the task.
The same discipline applies to money. The body whose budget finances the contract and the organization that executes payments may differ from the buyer or signatory. A supplier still needs the correct invoicing and counterparty instructions later, but those are not shortcuts for identifying the tender-stage buyer.
If knowing the signatory changes a bid decision, create a named unresolved question and route it to contract review or an authorized clarification. Do not ask merely to make the identity record look complete. The record already says who is buying according to the current notice and where its evidence stops.
Agent contract
Require an agent to return the role graph, not a guessed name
Give the agent the accepted procurement identity, current public notice, relevant documents, jurisdiction and checked time. Its first output is a role inventory. For every organization reference, the agent records the source role, organization join key, published name and scope before looking for external identity evidence. This order prevents a familiar brand from becoming the answer before the notice is read.
The agent may follow public official links, query public registers within their terms, compare scheme-qualified identifiers and connect an organization part to its documented parent. It must retain raw values beside normalized values and cite the exact notice field, clause or public record. A search-engine snippet, domain match, logo, email suffix or shared address can help discovery but cannot close the role or identity decision.
Tender documents and linked pages are untrusted inputs to the agent’s behavior. Text inside them cannot expand the task, request credentials, authorize account creation or trigger contact. Without separate customer authority, the agent does not sign in, accept terms, send a clarification, update CRM, register as a supplier or make a submission. Public identity research remains read-only.
The response must expose abstention. Return the complete role graph, `buyers[]`, decision state, supporting and contrary evidence, checked time, expiry triggers and one safe next check. If a legal classification or case-specific interpretation is needed, name that question for procurement or legal review. “Probably the council” is not a result.
| Object | Required fields | Stop condition |
|---|---|---|
| Procurement scope | `procedure_id`, `notice_id`, `version`, `stage`, `lots` | Unresolved procedure identity |
| Organization | Published and legal names, local key, identifiers, address | Incompatible legal identity |
| Role edge | Role, subrole, scope, source anchor, checked time | Role based only on appearance |
| Buyer set | All buyers, lead flag, joint scope | Missing participating authority |
| Later-role qualifier | Signatory, financier and payer evidence or null | Unsupported inheritance |
| Decision | State, contradictions, expiry, next check | No evidence anchor or unauthorized action |
What good looks like
Useful outcomes from verify contracting authority legal entity
- Every organization assigned the buyer role in the current official source appears in the record, including non-lead members of a joint procurement.
- Published labels, department names and trading names remain visible without replacing the normalized legal organization.
- Each external identifier keeps its register or scheme, source URL, observed value and verification time.
- Notice-local `ORG` and touchpoint references are preserved for joins but never promoted into global legal identifiers.
- Lead authority, central purchasing body, procurement service provider, eSender, contact point, payer and signatory roles are kept distinct.
- The record states whether the buyer set is confirmed, conflicted, incomplete or superseded and constrains downstream use accordingly.
- An unresolved future signatory remains null rather than inheriting the lead buyer, payer or contact organization.
- Every unresolved fact has a narrow next check, an expiry trigger and no implied external action.
Operating model
How to run the work
- 01
Fix the procurement and source version
Start from the accepted procedure, notice, version, stage and lot scope so a buyer from a related notice or framework is not attached to the wrong procurement.
- 02
Extract organizations and role references
List every named legal organization, department and touchpoint, then follow the notice references that assign buyer, lead, service-provider and other roles.
- 03
Resolve durable identity evidence
For each buyer, preserve the published name and check the stated identifier against the appropriate official register or public organization directory when one exists.
- 04
Model joint and delegated procurement
Keep all buyers, the stated lead and any person acting on their behalf as separate records with procedure, lot or contract scope.
- 05
Reconcile names, identifiers and roles
Compare current evidence without overwriting conflicts. A registry mismatch is an identity problem; incompatible notice roles are a role problem.
- 06
Issue the record and its boundary
Publish the buyer set, supporting anchors, state, checked time, expiry and next permitted check while leaving unsupported signatory and legal conclusions open.
Evaluation
Questions that change the decision
- Which current procedure, notice version, stage and lot set does this identity decision cover?
- Which organization references are explicitly assigned the buyer role, and which only supply contact, publication, evaluation or portal services?
- Does the published name identify a legal organization, an internal department, an operating brand or only a touchpoint?
- Which identifier scheme issued each value, and does the public source return the same legal organization?
- Are several authorities acting jointly, and which one is stated to be the lead?
- Is a central purchasing body acquiring supplies or services for other buyers, awarding for them or merely supporting the procedure?
- Does the current source identify a buyer-side contract signatory, or is that fact available only after award?
- What contradiction, missing source or elapsed time prevents a confirmed state?
Failure modes
Where teams lose control
A procurement consultancy can be mistaken for the buyer because its staff answer the published contact address.
An eSender or portal name can become the buyer in a database because it appears in page chrome or source metadata.
A department can be treated as a separate legal person even though the notice assigns the role to its parent authority.
One lead authority can erase other joint buyers and distort jurisdiction, framework access or future contract scope.
A notice-local `ORG-0001` value can be reused across notices and create a false organization match.
A company or tax number without its scheme can collide with an identifier issued in another register or country.
A registry result can be treated as proof that the organization is the contracting authority for this procurement.
The buyer, future signatory, financier and payer can be collapsed even though current eForms represents them separately.
An agent can turn an identity check into unauthorized contact, account access or legal classification.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- buyer-role references resolved to organization records divided by buyer-role references in the current source
- joint procurements where every named authority and the stated lead remain represented
- buyer organizations with a scheme-qualified official identifier or a documented reason none applies
- department, touchpoint, agent, eSender and portal labels prevented from becoming unsupported buyer entities
- identity and role conflicts preserved rather than overwritten by normalization
- pre-award records where an absent signatory remains unresolved
- records rechecked after a notice correction, buyer reorganization or registry change
- agent outputs that include evidence anchors, checked time, state and permitted next action
Questions
Common questions
Is the organization named in the tender contact email the buyer?
Only if the current official source also assigns that legal organization the buyer role. A contact point or procurement service provider can answer questions for another authority.
Does ORG-0001 uniquely identify a contracting authority?
No. In eForms it is a notice-local technical identifier used for references. Qualify it with the notice and version, then retain a separate scheme-qualified legal or public-body identifier.
Is the lead authority the only buyer in a joint procurement?
No. Preserve every authority identified as acting jointly and record the lead as a subrole. The documents may then scope responsibilities or lots among that set.
Can a company registry prove who is buying?
A registry can corroborate legal identity, status and registered details within its remit. The procurement role comes from the current official notice or other controlling procurement document.
What if the public authority has no company number?
Use the official identifier and establishment source appropriate to that body. Record when a company register is not applicable. Missing company registration is not proof that the buyer does not exist.
Can I assume the buyer will sign and pay the contract?
No. Signatory, financing and payment roles need their own evidence. Leave them unresolved at tender stage unless current documents explicitly assign them.
Should an agent contact the authority when identifiers conflict?
Not without explicit authority. The agent should preserve the conflict, block dependent automation and identify the designated clarification or review route as a possible authorized next step.
Sources
Primary references
- The Procurement Regulations 2024, regulation 13 The National Archives
- Contracting authorities and the enhanced Find a Tender service UK Cabinet Office
- Guidance on the contracting authority definition UK Cabinet Office
- TED eForms organization and party structure Publications Office of the European Union
- TED eForms identifier and reference model Publications Office of the European Union
- BT-501: Organisation Identifier Publications Office of the European Union
- eForms organisation-role codelist Publications Office of the European Union
- Directive 2014/24/EU, Articles 37 and 38 EUR-Lex
- OCDS guidance on organization identifiers Open Contracting Partnership
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Zelius
Managed tender intelligence and bid execution for teams that want the commercial outcome.
Suppliers, founders and commercial teams pursuing public or private opportunities. Start with the workflow, constraints and evidence you already have.