# 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.

## Statement reconciliation

One row is one statement component, not necessarily one route. ST-101 contains five components totaling $261: $120 + $16 + $95 + $12 + $18. RT-301 has 10 completed stops in the example, eight included in the base and two eligible for the $8 addition. The extra-stop calculation is 2 × $8, not 10 × $8.

The service dates cover current work and one older correction. The original-statement and original-route fields link the $18 correction to ST-100 and RT-288. Do not rewrite the paid amount on ST-100. Every line is approved but not yet paid in this example. No fees, withholding, or offsets apply. Thus $261 is both the approved total and authorized amount, but not evidence of bank receipt.

Add actual payment references and provider status meanings in your production statement design. If one statement spans several transfers, maintain a separate statement-to-payment mapping. If any authorized component changes the transfer amount, show it explicitly rather than relabeling the approved total as deposited funds.

Retain stop acceptance and receipt records in controlled systems. Check uniqueness of each earning component before creating payables. Treat profile or payment-destination changes through the identity verification process so the authorized recipient stays connected to the onboarded contractor.