Loads and rate cons

A load is here for two reasons: it decides what a driver is paid, and it decides what a customer is billed. Those are separate lifecycles, and the screen keeps them separate.

Getting them in

• Upload the rate con. The PDF is read into a load, including a multi-stop itinerary where the rate con has one.
• Type it. Add a load by hand when there is no paperwork to upload.
• Import a spreadsheet. Bulk import with a template. The whole batch can be undone afterwards.

A load whose reference number already exists gets flagged before it is added, because the same rate con entered twice is the most common way a driver gets overpaid.

Two paid flags, because they are two different questions

Billing

Set by hand, but only on a load with no invoice. Factored carriers get paid without ever raising an invoice here, so without that their loads would sit at “delivered” forever and the screen could not answer who still owes you.

Where an invoice does exist, the invoice owns the status. Marking a load paid underneath a live invoice is how AR quietly starts disagreeing with reality. Unmarking recomputes the real state (invoiced, delivered, or booked) rather than restoring a remembered one.

Driver pay

Read-only, derived from the settlement holding the load:

“On a draft” is called out separately on purpose. A draft is a proposal, and one badge for both would be claiming money had moved when it has not. To change it, settle the load or reopen the settlement holding it.