When Evidence Becomes Executable

The European Commission's proposed Public Procurement Act moves evidence from a supporting document toward an executable state inside a regulated workflow. Its proposed electronic eligibility service, digital business credentials, automated verification, once-only reuse and connected procurement data spaces could allow a verified fact to affect whether an economic operator enters a procedure, satisfies a criterion or proceeds to the next decision stage.

Executable Evidence does not mean that a document executes a contract by itself. It means a governed evidence state can trigger, block, condition or escalate an institutional action. The analytical chain is Evidence Identity → Authority → Validity → Verification State → Decision Binding → Auditability. A failure at any link can turn efficient automation into an untraceable exclusion, an unsupported award or a false sustainability claim.

EIA-002 identified procurement as an evidence-continuity problem because documents, supplier claims and performance records lose context across the procurement lifecycle. EIA-015 continues that argument. It asks what additional controls become necessary when the evidence infrastructure begins participating in eligibility, award, contract performance, monitoring and system-level analysis rather than merely supplying information to a human reader.

COM(2026) 590 was adopted by the European Commission on 9 September 2026 as a legislative proposal, not an enacted Regulation. It would replace three 2014 procurement directives with one proposed framework and remains subject to the European Parliament and Council. SNN.SG therefore treats its digital architecture as an institutional design signal, not a current legal obligation in the European Union, Singapore or ASEAN.

The proposal's operational detail matters. Articles 28 and 29 connect proof of eligibility to an electronic service and national databases. Article 99 addresses life-cycle costing. Article 133 sets out electronic eligibility, digital business credentials, data formats, semantic repositories, algorithms, interoperability, security, accountability and audit requirements. Article 134 establishes National Public Procurement Data Spaces, with Union-level exchange addressed alongside them.

The proposal also preserves reasons, documentation and safeguards. Automated verification is not presented as unlimited authority, and procurement decisions remain embedded in legal duties, data protection, review and remedies. The institutional distinction is decisive: a source database supplies a fact, a credential carries it, a service verifies it, a public buyer applies the rule, and a review body may later test the legality of the result.

Singapore already has several components of a digital procurement stack, but they perform different functions. GeBIZ supports opportunity discovery, bid submission and supplier participation. UEN and CorpPass support organisational identity and authorised access. ACRA records can establish company information. TradeTrust demonstrates how digital documents can be issued and verified. None of these components alone determines that a supplier satisfies a particular tender, sustainability, origin or performance requirement.

For a Singapore public buyer, government-linked entity or infrastructure procurer, the practical design question is how a verified record enters the decision. A valid company profile may support identity, but financial capacity still depends on the applicable period and criterion. A verified certificate may prove provenance and integrity, but the buyer must still test issuing authority, scope, expiry and relevance. A sustainability record may support evaluation, but it does not independently establish taxonomy alignment, life-cycle value or contract performance.

The same separation matters to boards, audit committees and finance functions. They should be able to see which evidence was reused, which rule transformed it into an eligibility or scoring state, who approved an exception, and what remedy exists if the source was wrong or later revoked. Singapore's advantage would come from connecting these controls across procurement and finance, not from hiding them behind a single green verification mark.

ASEAN is not one executable evidence environment. Member states use different company registries, procurement laws, digital identities, tax systems, exclusion grounds, review procedures, sustainability criteria and assurance practices. Infrastructure projects also involve public buyers, state-owned enterprises, multilateral lenders, engineering contractors and suppliers that may each require a different proof and retain a different decision mandate.

The ASEAN Single Window shows that regional systems can exchange trade-related documents while national systems and authorities remain distinct. Procurement evidence needs the same discipline. A supplier credential should travel with the issuing authority, entity and facility, jurisdiction, purpose, rule version, validity period, verification state and permitted use. Cross-border availability is not cross-border legal effect.

Five negative states must remain visible: evidence unavailable, technically unverifiable, expired or revoked, inconsistent with another authoritative source, and valid but insufficient for the destination rule. Collapsing those states into one failed result could unfairly exclude smaller ASEAN suppliers. Collapsing them into one passed result could expose buyers, lenders and investors to fraud, origin, sanctions, labour, environmental or delivery risk.

Public procurement decisions can become capital-market events before an asset is built. Eligibility can change a company's addressable pipeline. Award and performance evidence can affect backlog quality, revenue forecasts, working-capital availability, bonding, insurance and project-finance drawdowns. For listed contractors and infrastructure operators, a machine-executed procurement state may therefore become material to valuation and disclosure.

The failure chain is concrete: registry match → tender eligibility → expected award → bankability → revenue certainty; environmental credential → compliant bid → green activity → taxonomy-aligned entity → sustainable instrument eligibility; verified past delivery → future performance → lower credit risk. Each arrow changes the decision purpose and requires separate evidence, authority and review. Technical verification at the first step cannot support the final claim by inheritance.

Banks, asset managers, insurers and data vendors should retain procurement evidence as a bounded input. A lender may use an awarded contract in cash-flow analysis but still test termination, variation, performance and concentration risk. An investor may use procurement data as a demand signal but still distinguish a proposal, qualified bid, award, signed contract and recognised revenue. An arranger may use environmental criteria in diligence but must separately establish the instrument's eligibility and reporting basis.

The minimum evidence object should include the economic operator and relevant beneficial or operating entity, authoritative source, issuer and registry, procurement identifier and lot, requirement, legal basis, jurisdiction, period, credential type, data fields, scope, issue and expiry dates, revocation status, verification method, timestamp and source version.

The decision layer should separately retain the public buyer or institutional owner, applicable threshold, eligibility or scoring rule, automated result, confidence or validation state where relevant, human reviewer, exception, conflict, missing fact, permitted action, prohibited conclusion, decision time and reason. Post-decision fields should capture notice, challenge, correction, replacement evidence, appeal outcome, contract modification, performance record and supersession.

The controlled lifecycle is Eligibility → Tender → Award → Contract Performance → Monitoring → System-Level Analysis. Evidence should be reusable across those stages only when its identity and validity remain intact, while the decision must be re-performed for each stage. A system should preserve both the evidence that supported execution and the evidence that prevented or reversed it.

The first European checkpoints are the Parliament and Council negotiations, followed by any adopted text and the delegated or implementing rules needed for digital credentials, database connections, semantic repositories, algorithm design, interoperability, security, accountability, technical audit and data-space validation. The proposed 15 June 2029 database-connection milestone should not be treated as effective until the final legislative outcome is known.

The first regional test should use one Singapore-led ASEAN infrastructure procurement. Select a supplier evidence population and follow it through prequalification, bid evaluation, environmental or social criteria, award, financing, contract monitoring and assurance. Record every source, automated check, rule, human decision, exception, challenge, correction and downstream reuse. Include rejected and held states, not only successful verification.

Watch whether digital credentials reduce supplier friction without disadvantaging firms from weaker registry environments; whether sustainability criteria remain connected to measurable contract performance; whether banks and investors distinguish procurement verification from credit and instrument eligibility; and whether a corrected or revoked record reaches every downstream user. The decisive signal is not faster verification alone. It is a decision that can be reproduced, challenged and repaired without losing institutional responsibility.