How does the Driver Trips page work?
Trips is where every paid block is tied to the trip that earned it and the driver who ran it — matched by reference key, even when Amazon pays a week late. It’s your weekly checkpoint: clear the few blocks that need a decision and every pay stub and P&L downstream stays exact.
Most blocks land matched on their own. The rest carry a status that tells you what to do — and the KPI chips at the top of the page let you filter to just those, one at a time, so you can work them down to zero.
| Reference | Driver | Amount | Status |
|---|---|---|---|
| B-DEMO-0004 | Daniel Garcia | 2,769.47 | matched |
| B-DEMO-0002 | Emily Rodriguez | 2,410.40 | dup driver |
| T-DEMO-0177 | James Wilson | 0.00 | unpaid |
| B-DEMO-0031 | — | 1,905.11 | canceled |
A Dup driver flag means a paid block could belong to more than one driver who ran that truck or route that week. RppApp never guesses who to pay — it flags the block and asks you to confirm.
- Find the block marked dup driver.
- Open the Assign driver dropdown on that row — it lists only the drivers that plausibly match.
- Pick the correct driver. It saves instantly and the block turns manual.
- The amount now flows into that driver’s pay stub for the week, and your P&L stays exact.
| Reference | Driver | Amount | Status | Assign driver |
|---|---|---|---|---|
| B-DEMO-0002 | Emily Rodriguez | 2,410.40 | dup driver | — confirm / select — |
| B-DEMO-0003 | Jessica Brown | 2,362.85 | matched | — |
| B-DEMO-0004 | Daniel Garcia | 2,769.47 | matched | — |
The trip ran but no payment has matched it yet — usually Amazon pays it a week later. RppApp keeps it visible so it’s never lost, and matches it automatically when that week’s payment file arrives.
| Reference | Driver | Amount | Status |
|---|---|---|---|
| T-DEMO-0177 | James Wilson | 0.00 | unpaid |
| B-DEMO-0009 | Daniel Garcia | 2,745.78 | matched |