{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "ice-05-tranche-61-v1",
  "route_id": "agentic_reviewed_coupa_payment_detail_invoice_allocation",
  "record_id": "VXI-EXT-ICE05-COUPA-PAYMENT-DETAIL-INVOICE-ALLOCATION-01-v1",
  "question": "Can a Coupa payment header total be assigned to one invoice without inspecting payment-details?",
  "answer": "The API documents payment-detail rows with invoice identifiers, invoice references, payment amounts and currencies.",
  "records": [
    {
      "record_id": "VXI-EXT-ICE05-COUPA-PAYMENT-DETAIL-INVOICE-ALLOCATION-01-v1",
      "url": "/varexis-index/records/coupa-payment-detail-invoice-allocation.json",
      "content_sha256": "ad31b3d394f893b5315700be2b7ee903c85ee86a8458f1466ae8b8f8a7cb51d2",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-29T01:09:39.613311Z",
        "record_id": "VXI-EXT-ICE05-COUPA-PAYMENT-DETAIL-INVOICE-ALLOCATION-01-v1",
        "record_kind": "external_reference",
        "title": "Coupa payment details and invoice allocation",
        "system": "Coupa",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Can a Coupa payment header total be assigned to one invoice without inspecting payment-details?",
        "near_questions": [
          "Which invoice does this Coupa payment detail settle?",
          "Can one payment total cover several invoice references?",
          "How do I bind Coupa payment amounts to invoices?",
          "What prevents misallocating a payment header total?"
        ],
        "supported_claims": [
          {
            "claim": "The API documents payment-detail rows with invoice identifiers, invoice references, payment amounts and currencies.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Reconcile the detail population before allocating a total. These fields do not establish complete allocation, matching tolerances or final settlement.",
          "Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.",
          "No expanded capabilities or licences for existing INDEX executables."
        ],
        "public_summary": "The API documents payment-detail rows with invoice identifiers, invoice references, payment amounts and currencies.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "Coupa: Payments API",
          "source_url": "https://compass.coupa.com/_dita_/en-us/documentation/plat/integ/coupa_core_api/topics/payments_api_coupa_paypayments_.dita",
          "checked_on": "2026-10-29",
          "candidate_record_id": "VXI-EXT-ICE05-COUPA-PAYMENT-DETAIL-INVOICE-ALLOCATION-01-v1",
          "candidate_record_sha256": "0694ae612cadd3cbce1be433f88915cafd4eb4ec09a607d6d6dc3d5d27ef9976",
          "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 API documents payment-detail rows with invoice identifiers, invoice references, payment amounts and currencies.",
          "required_buyer_context": "Payment ID and detail rows; Invoice IDs and references; Amounts and currencies. 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-29",
          "claim_to_check": "Can a Coupa payment header total be assigned to one invoice without inspecting payment-details?",
          "documented_statement": {
            "status": "documented",
            "statement": "The API documents payment-detail rows with invoice identifiers, invoice references, payment amounts and currencies.",
            "source_ids": [
              "coupa-payments"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Review coupa payment details and invoice allocation before accepting the buyer claim. Existing order and despatch binding does not identify invoice allocations within Coupa payment details; the new decision needs invoice-level payment amounts. This is a documentation-review judgment, not an observed deployment outcome.",
            "source_ids": [
              "coupa-payments"
            ]
          },
          "buyer_evidence_required": [
            "Payment ID and detail rows",
            "Invoice IDs and references",
            "Amounts and currencies"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Reconcile the detail population before allocating a total. These fields do not establish complete allocation, matching tolerances or final settlement."
          },
          "unknowns": "Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.",
          "unknown_finding": {
            "status": "unknown",
            "statement": "Buyer configuration, effective authority, complete usage and final business outcomes were not inspected."
          },
          "evidence_sources": [
            {
              "source_id": "coupa-payments",
              "url": "https://compass.coupa.com/_dita_/en-us/documentation/plat/integ/coupa_core_api/topics/payments_api_coupa_paypayments_.dita",
              "final_url": "https://compass.coupa.com/_dita_/en-us/documentation/plat/integ/coupa_core_api/topics/payments_api_coupa_paypayments_.dita",
              "captured_at_utc": "2026-10-29T00:50:20.484459+00:00",
              "status": 200,
              "content_type": "text/html; charset=utf-8",
              "bytes": 250207,
              "sha256": "0a92b6f3a1edd180c8f466bd44952ae9726fd20303fb236f9f4591fc4cac1c03",
              "title": "Coupa: Payments API",
              "hash_basis": "SHA-256 of captured HTTP response body bytes",
              "checked_on": "2026-10-29",
              "capture_status": 200,
              "claim_review_completed": true,
              "reviewed_sections": [
                "Overview",
                "Elements",
                "Key Data Elements"
              ],
              "version_context": "Rolling official documentation captured 2026-10-29; exact response hash is pinned, not a stable vendor release. Verify the deployed API/version and account feature availability. ",
              "rights_review": "Original factual paraphrase and attributed source metadata only. Captured documentation and code remain private; no source prose, examples, images or vendor marks are redistributed. No licence to vendor software or buyer assurance is granted."
            }
          ],
          "observed_deployment": false,
          "commercial_reliance_boundary": "Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.",
          "paid_value": {
            "decision_context": "Review coupa payment details and invoice allocation before accepting the buyer claim. Existing order and despatch binding does not identify invoice allocations within Coupa payment details; the new decision needs invoice-level payment amounts.",
            "free": "Complete review, practical questions, source references and limitations; freely accessible and locally saveable.",
            "single_request": "Unavailable for this publication-only record; historical saved retrieval remains unchanged.",
            "evidence_receipt": "Unavailable for this publication-only record; no new paid retrieval entitlement.",
            "excluded": [
              "Fresh vendor research",
              "Live provider inspection",
              "Runtime enforcement or certification",
              "Expanded executable schemas or licences",
              "Native Coupa, Stripe Issuing, GitLab or Sigstore validation"
            ],
            "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
          },
          "revalidation": {
            "trigger": "Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included.",
            "specific_watch": "Elements;Key Data Elements"
          },
          "buyer_relevance": "Review coupa payment details and invoice allocation before accepting the buyer claim. Existing order and despatch binding does not identify invoice allocations within Coupa payment details; the new decision needs invoice-level payment amounts.",
          "refusal_conditions": [
            "Reconcile the detail population before allocating a total. These fields do not establish complete allocation, matching tolerances or final settlement.",
            "Do not infer buyer deployment conformance or successful business outcomes from source documentation."
          ]
        },
        "niche": {
          "niche_id": "ice05-payments",
          "label": "Agent Payments, Authority & Transaction Evidence",
          "classification_id": "payments",
          "classification_label": "Agent Payments, Authority & Transaction Evidence",
          "topic_id": "payments",
          "buyer_intent": "Review coupa payment details and invoice allocation before accepting the buyer claim. Existing order and despatch binding does not identify invoice allocations within Coupa payment details; the new decision needs invoice-level payment amounts.",
          "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#coupa-payment-detail-invoice-allocation",
        "machine_readable_record": "/varexis-index/records/coupa-payment-detail-invoice-allocation.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": "51d5c3ccac47cef694fe72aa1a5bc1e82a5c188164b2c886885ca2f02dd04f3a"
}
