What We Believe About
Logistics Finance
The beliefs and principles that shape how Routefig works — not as a statement of values for its own sake, but as an honest account of the thinking behind how we approach accounting for logistics operations.
Back to HomeOur Foundation
Routefig was built around a straightforward observation: logistics finance is not well served by generalist accounting. Not because general accountants lack competence, but because the domain has specific structures — carrier contracts, modal cost drivers, warehouse throughput economics — that require familiarity to account for properly.
The starting point wasn't a product idea. It was a recurring observation: companies with significant freight spend often had financial records that were technically accurate but operationally silent — they told you what was spent, but not where, how, or whether it matched what was contracted. The data was there. The structure to use it wasn't.
What we do is build that structure — reporting frameworks, reconciliation processes, and cost allocation methods designed around how logistics actually runs, not around how a general chart of accounts is organized. That's the foundation everything else sits on.
Philosophy & Direction
What we think good logistics accounting should do — and what it should stop pretending to be.
Financial records serve two purposes: compliance and decision-making. Most logistics accounting does the first adequately. The gap we're interested in closing is the second — making the numbers useful for the people managing freight lanes, carrier relationships, and warehouse operations, not just for year-end filings.
Accounting scope should follow operational structure. If a company runs freight across twelve lanes, the accounting should reflect that. If a warehouse is tracked by three cost centers, the reporting should match. Generic frameworks applied to specific operations produce generic outputs — which tend to be less useful than the operations team's own spreadsheets.
Accounting that hides operational complexity behind tidy summaries isn't serving anyone. Neither is reporting that's technically correct but practically unintelligible. The goal is clarity — not simplification at the expense of accuracy, and not precision at the expense of usability.
Core Beliefs
The specific beliefs that guide how we approach each engagement — and why we hold them.
Domain knowledge is not optional
Accounting for freight without understanding how freight pricing works — accessorial charges, fuel surcharges, volume tiers, contracted versus spot rates — produces records that are accurate in aggregate but misleading at the level where decisions are made. Familiarity with the domain isn't a nice-to-have; it's load-bearing.
Reconciliation before recording
Carrier invoices should be checked against contracted rates before they're entered into the books — not accepted as received and corrected later if someone notices a discrepancy. In high-volume freight environments, small per-shipment errors compound. The discipline of reconciling first is what keeps the records trustworthy.
Unit economics matter more than totals
Total freight spend is one number. Cost per shipment by lane, cost per unit handled by facility, cost per mode — these are the numbers that connect to actual operational decisions. Producing totals is the minimum. Producing unit economics on a consistent monthly basis is what makes the accounting genuinely useful.
WMS and financial records should agree
When warehouse management system data and financial records diverge — which they routinely do without deliberate reconciliation — it creates a persistent credibility problem for both. Neither team fully trusts the numbers. Closing that gap isn't a project; it's a monthly process that needs to be built into the accounting cycle.
Reporting structure is part of the product
How a report is organized determines how useful it is. A freight cost report structured by account type requires translation before it's usable by operations. One structured by lane, mode, and carrier can be read directly. The structure is a design decision, and it matters as much as the accuracy of the underlying numbers.
Context improves over time
A first month's report establishes a baseline. A twelfth month's report has eleven months of context behind it — seasonal patterns identified, carrier behavior understood, anomalies distinguishable from trends. The value of consistent monthly engagement compounds in a way that one-off reports never can.
Principles in Practice
How the beliefs above translate into the way an engagement actually runs — from first contact through ongoing delivery.
Onboarding reflects operations
The first conversation is about how your freight network or warehouse structure actually works — not a generic intake form about account types and software.
Setup is structured, not improvised
Data connections, allocation methods, and reporting frameworks are defined before the first reporting cycle — so the output is deliberate from month one.
Monthly delivery is consistent
Reports arrive on the same cadence every period — reconciled, reviewed, and structured for use by both operations and finance without further processing.
Scope follows the operation
When lanes change, facilities shift, or reporting needs evolve, the engagement adapts — not at extra cost of negotiation, but as part of how the relationship is structured.
Built Around the People Using It
Accounting reports don't make decisions — people do. The design of what we produce is shaped by who reads it and what they need to do with it.
For Operations Managers
Reports are structured around the decisions an operations manager actually makes — which lanes are running above cost, which carriers are performing against contract, which facilities are seeing cost-per-unit creep. The financial view is organized around operational reality.
For Finance Teams
The underlying records are maintained correctly — reconciled, allocated, and documented in a way that satisfies compliance requirements. Finance teams get the structured data they need without having to rebuild it from operational exports every month.
Why This Matters
When the same report can be read by both operations and finance without each team interpreting it differently, something useful happens: conversations about cost become easier. There's a shared reference point — not two parallel datasets that need to be reconciled before anyone can discuss what the numbers mean.
That shared reference is one of the less obvious outputs of logistics-specific accounting. It's not just that the numbers are more accurate. It's that they're organized in a way that multiple functions can use — without each one having to rebuild the data for their own purposes first.
How We Improve What We Do
We don't pursue novelty for its own sake. The way we change what we do is driven by what clients actually run into — where the current structure falls short of what the operation needs.
Starting from what doesn't work
The most reliable signal that something should change is a recurring friction point — a data gap, a reconciliation issue, a report that nobody reads because it's organized wrong. We track those and use them to improve how the next engagement is set up.
Iterating within the cycle
The monthly reporting cycle is also a review opportunity. Each period, we look at whether the current reporting structure is still aligned with how the operation is running — and adjust before gaps become habits.
Keeping what works
Consistency has its own value. A reporting structure that stays stable across periods is one where trends are comparable and anomalies are legible. We change things when it improves clarity — not to demonstrate activity.
Integrity & Transparency
What we believe about honest accounting — including what it's honest to say about the limits of what accounting can do.
Pricing is stated directly
The cost of each service is published — $2,000/month for freight accounting, $2,400/month for warehouse accounting, $4,000 for supply chain cost analysis. Those numbers are what they are. The value is in what they produce, and that's a judgment each client makes based on what they're currently working with.
Accounting doesn't fix operations
Better visibility into freight costs doesn't automatically lower them. Better warehouse cost reporting doesn't automatically improve facility efficiency. What it does is make those conversations possible — with clear data behind them rather than estimates and approximations.
Scope is agreed, not assumed
Each engagement is scoped based on what the operation actually needs — not padded out with services that add complexity without adding clarity. If something isn't useful, it shouldn't be in the engagement.
Discrepancies are reported, not smoothed
When carrier invoice reconciliation surfaces discrepancies, or when WMS data and financial records don't align, those gaps are documented and reported — not absorbed into rounding or classified as noise to avoid a difficult conversation.
Working Together
What a productive engagement looks like — and what both sides contribute to make it work.
From Our Side
Consistent monthly delivery, reconciliation that catches discrepancies before they become records, reporting structured around your operational model, and a standing willingness to discuss what the numbers are showing — not just deliver a package and move on.
From Your Side
Access to the data sources we need to do the work — carrier invoice exports, WMS data, ERP records — and a point of contact who can answer operational questions when something in the data needs context. The quality of the output is proportional to the quality of the input.
The Shared Goal
Financial records that actually reflect how your operation runs — accurate enough for compliance, structured enough for operational decisions, and consistent enough that month-over-month comparisons mean something. That's what a well-functioning logistics accounting engagement produces.
Thinking Beyond the First Month
The argument for consistent, long-form engagement over one-time analysis — and why we structure our services the way we do.
A one-time supply chain cost analysis — like what we offer — has clear value. It produces a cost model and a prioritized list of where the biggest gaps are. That's a useful starting point for conversations about modal shift, supplier selection, or carrier renegotiation.
But it's a snapshot. Six months later, when lanes have changed and carrier contracts have been renegotiated, the analysis may no longer reflect current conditions. The snapshot told you where you were — it doesn't tell you where you are now.
Monthly accounting is different. The first month establishes a baseline. Each subsequent month adds a data point. By the end of a year, you have something that a single analysis can never produce: a documented picture of how costs moved over time, which patterns are seasonal, which trends are structural, and which anomalies were noise versus signals.
That longitudinal view is what makes the accounting genuinely useful for decisions — not just for recording what happened, but for understanding what's likely to happen next.
What This Means for Your Operation
How the beliefs and principles above translate into what you'd actually experience working with Routefig — and what you'd get from it.
Monthly reports that can be read by operations and finance without each team having to reprocess the data for their own use. Structured around lanes, modes, and facilities — not account types.
Carrier invoices checked against contracted rates before being recorded. WMS data reconciled against financial records as part of the standard cycle. Gaps surfaced, not absorbed.
Records that are accurate for compliance purposes and structured for operational use — not a trade-off between the two. Both requirements are met through the same underlying discipline.
An engagement that runs consistently enough to accumulate useful context — so that by the time you need to make a significant cost decision, the data behind it has history, not just a single period.
If This Approach Sounds Right
A brief conversation is usually enough to know whether a logistics-specific accounting engagement would add anything meaningful to how your cost data is currently structured and used.