cadrumo.core.country_code module¶
The two-letter country code carried across counterparty and jurisdiction facts.
AEAT identifies a counterparty’s country, a perceptor’s country of fiscal
residence and an income’s source jurisdiction with an ISO 3166-1 alpha-2 code.
The shape was written out at twenty-two sites under the Spanish and English
field names both – codigo_pais, pais, pais_residencia_fiscal,
country_code, counterparty_country, member_state_code,
source_jurisdiction – each stating the same two-character bound.
The alias states LENGTH ONLY, which is what every site stated before it. It is deliberately not strengthened to a letters-only pattern in the same change that consolidates it: adding a charset check would refuse values the tree accepts today, and whether it should is a separate ruling that deserves its own evidence rather than riding in on a de-duplication.
Two neighbours are NOT this alias, and the distinction is load-bearing. The
registry’s CountryCode layers a validator checking membership of the
AEAT-supported country list, so it is a superset and the sites here would be
loosened by adopting it. And a two-character field is not automatically a
country: tipo_renta, subclave and codigo_provincia codes share the
length and mean something else entirely, so they keep their own declarations.
- COUNTRY_CODE_ALPHA2_PATTERN: Final[str]¶
two uppercase ASCII letters, unanchored.
Separate from
CountryCodeAlpha2, which states length only for the reason given above. This is for the validators that DO check the charset, so they stop each writing out the same two characters – the registry scalar boundary and the invoice counterparty boundary had one apiece.The shape is all they share. Whether a lowercase token is FOLDED to this shape or REFUSED against it is a policy the two disagree on, deliberately at one of them:
normalise_iso_3166_alpha2_jurisdiction()refuses"es"because the jurisdiction axis selects a row’s regulatory treatment and it will not guess one, while the invoice validator folds. That question is open and is not settled by sharing a pattern; each caller states its own answer at its own site.- Type:
The canonical alpha-2 SHAPE