Loading your workspace
Please wait while we prepare the page.
This page focuses only on the network story: how companies connect, how work is transferred, and how sender and receiver both stay aligned after the booking moves.
Network Journey
Create a deliberate associate relationship first so future exchanges are structured.
Transfer the booking request with enough trip context for the partner to act on it.
The receiving company accepts or rejects, making the next step operationally clear.
Allotment, trip progress, and invoice-side movement stay attached to the same network request.
The relationship starts with accepted associations, not a hidden vendor side process.
A booking is sent as a clear request with status movement that both companies can follow.
The transferred work remains visible through acceptance, allotment, and downstream updates.
Most systems stop at the transfer. A stronger network system keeps supplier-side execution and commercial follow-up visible too.
Sender companies should be able to see whether the partner has moved into allotment and trip execution instead of chasing for updates manually.
Network requests become more useful when purchase-side invoice movement and settlement context remain linked to the same workflow.
A SaaS-friendly associate model keeps company boundaries, request history, and execution records clear as your partner network grows.