See the handoff before you connect.

What the sample shows

The download contains two invented reviewed entries for ExampleClient and ExampleMatter identifiers. Its column names match the inspected release’s export contract. Dates, identifiers, narratives, hours, confidence values, and review status are illustrative. Rates and amounts are zero so the example does not imply a fee or product result.

This file demonstrates a format. It is not a customer export, a performance result, or a guarantee that a particular billing system will import it. Do not import fictional rows into a live billing ledger.

Export columns

The exact header, in order:

Date,Client ID,Matter ID,Timekeeper ID,Hours,Rate,Amount,Narrative,Task Code,Activity Code,Source Type,Confidence,Status

Columns	Check before use
Date	Confirm the work date and the receiving system’s expected format.
Client ID, Matter ID, Timekeeper ID	Map entry identifiers to the receiving system’s actual records. Exported IDs do not establish that mapping automatically.
Hours, Rate, Amount	Verify approved time, agreed rates, rounding, and totals. A proposed duration is not a contemporaneous timer measurement.
Narrative	Confirm accuracy, sufficient detail, and the firm’s confidentiality and billing requirements.
Task Code, Activity Code	Supply valid required codes for the receiving workflow. The sample leaves these blank; that may be unsuitable for your system.
Source Type, Confidence, Status	Keep these as review context or map them explicitly. A confidence value does not replace attorney review.

Review first, reconcile next

1. Check the source and confirm the client, matter, duration, narrative, and any required codes. Correct or reject unsuitable proposals.
2. Select the intended date range. The prepared desktop export requests entries with reviewed status for the inclusive range.
3. Compare against time already entered in the receiving system. Check duplicate and overlapping work before import.
4. Confirm the agreed mapping with a synthetic sample or the receiving system’s preview, then reconcile entry counts and total hours.
5. Keep a record of the range and file used. Re-exporting does not establish that the receiving system will avoid duplicates.

If the selected range contains no reviewed entries, the release returns no CSV for that range. Review the entries and date selection before trying again. The pilot does not publish directly into a billing system, create an invoice, or generate a LEDES file.

Client and matter roster example

The prepared roster importer uses UTF-8 CSV with exactly these four headers. Column order may vary; extra columns and blank cells are rejected. Start with a synthetic dry run arranged during guided setup.

client_number,client_name,matter_number,matter_name

Download the fictional two-matter roster. Roster numbers and exported entry IDs have different purposes; confirm their relationship in the agreed import mapping.

Agree on the receiving workflow

Tell us your billing system and version, the columns its importer expects, and whether it offers a preview or test environment. We will confirm one CSV workflow as part of the pilot scope. Keep client records out of the initial website inquiry; a blank template or synthetic example is enough to begin.

For a later LEDES requirement, complete that step in the appropriate billing workflow after validating the entry mapping. See the LEDES conversion guide.