> ## Documentation Index
> Fetch the complete documentation index at: https://www.presolve.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Report on resolution payments

> Create a shared payment-history report, including Washington workers’ compensation and Litify preparation.

Use native **Reporting** to view resolutions with their individual inbound payments. You need permission to view accounting and settlements within the selected scope.

## Create the report in the owning firm

1. Select the child firm that should own the report, such as your Washington office.
2. Open **Tools → Reporting → New Report**.
3. Choose **Resolution Payment History**, or **Washington WC Historical Payments** for the Washington workers' compensation template.
4. Name the report clearly. Inspect the data source and filters before running it; the Washington template restricts state and case type.
5. Add the columns below, choose the intended office scope, and select **Run Report**.
6. Verify representative rows against their source resolution/check, then **Save**.
7. Use the report's sharing controls to make it available to the intended team. Have an authorized HQ user open the shared child-owned report and verify the same configuration. Sharing does not grant underlying financial-data permissions.

If a report with the intended name already exists in Saved reports, open and verify it before creating another copy.

## Columns for payment history

| Columns | Use |
| - | - |
| Client name, Office, Case ID, External case ID | Identify the person, owning office, and destination-system match. |
| Resolution ID, Resolution number, Resolution type, Resolution status | Identify the arrangement. |
| Payment ID, Check sequence ID, Check number | Distinguish the stored payment from a printed check reference. |
| Payment amount, Deposit date, Date received | Record the actual receipt and its recorded dates. |
| Payment period start, Payment period stop | Describe the period covered by this individual payment. |
| Recurring start date, Recurring stop date, Cadence | Describe the recurring resolution's schedule. |
| Fee type (allocation category), Fee type source | Show the payment category, or distinct split-allocation categories when the payment category is absent. |
| Data notes | Identify missing deposit dates, missing allocation categories, or no linked payment. |

## Understand the rows before exporting

There is **one row per linked inbound payment**. A resolution without a linked payment retains one row with blank payment fields. Three payments for one resolution therefore produce three rows; an unpaid resolution produces one blank-payment row.

Allocation splits do not multiply the payment amount. Several categories may appear in one Fee type cell. **Fee type means allocation category**, not resolution type or attorney fee percentage.

A blank deposit date is missing source data, not zero, today's date, or the received date. Payment period dates and recurring schedule dates have different meanings; do not substitute one for the other. Use Data notes to find records needing correction.

## Prepare a Litify handoff

1. Confirm with the recipient which identifiers match their cases and payments.
2. Review office, state, and case-type filters. Keep IDs and Data notes in a review copy.
3. Compare a paid resolution, a recurring resolution with multiple receipts, and an unpaid resolution to the source records.
4. Check displayed currency amounts and date formats in the downloaded CSV.
5. Export using Reporting's [delivery controls](https://www.presolve.com/docs/help/reporting/delivery.md). Map the columns to the receiving import template before uploading; this report is not a claim of a validated Litify import format.
6. Retain the exported file and its filter/date context so later changes can be explained.

Report row counts are not resolution counts. Do not count the blank-payment row as a receipt or sum repeated resolution-level values as if each row were a different resolution.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.