{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T00:16:54.726Z",
  "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-BILLING-SCHEMA-BUSINESS-VALIDATION-01-v1",
  "record_kind": "external_reference",
  "title": "Peppol schema versus business-rule validation",
  "system": "Peppol BIS Billing 3.0.21",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does successful UBL schema validation establish all Peppol invoice business rules passed?",
  "near_questions": [
    "Does valid UBL XML satisfy all Peppol business rules?",
    "What validation follows invoice schema checks?",
    "Why must a Peppol rule version be retained?",
    "Can document conformance prove real invoice facts?"
  ],
  "supported_claims": [
    {
      "claim": "BIS Billing separates UBL schema validation from semantic business rules and the applicable Peppol restrictions, including conditionally applicable country rules. Passing XML structure checks alone does not establish that those other layers passed, nor that the invoice facts are correct. Retain the validation layer, version and results.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "No invoice instance or production validator was tested.",
    "No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.",
    "Applies to the cited published profile; current deployment and release applicability require separate verification.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "BIS Billing separates UBL schema validation from semantic business rules and the applicable Peppol restrictions, including conditionally applicable country rules. Passing XML structure checks alone does not establish that those other layers passed, nor that the invoice facts are correct. Retain the validation layer, version and results.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "BIS Billing 3.0.21 — May 2026 release",
    "source_url": "https://docs.peppol.eu/poacc/billing/3.0/bis/",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-PEPPOL-BILLING-SCHEMA-BUSINESS-VALIDATION-01-v1",
    "candidate_record_sha256": "bc4cee9c323c16ebbb2aab7c702bb83a7e20a530703a0d2777a7c025c079b8c2",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "BIS Billing separates UBL schema validation from semantic business rules and the applicable Peppol restrictions, including conditionally applicable country rules. Passing XML structure checks alone does not establish that those other layers passed, nor that the invoice facts are correct. Retain the validation layer, version and results.",
    "required_buyer_context": "Schema validation result; Applicable rule versions and business-rule results; Invoice facts and country context. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-25",
    "claim_to_check": "Does successful UBL schema validation establish all Peppol invoice business rules passed?",
    "documented_statement": {
      "status": "documented",
      "statement": "BIS Billing separates UBL schema validation from semantic business rules and the applicable Peppol restrictions, including conditionally applicable country rules. Passing XML structure checks alone does not establish that those other layers passed, nor that the invoice facts are correct. Retain the validation layer, version and results.",
      "source_ids": [
        "peppol-billing"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Identify which validation evidence is still missing before invoice reliance. This is a review judgment, not an observed buyer outcome.",
      "source_ids": [
        "peppol-billing"
      ]
    },
    "buyer_evidence_required": [
      "Schema validation result",
      "Applicable rule versions and business-rule results",
      "Invoice facts and country context"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse full conformance or factual correctness from schema validation alone."
    },
    "unknowns": "No invoice instance or production validator was tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No invoice instance or production validator was tested."
    },
    "evidence_sources": [
      {
        "source_id": "peppol-billing",
        "url": "https://docs.peppol.eu/poacc/billing/3.0/bis/",
        "final_url": "https://docs.peppol.eu/poacc/billing/3.0/bis/",
        "status": 200,
        "captured_at_utc": "2026-10-24T23:51:30.444Z",
        "sha256": "a30f773b96dc7e7e5596cce9e5f62c2f862d0a53232b57411a9e969c0a85dfd3",
        "bytes": 761312,
        "title": "BIS Billing 3.0.21 — May 2026 release",
        "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
        "rights_review": "Original factual paraphrase only. CEN/OpenPeppol reserve rights in their BIS documents. Raw captures remain private; no document, schema, code or modified standard is redistributed or relicensed.",
        "checked_on": "2026-10-25",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "11.1.3",
          "11.3.1–11.3.2",
          "11.4",
          "11.6",
          "11.7.2",
          "11.10 plus calculation section review needed",
          "13.2–13.3 and billing release3.0.21",
          "15.1"
        ],
        "version_context": "Billing 3.0.21, published 2026-05-20; exact captured body hash. Current deployment applicability is not verified."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Identify which validation evidence is still missing before invoice reliance.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction."
    },
    "buyer_relevance": "Identify which validation evidence is still missing before invoice reliance.",
    "refusal_conditions": [
      "Refuse full conformance or factual correctness from schema validation alone."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Identify which validation evidence is still missing before invoice reliance.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#peppol-billing-schema-business-validation",
  "machine_readable_record": "/varexis-index/records/peppol-billing-schema-business-validation.json"
}