# EU27 business annexes and applicability evidence

**C0-001 · prepared 20 November 2026 · English canonical worksheets**

This collection connects the HSIMC global-value language core to an actual business transaction in each of the 27 EU member countries. It contains 27 country worksheets, four official starting routes per country, a common transaction template and a claim-level evidence schema.

The shared written core covers the 26 state languages identified by the European Commission: the 24 EU institutional official languages plus Luxembourgish and Turkish. Country business annexes in this release are English canonical worksheets. Their legal, tax and local-language review is still pending. Publishing a worksheet does not settle a transaction or upgrade the review status of a reused translation.

## What is ready

| Component | Prepared content | Remaining transaction input |
| --- | --- | --- |
| Country scope | 27 country IDs and their state-language master mappings | Exact territory, municipality, work site and required document languages |
| Official routes | 108 country route records for tax, customs, business procedures and product rules | Authority response or professional assessment for the actual facts |
| Business worksheet | Consistent actor, product, route, tax, delivery and acceptance fields | Named entities, actual product/service version and transaction date |
| Evidence structure | Method, configuration, conditions, competence, calibration, applicability and reuse decisions | Actual observations, artifact hashes, assessments and signatures/decisions |
| Value measurement | Comparable baseline, all-inclusive actual cost and separate cash-flow fields | Evidence supporting any claimed reduction in cost, time or rework |

There are no completed business clearances, tax opinions or customer acceptances in these files. No partner or reviewer has been appointed, and no authority has been contacted on the user's behalf.

## Use a country worksheet

1. **Define the result.** Identify the object or service, intended use, delivery version and acceptance criteria. Select goods, remote service, local service or a mixed delivery.
2. **Name the actors.** Enter the seller, buyer, invoice issuer, local operator and, where relevant, importer and customs declarant. Record the actual inventory, performance and delivery locations.
3. **Fix the scope and date.** Record the destination territory, route, origin, delivery terms and effective date. Country membership is only the first scope field.
4. **Choose the required language set.** Separate the languages used for communication from legally required instructions, labels, filings and contract documents. Retain source and target version hashes. Assign the language and subject reviewer when a real person is engaged.
5. **Resolve product and local-operation questions.** Use the country's business and product contact routes to identify relevant rules, permits, qualifications and responsible economic operators. Record the rule version and the basis of the decision.
6. **Resolve the transaction tax and customs position.** Determine supply classification, registration, invoice/reporting, VAT/OSS applicability where relevant, customs classification, origin and valuation. Record the qualified reviewer and decision rather than copying a generic country rate.
7. **Execute and collect evidence.** Record the responsible node and person, method, equipment, calibration, site conditions, raw observations, result version and deviations. Assess any reused evidence against the new claim.
8. **Accept and measure.** The authorised acceptor identifies the exact delivery and criteria version, decision date, evidence and unresolved changes. Compare like-for-like costs or cycle times before reporting value.

## The common evidence record

An evidence record answers a particular question about a particular version of an object, service or action. A photograph, test report or model output can be a referenced artifact, but the artifact alone does not determine its applicability.

| Record section | Purpose |
| --- | --- |
| `claim` | Links the evidence to the task, contract and acceptance criterion it is meant to support. |
| `subject` | Identifies the object, version, configuration, material/firmware, intended use, destination and operating conditions. |
| `legal_and_method_scope` | Identifies the rule and method versions, thresholds, units, measurement uncertainty and exclusions. |
| `execution` | Associates the actual inputs, equipment, calibration, competent operator, site, timestamp and raw observations with the produced result. |
| `applicability` | Records conditions that match, differences that remain, territorial/time limits and the assessment of previous evidence proposed for reuse. |
| `reviews` | Separates language/domain, product/local-operation, tax/customs and evidence-reuse review. |
| `acceptance` | Records who was authorised to accept which exact delivery and criterion version, with evidence and conditions. |
| `value_measurement` | Records the comparison basis and observed result without mixing recoverable tax cash flow with permanent cost reduction. |
| `invalidation` | States changes that require reopening, next review and the relation to superseded records. |

Every evidence artifact has a URI, SHA-256 hash, version and access classification. A public catalogue can expose an evidence ID and coverage statement while keeping contracts, tax identifiers, customer information and detailed professional opinions in the intended restricted audience.

### Reuse is a recorded decision

Before reusing a test, calculation or professional conclusion, compare its subject, configuration, method, operating conditions, calibration, competence, intended use, jurisdiction and effective date with the new claim. A matching filename, language or product family is insufficient. Record the differences, the permitted reuse scope, who assessed it and which artifact supports that decision.

Reopen the decision when a relevant product, material, firmware, rule, method, destination, operator, route, calibration or acceptance criterion changes. An old result remains part of the history; its reuse permission can change independently.

Schema validation checks the record structure. It does not verify the truth of measurements, the authenticity of documents, a reviewer's competence or the legal correctness of an opinion. The supplied template is deliberately in `TEMPLATE` state with `PENDING` decisions.

## How the EU common layer and national layer relate

The Commission distinguishes EU-wide and national product requirements. CE marking and the applicable conformity procedure depend on the product and governing legislation. The EU layer helps identify a common technical basis; it does not turn a generic HSIMC publication into a conformity certificate. See the [Commission manufacturer guidance](https://single-market-economy.ec.europa.eu/single-market/goods/ce-marking/manufacturers_en) and [general product compliance guidance](https://europa.eu/youreurope/business/product-rules-compliance/general-product-compliance/index_en.htm).

VAT OSS is organised by scheme and covered supply. The transaction record therefore asks for the actual scheme and eligibility decision, while retaining separate national registration, invoicing, direct-tax and customs questions. See the [Commission OSS registration guidance](https://vat-one-stop-shop.ec.europa.eu/one-stop-shop/register-oss_en).

Customs, VAT and excise territorial scope are separate fields. Use the [Commission territorial-scope table](https://taxation-customs.ec.europa.eu/taxation/vat/vat-directive/how-does-vat-work/territorial-scope_en) when the route involves an island, overseas area or other special territory. Cyprus also requires the specific legal-territory qualification recorded in its annex and [EU country profile](https://european-union.europa.eu/principles-countries-history/eu-countries/cyprus_en).

The 26-language core follows the Commission's [state-language scope](https://translation.ec.europa.eu/languages-eu-why-multilingualism-matters/linguistic-diversity-eu_en). Regional/co-official, minority, signed and product-specific document-language duties remain separately assessable. The presence of a Turkish master does not add Türkiye to the EU27 country collection.

## Source observations and link maintenance

Every country has four selected routes. These are starting points, not endorsements or evidence that a particular application has been approved. Several authorities use JavaScript, access challenges or pages that could not be extracted by the research service. Their access observations are preserved instead of being labelled as fully readable.

`READABLE_CONTENT` means the retrieval returned readable content. `SEARCH_INDEX_CONTENT` means the official page was found with indexed content but no separate readable endpoint retrieval is recorded. `FETCH_UNAVAILABLE`, `NO_EXTRACTABLE_CONTENT`, `AUTOMATED_ACCESS_CHALLENGE` and `MAINTENANCE_PAGE` describe the research observation; they do not establish that the public service is unavailable to a person.

Where the Commission directory pointed to an old page, the work records the observed failure and the replacement selected from current official sources. The French and Luxembourg product-contact routes were updated. Malta uses the current MTCA portal and MCCAA authority homepage. Slovakia uses the working Financial Administration contact and current UNMS homepage. The Hungarian business entry is explicitly a narrower official branch/representative-office guide because the EUGO endpoint could not be fetched.

The original national directories remain available for maintenance: [tax administrations](https://taxation-customs.ec.europa.eu/taxation/national-tax-administrations_en), [customs administrations](https://taxation-customs.ec.europa.eu/customs/national-customs-administrations-0_en), [product contact points](https://single-market-economy.ec.europa.eu/single-market/goods/free-movement-sectors/mutual-recognition-goods/product-contact-points_en), and [services Points of Single Contact](https://single-market-economy.ec.europa.eu/single-market/services/directive/points-single-contact_en).

## Files and update rules

- `country-annexes.json` is the public country catalogue and source-backed worksheet collection. Country and annex IDs remain stable.
- `country-directory.csv` is the compact routing table. It does not replace the structured record.
- `country-worksheets/` contains the 27 readable English worksheets.
- `transaction-template.json` starts an actual private transaction record.
- `applicability-evidence.schema.json` defines the shared evidence record; `applicability-evidence-template.json` is its empty starting record.
- `research.json` retains selected official references, retrieval observations and link repairs. `research-source-observations.json` retains the broader research observation history.

When a transaction begins, create a transaction-specific instance and stable profile ID. Keep completed inputs and decisions intact; merge catalogue changes by country ID and source ID. The build scripts initialize this release and must not be run over completed customer records. Acceptance in the country catalogue is an initial status view; the actual transaction's acceptance record becomes authoritative.

Keep language production, professional review, digital publication, physical validation and customer acceptance as distinct states in the continuing task register. An accepted finding should identify its applicable scope and exact version so the next participant knows what can be reused.
