Forward a job to iDrv4

iDrv4 (Ceres TMS) is the transport-management system that handles dispatch and proof-of-delivery. Forwarding a job from JATT Portals into iDrv4 hands the booking to ops for execution.

When to forward

Forward a job to iDrv4 once:

• The customer and addresses are confirmed.
• The pickup date and cargo are accurate.
• The pricing is locked in.

After it’s forwarded, the iDrv4 booking is owned by Ceres. Edits to the JATT-side connote no longer flow downstream.

How to forward

1. Open /operations/jobs.
2. Click the row of the job you want to forward.
3. In the drawer header, click Send to iDrv4 (paper-plane icon).
4. Confirm the prompt.

The button shows a spinner while the request is in flight (typically 1-3 seconds). On success:

• A Forwarded to iDrv4 (CN…) toast shows the iDrv4 control number.
• The drawer reloads. The Send to iDrv4 button is replaced by a green Forwarded to iDrv4 (CN…) badge.
• The Jobs list refreshes.

What is sent

As well as the customer, addresses, dates and cargo, the forward carries:

• Every stop at its own time — on a multi-drop job, each pickup and delivery keeps the date and time entered for it.
• A TBA delivery — sent with no location, which iDrv4 records as a delivery to be filled in later.
• Handling options — tailgate, hand unload or Residential, so iDrv4 dispatches a house as a house. iDrv4 takes one of these per stop, so if several are ticked it receives tailgate first, then hand unload, then residential.
• Fuel levy — the percentage, whichever fuel levy add-on was applied.
• Dangerous goods — the DG class and type. iDrv4 holds one class per consignment and has no field for a subsidiary risk; anything that cannot be sent is named at the moment you forward (“Not sent to iDrv4: …”). See Dangerous goods.
• What the booking was charged on — for example the number of chargeable pallets.

Forward documents

Booking documents attached after the job was forwarded are not included in the original send. Once forwarded, the drawer shows Forward documents: it sends anything added since, and skips documents already sent, so it is safe to press again.

Idempotency

Once a job is tagged with an iDrv4 control number, the Send to iDrv4 button disappears and the green badge stays in its place. Clicking the badge does nothing — it’s purely informational. This prevents accidental double-forwards.

If iDrv4 ever needs a re-send (their record was purged, the consignment ref needs to change, etc.), contact your administrator. Clearing the tag is a database operation, not a user action.

When iDrv4 rejects it

A rejection names the field in plain words first — Pickup or Delivery, then the field (for example Delivery postcode, Pickup date/time window) — followed by iDrv4’s own message. If there are more problems than the toast shows, it ends with (+N more): fix all of them before retrying.

Common cases:

• iDrv4 integration not configured — environment isn’t set up to talk to Ceres. Contact your administrator.
• Missing email (or other customer field) — the customer record on the JATT side is missing data that Ceres requires for the auto-create flow. Edit the customer to add it, then retry.
• Customer match is ambiguous — the customer matches two records on the Ceres side via different fields (e.g., ABN matches one, email matches another). Correct the customer’s ABN or ACN — both are editable on the customer — then retry.
• Pickup state — the state on the connote isn’t a clean Australian abbreviation (NSW, VIC, QLD, etc.). Edit the job to clean it up, then retry.
• “Delivery address is invalid.” — iDrv4 could not find the address line on a map. Open the booking and re-pick the address from the autocomplete; retyping the same text does not repair it.
• Network error contacting iDrv4 — transient connectivity. Wait a few seconds and retry.

Out of scope

• Inbound status updates from iDrv4 are not currently flowing back into JATT Portals. Status changes on the iDrv4 side need to be monitored there.
• Re-syncing a job after it’s been edited is not yet supported. Edit JATT-side fields with the understanding that iDrv4’s record will not reflect them.