So in the carrier portal, the carrier user can add an unmatched invoice, but it still appears in the form of a load with a pickup and drop location.
This could still be re-tooled to be an invoice for a non-load event.
Alternatively, we could create “loads” with a shipment type (yard jockey, overhead, etc) that the carrier could transmit via EDI 210 as a … service load. ITSO and ITSB are already sending 210’s for yard jockey services, we just need to build and define these special cases.
Kayvan Shadpour
