The problem
The carrier’s financial records lived in Great Plains. Its operating records lived across the systems that run dispatch, billing, hauling, and delivery. Pending invoices from the carrier’s banking provider were another separate feed. Each system had its own view of the business, but none brought finance and operations together in the same reporting layer.
That separation made routine questions harder than they needed to be. Finance reporting required a separate export. Billing completeness had to be checked against operating activity by hand. Every two weeks, the billing department spent about five hours editing spreadsheets, building charts, and preparing revenue projections for leadership.
Riyex had already built the carrier’s operations data platform, including the curated layer that joins raw source data into business-ready tables. What it lacked was the financial-data integration that could turn Great Plains records into a dependable reporting model.
What we built
We integrated Great Plains financial data into the platform: raw accounting files are exposed in Athena, then scheduled refresh jobs rebuild curated financial datasets every day. Those datasets join Great Plains invoices to Gravitate order, driver, and tractor records where the reporting needs operational context; financial ledger and payables datasets remain available at their appropriate accounting grain.
The banking provider’s daily pending-invoice snapshot lands in the same pipeline. A dedicated payables refresh combines current, unapproved pending invoices with approved Great Plains AP activity. When the same vendor invoice appears in both systems during approval, the model keeps the Great Plains record, preventing the handoff from being counted twice.
The important work was not simply moving an accounting export. We designed the curated tables, scheduled the daily rebuilds, and made the joins and business definitions reliable enough for reporting. The financial data can now be read beside the operational records it explains: billing activity, line-haul work, and projected revenue. That gives the carrier one reporting layer instead of a finance report on one side and a stack of operations dashboards on the other.
Metabase now provides daily views for five connected areas:
- Finance reporting, with Great Plains data available in the same environment as the carrier’s operating metrics.
- Payables reporting, combining pending banking-provider invoices with approved Great Plains AP activity.
- Billing-completeness curves, so teams can compare billing progress against the work moving through the operation.
- Line-haul analysis, connecting financial performance to the carrier’s transportation activity.
- Revenue projections, built from the data the carrier already produces each day.
Metabase is one access path, not a limit. Because the data mart applies consistent business definitions before the data reaches a person or a model, TTE’s executives can also use an MCP-compatible AI assistant to investigate the same financial and operational data conversationally. MCP, or Model Context Protocol, is the standard connection layer that lets an AI assistant use approved tools and data sources. A leader can ask a question in plain language and work from the same governed dataset behind the dashboards, rather than a separate AI-only copy of the numbers.
Results
Great Plains and the carrier’s banking provider are now daily sources in the carrier’s data lake rather than separate financial exports. Their raw files refresh the same curated data mart that supports the carrier’s operational reporting, and the team can use Metabase to move between finance, payables, billing completeness, line haul, and revenue projections without rebuilding the dataset for each question. Revenue projections now arrive daily rather than every two weeks: a 14× increase in reporting cadence.
The billing department has recovered about five hours every two weeks, or roughly 130 hours a year, that previously went to spreadsheet edits, charting, and leadership-report preparation. The result is a shared view of financial and operating performance: the numbers that describe the work and the numbers that explain its economics, available together each day. Teams can reach it through Metabase’s standing dashboards, while executives have a conversational path through their preferred MCP-compatible AI assistant to explore the same governed data.
