{ "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-25T00:16:54.726Z", "record_id": "VXI-EXT-PROCUREMENT-PEPPOL-BILLING-PROFILE-RESPONSE-CAPABILITY-01-v1", "record_kind": "external_reference", "title": "Peppol billing profile and response capability", "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 basic Peppol Billing Profile 01 guarantee a structured invoice response?", "near_questions": [ "Does Peppol Billing Profile 01 include invoice responses?", "What changes with Billing with Response Profile 02?", "Is separate SMP registration needed for invoice responses?", "How can an agent confirm structured invoice feedback capability?" ], "supported_claims": [ { "claim": "Billing 3.0.21 distinguishes basic Profile 01 from Billing with Response Profile 02. The release notes require separate SMP registration for the response profile. An invoice under the basic profile does not itself establish structured response support; check the recipient capability and the actual process agreement.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Live recipient registration and response delivery were not checked.", "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": "Billing 3.0.21 distinguishes basic Profile 01 from Billing with Response Profile 02. The release notes require separate SMP registration for the response profile. An invoice under the basic profile does not itself establish structured response support; check the recipient capability and the actual process agreement.", "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-PROFILE-RESPONSE-CAPABILITY-01-v1", "candidate_record_sha256": "6527c16b91a8332782459b1cf61e8b207f9c90b1c7047ffd95c05650e2e29e2f", "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": "Billing 3.0.21 distinguishes basic Profile 01 from Billing with Response Profile 02. The release notes require separate SMP registration for the response profile. An invoice under the basic profile does not itself establish structured response support; check the recipient capability and the actual process agreement.", "required_buyer_context": "Invoice ProfileID; Recipient SMP capability registration; Agreed response process. 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 basic Peppol Billing Profile 01 guarantee a structured invoice response?", "documented_statement": { "status": "documented", "statement": "Billing 3.0.21 distinguishes basic Profile 01 from Billing with Response Profile 02. The release notes require separate SMP registration for the response profile. An invoice under the basic profile does not itself establish structured response support; check the recipient capability and the actual process agreement.", "source_ids": [ "peppol-billing", "peppol-billing-release" ] }, "review_inference": { "status": "review_inference", "statement": "Confirm response capability before depending on automated invoice feedback. This is a review judgment, not an observed buyer outcome.", "source_ids": [ "peppol-billing", "peppol-billing-release" ] }, "buyer_evidence_required": [ "Invoice ProfileID", "Recipient SMP capability registration", "Agreed response process" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse guaranteed structured feedback inferred from basic Billing Profile 01." }, "unknowns": "Live recipient registration and response delivery were not checked.", "unknown_finding": { "status": "unknown", "statement": "Live recipient registration and response delivery were not checked." }, "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." }, { "source_id": "peppol-billing-release", "url": "https://docs.peppol.eu/poacc/billing/3.0/release-notes/", "final_url": "https://docs.peppol.eu/poacc/billing/3.0/release-notes/", "status": 200, "captured_at_utc": "2026-10-24T23:51:30.375Z", "sha256": "02b9fce42de14e8b33518de7aa860c1672dc2c545c8b1e0261b43125748e752c", "bytes": 98058, "title": "BIS Billing 3.0.21 release notes — 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": [ "13.2–13.3 and billing release3.0.21" ], "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": "Confirm response capability before depending on automated invoice feedback.", "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": "Confirm response capability before depending on automated invoice feedback.", "refusal_conditions": [ "Refuse guaranteed structured feedback inferred from basic Billing Profile 01." ] }, "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": "Confirm response capability before depending on automated invoice feedback.", "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-profile-response-capability", "machine_readable_record": "/varexis-index/records/peppol-billing-profile-response-capability.json" }