Separate AR from AP Approvals

Not sure the best way to solve this.

Use Case 1: Currently with multi-vendor loads if I approve the first carrier, let's call that a TONU, all of the AR data is sent back to the TMS as if we are ready to invoice that customer. When I approve the second carrier that actually hauled the load the same AR data is sent back to the TMS again. We don't have a way to create Orders and relate more data to each carrier like IDs, AR charges, etc. and the data we send back is formatted the same way. These almost need to be treated as completely separate but related data sets.

Use Case 2: We have a request to be able to Pre-Bill (send docs back to TMS to invoice customer before carrier invoice is received)

Use Case 3: We have a request to be able to force the AR approval and hold AP approval. I have a deadline to invoice my customer but I'm still disputing something with the carrier so I want to ad hoc push the docs back to the TMS and invoice my customer (not the exact Pre-Bill use case)

Use Case 4: I've already paid AP and invoiced my customer. I get a supplemental bill from the carrier, great example is Dray per diem charges and chassis rental fees coming in. When I receive that I want to audit and approve the AP side but I also want to add to the AR side and either send a corrected Invoice or supplemental invoice to my customer. Today we can attach the supplemental to the order and approve that but the AR sent is the original AR from the Order.

These are all very similar but slightly different scenarios. Can we solve them all with one set of features? Do we need to think about solving these separately? I don't have the answers but enough of these scenarios are coming up with prospects and I KNOW current customers are also running into these scenarios in regular day to day. All scenarios affect DSO and important audit metrics plus I want to capture the data and analytics within Navix so I do think it would be beneficial to solve them within the platform.