Skip to content

Settlement and legal-order payment processing

This operation covers clsSettlementPayment and its concrete types clsCDAPayment, clsDCSPayment, clsFederalSettlement, and clsLegalOrderPayment, which validate settlement amount/distribution consistency, enforce statutory distribution caps and duplicate-settlement guards, and — for CDA and DCS — trigger claim-status side effects on release.

Field Value
Operation ID OP-CP-13
Trigger Adjuster creates a clsCDAPayment/clsDCSPayment/clsFederalSettlement/clsLegalOrderPayment and calls CheckApprovalErrors/Approve()/Save()
Inputs Settlement total, per-payee distribution amounts, order-approved date, claim jurisdiction, structured-settlement flag
Outputs Released settlement financial transaction; claim status update (CDA close, DCS deactivation) for released non-structured settlements; updated CL_INJURY_CLAIM rows
Primary components clsSettlementPayment, clsCDAPayment, clsDCSPayment, clsFederalSettlement, clsLegalOrderPayment
Entry point Business\SAIF.Business.Claim.Payment\Payments\SettlementPayments\clsSettlementPayment.vb

Steps

  1. Require a responsible adjuster and non-void claim (BR-CP-057), same as every other payment type in this library.
  2. Validate settlement amount and distribution consistency (BR-CP-064). clsSettlementPayment.CheckApprovalErrors requires the total between $0.01 and $999,999.99, requires it to equal the sum of payee payment amounts ("Error: Sum of benefit amounts must = settlement amount."), and requires the order-approved date to fall between the injury date and today (or be blank for a structured settlement).
  3. Warn on excessive support-order deduction (BR-CP-065). CheckApprovalWarnings caps the support-order deduction at 25% (issue date on/after the configured cutover) or 50% (before) of the total payment, skipped for federal settlements; a support order with arrearage but no deduction also warns.
  4. Apply the DCS statutory-minimum distribution cap when applicable (BR-CP-066). clsDCSPayment.DistributeAmounts(StatutoryMinimum)/GetMedProviderAmounts cap the total payable to medical providers at 40% of the settlement total, proportionally scaling down each medical payee's audited amount with the rounding remainder assigned to the last non-zero payee.
  5. Block self-approval of legal-order payments unconditionally (BR-CP-067). clsLegalOrderPayment.AwaitingApprovalChecks refuses approval for the initiator's own payment regardless of authority level.
  6. Guard against duplicate DCS payments (BR-CP-068). A DCS "Full" payment cannot be approved if a prior Full DCS payment already exists for the claim; a DCS "Partial" payment cannot repeat the same issue date and amount as a prior partial payment.
  7. Guard against a repeat CDA/federal settlement by the same initiator (BR-CP-068). clsSettlementPayment.HasPreviouslyPaid blocks a CDA or federal settlement's approval by an initiator who previously released a settlement of the same category on the claim.
  8. Require federal jurisdiction for a federal settlement (BR-CP-070). clsFederalSettlement.Rule_IsFederal blocks retrieval/save with "Error: The claim's jurisdiction must be federal." on a non-federal claim.
  9. Restrict federal settlement auto-payees. A federal settlement's automatic-payee set excludes Medical Provider, unlike CDA and DCS settlements which include it (BR-CP-070).
  10. Release the settlement. On success, the settlement is posted through Payment posting and totals management and Financial transaction and remark management, updating CL_INJURY_CLAIM via SQL-109/SQL-110 (CL_INJURY_CLAIM).
  11. Trigger claim-status side effects for CDA. A released, non-structured CDA settlement on an open claim whose status-effective date is on or before the order-approved date closes the claim (clsCDAPayment.Save override) (BR-CP-069).
  12. Trigger claim-status side effects for DCS. A released, non-structured full DCS payment deactivates the claim and finalizes the denial status of any pending medical-condition compensability decision (clsDCSPayment.Save override, UpdateClaimDecisions) (BR-CP-069).
  13. Enforce overpayment recovery on settlement approval (BR-CP-025). CheckApprovalErrors enforces the claim's outstanding overpayment balance against the settlement — the production rule that supersedes the unconfirmed BR-CP-003 citation (see the business rules notes); the related payee-level enforcement is also discussed in Payee management.

Process flow

flowchart TD
    Start([Adjuster creates settlement payment]) --> AmountCheck{Amount/distribution/<br>order-date consistent?}
    AmountCheck -->|No| Blocked1([Blocked: approval error])
    AmountCheck -->|Yes| SupportWarn[Warn if support deduction<br>exceeds ceiling]
    SupportWarn --> SettlementType{Settlement type?}
    SettlementType -->|DCS Statutory Min| DistCap[Cap medical providers<br>at 40% of total]
    SettlementType -->|Legal order| SelfCheck{Initiator = approver?}
    SelfCheck -->|Yes| Blocked2([Blocked: cannot self-approve])
    SettlementType -->|Federal| FedCheck{Claim jurisdiction<br>is federal?}
    FedCheck -->|No| Blocked3([Blocked: jurisdiction error])
    SettlementType -->|CDA or Federal| RepeatCheck{Initiator previously<br>released same category?}
    RepeatCheck -->|Yes| Blocked4([Blocked: previously paid])
    DistCap --> DupDCS
    FedCheck -->|Yes| DupDCS
    RepeatCheck -->|No| Release
    SelfCheck -->|No| Release
    DupDCS{DCS: duplicate Full<br>or repeat Partial?} -->|Yes| Blocked5([Blocked: DCS duplicate])
    DupDCS -->|No| Release[Release settlement payment]
    Release --> SideEffect{CDA or DCS,<br>non-structured, released?}
    SideEffect -->|CDA| CloseClaim[Close claim if<br>eligible by status-effective date]
    SideEffect -->|DCS Full| Deactivate[Deactivate claim;<br>finalize denial decision]
    SideEffect -->|No| Done([Settlement released])
    CloseClaim --> Done
    Deactivate --> Done

Failure and edge-case behavior

  • The CDA claim-closure side effect is conditional on the claim's status-effective date being on or before the order-approved date — a CDA settlement can be released without closing the claim if that date condition is not yet met, meaning claim closure is not guaranteed by settlement release alone.
  • Structured settlements are exempt from the order-approved-date bounds check (BR-CP-064) and from the CDA/DCS claim-status side effects, since those side effects apply only to non-structured settlements.
  • The DCS statutory-minimum distribution cap's rounding remainder is assigned entirely to the last non-zero medical payee, which could produce a visibly uneven per-payee cent allocation among otherwise identical medical bills.
  • Federal settlements skip the support-deduction warning check entirely (BR-CP-065), which is an intentional carve-out tied to federal jurisdiction rules rather than an omission.

Note: Statements marked with * were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts.

Sources

  • Business\SAIF.Business.Claim.Payment\Payments\SettlementPayments\clsSettlementPayment.vb
  • Business\SAIF.Business.Claim.Payment\Payments\SettlementPayments\clsCDAPayment.vb
  • Business\SAIF.Business.Claim.Payment\Payments\SettlementPayments\clsDCSPayment.vb
  • Business\SAIF.Business.Claim.Payment\Payments\SettlementPayments\clsFederalSettlement.vb
  • Business\SAIF.Business.Claim.Payment\Payments\SettlementPayments\clsLegalOrderPayment.vb