Problem (current behavior) On the Driver Pay Settlement PDF, extra pickup and extra drop fees are auto-calculated and placed in the "Other Pay" section at the bottom of the report. They're only identified by load number and an internal ticket reference — e.g. "138571 | TR-000076-01 | Auto calculated: Extra Stop". This detaches the extra-stop charge from the load it actually belongs to. To understand which stop generated the fee and where it happened, the driver has to manually cross-reference the load number in the Earnings table at the top with the line buried in Other Pay at the bottom. Why it matters Arctic is migrating from ITS Dispatch, whose pay report shows the pick/drop fee directly inside the load's information block, right alongside the stop's city and date (e.g. each delivery listed as its own row, with the "Pick / Drop Fee" line sitting within that same load). Drivers are accustomed to seeing the full picture of a load — its stops, miles, and the fees tied to those stops — in one place. Splitting extra-stop fees out to the bottom makes the settlement harder to read and tends to generate avoidable pay questions from drivers. Proposed solution In the Earnings section, when a load has extra pickups or drops, render those stops as their own line(s) within that load's row — showing the stop city and date together with the associated fee — the same way loaded/empty miles already appear under a load. Keep each load's stops and their related fees grouped with the load rather than aggregating extra-stop fees separately in Other Pay. Example (desired) Within Load 138571's block: Extra Stop — Vineland, NJ — 6/7/2026 — $50.00 (mirroring how ITS Dispatch lists the "Pick / Drop Fee" inside the load block alongside its delivery cities/dates) Scope note This is a display/layout change to the settlement PDF only — fee calculation and amounts stay the same; this just moves where the line is rendered so it appears in context with its load. Example attachment is attached
