Administration
Approvals
One queue for every decision that needs a person, new customers, new carriers, credit limits, early carrier payments and portal submissions, each decided with a written comment.
Approvals gathers every decision the business has to make by hand into one queue. Nothing is approved automatically. Each decision needs a written comment, which is kept with the outcome, shown to the person who asked, and written to the audit log.
- Where
- Administration → Approvals (/approvals)
- Who can open it
- Approvals · view. By default: Owner, General Manager, Finance Manager, Compliance Manager, Compliance Team
- Who can decide
- The approve action on the item's own module (see the table below)
- Comment
- Required on every decision, 3 to 1,000 characters
- Saves to
- The item itself (customer, carrier, request or submission), notifications and the audit log
What waits here
| Kind | Comes from | Decided with | Default deciders | Urgency |
|---|---|---|---|---|
| Carrier | A new carrier in pending_compliance | Carriers · approve | Owner, General Manager, Compliance Manager | Red when more than two compliance items are missing, else amber |
| Customer | A new customer waiting on a credit decision | Customers · approve | Owner, General Manager | Amber |
| Credit limit | A request to change a customer's limit, from Credit limits | Approvals · approve | Owner, General Manager, Finance Manager, Compliance Manager | Red: loads for that account are blocked until it is decided |
| Early payment | A carrier asking to be paid early, from Payables | Payables · approve | Owner, General Manager, Finance Manager | Amber |
| Portal submission | Something a customer or carrier sent through a portal | Approvals · approve | As for credit limits | Blue (information) |
Each item names who decides it, so nobody sits on someone else's queue. If your role cannot decide an item, its Decide button explains why when you hover or focus it.
What you see
Figures
| Figure | Meaning |
|---|---|
| Waiting | Items in the queue |
| Urgent | Red items, shown in red when there are any |
| Decided | Items in the history below |
| Outcomes | A bar split into Approved, Rejected and Applied |
Waiting
Most urgent first. Each card shows the kind, the title (for example the carrier's name), what is missing or at stake, the amount where there is one, who asked and when, and two buttons: Open (the record itself) and Decide. With nothing in the queue: "Nothing waiting".
Decided
The twelve most recent decisions, newest first.
| Column | Meaning |
|---|---|
| Item | What was decided, with its kind |
| Decision | Approved, Rejected or Applied (a portal submission that was put into effect) |
| Reason | The decider's comment |
| Decided by | Who, and when |
An Audit log link opens the full history.
Decide an item
Click Decide
A window opens titled "Decide: …" with the detail and what is at stake.Set a credit limit (customers only)
For a new customer, enter the Credit limit the account is approved with. It is needed to approve.Write the comment
Say why. It is kept with the decision and shown to the requester.Approve or Reject
The item leaves the queue and appears under Decided.
If someone else decided the item a moment before you, you see "Somebody has already decided this. Refresh to see the outcome."
What each decision does
Carrier
On approve, the server checks R1 and then your company's own vetting requirements (set on Company profile). If anything is missing it refuses with "Cannot approve yet: …" and lists what to put on file. Approved carriers can be dispatched; rejected ones cannot. The reviewer's name and comment are stored on the carrier. See Carrier compliance.
Customer
Approving sets the customer to approved with the credit limit you entered. The server refuses an approval with no limit: "Give the account a credit limit to approve it — every load is measured against it." Rejecting blocks every load for that account.
Credit limit request
Approving writes the requested limit onto the customer. Rejecting leaves the limit as it was. See R2.
Early payment
Approving or rejecting records the decision and who made it. It does not pay anything by itself; finance pays on Payables.
Portal submission
When you approve a portal submission, it is applied there and then:
| Submission | What approving does |
|---|---|
| POD upload | Attaches the POD to the load and clears "POD requested" |
| Invoice (carrier) | Records the carrier's invoice number and date on the load |
| Appointment | Marks the appointment acknowledged by the carrier |
| Delivery order | Marks the delivery order signed |
| Rate query | Your comment is the answer; a changed rate is reissued on the load itself |
| Tracking update | Adds a manual tracking ping with the place and miles remaining |
The load must still be the one named on the submission and still assigned to the carrier (or customer) who sent it. If not, the server refuses: "LD-… is no longer assigned to …". Each applied submission writes a line to the load's feed.
Who is told
- The person who asked is notified of the outcome, unless they decided it themselves.
- Every decision writes an audit entry with the before and after values and your comment.