Squarerigger plans maintenance around loads and sends GL-ready costs to
McLeod, while odometer and dispatch data flow back to trigger PMs.
Built around McLeod dispatch, AP, AR, settlements, and GL mapping.
Here is exactly what crosses between the systems, and in which direction.
Squarerigger maps units, GL structure, and settlements to McLeod, so costs and billing land where they belong.
We confirm your McLeod setup,
units, GL rules, settlements, and
permissions.
Units, vouchers, work orders,
settlements, and GL rules line
up both ways.
A sample of records runs
both directions so each one
lands where it should.
Service fits between
dispatch commitments
Maintenance spend posts
through McLeod
No re-keying between the
shop and McLeod
Dispatch, shop, and
finance stay aligned
Squarerigger works with McLeod dispatch, accounting, and settlements, mapped to your configuration.
For McLeod fleets already running dispatch and billing through one system, a two-way sync moves
the needle on scheduling, cost posting, and duplicate entry all at once.
No. McLeod stays your TMS and accounting hub. Squarerigger runs maintenance and keeps its timing and costs aligned with it.
Squarerigger uses dispatch data from McLeod to line maintenance up with availability, so trucks are not pulled mid-load.
Maintenance costs flow to McLeod as AP vouchers, AR billing, settlement deductions, and GL-coded work order cost detail.
A short demo to review your McLeod configuration, then GL and permission mapping before any records move between systems.