MapLedger solves a structural problem in trucking finance: every carrier’s general ledger is different, making consistent benchmarking and precise profitability analysis difficult until the accounts are translated and costs are assigned to the activities that caused them.
One carrier may record driver pay as “Driver Pay – OTR Company,” another as “4100 – Wage Expense – Line,” and a third may still use an inherited accounting default. All three record the same economic event, but they cannot be compared with each other, industry benchmarks, or even prior periods without substantial manual translation.
MapLedger was designed to eliminate that work and support a precise Activity-Based Costing model for trucking. Its mapping and distribution framework seeks to match every cost dollar to the activity that caused it as closely as the data permits.
From GL Data to Load-Level Profitability
The MapLedger pipeline is based on one principle: every dollar entering the general ledger should ultimately be traceable to the loads and operating activity it affected.
Getting Data In: Every Source, One Pipeline
MapLedger accepts financial data from several sources:
- CSV and Excel trial-balance uploads, including multi-sheet workbooks and historical periods.
- Direct McLeod Software integration with automated GL exports and period synchronization.
- Scheduled or real-time APIs for QuickBooks, Sage, Xero, and other accounting or ERP platforms.
The native chart of accounts is not changed. MapLedger preserves it and builds a standardized analytical layer alongside it, allowing the books to remain intact while the analysis uses common definitions.
Step 1: Data Import
The Data Import screen accepts a trial-balance file, parses it, validates the format, and records the file details, period range, row count, and upload time. Each import remains traceable and auditable.
The required structure includes GL account, description, period, and net change. User-defined fields may carry additional classifications or cost-center information through the process. A template allows data from other systems to be organized into a compatible format.
Step 2: GL Mapping
Each native account is assigned to the FreightMath Standard Chart of Accounts through one of three mapping types.
Direct (1:1)
The entire balance of a native account flows unchanged to one standard account. This is appropriate when the native description already matches a standard category, such as company-driver wages or OTR fuel expense.
Percentage
A native account that covers several standard categories can be divided using fixed percentages. For example, a combined insurance account might be allocated 60% to liability insurance and 40% to physical-damage insurance. The split is configured once and reused when the underlying relationship is stable.
Dynamic
Dynamic mapping uses actual relationships among accounts and same-period operating statistics rather than a fixed percentage. A fuel account shared by multiple divisions, for example, can be divided according to each division’s actual loaded miles for that period.
This is the main distinction between Dynamic mapping and a conventional GL transformation. A static split assumes that the relationship never changes; Dynamic mapping recalculates the allocation when the operating mix changes.
Each mapping includes a polarity flag so revenue and expenses affect operating ratio correctly regardless of source-system conventions. Confidence scores identify accounts that may need review. A mapping can apply to one period or be carried forward.
The mapping screen displays the count of mapped accounts, any unmapped balance, and operating ratio in raw, raw-with-exclusions, and adjusted forms. When all accounts are mapped and the unmapped balance reaches zero, the period is ready for distribution.
The standard chart is organized around trucking economics: linehaul, fuel surcharge, and accessorial revenue; driver, fuel, equipment, and maintenance expense; brokered capacity and third-party network cost; and overhead such as administration, technology, facilities, and insurance. Statistical accounts for miles, loads, assets, and headcount travel through the same structure to support ratios and allocations.
Step 3: Distribution
Mapping identifies what a cost is. Distribution determines where it belongs.
The process asks which operation actually caused the expense in the current period, rather than relying on a historical budget split or a management assumption. Variable costs such as fuel and driver wages follow loaded and empty miles. Overhead can follow loads, empty miles, and dwell hours in proportion to resource use. Driver settlements, equipment charges, and other known direct amounts can be assigned to the loads they concern without statistical spreading.
More complex allocations use FreightMath operating measures such as miles, loads, utilization, and revenue by operation. When all standard accounts have been distributed and the total reconciles to zero variance, the period’s cost structure is ready for analysis.
Step 4: Review and Publish: FP&A for the Trucking Operation
The Review module functions as a financial-planning and analysis environment rather than a simple summary page. Finance teams validate and interpret standardized period data before publishing it into FreightMath and BidRight.
The Review Summary displays operating ratio, gross margin, total loads, total miles, and revenue per mile, with prior-period and FreightMarks peer comparisons. A trailing 16-month view plots 15 months of revenue and expense history so users can distinguish seasonal movement from a structural margin change.
A detailed standardized P&L is available for each operation in raw and adjusted views over one-, three-, six-, and 12-month intervals. Every line appears both as a percentage of revenue and as a cost per mile, with peer variances in both dimensions.
The two comparisons answer different questions. Percentage of revenue shows how efficiently the carrier converts revenue to profit. Cost per mile shows whether its cost structure is competitive. A short-haul carrier may have a favorable operating ratio and still appear expensive per mile, so both views are needed.
After validation, publishing sends the data into FreightMath for load-level profitability, FreightMarks for industry benchmarking, and BidRight for bid analysis and rate validation.
Free Tool: Build Your GL Before You Map It
The FreightMath GL Builder addresses the blank-page problem of designing a standardized chart of accounts. It guides the user through three steps:
- Define operational groups or business lines and assign numeric codes.
- Select labor groups such as Company Driver, Owner Operator, and Lease Purchase.
- Enter basic company information and generate the chart.
The output is a MapLedger-ready chart of accounts in CSV and Excel formats. Common structures include OTR, Dedicated, Local or Shuttle, and Brokerage, with separate codes for equipment programs or customer-specific dedicated operations.
The Operating Ratio Is a Conclusion, Not a Starting Point
An operating ratio is meaningful only when the data beneath it is structured correctly. A 93% OR built on commingled driver wages and owner-operator settlements, netted fuel surcharge and fuel expense, or overhead spread without causal logic reflects accounting convenience rather than operating reality.
MapLedger starts from the belief that carriers already generate the financial information needed for detailed performance analysis. The task is to organize that information around actual cost causation.
When a dedicated division and an OTR fleet operate together, each should receive the costs it consumed in that period. When the operating mix shifts, the allocation should shift with it. That enables a carrier to compare operating ratio by division, benchmark standardized driver cost against comparable fleets, and use the same financial foundation for pricing and scenario analysis.