{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T00:16:54.726Z",
  "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-ORDER-RESPONSE-LINE-BINDING-01-v1",
  "record_kind": "external_reference",
  "title": "Peppol order and line references",
  "system": "Peppol BIS Ordering 3.3 (November 2025 archive)",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "How should a Peppol order response be matched to the original order and individual lines?",
  "near_questions": [
    "How do Peppol response lines reference purchase-order lines?",
    "Can product descriptions identify an accepted order line?",
    "Where is the original order ID in a Peppol response?",
    "What identifiers prevent order-line reconciliation mistakes?"
  ],
  "supported_claims": [
    {
      "claim": "Ordering 3.3 requires an order reference at header level. If response lines are supplied, each needs the related original order-line reference. Reconciliation should use those identifiers and the correct document context; matching by item description or response position alone can attach a decision to the wrong line.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "The buyer order and response were not inspected.",
    "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": "Ordering 3.3 requires an order reference at header level. If response lines are supplied, each needs the related original order-line reference. Reconciliation should use those identifiers and the correct document context; matching by item description or response position alone can attach a decision to the wrong line.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "BIS Ordering 3.3 — published November 2025 archive",
    "source_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/28-ordering/",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-PEPPOL-ORDER-RESPONSE-LINE-BINDING-01-v1",
    "candidate_record_sha256": "653a954bf21f47bd4b9e6111fb0af8a0895a59c9fc471234c8b4880d70fddd3b",
    "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": "Ordering 3.3 requires an order reference at header level. If response lines are supplied, each needs the related original order-line reference. Reconciliation should use those identifiers and the correct document context; matching by item description or response position alone can attach a decision to the wrong line.",
    "required_buyer_context": "Original order identifier and lines; Response header order reference; Response line references. 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": "How should a Peppol order response be matched to the original order and individual lines?",
    "documented_statement": {
      "status": "documented",
      "statement": "Ordering 3.3 requires an order reference at header level. If response lines are supplied, each needs the related original order-line reference. Reconciliation should use those identifiers and the correct document context; matching by item description or response position alone can attach a decision to the wrong line.",
      "source_ids": [
        "peppol-ordering"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Bind seller decisions to the intended original purchase lines. This is a review judgment, not an observed buyer outcome.",
      "source_ids": [
        "peppol-ordering"
      ]
    },
    "buyer_evidence_required": [
      "Original order identifier and lines",
      "Response header order reference",
      "Response line references"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse line-level acceptance attribution where original references cannot be resolved."
    },
    "unknowns": "The buyer order and response were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer order and response were not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "peppol-ordering",
        "url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/28-ordering/",
        "final_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/28-ordering/",
        "status": 200,
        "captured_at_utc": "2026-10-24T23:51:30.410Z",
        "sha256": "4ffedba4884733d8f56287e0d723293fa5d166496bc69fbc5e3a29b9fe541519",
        "bytes": 197806,
        "title": "BIS Ordering 3.3 — 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": [
          "7.1.1",
          "7 and 7.3",
          "7.1.2",
          "7.2",
          "7.5"
        ],
        "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": "Bind seller decisions to the intended original purchase lines.",
      "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": "Bind seller decisions to the intended original purchase lines.",
    "refusal_conditions": [
      "Refuse line-level acceptance attribution where original references cannot be resolved."
    ]
  },
  "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": "Bind seller decisions to the intended original purchase lines.",
    "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-order-response-line-binding",
  "machine_readable_record": "/varexis-index/records/peppol-order-response-line-binding.json"
}