Final Review — approving a document into PPU

Into the PPU review screen

Opening a document splits the screen: the AI recommendation on one side, what is already in the system on the other. The panes scroll together, so when you move to the charge tables you are comparing the same section of both records rather than hunting for the corresponding row.

The gap

The invoice totals $2,445.60. The TMS holds $2,350.41. A $95.19 difference — the kind of number that gets approved without thought on a busy afternoon, and shouldn't be.

Where the $95.19 actually is

The charge tables answer it precisely. The AI extracted four lines: 1,462.72 freight + 841.06 fuel + 46.63 lumper + 95.19 detention = 2,445.60. The TMS holds two: 2,303.78 freight + 46.63 lumper = 2,350.41. And 2,303.78 is exactly 1,462.72 + 841.06 — the TMS has rolled freight and fuel into a single line. So three of the four charges reconcile perfectly, and the entire discrepancy is one line: a $95.19 detention charge that never made it into the TMS.

• Freight + fuel — Split on the invoice, combined in the TMS — same money.
• Lumper — $46.63 on both sides. Matches.
• Detention — $95.19 on the invoice, absent from the TMS. The whole gap.

Why that distinction changes the decision

"The invoice is $95 higher" is a dispute. "The invoice includes a detention charge the TMS never recorded" is a question with an answer — was there detention on this load? If yes, approve and let the accessorial flow through. If no, you have a specific line to challenge rather than a vague overcharge. The side-by-side turns an argument into a lookup.

Approve & Submit

Approving steps the queue from 127 to 126 and submits the document onward to PPU. The record of what you compared travels with it, so the next person to open it — or an auditor a year later — sees the same reconciliation you did.