How this demo works
Driver Payroll Desk turns the XML reports your TMS already exports into a weekly payroll you can trust. It keeps a permanent history of every load, deduction, and payment, so money that was already paid never gets paid again.
The flow
Reconciliation rules
- Duplicate files are rejected by content fingerprint, and duplicate reports by report ID. Nothing changes in the database.
- A transaction ID is recorded once. If it shows up again with the same amount, it’s skipped, and it’s marked as already paid when that week was settled. If the amount differs, the original stays and the difference goes to review.
- Amount payable = gross earnings − deductions + adjustments + balance from prior weeks.
- Unpaid amounts and negative balances carry into the next week. A carried balance older than 7 days is flagged past due.
- Payments the TMS or a driver reports don’t count until a manager confirms them. “Confirm matched payments” only confirms amounts that exactly match what’s payable.
- A driver can’t be approved while they have open discrepancies.
- All money math runs in whole cents with fixed rules. AI never changes an amount.
Where AI fits
Drivers send messages like “Load 496512 entregado, el broker me pagó el lumper $225 en Comchek.” The Driver messages page shows how AI reads that message and pulls out the load, amount, and payment method. The system then applies fixed rules. A message can only add a reported payment, and anything uncertain goes to manual review. In production, those messages come in through a Telegram bot.
Production setup on your own server
This demo runs in the cloud so you can try it right away. A production build runs on your dedicated server with Docker Compose and uses the same rules and the same tests.
| Piece | In this demo | On your server |
|---|---|---|
| Folder watching and scheduling | “Process next file” button | n8n watches the inbox folder and runs the import |
| XML parsing and validation | JavaScript service | Python service with the same validation rules |
| Database | Managed SQL database | PostgreSQL with nightly backups |
| Dashboard | This web app | This web app, or Appsmith or NocoDB if you prefer |
| Statements and exports | Print to PDF, Excel export | Same, plus a stored PDF for every pay period |
| Access | Shared demo accounts | Named users, admin role, HTTPS, remote desktop access |
| Driver messages | Paste a sample message | Telegram bot with AI reading (optional phase 2) |
About the sample data
The carrier, drivers, loads, and amounts are fictional. They’re modeled on a South Florida fleet: owner-operators and lease-purchase drivers paid a percentage of linehaul, fuel surcharge passed through, and typical weekly deductions like fuel card purchases, SunPass tolls, insurance, escrow, ELD fees, and truck lease payments. The real XML layout from your TMS gets mapped in during setup.
Demo build · sample data only · each sign-in creates a private copy that’s deleted after 24 hours.