{ "schema": "varexis-index-free-publication-preview/1", "catalogue_version": "pub-7-tranche-57-v1", "route_id": "agentic_reviewed_peppol_mlr_technical_business_acceptance", "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-TECHNICAL-BUSINESS-ACCEPTANCE-01-v1", "question": "Does a Peppol Message Level Response accepting a document also accept its commercial terms?", "answer": "The published Message Level Response profile separates transport receipt, document conformance and the business decision. An accepted technical response therefore does not establish that a supplier accepted a purchase, that an invoice was approved or that a payment was authorised. Retain the appropriate business response as a separate item of evidence.", "records": [ { "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-TECHNICAL-BUSINESS-ACCEPTANCE-01-v1", "url": "/varexis-index/records/peppol-mlr-technical-business-acceptance.json", "content_sha256": "e5160d903eb7e45aef18137edc4673af37dbe7c4070ad2bb8596a24849e33140", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-25T00:16:54.726Z", "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-TECHNICAL-BUSINESS-ACCEPTANCE-01-v1", "record_kind": "external_reference", "title": "Peppol technical response versus commercial acceptance", "system": "Peppol BIS Message Level Response 3.0 (November 2025 archive)", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does a Peppol Message Level Response accepting a document also accept its commercial terms?", "near_questions": [ "Does Peppol technical acceptance approve an invoice?", "Can a Peppol transport acknowledgement authorise a purchase?", "What distinguishes Peppol conformance from business acceptance?", "Which response proves the supplier accepted commercial terms?" ], "supported_claims": [ { "claim": "The published Message Level Response profile separates transport receipt, document conformance and the business decision. An accepted technical response therefore does not establish that a supplier accepted a purchase, that an invoice was approved or that a payment was authorised. Retain the appropriate business response as a separate item of evidence.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "The recipient business decision was not observed.", "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": "The published Message Level Response profile separates transport receipt, document conformance and the business decision. An accepted technical response therefore does not establish that a supplier accepted a purchase, that an invoice was approved or that a payment was authorised. Retain the appropriate business response as a separate item of evidence.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "BIS Message Level Response 3.0 — published November 2025 archive", "source_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/36-mlr/", "checked_on": "2026-10-25", "candidate_record_id": "VXI-EXT-PROCUREMENT-PEPPOL-MLR-TECHNICAL-BUSINESS-ACCEPTANCE-01-v1", "candidate_record_sha256": "f7a954639831c1c8e7b883d9a532dbe265645151e4feff445f3736c10c1ad67a", "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": "The published Message Level Response profile separates transport receipt, document conformance and the business decision. An accepted technical response therefore does not establish that a supplier accepted a purchase, that an invoice was approved or that a payment was authorised. Retain the appropriate business response as a separate item of evidence.", "required_buyer_context": "Message Level Response and code; Referenced business message; Separate business 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": "Does a Peppol Message Level Response accepting a document also accept its commercial terms?", "documented_statement": { "status": "documented", "statement": "The published Message Level Response profile separates transport receipt, document conformance and the business decision. An accepted technical response therefore does not establish that a supplier accepted a purchase, that an invoice was approved or that a payment was authorised. Retain the appropriate business response as a separate item of evidence.", "source_ids": [ "peppol-mlr" ] }, "review_inference": { "status": "review_inference", "statement": "Avoid releasing a purchase on technical acceptance alone. This is a review judgment, not an observed buyer outcome.", "source_ids": [ "peppol-mlr" ] }, "buyer_evidence_required": [ "Message Level Response and code", "Referenced business message", "Separate business decision" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse commercial-acceptance claims based solely on a technical response." }, "unknowns": "The recipient business decision was not observed.", "unknown_finding": { "status": "unknown", "statement": "The recipient business decision was not observed." }, "evidence_sources": [ { "source_id": "peppol-mlr", "url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/36-mlr/", "final_url": "https://docs.peppol.eu/poacc/upgrade-3/2025-Q4/profiles/36-mlr/", "status": 200, "captured_at_utc": "2026-10-24T23:51:30.448Z", "sha256": "e9ed0f5509414c85119a6b09b0e927ed2a979a7bac29584a74b231e832399e57", "bytes": 100435, "title": "BIS Message Level Response 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–2.2", "6.2", "6.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": "Avoid releasing a purchase on technical acceptance alone.", "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": "Avoid releasing a purchase on technical acceptance alone.", "refusal_conditions": [ "Refuse commercial-acceptance claims based solely on a technical response." ] }, "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": "Avoid releasing a purchase on technical acceptance alone.", "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-mlr-technical-business-acceptance", "machine_readable_record": "/varexis-index/records/peppol-mlr-technical-business-acceptance.json" } } ], "access": { "mode": "exact_http_only", "payment_required": false, "purchase_url": null, "mcp_preview_available": false, "paid_saved_retrieval_available": false, "natural_language_search_qualified": false }, "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.", "content_sha256": "9452d24c5dbaf5d6fdeb1999b9857058c215155e460e1b175f948051acae314e" }