A fixed-price pilot for transportation invoice review
Review the proposed RouteLedger pilot, its published price, and the actual sample-data workspace. Your district alone determines its purchasing process, required approvals, and whether a quote or purchase order is appropriate.
A focused problem and a defined pilot scope
Comparing transportation invoices with route assignments, service records, and contract rates can involve records maintained in separate systems. The proposed pilot focuses on one vendor or one exception category, subject to the district's actual data availability and review requirements.
The existing RouteLedger sample workspace demonstrates invoice matching and staff-reviewed sample credit actions. District data connections and production controls are separate pilot requirements, not established implementations.
How RouteLedger works
Scope
Identify the vendor invoices, route records, and export formats that the district can actually provide.
Match
Review the actual sample-data demonstration and agree on any district-specific matching rules separately.
Review
District staff retain authority over every payment, credit, exception, and accounts-payable action.
Validate
Any production data mapping, security control, response process, or export must be separately scoped and verified.
Your district determines the purchasing process
The proposed $7,500 fixed-price pilot covers a 60-day, separately agreed scope for one vendor or one exception category. Your district determines the applicable purchasing process, threshold, approvals, and documentation. A quote or purchase order is available only if your district confirms that its own rules permit that route.
No purchasing exemption, contract vehicle, automatic eligibility, or production implementation is represented. Any later subscription requires its own district review and purchasing authorization.
Potential data mappings require separate verification
Possible file-based mappings to routing, GPS, student-information, or accounts-payable systems must be scoped against actual district exports, permissions, security requirements, and vendor constraints. No third-party connector or production integration is represented as deployed. Review the proposed mappings for Edulog, Zonar and GPS telematics, Transfinder and Versatrans, or Tyler Munis and other ERPs.
What it costs
Published pricing includes a fixed-price pilot and possible subscription tiers. A district must evaluate any purchase against its own process and verify the proposed implementation scope. See the published pricing.
Common questions
Who decides the purchasing requirements?
Your district decides. Its procurement team determines the applicable process, threshold, required approvals, and whether a quote or purchase order is permitted.
Are vendor or system integrations already deployed?
No third-party connector is represented as deployed. Available exports, field mappings, vendor permissions, and implementation work must be separately scoped and verified.
What is actually available today?
A working sample-data RouteLedger workspace demonstrates invoice matching and staff-reviewed credit actions. Any district-connected pilot requires its own approved implementation scope.
How would district data be handled?
Data minimization, role-based access, retention, and logging are proposed pilot requirements. The district must review and verify those controls before any production data is processed.
Review the actual sample-data workspace
Inspect the working demonstration on fictional sample invoices, then discuss a separately scoped district pilot.
Request a demo