{
  "format": "vercy-enterprise-adoption-profile/v1",
  "contourId": "EM-FIN-03",
  "name": "Enterprise Invoice-Payment Allocation",
  "decision": "PROFILE",
  "newRuntimeId": false,
  "bases": [
    "WM-ECO-009",
    "WM-ECO-008"
  ],
  "constraints": [
    "Commercial-document and payment identifiers remain distinct; remittance references correlate and never merge identity.",
    "Each append-only allocation tuple pins payment ID, document ID, sequence, signed allocation amount and currency, allocating party, allocation instant and a basis-entry set.",
    "Each basis entry contains a governed reason code and signed amount; mixed discount, credit, adjustment and deduction entries sum exactly to the tuple's documented deduction and never collapse into allocation amount.",
    "Payer-advised, payee-applied and accepted allocations remain distinct voices; disagreement creates a reconciliation break and never overwrites another voice or silently yields an accepted tuple.",
    "Document residual at instant T derives from accepted allocations through T plus the complete WM-ECO-008 correction chain at T and is never written onto the issued document.",
    "Settlement amount, document-currency allocation, FX difference, rounding difference, rate quote/basis/time/source, charge-bearer deduction and unallocated payment residual are distinct money facts governed by WM-XCT-032 references.",
    "For each payment direction, the signed sum of accepted allocations plus separately signed charge-bearer deductions cannot exceed the signed final settlement amount in that direction; instructed amount is never the conservation base.",
    "Accepted allocations to one document cannot exceed its admissible chain-derived claim without an explicit overpayment or exception outcome.",
    "Overpayment remains an explicit payment-side residual; on-account cash is a payment with an empty accepted-allocation set and no inferred invoice credit.",
    "Payee may differ from seller only when an external receivables-assignment or authorized-collection reference proves standing; missing assignment authority fails closed.",
    "Post-finality return or recovery creates a new opposite-direction payment and signed counter-allocation; original payment and tuples remain immutable and final.",
    "Invoice cancellation or credit is a WM-ECO-008 chain event; it recomputes residual without becoming a payment reversal or deleting prior allocations.",
    "Closure is a read-side derivation owned by no write authority and is true only for zero residual, settlement finality, no open dispute and no discharge exception; it is never materialized as authoritative payment or document state.",
    "Cash application, bank or statement reconciliation, and invoice/order/receipt matching are separately namespaced and never treated as evidence for one another.",
    "Payment reconciliation never establishes delivery or fulfilment and accounting handoff never owns posting rules."
  ],
  "candidateRevision": 3,
  "references": [
    "WM-XCT-032",
    "WM-ECO-016"
  ],
  "holds": [
    "WM-ECO-008 and WM-ECO-009 are non-canonical reviewable drafts and the profile cannot promote ahead of them.",
    "Account or Holding ownership for credit balances is unresolved; on-account cash and overpayment remain payment-side residual only.",
    "Receivables assignment and collection authority are external and unallocated in this contour; factoring fails closed without an authority reference.",
    "Contractual appropriation priority and rail-specific return or revocability rules require regime profiles.",
    "ISO 20022, UBL RemittanceAdvice and EN 16931 BT-83 crosswalks remain unpinned alignment targets.",
    "WM-ECO-016 remains the external accounting-posting authority."
  ],
  "version": "0.1.0",
  "assurance": "reviewable-research-profile",
  "publicationState": "published-partial",
  "runtimeId": null,
  "canonical": false,
  "installable": false
}