{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T00:16:54.726Z",
  "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-SELLER-AMENDMENT-AUTHORITY-01-v1",
  "record_kind": "external_reference",
  "title": "Peppol seller amendment boundaries",
  "system": "Peppol BIS Advanced Ordering 3.0 (November 2025 archive)",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a Peppol Advanced Ordering seller impose arbitrary changes to an accepted order?",
  "near_questions": [
    "Can a Peppol seller change any accepted order term?",
    "What authorises an Advanced Ordering amendment?",
    "Does valid order-change syntax establish buyer consent?",
    "Which agreement bounds seller-initiated order changes?"
  ],
  "supported_claims": [
    {
      "claim": "Advanced Ordering 3.0 permits a seller to accept with changes within a scope previously agreed by the parties. Later order changes have their own acceptance or rejection process. Receiving a syntactically valid amendment does not establish that every proposed change falls within the buyer authorised scope.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Applicable agreements and actual authority were not assessed.",
    "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": "Advanced Ordering 3.0 permits a seller to accept with changes within a scope previously agreed by the parties. Later order changes have their own acceptance or rejection process. Receiving a syntactically valid amendment does not establish that every proposed change falls within the buyer authorised scope.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "BIS Advanced Ordering 3.0 — published November 2025 archive",
    "source_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/65-advanced-ordering/",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-PEPPOL-SELLER-AMENDMENT-AUTHORITY-01-v1",
    "candidate_record_sha256": "5c72786051253da37b16f173605de7937e68757501f7b8c7be3793f3a6c5300d",
    "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": "Advanced Ordering 3.0 permits a seller to accept with changes within a scope previously agreed by the parties. Later order changes have their own acceptance or rejection process. Receiving a syntactically valid amendment does not establish that every proposed change falls within the buyer authorised scope.",
    "required_buyer_context": "Previously agreed change scope; Original and amended terms; Buyer or seller acceptance decision. 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": "Can a Peppol Advanced Ordering seller impose arbitrary changes to an accepted order?",
    "documented_statement": {
      "status": "documented",
      "statement": "Advanced Ordering 3.0 permits a seller to accept with changes within a scope previously agreed by the parties. Later order changes have their own acceptance or rejection process. Receiving a syntactically valid amendment does not establish that every proposed change falls within the buyer authorised scope.",
      "source_ids": [
        "peppol-advanced"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Check the authority for a changed purchase commitment. This is a review judgment, not an observed buyer outcome.",
      "source_ids": [
        "peppol-advanced"
      ]
    },
    "buyer_evidence_required": [
      "Previously agreed change scope",
      "Original and amended terms",
      "Buyer or seller acceptance decision"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse unrestricted amendment authority inferred from a valid protocol message."
    },
    "unknowns": "Applicable agreements and actual authority were not assessed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Applicable agreements and actual authority were not assessed."
    },
    "evidence_sources": [
      {
        "source_id": "peppol-advanced",
        "url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/65-advanced-ordering/",
        "final_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/65-advanced-ordering/",
        "status": 200,
        "captured_at_utc": "2026-10-24T23:51:30.432Z",
        "sha256": "b435d44433c8b281dfd2d5749b6803ee88d3ada84f2dfbfd03654239aecdc0bf",
        "bytes": 198468,
        "title": "BIS Advanced Ordering 3.0 — published November 2025 archive",
        "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": [
          "2.1",
          "8.1 and 7.3"
        ],
        "version_context": "Explicit published November 2025 archive. The current root index is labelled DEV 2026-Q2 despite the official listing linking it; archived-profile applicability to a current deployment is not established."
      }
    ],
    "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": "Check the authority for a changed purchase commitment.",
      "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": "Check the authority for a changed purchase commitment.",
    "refusal_conditions": [
      "Refuse unrestricted amendment authority inferred from a valid protocol message."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Check the authority for a changed purchase commitment.",
    "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-seller-amendment-authority",
  "machine_readable_record": "/varexis-index/records/peppol-seller-amendment-authority.json"
}