---
title: SAIF.Business.Claim.ThirdParty operations and processes
summary: Operation catalog and cross-operation hub for the third-party subrogation and recovery business objects.
status: draft
owner: SAIF
last_reviewed: 2026-07-30
library: SAIF.Business.Claim.ThirdParty
reference_type: package
---

# SAIF.Business.Claim.ThirdParty operations and processes

This page is the operation catalog and cross-operation hub for `SAIF.Business.Claim.ThirdParty`. The library exposes nine operations covering third-party recovery case management, recovery participants (people, companion claims, firms), expenses and their approval workflow, liens and settlements, distributions and refunds, notes and tasks, case search and prediction/statute analytics, billed-cost and payment reconciliation, and batch new-claim intake with adjuster assignment. Each operation's detailed, step-by-step logic lives in its own page under `operations/`.

## Operation catalog

| Operation | Intent | Trigger | Inputs | Outputs | Rules | Tables | SQL |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Maintain recovery case](operations/maintain-recovery-case.md) | Create, retrieve, update, and delete third-party recovery cases, cascade firm associations, and drive status-based task/letter generation | `clsThirdPartyCase.NewThirdPartyCase`/`GetThirdPartyCase` followed by property edits and `Save()` | `ClaimID`, date of injury, adjuster code, case status, closure code, statute/suit dates | Persisted `THRDPARTY_CASE` row; cascaded firm saves; status-driven tasks; letter print flags | [BR-009](business-rules.md#br-009-third-party-case-adjuster-code-is-required), [BR-010](business-rules.md#br-010-case-closure-requires-a-closure-code), [BR-011](business-rules.md#br-011-subsequent-intervening-cause-and-suit-filed-dates-must-fall-between-doi-and-today), [BR-012](business-rules.md#br-012-statute-date-is-required-and-must-follow-the-date-of-injury), [BR-013](business-rules.md#br-013-statute-date-monthday-should-match-doi-warning), [BR-005](business-rules.md#br-005-recovery-save-operations-require-one-affected-row) | [THRDPARTY_CASE](database-tables.md#thrdparty_case) | [SQL-054](sql/sql-054-pk82033_thirdparty-thrdparty_expense_select.md), [SQL-058](sql/sql-058-pk82033_thirdparty-thrdparty_lien_select_by_seq.md) |
| [Manage recovery participants](operations/manage-recovery-participants.md) | Persist third-party people, standalone firms, and companion claim associations for a case | `clsThrdparty.NewThirdParty`/`GetThirdParty`, `clsThrdPartyFirm.NewThrdPartyFirm`, or `clsThrdpartyCompanionClaim.NewThrdpartyCompanionClaim` followed by `Save()` | Case sequence number, person name/DOB/phone/fax, firm company name/phone/fax, companion claim number | Persisted person, firm, and companion-claim rows; resolved companion-claim worker name and conflict warnings | [BR-014](business-rules.md#br-014-third-party-person-requires-a-name-and-a-reasonable-birth-date), [BR-015](business-rules.md#br-015-third-party-phone-and-fax-numbers-must-be-full-domestic-format-length), [BR-016](business-rules.md#br-016-companion-claim-number-must-resolve-to-a-valid-claim-conflict-claims-warn-of-restricted-access), [BR-017](business-rules.md#br-017-third-party-firm-requires-a-company-name-and-full-length-phonefax-numbers), [BR-007](business-rules.md#br-007-firm-associations-use-fixed-recovery-firm-categories), [BR-005](business-rules.md#br-005-recovery-save-operations-require-one-affected-row) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_COMPANION_CLAIM](database-tables.md#thrdparty_companion_claim) | [SQL-025](sql/sql-025-pk82033_thirdparty-thrdparty_firm_insert.md), [SQL-080](sql/sql-080-pk82033_thirdparty-thrdparty_firm_update.md), [SQL-039](sql/sql-039-pk82033_thirdparty-companion_claim_select.md), [SQL-055](sql/sql-055-pk82033_thirdparty-thrdparty_firm_select.md) |
| [Manage expenses](operations/manage-expenses.md) | Create, validate, and approve third-party recovery expenses against case-level approval thresholds | `clsThrdpartyExpense.NewThrdpartyExpense`/`GetThrdpartyExpense` followed by `Save()`; `clsThrdpartyExpenseApproval.SetExpenseApproval` | Case sequence number, expense type, amount, expense date, budget code, recovery amount | Persisted `THRDPARTY_EXPENSE` rows; case-level approval status (`PEND`/`APPR`/`DISA`/`NOTR`) | [BR-018](business-rules.md#br-018-expense-type-amount-and-expense-date-are-required-and-must-fall-within-the-claims-injury-to-today-window), [BR-019](business-rules.md#br-019-budget-code-required-whenever-recovery-amount-entered-recovery-amount-cannot-exceed-expense-amount), [BR-020](business-rules.md#br-020-expense-totals-of-5000-or-more-require-supervisor-approval-25000-or-more-require-director-approval), [BR-001](business-rules.md#br-001-expense-approval-status-is-constrained-to-defined-constants) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_EXPENSE](database-tables.md#thrdparty_expense) | [SQL-060](sql/sql-060-pk82033_thirdparty-thrdparty_select.md), [SQL-061](sql/sql-061-pk82033_thirdparty-thrdparty_select.md) |
| [Manage liens and settlements](operations/manage-liens-and-settlements.md) | Persist liens, lien categories, settlements, and settlement detail rows, reconciling settlement totals to their detail lines | `clsThrdpartyLien.NewThrdpartyLien`, `clsThrdpartySettlement.NewThrdpartySettlement`, or `clsThrdpartySettlementDetail.NewThrdpartySettlementDetail` followed by `Save()` | Case/lien identifiers, lien date, settlement type/date/amount, settlement detail category codes and amounts | Persisted lien, lien category, settlement, and settlement detail rows | [BR-021](business-rules.md#br-021-lien-date-is-required), [BR-022](business-rules.md#br-022-settlement-total-must-equal-the-sum-of-settlement-detail-amounts-and-be-greater-than-zero), [BR-023](business-rules.md#br-023-settlement-type-and-settlement-date-are-required-date-cannot-be-in-the-future-or-otherwise-unreasonable), [BR-024](business-rules.md#br-024-settlement-detail-category-amount-cannot-be-negative-and-category-code-is-required), [BR-005](business-rules.md#br-005-recovery-save-operations-require-one-affected-row) | [THRDPARTY_LIEN](database-tables.md#thrdparty_lien), [THRDPARTY_LIEN_CATEGORY](database-tables.md#thrdparty_lien_category), [THRDPARTY_CASE](database-tables.md#thrdparty_case) | [SQL-056](sql/sql-056-pk82033_thirdparty-thrdparty_lien_cat_select.md), [SQL-058](sql/sql-058-pk82033_thirdparty-thrdparty_lien_select_by_seq.md), [SQL-065](sql/sql-065-pk82033_thirdparty-thrdparty_settl_dtl_select.md), [SQL-072](sql/sql-072-pk82033_thirdparty-claimcost_update.md) |
| [Manage distributions and refunds](operations/manage-distributions-and-refunds.md) | Persist distribution records reconciling check amounts against claim-cost, refund, employer-credit, and other amounts | `clsThirdpartyDistribution.NewThirdpartyDistribution`/`GetThirdpartyDistribution` followed by `Save()` | Case/distribution identifiers, payee name, check number/date/amount, refund/other amounts and names | Persisted distribution rows; read-only distribution history and refundee data | [BR-025](business-rules.md#br-025-distribution-requires-payee-name-check-number-and-a-valid-check-date), [BR-026](business-rules.md#br-026-distribution-check-amount-is-required-and-must-equal-the-sum-of-refund-claim-cost-and-other-amounts-including-excess-cash-refund-total), [BR-027](business-rules.md#br-027-distribution-refundother-amount-names-are-required-whenever-the-corresponding-amount-is-entered), [BR-002](business-rules.md#br-002-distribution-from-name-is-required), [BR-005](business-rules.md#br-005-recovery-save-operations-require-one-affected-row) | [THRDPARTY_CASE](database-tables.md#thrdparty_case) | [SQL-030](sql/sql-030-pk82033_thirdparty-thrdparty_settlement_insert.md), [SQL-066](sql/sql-066-pk82033_thirdparty-thrdparty_settlement_select.md) |
| [Manage notes and tasks](operations/manage-notes-and-tasks.md) | Persist recovery notes and assigned tasks, including a multi-outcome guard on deleting a case's last remaining task | `clsThirdpartyNote.NewThirdPartyNote`/`clsThirdpartyTask.NewThirdpartyTask` followed by property edits and `Save()` | Case sequence number, note category/text, task code, task text, assignee, due date, marked-for-delete flag | Persisted `THRDPARTY_CASE`-scoped note rows and `THRDPARTY_TASK` rows; blocked or warned deletions | [BR-028](business-rules.md#br-028-third-party-note-requires-a-category-and-note-text-limited-to-4000-characters), [BR-029](business-rules.md#br-029-third-party-task-requires-a-case-category-assignee-and-task-text), [BR-030](business-rules.md#br-030-task-due-dates-falling-on-a-non-work-day-are-automatically-shifted-to-the-next-work-day), [BR-003](business-rules.md#br-003-third-party-task-due-dates-are-limited-to-a-one-year-window), [BR-004](business-rules.md#br-004-pending-case-tasks-cannot-be-deleted-directly), [BR-005](business-rules.md#br-005-recovery-save-operations-require-one-affected-row) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_TASK](database-tables.md#thrdparty_task) | [SQL-028](sql/sql-028-pk82033_thirdparty-thrdparty_note_insert.md), [SQL-031](sql/sql-031-pk82033_thirdparty-thrdparty_task_insert.md), [SQL-059](sql/sql-059-pk82033_thirdparty-thrdparty_note_select.md), [SQL-045](sql/sql-045-pk82033_thirdparty-selecttasks.md), [SQL-046](sql/sql-046-pk82033_thirdparty-selecttasksbycase.md) |
| [Run case search and predictions](operations/run-case-search-and-predictions.md) | Search recovery cases and compute/validate lien-recovery predictions, plus read-only statute-date, unit-stat, and claim-condition lookups | `clsThrdpartyCaseSearchCollection` criteria-based search; `clsThrdpartyPrediction.GetThrdpartyPrediction`/`NewThrdpartyPrediction` followed by `Save()` | Search criteria, lien sequence number, prediction percent factor or amount, prediction status code, claim ID | Filtered case-search collection; persisted `THRDPARTY_PREDICTION`/`THRDPARTY_PREDICTION_DETAIL` rows; read-only statute-date, unit-stat, and claim-condition projections | [BR-031](business-rules.md#br-031-recovery-predictions-require-a-valid-lien-and-percent-factor-and-cannot-exceed-projected-plus-lienable-paid-amounts-or-be-negative), [BR-032](business-rules.md#br-032-predictions-pending-supervisor-approval-are-flagged-with-a-warning-and-prediction-detail-totals-must-match-the-prediction-amount), [BR-005](business-rules.md#br-005-recovery-save-operations-require-one-affected-row) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_PREDICTION](database-tables.md#thrdparty_prediction), [THRDPARTY_PREDICTION_DETAIL](database-tables.md#thrdparty_prediction_detail) | [SQL-044](sql/sql-044-pk82033_thirdparty-prediction_select.md), [SQL-048](sql/sql-048-pk82033_thirdparty-thrdparty_case_search_select.md), [SQL-047](sql/sql-047-pk82033_thirdparty-statute_date_list.md), [SQL-067](sql/sql-067-pk82033_thirdparty-unit_stat_prediction_list.md), [SQL-036](sql/sql-036-pk82033_thirdparty-claim_condition_select.md) |
| [Retrieve billed-cost and payment details](operations/retrieve-billed-cost-and-payment-details.md) | Reconcile medical bill-audit service and claim payment transaction detail amounts between lien and non-lien portions; look up cost category codes and policy note/mail routing | `clsBillAuditService.Save()`; `clsClaimPaymentTransDetail.Save()`; direct calls to `clsClaimCostCategoryCode` and `clsPolicyNote` | Lien/non-lien/allowed amounts, lien/non-lien/unknown/transaction amounts, policy number, team code, memo text | Persisted reconciled bill-audit service and payment transaction detail rows; cost-category lookups; inserted policy memo entries and resolved team mail IDs | [BR-033](business-rules.md#br-033-bill-audit-service-and-claim-payment-transaction-detail-lien-and-non-lien-amounts-must-reconcile-to-the-allowed-or-paid-amount) | [THRDPARTY_BILL_SERVICE](database-tables.md#thrdparty_bill_service), [TP_CLAIM_COST_CATEGORY_CODE](database-tables.md#tp_claim_cost_category_code) | [SQL-017](sql/sql-017-pk82033_thirdparty-billservice_insert.md), [SQL-071](sql/sql-071-pk82033_thirdparty-billservice_update.md), [SQL-040](sql/sql-040-pk82033_thirdparty-cost_category_select.md), [SQL-032](sql/sql-032-policy_pkg-get_team_mailid.md), [SQL-033](sql/sql-033-sp72155_insert_memo_entry.md) |
| [New claim intake and adjuster assignment](operations/new-claim-intake-and-adjuster-assignment.md) | Batch-process newly reported claims and open recovery cases, assign recovery adjusters, and generate initial follow-up tasks | `clsThirdPartyNewClaim.NewThirdPartyNewClaim(runDate).Save()`; `clsClaimActivityManager.NewClaimActivityManager(runDate).Save()` | Run date; new-claim list rows (claim ID, claim number, policy number, DOI, security flags); open-case list rows with task code/text/assignee | New `THRDPARTY_CASE` rows with assigned adjuster; new `THRDPARTY_TASK` rows; processed-record count; per-record error messages | [BR-034](business-rules.md#br-034-new-claim-adjuster-assignment-follows-a-policy-match-then-claim-number-range-then-conflict-override-precedence), [BR-005](business-rules.md#br-005-recovery-save-operations-require-one-affected-row) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_TASK](database-tables.md#thrdparty_task) | [SQL-041](sql/sql-041-pk82033_thirdparty-new_claim_list.md), [SQL-042](sql/sql-042-pk82033_thirdparty-open_case_list.md) |

> **Note:** [New claim intake and adjuster assignment](operations/new-claim-intake-and-adjuster-assignment.md) was not present in the prior flat-format documentation for this library; it was identified through direct source tracing of `clsThirdPartyNewClaim.vb`, `clsClaimActivityManager.vb`, and `clsAdjusterAssignment.vb`.

## Process flow diagram

The following diagram shows how the nine operations relate: a recovery case is created or retrieved (directly, or via batch new-claim intake with automatic adjuster assignment), participants and financial sub-records are maintained against it, and search/prediction and billed-cost/payment reconciliation support downstream reporting.

```mermaid
flowchart TD
	Start([Caller initiates recovery workflow]) --> Batch{Batch new-claim<br>intake run?}
	Batch -->|Yes| Intake[New claim intake and<br>adjuster assignment]
	Batch -->|No| CaseOp[Maintain recovery case]
	Intake --> CaseOp
	CaseOp --> Participants[Manage recovery participants]
	CaseOp --> Expenses[Manage expenses]
	CaseOp --> Liens[Manage liens and settlements]
	CaseOp --> Distributions[Manage distributions and refunds]
	CaseOp --> NotesTasks[Manage notes and tasks]
	CaseOp --> Search[Run case search and predictions]
	Search --> BilledCost[Retrieve billed-cost<br>and payment details]
	Liens --> BilledCost
	Participants --> Edit[Caller edits properties]
	Expenses --> Edit
	Liens --> Edit
	Distributions --> Edit
	NotesTasks --> Edit
	Search --> Edit
	Edit --> Validate{Validation rules pass?}
	Validate -->|No| Errors([Broken rules returned;<br>changes retained in memory])
	Validate -->|Yes| Save[Save via PK82033_THIRDPARTY<br>package-backed criteria]
	Save --> Concurrency{RowsAffected = 1?}
	Concurrency -->|Yes| Done([Changes persisted;<br>objects marked clean])
	Concurrency -->|No| Contention([DB contention error added;<br>save reported as failed])
	BilledCost --> ReadOnly([Reconciled or read-only<br>projection returned])
```

## Database interactions

The following table summarizes which operations read from or write to the database. Per-step SQL and table citations live in each operation's detail page under `operations/`.

| Operation | SQL | Tables | Type |
| --- | --- | --- | --- |
| [Maintain recovery case](operations/maintain-recovery-case.md) | [SQL-054](sql/sql-054-pk82033_thirdparty-thrdparty_expense_select.md), [SQL-058](sql/sql-058-pk82033_thirdparty-thrdparty_lien_select_by_seq.md) | [THRDPARTY_CASE](database-tables.md#thrdparty_case) | Read/Write |
| [Manage recovery participants](operations/manage-recovery-participants.md) | [SQL-025](sql/sql-025-pk82033_thirdparty-thrdparty_firm_insert.md), [SQL-080](sql/sql-080-pk82033_thirdparty-thrdparty_firm_update.md), [SQL-039](sql/sql-039-pk82033_thirdparty-companion_claim_select.md), [SQL-055](sql/sql-055-pk82033_thirdparty-thrdparty_firm_select.md) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_COMPANION_CLAIM](database-tables.md#thrdparty_companion_claim) | Read/Write |
| [Manage expenses](operations/manage-expenses.md) | [SQL-060](sql/sql-060-pk82033_thirdparty-thrdparty_select.md), [SQL-061](sql/sql-061-pk82033_thirdparty-thrdparty_select.md) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_EXPENSE](database-tables.md#thrdparty_expense) | Read/Write |
| [Manage liens and settlements](operations/manage-liens-and-settlements.md) | [SQL-056](sql/sql-056-pk82033_thirdparty-thrdparty_lien_cat_select.md), [SQL-058](sql/sql-058-pk82033_thirdparty-thrdparty_lien_select_by_seq.md), [SQL-065](sql/sql-065-pk82033_thirdparty-thrdparty_settl_dtl_select.md), [SQL-072](sql/sql-072-pk82033_thirdparty-claimcost_update.md) | [THRDPARTY_LIEN](database-tables.md#thrdparty_lien), [THRDPARTY_LIEN_CATEGORY](database-tables.md#thrdparty_lien_category), [THRDPARTY_CASE](database-tables.md#thrdparty_case) | Read/Write |
| [Manage distributions and refunds](operations/manage-distributions-and-refunds.md) | [SQL-030](sql/sql-030-pk82033_thirdparty-thrdparty_settlement_insert.md), [SQL-066](sql/sql-066-pk82033_thirdparty-thrdparty_settlement_select.md) | [THRDPARTY_CASE](database-tables.md#thrdparty_case) | Read/Write |
| [Manage notes and tasks](operations/manage-notes-and-tasks.md) | [SQL-028](sql/sql-028-pk82033_thirdparty-thrdparty_note_insert.md), [SQL-031](sql/sql-031-pk82033_thirdparty-thrdparty_task_insert.md), [SQL-059](sql/sql-059-pk82033_thirdparty-thrdparty_note_select.md), [SQL-045](sql/sql-045-pk82033_thirdparty-selecttasks.md), [SQL-046](sql/sql-046-pk82033_thirdparty-selecttasksbycase.md) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_TASK](database-tables.md#thrdparty_task) | Read/Write |
| [Run case search and predictions](operations/run-case-search-and-predictions.md) | [SQL-044](sql/sql-044-pk82033_thirdparty-prediction_select.md), [SQL-048](sql/sql-048-pk82033_thirdparty-thrdparty_case_search_select.md), [SQL-047](sql/sql-047-pk82033_thirdparty-statute_date_list.md), [SQL-067](sql/sql-067-pk82033_thirdparty-unit_stat_prediction_list.md), [SQL-036](sql/sql-036-pk82033_thirdparty-claim_condition_select.md) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_PREDICTION](database-tables.md#thrdparty_prediction), [THRDPARTY_PREDICTION_DETAIL](database-tables.md#thrdparty_prediction_detail) | Read/Write |
| [Retrieve billed-cost and payment details](operations/retrieve-billed-cost-and-payment-details.md) | [SQL-017](sql/sql-017-pk82033_thirdparty-billservice_insert.md), [SQL-071](sql/sql-071-pk82033_thirdparty-billservice_update.md), [SQL-040](sql/sql-040-pk82033_thirdparty-cost_category_select.md), [SQL-032](sql/sql-032-policy_pkg-get_team_mailid.md), [SQL-033](sql/sql-033-sp72155_insert_memo_entry.md) | [THRDPARTY_BILL_SERVICE](database-tables.md#thrdparty_bill_service), [TP_CLAIM_COST_CATEGORY_CODE](database-tables.md#tp_claim_cost_category_code) | Read/Write |
| [New claim intake and adjuster assignment](operations/new-claim-intake-and-adjuster-assignment.md) | [SQL-041](sql/sql-041-pk82033_thirdparty-new_claim_list.md), [SQL-042](sql/sql-042-pk82033_thirdparty-open_case_list.md) | [THRDPARTY_CASE](database-tables.md#thrdparty_case), [THRDPARTY_TASK](database-tables.md#thrdparty_task) | Read/Write |

## Stored procedure operations

Operations implemented in Oracle stored procedures referenced by this library.

| Operation | Description | Source | Link |
| --- | --- | --- | --- |
| PK82033_THIRDPARTY package operations | Package-backed insert, update, delete, and list operations (case, task, note, expense, companion claim, settlement, prediction, distribution, and related entities) used across all nine operations. | `PK82033_THIRDPARTY` | [Details](procedures/pk82033-thirdparty.md#operations) |
| Policy memo and mail routing | Direct, non-package-backed stored procedure calls used by the billed-cost and payment details operation to insert policy memo entries and resolve team mail IDs. | `sp72155_insert_memo_entry`, `policy_pkg.get_team_mailid` | [SQL-033](sql/sql-033-sp72155_insert_memo_entry.md), [SQL-032](sql/sql-032-policy_pkg-get_team_mailid.md) |

## Failure and edge-case behavior

- Optimistic/contention checking is the dominant failure mode: every persisting operation checks the affected row count and adds an insert/update/delete error instead of throwing ([BR-005](business-rules.md#br-005-recovery-save-operations-require-one-affected-row)). Detailed per-operation behavior is documented on each operation page.
- Several reconciliation rules (settlement totals, distribution check amounts, prediction dispersement, bill-audit/payment-detail lien splits) use exact equality checks rather than a rounding tolerance, so even one-cent discrepancies fail validation.
- Warning-severity rules (statute date month/day mismatch, task due date on a non-work day, expense approval thresholds, prediction pending-approval, companion-claim conflict) surface messages without necessarily blocking the save.
- The last-task-delete guard in [Manage notes and tasks](operations/manage-notes-and-tasks.md) requires a confirmed second delete attempt within the same object instance; a fresh retrieval resets that confirmation state.
- New-claim adjuster assignment falls back to the last-iterated range entry when no policy or claim-number-range match is found, rather than failing or assigning an explicit "unassigned" adjuster.
- Some source-registered rules are commented out or otherwise unregistered at runtime (a lien expense-amount rule, a claim-costs-amount rule on distribution, and an expense security-rule stub that always returns `True`); they are documented in the relevant operation pages as inactive rather than omitted.
- `clsPolicyNote`'s memo-insert and mail-ID lookup calls bypass the standard BOF save/business-rule pipeline, issuing their stored procedures directly with no `RulesAffected`/row-count protection of their own.

## Related documentation

- [Index](index.md)
- [Overview](overview.md)
- [Architecture](architecture.md)
- [Dependencies](dependencies.md)
- [Business rules](business-rules.md)
- [Database tables](database-tables.md)
- [SQL catalog](sql/index.md)
- [Procedures](procedures/index.md)
- [API reference](api/index.md)

> **Note:** Statements marked with `*` were inferred from code structure, naming
> conventions, or contextual evidence where direct confirmation was not available
> in source artifacts. Detailed inferred/unknown confidence markers are applied
> per-statement within each operation's detail page under `operations/`.

## Sources

- `Business\SAIF.Business.Claim.ThirdParty\clsThirdPartyCase.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdparty.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdPartyFirm.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdpartyCompanionClaim.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdpartyExpense.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdpartyExpenseApproval.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdpartyLien.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdpartySettlement.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdpartySettlementDetail.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThirdpartyDistribution.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThirdpartyNote.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThirdpartyTask.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdpartyCaseSearchCollection.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThrdpartyPrediction.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsBillAuditService.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsClaimPaymentTransDetail.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsPolicyNote.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsThirdPartyNewClaim.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsClaimActivityManager.vb`
- `Business\SAIF.Business.Claim.ThirdParty\clsAdjusterAssignment.vb`