# Worksheet instructions

These files contain a blank template and synthetic worked example. They are planning records, not a payment import specification. Import IDs as text and preserve leading zeros. Amounts are USD. Keep bank details, tax identifiers, patient data, customer addresses, and confidential source content out of these files. Store evidence in an access-controlled system and use references here.

The example uses invented rates and agreements. Replace them with your approved terms, due dates, authority rules, and legal requirements. No formulas or external links execute in these CSVs. Calculate values in your controlled working copy and validate totals before relying on them.

## Event settlement

One row is one authorized compensation or expense component. Every row in the example belongs to provider ET-006 and payer ENTITY-A. Venue IDs are operational references, not separate legal payers. Assignment A is completed; Assignment B is canceled with an agreed amount due.

Approved obligations total $724: $450 + $100 + $24 + $150. Event EV-101 totals $574; EV-102 totals $150. There are no prior payments, fees, withholding, or offsets, so remaining due also totals $724. All amounts are approved and unpaid in this snapshot.

For the optional deposit scenario described in the article, allocate a verified $200 deposit to the performance-fee line's prior_paid_allocated_usd field. That line's remaining due becomes $250. EV-101's remaining balance becomes $374 and the total remaining due becomes $524. Preserve the deposit's actual payment reference in a supporting payment-allocation record. Never allocate the same prior payment more than once.

An advance reduces the remaining payment balance; it does not reduce total agreed compensation. Cancellation amounts are specific to the illustrative agreement, not general legal rules. Keep the original and replacement assignment linked if an event is rescheduled, and document whether any deposit transfers.