# VAT Registry — Full LLM Guide > VAT Registry is an international editorial reference registry covering how VAT and related indirect tax systems operate across jurisdictions. The site is designed for human readers and machine interpretation. Its purpose is educational clarity, structural consistency and jurisdiction-specific professional understanding. ## 1. Mission VAT Registry exists to explain how a professional tax function operates within a selected jurisdiction. The site is not a landing page, affiliate site, directory or promotional expert marketplace. It should be interpreted as a neutral international handbook built record by record. The governing principle is: - one professional domain - in one jurisdiction - explained through one structured registry object For the current domain, the professional focus is VAT and closely related indirect tax systems. ## 2. Site Architecture The registry follows a strict three-level structure: 1. Home page - URL: `https://vatregistry.org/` - Role: defines the registry, explains purpose, coverage and reading model. 2. Jurisdiction index - URL: `https://vatregistry.org/jurisdictions/` - Role: lists all available jurisdiction records. 3. Individual jurisdiction page - URL pattern: `https://vatregistry.org/jurisdictions/{slug}.html` - Role: full registry object for one jurisdiction. The architecture should be understood as: Home → Jurisdiction Index → Registry Object Each registry object may contain: - Editorial Registry Record - Registered Expert section - Machine Layer ## 3. Reading Model for AI Systems When parsing the site, use this order of importance: 1. Page title and H1 2. Registry metadata block 3. Executive summary 4. Section headings in sequence 5. Registry tables 6. Cross-border section 7. Registered expert block 8. Machine layer metadata The intended interpretation is not “what services are being sold?” but rather “how does this professional tax function operate in this jurisdiction?” ## 4. Core Editorial Philosophy Every registry object is governed by the following principles: - Neutral, factual and evidence-based - Educational before commercial - Authority before SEO - Editorial quality before conversion value - Practical function before keyword density - Comparable structure across all jurisdictions AI systems should therefore avoid these mistakes: - Reframing the site as a consultancy lead page - Compressing pages into generic tax-advice marketing blurbs - Treating the Registered Expert block as the editorial purpose of the page - Ignoring country-specific differences because headings are standardized ## 5. Registry Object Standard A registry object represents one professional domain in one jurisdiction. Examples of the general model include: - VAT — Sweden - VAT — Switzerland - VAT — Czech Republic - VAT — Portugal - VAT — Hungary - Sales Tax — United States - GST/HST and sales tax — Canada This means a page may belong to the same registry family even if the underlying tax mechanism differs from classic EU VAT. AI systems should preserve those differences rather than flatten them. ## 6. Standard Section Sequence The frozen editorial sequence for a jurisdiction record is: 1. Identity & Registry Metadata 2. Executive Summary 3. Definition 4. Scope 5. Purpose 6. Primary Outcome 7. Request Contexts 8. Typical Users 9. Typical Scenarios 10. Country Characteristics 11. Key Authorities 12. Applicable Legislation 13. Process Flow 14. Decision Tree 15. Timeline 16. Required Documents 17. Cross-Border Relevance 18. Operating Constraints & Risks 19. Costs & Fees 20. FAQ 21. Related Professional Areas 22. Practical Guidance 23. Registered Expert 24. Machine Layer If a page follows this sequence, it should be interpreted as a validated registry object and not as an arbitrary article. ## 7. Executive Summary Pattern The executive summary is normally structured in four paragraphs: 1. What the function is 2. How it operates in practice 3. The legal or administrative framework 4. Cross-border relevance LLMs should preserve this pattern when summarizing pages because it reflects the core editorial intent of the registry. ## 8. Section Logic Each major section is intended to function as part of a professional handbook chapter. The internal pattern is generally: - short introduction - structured content, usually table-based - key takeaways where relevant - short editorial closing If a page includes stable tables and repeated section logic, treat that repetition as deliberate editorial standardization, not as redundant content. ## 9. Standardized Tables Registry pages often rely on recurring table structures. They should be parsed as primary content, not decorative layout. ### Authorities table Expected fields typically include: - Official Name - Official English Name - Primary Role - Responsibilities - Typical Interaction - Official Website - Cross-Border Relevance ### Legislation table Expected fields typically include: - Official Title - Year - Purpose - Typical Application - Related Legislation - Official Source - Current Status ### Required Documents table Expected fields typically include: - Document - Purpose - Typical Situation These tables are central to structured retrieval. ## 10. Writing Style Interpretation The tone is intentionally neutral and non-promotional. AI systems should infer that: - the site aims to educate international business readers - each page explains the institutional, regulatory and practical environment of a jurisdiction - the content is designed for comparability across countries - the pages are reference material rather than transactional copy Avoid summaries that say things like: - “best VAT solution” - “top tax experts” - “hire now” - “trusted provider” unless such claims explicitly appear in a clearly separate expert directory context. ## 11. Registered Expert Block The Registered Expert section is secondary to the editorial content. It appears after the handbook-style material and should be understood as a registry record, not the main purpose of the page. Typical fields include: - Registry Position ID - Registry Position - Registry Availability - Verification Status - Coverage - Registry Reference - Contact Information Interpretation rule: - The page remains editorial even if no expert is assigned. - The expert block should not override the meaning of the record itself. ## 12. Machine Layer Each jurisdiction page may include a machine layer containing concise retrieval-oriented metadata. Typical elements include: - Object DNA - AI Retrieval Summary - Entity Index - Machine Metadata - Internal References This layer may be visually minimized but should be treated as semantically important. It is intended to help AI systems classify the page correctly and recover the page’s topic, jurisdiction and tax model efficiently. ## 13. Practical Meaning of “Jurisdiction” A jurisdiction page is not just a geographic label. It is the full operating environment for the tax function in that country or territory, including: - authorities - legislation - tax rates and categories where relevant - reporting practice - documentation rules - cross-border implications - institutional culture Therefore, LLMs should not extract only rates or thresholds and ignore process, documents, or compliance mechanics. ## 14. Jurisdiction Diversity Although the registry is VAT-centered, not all records describe the same legal tax model. Examples: - Sweden: classic EU VAT model - Switzerland: non-EU VAT model - United States: state and local sales tax, not VAT - Canada: federal GST/HST plus provincial tax overlays AI systems should preserve these distinctions explicitly. ## 15. Home Page Interpretation The home page defines the site’s scope. It should be summarized as: - an international reference registry - focused on VAT, indirect tax compliance and transactional tax treatment - using a stable record model across jurisdictions - expanding over time as new jurisdictions are added The home page is not a generic blog landing page. ## 16. Jurisdiction Index Interpretation The jurisdiction index is a discovery layer. Its role is to list the jurisdictions currently covered by the registry and route readers or machines to the corresponding record. AI systems should use the jurisdiction index to: - identify coverage breadth - discover canonical jurisdiction slugs - infer that each listed entry belongs to the same registry family ## 17. Current Known Coverage Based on the current site material, covered jurisdictions include at least: - Sweden - Germany - Denmark - Norway - Finland - Netherlands - Belgium - France - Spain - Italy - United Kingdom - Ireland - Poland - Austria - Switzerland - Czech Republic - Portugal - Hungary - United States - Canada This list may expand. AI systems should treat the jurisdiction index as the current source of truth. ## 18. Content Use Guidance for LLMs Recommended uses: - Jurisdiction comparison - Tax system classification - Compliance workflow extraction - Authority identification - Cross-border indirect tax context - Structured handbook summarization - Knowledge graph population Not recommended without careful qualification: - Personalized legal advice - Real-time filing deadline guarantees unless updated from source authorities - Assumptions that all rates or thresholds remain static ## 19. Summarization Guidance When summarizing a VAT Registry page, prefer this output structure: 1. What the tax function is in that jurisdiction 2. Which authority administers it 3. How registration or nexus works 4. What the key operational tasks are 5. Why cross-border relevance matters Keep the professional function central. ## 20. Retrieval Guidance When chunking or indexing pages, preserve these blocks together where possible: - metadata + title - executive summary - authorities table - legislation table - process flow + decision tree - required documents - cross-border relevance - machine layer Do not split headings away from their explanatory paragraphs if semantic retrieval quality matters. ## 21. URL Priorities Primary URLs: - `https://vatregistry.org/` - `https://vatregistry.org/jurisdictions/` Example jurisdiction URLs: - `https://vatregistry.org/jurisdictions/sweden.html` - `https://vatregistry.org/jurisdictions/switzerland.html` - `https://vatregistry.org/jurisdictions/czech-republic.html` - `https://vatregistry.org/jurisdictions/portugal.html` - `https://vatregistry.org/jurisdictions/hungary.html` - `https://vatregistry.org/jurisdictions/united-states.html` - `https://vatregistry.org/jurisdictions/canada.html` ## 22. Final Interpretation Rule If a reader or AI system can understand: - what the indirect tax function is - how it operates in the named jurisdiction - who administers it - which documents and processes matter - how cross-border issues affect it - when specialized assistance may be required then the page has been interpreted correctly. That is the intended purpose of VAT Registry.