At a glance
- A new Receivables page under Billing adds up what every client owes, with how much is past due
- Collections lists the clients to chase today, and Aging splits each client's balance by how late it is
- Split, merge and unmerge dialogs show the handoff, what is removed and where orders go before you confirm
- Fuel cost items and the payment term on a carrier bill can be changed after they are created
- Exported invoices carry the order ID and reference in the memo field
New features 1
Receivables: see what every client owes, and who to chase today
A new Receivables page under Billing adds up everything your clients owe: orders not billed yet, invoices they owe you directly and invoices with your factoring company, with how much of it is past due. Collections lists the clients to chase today, Aging splits each client's balance by how late it is, and every number opens the orders behind it.
Improvements 20
An AR aging screen shows what customers owe you by age bucket
- Why we changed it
- There was no place in the product to see outstanding receivables grouped by how long they had been open.
- How it helps
- Billing staff can chase the oldest balances first without exporting invoices to a spreadsheet.
- How to use it
- Open the receivables aging screen under accounting.
Fuel cost items can be edited and deleted after they are added
- Why we changed it
- A fuel cost item was write-once, so a wrong amount or a duplicate stayed on the profit calculation.
- How it helps
- Profit figures can be corrected in place instead of being worked around.
- How to use it
- Open the cost items on an order and edit or remove the fuel line.
Recurring presets can download the account statement or email it to the payee
- Why we changed it
- Account statements from a recurring preset had to be produced and sent by hand.
- How it helps
- Statements reach the payee on schedule without anyone assembling and sending them.
- How to use it
- Open a recurring preset and choose to download or email the statement.
Recurring presets now have a transaction ledger, reachable from the settlement line they created
- Why we changed it
- There was no way to see what a recurring preset had actually posted, or to get from a settlement line back to the preset behind it.
- How it helps
- Accounting staff can audit what a recurring charge or deduction has produced over time without reconstructing it from settlements.
- How to use it
- Open a recurring preset to see its ledger, or follow the link from a settlement line.
Settlement detail now shows gallons purchased under Fuel and total miles under Tolls
- Why we changed it
- Fuel and toll lines on a settlement showed only money, so the numbers behind them had to be looked up elsewhere.
- How it helps
- Payroll and settlement staff can check the volume and mileage behind each deduction without leaving the settlement.
- How to use it
- Open a settlement and look at the Fuel and Tolls sections.
You can change the payment term on a carrier bill that has already been created
- Why we changed it
- The payment term was fixed at creation, so a wrong term meant voiding the bill and entering it again.
- How it helps
- Billing staff correct a term in place and the due date follows.
- How to use it
- Open the carrier bill and edit the payment term field.
A handoff whose freight is still on the dock now says so on the manifest
- Why we changed it
- Nothing on the manifest distinguished a handoff that had actually moved from one whose freight had not left the dock.
- How it helps
- Dispatchers see at a glance which handoffs still need the freight picked up.
- How to use it
- Open the manifest; the state shows on the handoff.
An order merged into a manifest records which manifest it came from
- Why we changed it
- After a merge there was no trace of the order's original manifest, which made unmerging and auditing guesswork.
- How it helps
- Dispatchers can see the origin of every merged order and put it back where it belongs.
- How to use it
- Open a merged manifest and check the order's origin.
Manifest lineage shows a handoff card, a status pill on the bar and a boxed timeline
- Why we changed it
- The lineage view ran the handoff details together with the rest of the page, so the chain was hard to follow.
- How it helps
- Dispatchers can see where a manifest was handed off and read the chain as a timeline.
- How to use it
- Open a manifest and go to its lineage.
Split on a manifest says it is disabled until the handoff has an address
- Why we changed it
- The Split action was greyed out with no reason given, so dispatchers did not know what to fix.
- How it helps
- Dispatchers see the missing handoff address is what blocks the split and can add it and carry on.
- How to use it
- Hover the disabled Split action on a manifest handoff.
The chain map responds to selection and stays where you put it
- Why we changed it
- The lineage map re-centred and re-zoomed on its own and did not react when a record was selected.
- How it helps
- You can follow a chain of related records without the view jumping away from what you were reading.
- How to use it
- Open the lineage view on a record and click through the chain.
The manifest split dialog shows the handoff it will create before you confirm
- Why we changed it
- Splitting a manifest created a handoff without showing what it would look like, so dispatchers had to split first and check after.
- How it helps
- You can see the resulting handoff while still in the dialog and back out if it is not what you wanted.
- How to use it
- Open a manifest and start a split; the handoff preview is in the dialog.
The merge dialog states what the merge will remove and colours the map to match
- Why we changed it
- Merging left it unclear which record would disappear, and the preview map was hard to read against the rest of the screen.
- How it helps
- Dispatchers can confirm the outcome of a merge before committing it instead of finding out afterwards.
- How to use it
- Start a merge and read the summary above the map.
The merge-into step is a radio list you can operate from the keyboard
- Why we changed it
- Choosing the record to merge into required a mouse and gave no clear selected state.
- How it helps
- The target of a merge is easier to see and can be picked with arrow keys and the space bar.
- How to use it
- Open the merge dialog and tab to the merge-into list.
The order shows its most recent check call
- Why we changed it
- The latest check call was recorded but not surfaced on the order, so dispatchers had to open the check call history to see it.
- How it helps
- The current status of a load is visible where dispatchers already work.
- How to use it
- Open an order; the newest check call shows on it.
The unmerge dialog says which manifest each order will go back to
- Why we changed it
- Unmerging gave no indication of where the orders would land, so you had to unmerge and then check.
- How it helps
- You can confirm the outcome before unmerging instead of correcting it after.
- How to use it
- Open a merged manifest and start an unmerge.
You can find a manifest chain's root from the list and jump to its lineage
- Why we changed it
- From the manifest list there was no way to get to the start of a chain without opening manifests one by one.
- How it helps
- Dispatchers reach the root of a chain and its full lineage in one step.
- How to use it
- Use the lineage action on a manifest row in the list.
You can pick the split point directly on the map, and the map keeps its own view
- Why we changed it
- The split point could only be chosen from the form, and the map reset its framing while you worked.
- How it helps
- Splitting at the right stop is faster and you can see exactly where the break falls.
- How to use it
- Open the split dialog and click the point on the map.
Document type names are no longer preceded by a cloud icon
- Why we changed it
- An icon sat beside every document type name and carried no meaning.
- How it helps
- Document lists read more cleanly and names line up.
- How to use it
- Nothing to switch on; visible wherever document types are listed.
Fixes 18
Exported invoices carry the order ID and reference in the memo field
- Why we changed it
- Invoices sent to the accounting system arrived without the order ID or reference, so they had to be matched by hand.
- How it helps
- Bookkeepers can tie each exported invoice back to its order straight from the memo.
- How to use it
- Export invoices as usual and check the memo line in the accounting system.
The AR aging screen is easier to read
- Why we changed it
- Columns and figures on the receivables aging screen were cramped and hard to scan.
- How it helps
- Billing staff can read aging buckets and balances at a glance.
- How to use it
- Open the AR aging screen.
A detention you have just decided stays in place on the board until you leave or reload
- Why we changed it
- Deciding a detention removed the row immediately, so there was no chance to confirm the decision or undo a misclick.
- How it helps
- You can see what you just approved or denied before the list rearranges itself.
- How to use it
- Nothing to switch on.
An unconfirmed delivery submission no longer drops the stop out of its phase on the progress view
- Why we changed it
- When a submission went unconfirmed the delivery progress lost the phase it belonged to, so the stop looked out of sequence.
- How it helps
- Progress stays readable while a submission waits on confirmation.
- How to use it
- Nothing to switch on.
Note visibility permissions are now enforced when notes are read through order invoice and pay screens
- Why we changed it
- Order invoice and pay reads returned notes without checking the note-visibility permissions those notes were filed under.
- How it helps
- Restricted notes stay restricted no matter which screen they are reached from.
- How to use it
- Nothing to switch on; existing note visibility settings apply.
Several display problems in the tender flow and driver pay entry are corrected
- Why we changed it
- Four interface issues in tendering and driver pay showed wrong or misplaced values while working through a tender.
- How it helps
- Tendering an order and entering driver pay read correctly without double-checking against another screen.
- How to use it
- Nothing to switch on.
The manifest details dialog holds steady when you switch manifests, and the lineage page opens the edit dialog directly
- Why we changed it
- Switching manifests made the details dialog jump and reload, and the lineage page had no way into editing.
- How it helps
- Dispatchers move between manifests without losing their place and can edit straight from the lineage view.
- How to use it
- Open a manifest and switch between them, or open a lineage page and use the edit action.
The manifest lineage handoff shows the stored handoff details instead of values worked out in the browser
- Why we changed it
- The handoff card guessed its details from what the page had loaded, so it could disagree with the record.
- How it helps
- Dispatchers see the same handoff facts the rest of the system uses.
- How to use it
- Open a manifest's lineage.
The rate shows on the order page again
- Why we changed it
- On some orders the rate was missing from the order page even though it was set.
- How it helps
- Dispatchers and billing staff read the rate where they expect it instead of opening the rate record.
- How to use it
- Nothing to switch on.
The status filter on the detention board matches records again
- Why we changed it
- Status values stored as text were not read by the column filter, so filtering by status returned nothing.
- How it helps
- You can narrow the detention board by status and get the rows you expect.
- How to use it
- Use the status column filter on the detention board.
A document keeps its own field values where the catalog does not define them
- Why we changed it
- Fields that belonged to an individual document were overwritten or dropped when the document type catalog had no matching entry.
- How it helps
- Data entered on a document stays on it instead of disappearing on save.
- How to use it
- Nothing to switch on.
A failed autosave no longer blocks submitting the form you are working in
- Why we changed it
- A background autosave that failed harmlessly caused the submit to be rejected.
- How it helps
- Work can be submitted without retyping or reloading when autosave hiccups.
- How to use it
- Nothing to switch on.
Columns can be dragged into a new order in table settings again
- Why we changed it
- Drag to reorder columns in table settings did nothing, so column order could not be changed.
- How it helps
- Each user can arrange table columns in the order they work in.
- How to use it
- Open table settings on any list and drag a column into place.
The document editor reports a page operation that fails instead of appearing to succeed
- Why we changed it
- A failed page operation was swallowed, so the editor looked like it had applied a change it had not.
- How it helps
- You find out right away when a rotate, delete or reorder did not go through.
- How to use it
- Nothing to switch on.
The document viewer no longer reloads a page it has already downloaded
- Why we changed it
- Scrolling back to a page refetched the image every time, which made viewing slow on large documents.
- How it helps
- Paging through scans and PDFs is faster and uses less data.
- How to use it
- Nothing to switch on; open any document.
