Review bus-vendor invoices against routes and service records.
Explore a fixed-price transportation invoice-reconciliation pilot. The working demonstration uses fictional embedded invoices, contract rates, route records, and service data to illustrate exception review.
Offered by JS Technology Solutions. The public demonstration contains fictional embedded records and does not represent a deployed district or customer system.
A sample reconciliation workflow, step by step.
The working demonstration applies deterministic rules to fictional embedded records. Production data sources and integrations are separately scoped.
Load sample records
The demonstration starts with fictional embedded invoices, routes, contract rates, and service records.
Match
Deterministic rules compare each sample invoice line with its assigned route and recorded sample service.
Classify
Matching sample lines are marked cleared. Discrepancies are shown with their supporting sample evidence.
Review
A human can inspect each sample exception and approve or waive a sample credit within the demonstration.
A working interface on fictional sample records.
Explore a sample reconciliation dashboard and an exception view with the fictional records behind each proposed credit.
August 2026 · Fictional sample records
Sample workspace| Vendor | Invoices | Accuracy | On-time | Flagged |
|---|---|---|---|---|
| Metro Yellow Bus Co. | 10 | 81.6% | $33.60 | |
| Northside Transit Partners | 6 | 90% | $120.00 | |
| Lakeshore Student Lines | 4 | 84.2% | $0.00 | |
| Gateway School Bus | 8 | 92.5% | $60.00 | |
| Prairie Paratransit | 10 | 100% | $94.00 |
Fictional exception · Central Charter Coach
Cancelled route billedAll vendors, invoice lines, figures, and credits shown are fictional embedded sample data. Buyer-specific scope and integrations are agreed separately.
A transportation invoice workflow scoped around your needs.
The working sample demonstrates rule-based reconciliation. Production scope, integrations, reporting, and services are agreed separately.
Sample invoice review
Review the working demonstration's fictional embedded invoice lines and route records.
Rule-based matching
Compare fictional sample invoice lines against contract rates, route assignments, and recorded sample service.
Documented sample exceptions
Inspect duplicate charges, cancelled routes, rate differences, and other exceptions planted in the sample dataset.
Sample vendor views
Browse fictional vendor-level records and the sample evidence supporting each exception.
Reporting scope
Discuss which reporting questions and source records your proposed pilot would need to support.
Optional service scope
Any managed exception-review service is discussed, scoped, and quoted separately.
Deterministic reconciliation with human-reviewed sample credits.
The public demonstration applies documented rules to fictional embedded data. No live customer systems, real payments, or production outcomes are represented.
Compares embedded sample records
The demonstration compares fictional invoice lines with embedded sample contract rates, route records, and service events.
Flags rule-based discrepancies
Deterministic sample rules identify duplicate lines, cancelled routes, contract-rate differences, and other documented sample exceptions.
Keeps sample credits human-approved
Each sample exception shows its supporting fictional records, and a person decides whether to approve or waive the sample credit.
The demonstration contains fictional embedded records only. It does not connect to a district, send a payment, contact a vendor, or apply a real credit.
Production integrations are separately scoped.
The public demonstration uses embedded fictional data and has no live district-system connections. Any proposed file exchange or integration must be separately evaluated and agreed.
Discuss the actual source systems first
Routing, service records, invoice formats, and finance systems vary by district. Their availability, permissions, and required mappings are determined during a separately scoped discussion.
Named-system pages describe possible scoping topics, not existing integrations, partnerships, or deployed customer connections.
Integration scoping topics: Edulog · Zonar / GPS · Transfinder & Versatrans · Tyler Munis / ERP · Samsara & Aspen. Or read the pilot purchasing guide and the developer docs.
Practical resource: school transportation invoice audit checklist.
Discuss security requirements before a production pilot.
The demonstration uses fictional embedded records. Any production data handling, access controls, and district security review must be separately scoped and approved.
Student-data privacy
Designed to student-data-protection standards, with data minimization and access controls appropriate to education records.
Documented sample evidence
Each demonstration exception shows the fictional route, service, and contract records supporting its sample calculation.
District review first
Discuss the buyer's security, legal, technical, and data-handling requirements before any production work.
Humans hold the controls
No payment is released, no credit applied, and no vendor contacted without a person approving it. Automation prepares the decision; your staff make it.
Data-handling scope
Discuss permitted data sources, ownership, retention, and export requirements before any buyer data is used.
Pilot controls
Define file handling, review ownership, exception resolution, and any operational controls as part of the proposed pilot.
Discuss a pilot and separately scoped service options.
Published prices describe proposed pilot and subscription scopes. Final requirements, integrations, implementation, and buyer approval are agreed separately.
- Proposed review scope
- Sample exception workflow
- Buyer requirements apply
- Proposed review scope
- Sample exception workflow
- Separately scoped data mapping
- Separately scoped source records
- Proposed reporting requirements
- District review and approval
- District review and implementation scope
- Separately evaluated source systems
- Requirements agreed before work
Two ways in, shaped around your purchasing rules.
A fixed-price pilot
The proposed pilot is $7,500 for 60 days and focuses on one vendor or one exception category. Your district's own procurement requirements and approval process always apply.
Scope a pilotA direct subscription
Discuss a separately scoped subscription only if the pilot and your district's procurement, technical, and approval requirements support moving forward.
Request a quoteExplore the working sample demonstration.
Review fictional embedded sample invoices, routes, and contract records. The demonstration contains no buyer or live customer data.
Request a demoStraight answers.
What data does the demonstration use?
Only fictional embedded invoice, route, contract, and service records. It does not contain buyer data or connect to a district system.
How are sample exceptions identified?
Deterministic rules compare the embedded sample records and identify documented differences such as duplicate billing, cancelled routes, and rate mismatches.
Who approves credits?
A person reviews the sample evidence and chooses whether to approve or waive the sample credit. The demonstration does not issue payments or contact vendors.
Which purchasing requirements apply?
Your district's own procurement requirements, approval process, and applicable rules always apply.
Are integrations already available?
No production district integration is represented by the demonstration. Any proposed source systems, permissions, mappings, and integration work are separately scoped.
What does the pilot include?
The proposed fixed-price pilot is $7,500 for 60 days, focused on one vendor or one exception category, with final scope agreed before work begins.