<?xml version="1.0" encoding="UTF-8"?>
<!-- AUTO-GENERATED by scripts/generate-blog.mjs — edit the markdown sources, not this file. -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>MantleTMS Blog</title>
    <link>https://mantletms.com/blog</link>
    <description>Practical guides on cost per mile, compliance, cash flow, and the back-office work that keeps a fleet profitable — from the team building MantleTMS.</description>
    <language>en-us</language>
    <atom:link href="https://mantletms.com/rss.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Sun, 12 Jul 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Dispatch Board 101: A Visual System for Never Losing a Load Again</title>
      <link>https://mantletms.com/blog/dispatch-board-101-visual-load-tracking</link>
      <guid isPermaLink="true">https://mantletms.com/blog/dispatch-board-101-visual-load-tracking</guid>
      <pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate>
      <description>Why a whiteboard or spreadsheet breaks down as a fleet grows, and how a visual, drag-and-drop dispatch board turns load assignment into a 10-second decision instead of a guessing game.</description>
      <category>dispatch</category>
      <category>fleet management</category>
      <category>load tracking</category>
      <content:encoded><![CDATA[<p>Every fleet starts somewhere. For a lot of owner-operators and small carriers, that somewhere is a whiteboard, a sticky note, or a spreadsheet tab titled &quot;Loads (2)&quot; that everyone is too afraid to rename. It works fine — right up until it doesn&#39;t.</p>
<p>The failure mode is always the same. A dispatcher glances at the board and it <em>looks</em> current. But the driver marked &quot;available&quot; already picked up a load an hour ago over the phone. The truck listed next to a load is actually in the shop. Nobody erased last week&#39;s job. The board isn&#39;t wrong on purpose — it&#39;s just a snapshot that goes stale the second someone looks away from it.</p>
<p>A dispatch board fixes this by being a system, not a surface. Here&#39;s what that actually looks like.</p>
<h2>The four states every load moves through</h2>
<p>The first thing a real system gives you that a whiteboard can&#39;t is <strong>enforced status</strong>. A load isn&#39;t just &quot;out there somewhere&quot; — it&#39;s always in exactly one of four states, and it can only move forward through them in order:</p>
<figure class="bp-figure">
<div class="bp-scroll">
<svg viewBox="0 0 680 110" role="img" aria-labelledby="loadFlowTitle" style="min-width:560px">
<title id="loadFlowTitle">Load status flow: Pending, Assigned, In Transit, Delivered</title>
<line x1="142" y1="50" x2="176" y2="50" class="bp-muted" stroke-width="2" stroke-linecap="round" />
<polygon points="176,44 186,50 176,56" class="bp-muted" />
<line x1="318" y1="50" x2="352" y2="50" class="bp-muted" stroke-width="2" stroke-linecap="round" />
<polygon points="352,44 362,50 352,56" class="bp-muted" />
<line x1="494" y1="50" x2="528" y2="50" class="bp-muted" stroke-width="2" stroke-linecap="round" />
<polygon points="528,44 538,50 528,56" class="bp-muted" />
<rect x="10" y="30" width="130" height="40" rx="20" class="bp-pending-dk" />
<text x="75" y="55" text-anchor="middle" class="bp-white" font-weight="600" font-size="14">Pending</text>
<rect x="186" y="30" width="130" height="40" rx="20" class="bp-assigned-dk" />
<text x="251" y="55" text-anchor="middle" class="bp-white" font-weight="600" font-size="14">Assigned</text>
<rect x="362" y="30" width="130" height="40" rx="20" class="bp-transit-dk" />
<text x="427" y="55" text-anchor="middle" class="bp-white" font-weight="600" font-size="14">In Transit</text>
<rect x="538" y="30" width="130" height="40" rx="20" class="bp-delivered-dk" />
<text x="603" y="55" text-anchor="middle" class="bp-white" font-weight="600" font-size="14">Delivered</text>
</svg>
</div>
<figcaption>Every load moves through the same four states — no ambiguity about who's supposed to do what next.</figcaption>
</figure>

<p>A <strong>Pending</strong> load has no driver yet. <strong>Assigned</strong> means a driver and truck are locked in. <strong>In Transit</strong> means it&#39;s actually moving. <strong>Delivered</strong> means it&#39;s done and ready to invoice. You can&#39;t drag a Pending load straight to Delivered — the system simply won&#39;t let you, the same way you can&#39;t cash a check before you&#39;ve deposited it. That guardrail alone eliminates the most common whiteboard mistake: a load that gets marked done because someone <em>assumed</em> it shipped.</p>
<h2>What a board should show you at a glance</h2>
<p>A spreadsheet gives you rows. A board gives you <em>shape</em>. When every load in the same state sits in the same column, you stop reading line by line and start seeing patterns — a column that&#39;s too full, a driver who&#39;s been idle since Tuesday, a lane that keeps stalling in transit.</p>
<figure class="bp-figure">
<div class="bp-scroll">
<svg viewBox="0 0 700 300" role="img" aria-labelledby="boardMockTitle" style="min-width:600px">
<title id="boardMockTitle">Illustrative dispatch board with four columns: Pending, Assigned, In Transit, Delivered</title>
<rect x="8" y="10" width="160" height="280" rx="12" class="bp-col" />
<rect x="8" y="10" width="160" height="6" rx="3" class="bp-pending" />
<text x="20" y="34" class="bp-sub" font-weight="700" font-size="10" letter-spacing="0.05em">PENDING · 3</text>
<rect x="16" y="48" width="144" height="58" rx="10" class="bp-surface" />
<rect x="16" y="54" width="4" height="46" rx="2" class="bp-pending" />
<circle cx="40" cy="68" r="9" fill="none" class="bp-muted" stroke-width="1.5" stroke-dasharray="3 3" />
<rect x="58" y="61" width="86" height="7" rx="3.5" class="bp-ink" opacity="0.85" />
<rect x="58" y="74" width="64" height="6" rx="3" class="bp-sub" />
<rect x="112" y="88" width="36" height="12" rx="6" class="bp-chip-neutral" />
<text x="130" y="97" text-anchor="middle" class="bp-ink" font-size="7">TBD</text>

<rect x="182" y="10" width="160" height="280" rx="12" class="bp-col" />
<rect x="182" y="10" width="160" height="6" rx="3" class="bp-assigned" />
<text x="194" y="34" class="bp-sub" font-weight="700" font-size="10" letter-spacing="0.05em">ASSIGNED · 5</text>
<rect x="190" y="48" width="144" height="58" rx="10" class="bp-surface" />
<rect x="190" y="54" width="4" height="46" rx="2" class="bp-assigned" />
<circle cx="214" cy="68" r="9" class="bp-assigned-dk" />
<text x="214" y="71" text-anchor="middle" class="bp-white" font-size="7">JT</text>
<rect x="232" y="61" width="86" height="7" rx="3.5" class="bp-ink" opacity="0.85" />
<rect x="232" y="74" width="64" height="6" rx="3" class="bp-sub" />
<rect x="286" y="88" width="36" height="12" rx="6" class="bp-chip-brand" />
<text x="304" y="97" text-anchor="middle" class="bp-ink" font-size="7">$1.4k</text>
<rect x="190" y="114" width="144" height="58" rx="10" class="bp-surface" />
<rect x="190" y="120" width="4" height="46" rx="2" class="bp-assigned" />
<circle cx="214" cy="134" r="9" class="bp-assigned-dk" />
<text x="214" y="137" text-anchor="middle" class="bp-white" font-size="7">MR</text>
<rect x="232" y="127" width="86" height="7" rx="3.5" class="bp-ink" opacity="0.85" />
<rect x="232" y="140" width="64" height="6" rx="3" class="bp-sub" />
<rect x="286" y="154" width="36" height="12" rx="6" class="bp-chip-brand" />
<text x="304" y="163" text-anchor="middle" class="bp-ink" font-size="7">$980</text>

<rect x="356" y="10" width="160" height="280" rx="12" class="bp-col" />
<rect x="356" y="10" width="160" height="6" rx="3" class="bp-transit" />
<text x="368" y="34" class="bp-sub" font-weight="700" font-size="10" letter-spacing="0.05em">IN TRANSIT · 2</text>
<rect x="364" y="48" width="144" height="58" rx="10" class="bp-surface" />
<rect x="364" y="54" width="4" height="46" rx="2" class="bp-transit" />
<circle cx="388" cy="68" r="9" class="bp-transit-dk" />
<text x="388" y="71" text-anchor="middle" class="bp-white" font-size="7">KP</text>
<rect x="406" y="61" width="86" height="7" rx="3.5" class="bp-ink" opacity="0.85" />
<rect x="406" y="74" width="64" height="6" rx="3" class="bp-sub" />
<rect x="460" y="88" width="36" height="12" rx="6" class="bp-chip-amber" />
<text x="478" y="97" text-anchor="middle" class="bp-ink" font-size="7">$2.1k</text>
<text x="372" y="128" class="bp-sub" font-size="10">+ 1 more</text>

<rect x="530" y="10" width="160" height="280" rx="12" class="bp-col" />
<rect x="530" y="10" width="160" height="6" rx="3" class="bp-delivered" />
<text x="542" y="34" class="bp-sub" font-weight="700" font-size="10" letter-spacing="0.05em">DELIVERED · 11</text>
<rect x="538" y="48" width="144" height="58" rx="10" class="bp-surface" />
<rect x="538" y="54" width="4" height="46" rx="2" class="bp-delivered" />
<circle cx="562" cy="68" r="9" class="bp-delivered-dk" />
<path d="M558 68 L561 71 L567 63" fill="none" stroke="#fff" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" />
<rect x="580" y="61" width="86" height="7" rx="3.5" class="bp-ink" opacity="0.85" />
<rect x="580" y="74" width="64" height="6" rx="3" class="bp-sub" />
<rect x="634" y="88" width="36" height="12" rx="6" class="bp-chip-green" />
<text x="652" y="97" text-anchor="middle" class="bp-ink" font-size="7">$1.7k</text>
<rect x="538" y="114" width="144" height="58" rx="10" class="bp-surface" />
<rect x="538" y="120" width="4" height="46" rx="2" class="bp-delivered" />
<circle cx="562" cy="134" r="9" class="bp-delivered-dk" />
<path d="M558 134 L561 137 L567 129" fill="none" stroke="#fff" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" />
<rect x="580" y="127" width="86" height="7" rx="3.5" class="bp-ink" opacity="0.85" />
<rect x="580" y="140" width="64" height="6" rx="3" class="bp-sub" />
<rect x="634" y="154" width="36" height="12" rx="6" class="bp-chip-green" />
<text x="652" y="163" text-anchor="middle" class="bp-ink" font-size="7">$2.3k</text>
<text x="546" y="194" class="bp-sub" font-size="10">+ 9 more</text>
</svg>
</div>
<figcaption>Illustrative dispatch board — driver, route, and rate at a glance, grouped by status instead of buried in spreadsheet rows.</figcaption>
</figure>

<p>Notice the Pending card has an empty, dashed circle where a driver avatar would go — that&#39;s deliberate. An unassigned load should look visibly incomplete, not just sit there indistinguishable from everything else. And a fast-moving Delivered column doesn&#39;t need to show every load ever completed; it shows the recent ones and tells you honestly how many more there are, instead of scrolling forever or quietly going stale.</p>
<h2>The habit that actually saves time: drag, don&#39;t dig</h2>
<p>The daily win isn&#39;t the board&#39;s layout — it&#39;s what happens when a load needs a driver. On a whiteboard, &quot;assigning a load&quot; means cross-referencing three things in your head: who&#39;s free, what equipment they&#39;re pulling, and whether the timing actually works. On a real board, you drag a card from Pending into a driver&#39;s lane, and the system checks all of that for you before it lets the drop happen.</p>
<figure class="bp-figure">
<div class="bp-scroll">
<svg viewBox="0 0 640 120" role="img" aria-labelledby="timeChartTitle" style="min-width:520px">
<title id="timeChartTitle">Time to assign one load: whiteboard versus a drag-and-drop dispatch board</title>
<text x="0" y="14" class="bp-sub" font-weight="600" font-size="12">Whiteboard or spreadsheet</text>
<line x1="0" y1="20" x2="0" y2="104" class="bp-muted" stroke-width="1.5" />
<rect x="0" y="20" width="460" height="22" rx="6" class="bp-neutral" />
<text x="474" y="36" class="bp-ink" font-weight="700" font-size="13">~15 min / load</text>
<text x="0" y="76" class="bp-sub" font-weight="600" font-size="12">MantleTMS dispatch board</text>
<rect x="0" y="82" width="14" height="22" rx="6" class="bp-assigned" />
<text x="28" y="98" class="bp-ink" font-weight="700" font-size="13">~10 sec</text>
</svg>
</div>
<figcaption>Illustrative — time to find an available driver and matching equipment for one load, whiteboard/spreadsheet versus a drag-and-drop board.</figcaption>
</figure>

<p>That single motion also does more than reposition a card. The moment a driver locks in, MantleTMS&#39;s board computes the driver&#39;s pay for that load right there — no separate step, no forgetting to fill it in three weeks later when it&#39;s time to run settlements. What used to be a phone call, a mental checklist, and a follow-up note becomes one drag.</p>
<h2>The board is the front door to everything else</h2>
<p>A dispatch board that&#39;s just a prettier whiteboard would still be a step up. But because every card is a real record, moving it forward feeds the rest of the business automatically. A load that lands in Delivered is now eligible for an invoice. Its driver pay is already sitting there waiting for the next settlement run. Its state miles are ready to roll into the quarterly IFTA worksheet. None of that requires re-entering anything — it&#39;s the same load, just further along.</p>
<p>That&#39;s really the whole pitch for moving off a whiteboard: not that it looks nicer, but that &quot;assign the load&quot; stops being a dead end and starts being the first domino in a chain that runs itself.</p>
<p>If you&#39;re still tracking loads on a board you have to erase by hand, <a href="https://mantletms.com/signup">try MantleTMS free</a> and drag your first load into Assigned.</p>]]></content:encoded>
    </item>
    <item>
      <title>How to Calculate Your Trucking Cost Per Mile (and Why It Decides Every Load)</title>
      <link>https://mantletms.com/blog/how-to-calculate-trucking-cost-per-mile</link>
      <guid isPermaLink="true">https://mantletms.com/blog/how-to-calculate-trucking-cost-per-mile</guid>
      <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
      <description>A step-by-step guide to calculating cost per mile for owner-operators and small fleets — fixed costs, variable costs, and the break-even number that tells you which loads to take.</description>
      <category>cost per mile</category>
      <category>owner-operator</category>
      <category>trucking finance</category>
      <content:encoded><![CDATA[<p>Cost per mile (CPM) is the single most important number in your trucking business. It is the line in the sand that tells you whether a load makes money or quietly costs you money. Brokers know their numbers cold — if you don&#39;t know yours, you are negotiating blind.</p>
<p>This guide walks through exactly how to calculate it.</p>
<h2>Why cost per mile matters more than rate per mile</h2>
<p>A load paying $2.10 per mile sounds better than one paying $1.95. But if your true cost is $1.85 per mile, the difference between those two loads is the difference between a $0.25 and a $0.10 margin — a load that earns 2.5x more profit. And if your cost is actually $2.00 because you forgot to account for an empty backhaul, that &quot;good&quot; load is losing money.</p>
<p>You cannot make that judgment without a CPM you trust.</p>
<h2>Step 1: Add up your fixed costs</h2>
<p>Fixed costs are the bills that arrive whether the truck rolls or sits. Per month, total up:</p>
<ul>
<li>Truck and trailer payments</li>
<li>Insurance (liability, cargo, physical damage)</li>
<li>Permits, licensing, IFTA, and IRP</li>
<li>ELD subscription and other recurring software</li>
<li>Accounting, dispatch, or factoring fees</li>
<li>Parking and any office overhead</li>
</ul>
<p>Add it all up and divide by the miles you realistically run in a month. If your fixed costs are $6,500 and you run 10,000 miles, that&#39;s <strong>$0.65 per mile</strong> before the truck even moves.</p>
<h2>Step 2: Add up your variable costs</h2>
<p>Variable costs scale with the miles you drive:</p>
<ul>
<li><strong>Fuel</strong> — usually your single largest variable cost</li>
<li>Tires</li>
<li>Maintenance and repairs (set aside a per-mile reserve even in good months)</li>
<li>Tolls</li>
<li>Def, oil, and consumables</li>
</ul>
<p>Track these per mile. Fuel alone is often <strong>$0.50–$0.70 per mile</strong> depending on your truck and lane.</p>
<h2>Step 3: Don&#39;t forget the driver</h2>
<p>If you pay yourself or a company driver, that pay is a real cost. Whether you express it as a per-mile rate, a percentage, or a salary divided by miles, it belongs in the calculation. Leaving driver pay out is the most common way owner-operators fool themselves into thinking a lane is profitable.</p>
<h2>Step 4: Account for deadhead</h2>
<p>Your costs accrue on empty miles too. If you run 10% deadhead, your effective cost per <em>loaded</em> mile is higher than your raw CPM. Divide total costs by <strong>loaded</strong> miles, not total miles, to get the number that actually matters when you quote a rate.</p>
<h2>Putting it together</h2>
<p>A simplified example for a single-truck operation:</p>
<table>
<thead>
<tr>
<th>Category</th>
<th>Cost per mile</th>
</tr>
</thead>
<tbody><tr>
<td>Fixed costs</td>
<td>$0.65</td>
</tr>
<tr>
<td>Fuel</td>
<td>$0.60</td>
</tr>
<tr>
<td>Maintenance + tires</td>
<td>$0.20</td>
</tr>
<tr>
<td>Driver pay</td>
<td>$0.55</td>
</tr>
<tr>
<td><strong>Total</strong></td>
<td><strong>$2.00</strong></td>
</tr>
</tbody></table>
<p>Now you know: any load under $2.00 per <em>loaded</em> mile loses money. A load at $2.50 nets $0.50 per mile. That is your decision rule.</p>
<h2>Keep the number current</h2>
<p>Your CPM is not a one-time exercise. Fuel moves, insurance renews, a major repair changes the maintenance line. Recalculate quarterly — or let your software do it continuously.</p>
<p>This is exactly where a TMS earns its keep. In <strong>MantleTMS</strong>, every expense you log can be attributed to a load, a driver, or a power unit, and the trip-profitability report turns that ledger into a per-load margin automatically — so your cost per mile stays live instead of living in a spreadsheet you update twice a year.</p>
<p><a href="https://mantletms.com/signup">Start free</a> and put a real number behind every load you book.</p>]]></content:encoded>
    </item>
    <item>
      <title>The Owner-Operator&apos;s Guide to IFTA Filing (Without the Quarterly Panic)</title>
      <link>https://mantletms.com/blog/ifta-filing-guide-owner-operators</link>
      <guid isPermaLink="true">https://mantletms.com/blog/ifta-filing-guide-owner-operators</guid>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <description>What IFTA is, who has to file, how the quarterly fuel-tax report actually works, and the record-keeping habits that make filing a five-minute job instead of a weekend.</description>
      <category>IFTA</category>
      <category>compliance</category>
      <category>owner-operator</category>
      <content:encoded><![CDATA[<p>For a lot of owner-operators, IFTA is the quarterly chore that turns a Sunday into a shoebox-of-receipts archaeology dig. It doesn&#39;t have to be. Once you understand what the report is actually asking for, the whole thing comes down to two numbers per state — and good record-keeping makes those numbers fall out automatically.</p>
<h2>What IFTA is</h2>
<p>The <strong>International Fuel Tax Agreement</strong> is a deal between the lower 48 U.S. states and most Canadian provinces to simplify fuel-tax reporting for carriers that operate across state lines. Instead of filing fuel taxes separately in every jurisdiction you drove through, you file <strong>one quarterly return</strong> with your base state, and the system settles the money between jurisdictions for you.</p>
<h2>Who has to file</h2>
<p>You need an IFTA license if you operate a &quot;qualified motor vehicle&quot; across two or more member jurisdictions. That generally means a vehicle that:</p>
<ul>
<li>Has two axles and a gross weight over 26,000 lbs, <strong>or</strong></li>
<li>Has three or more axles regardless of weight, <strong>or</strong></li>
<li>Is used in combination exceeding 26,000 lbs</li>
</ul>
<p>If that&#39;s you, your base state issues an IFTA license and decals, and you file every quarter — even quarters where you didn&#39;t leave your home state (you still file a &quot;zero&quot; return).</p>
<h2>How the report actually works</h2>
<p>IFTA reconciles two things for each jurisdiction:</p>
<ol>
<li><strong>Miles driven</strong> in that jurisdiction</li>
<li><strong>Fuel purchased</strong> in that jurisdiction</li>
</ol>
<p>From your total miles and total gallons, the system computes your fleet&#39;s average miles per gallon. It then uses that MPG to figure out how much fuel you <em>burned</em> in each state, multiplies by that state&#39;s tax rate, and compares it to how much fuel you <em>bought</em> (and already paid tax on) there.</p>
<ul>
<li>Burned more than you bought in a state? You owe that state.</li>
<li>Bought more than you burned? You get a credit.</li>
</ul>
<p>The quarterly return nets it all into a single payment or refund.</p>
<h2>The two records that make or break filing</h2>
<p>Everything above depends on two clean data sets:</p>
<ul>
<li><strong>Distance records</strong> by jurisdiction — your trip miles, broken out by state. Your ELD captures most of this, but you need it summarized per state per quarter.</li>
<li><strong>Fuel receipts</strong> — every purchase, with date, location (state), gallons, and amount. A bank statement is not enough; IFTA wants the detail.</li>
</ul>
<p>The owner-operators who dread IFTA are almost always the ones reconstructing these from memory at the deadline. The ones who file in five minutes captured both as they went.</p>
<h2>Filing deadlines</h2>
<p>Returns are due the last day of the month following the quarter:</p>
<table>
<thead>
<tr>
<th>Quarter</th>
<th>Period</th>
<th>Due</th>
</tr>
</thead>
<tbody><tr>
<td>Q1</td>
<td>Jan–Mar</td>
<td>April 30</td>
</tr>
<tr>
<td>Q2</td>
<td>Apr–Jun</td>
<td>July 31</td>
</tr>
<tr>
<td>Q3</td>
<td>Jul–Sep</td>
<td>October 31</td>
</tr>
<tr>
<td>Q4</td>
<td>Oct–Dec</td>
<td>January 31</td>
</tr>
</tbody></table>
<p>Miss a deadline and you&#39;re looking at penalties and interest — and a pattern of late filings can put your license at risk.</p>
<h2>Build the habit, not the panic</h2>
<p>The fix for IFTA stress isn&#39;t a better weekend; it&#39;s logging fuel and miles continuously instead of in a quarterly sprint. Capture every fuel purchase as an expense the day it happens, with the state attached, and keep your trip miles where you can pull them by jurisdiction.</p>
<p>In <strong>MantleTMS</strong>, fuel goes into the same categorized expense ledger you already use for the rest of your costs — attributable to a load or a power unit — so when the quarter closes, the raw material for your return is already organized instead of scattered across a glovebox. Live ELD/IFTA mileage automation is on our roadmap; the record-keeping discipline that makes filing painless you can start today.</p>
<p><a href="https://mantletms.com/signup">Create your account</a> and stop dreading the last day of the month.</p>]]></content:encoded>
    </item>
    <item>
      <title>Factoring vs. Quick Pay: Which Gets You Paid Without Eating Your Margin?</title>
      <link>https://mantletms.com/blog/factoring-vs-quick-pay-trucking</link>
      <guid isPermaLink="true">https://mantletms.com/blog/factoring-vs-quick-pay-trucking</guid>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain-English comparison of freight factoring and broker quick pay — what each costs, when each makes sense, and how to keep more of your rate while still getting paid fast.</description>
      <category>factoring</category>
      <category>cash flow</category>
      <category>trucking finance</category>
      <content:encoded><![CDATA[<p>You hauled the load, delivered on time, and sent the invoice. Now you wait 30, 45, sometimes 60 days to get paid — while fuel, insurance, and the truck payment don&#39;t wait at all. That gap between doing the work and seeing the money is the cash-flow squeeze that sinks otherwise-healthy trucking businesses.</p>
<p>Two tools close that gap: <strong>factoring</strong> and <strong>quick pay</strong>. They solve the same problem in very different ways.</p>
<h2>Quick pay: faster money from the broker</h2>
<p>Quick pay is a broker&#39;s offer to pay your invoice early — often within 1–2 days — in exchange for a small discount, typically <strong>1.5%–5%</strong> of the load.</p>
<p><strong>Pros:</strong></p>
<ul>
<li>Simple — no third party, you deal directly with the broker</li>
<li>No contract or monthly minimums</li>
<li>You choose it load by load</li>
</ul>
<p><strong>Cons:</strong></p>
<ul>
<li>Only available on loads with brokers who offer it</li>
<li>The rate varies by broker, and the best brokers don&#39;t always offer it</li>
<li>It does nothing for your direct-shipper invoices</li>
<li>You&#39;re still chasing every other invoice yourself</li>
</ul>
<p>Quick pay is a per-load convenience, not a system.</p>
<h2>Factoring: sell your invoices to get paid now</h2>
<p>With factoring, a factoring company buys your unpaid invoices and pays you most of the value immediately — usually <strong>95%–98%</strong> — then collects from the broker or shipper for you. Their fee is typically <strong>1%–4%</strong>.</p>
<p><strong>Pros:</strong></p>
<ul>
<li>Works on <em>every</em> invoice, broker or direct shipper</li>
<li>Predictable, fast cash flow on all your freight</li>
<li>Many factors take over collections and credit-checking customers for you</li>
<li>Some offer fuel cards and other perks</li>
</ul>
<p><strong>Cons:</strong></p>
<ul>
<li>It&#39;s a relationship — contracts, and sometimes monthly minimums</li>
<li><strong>Recourse vs. non-recourse</strong> matters: with recourse factoring, you&#39;re on the hook if the customer never pays; non-recourse costs more but shifts that risk</li>
<li>Watch for hidden fees — ACH charges, monthly minimums, termination fees</li>
<li>The discount applies to all your freight, not just the loads where you need speed</li>
</ul>
<h2>The real cost comparison</h2>
<p>On a single $2,000 load:</p>
<ul>
<li><strong>Quick pay at 3%</strong> costs you $60</li>
<li><strong>Factoring at 2%</strong> costs you $40</li>
</ul>
<p>Factoring looks cheaper per load — but it usually applies to <em>all</em> your invoices, while quick pay you pick and choose. The honest comparison isn&#39;t per-load; it&#39;s: <em>how much total margin am I giving up each month, and what am I getting for it?</em></p>
<h2>How to choose</h2>
<ul>
<li><strong>You run mostly broker freight and only occasionally need cash fast?</strong> Quick pay, used selectively, keeps more of your margin.</li>
<li><strong>You haul for direct shippers, or you need every invoice to convert to cash predictably?</strong> Factoring buys you a system and offloads collections.</li>
<li><strong>Cash flow is genuinely tight and unpredictability is the real problem?</strong> Factoring&#39;s consistency is often worth the fee.</li>
</ul>
<p>Many established operators use both: factoring as the backbone, and they simply skip quick pay on factored loads.</p>
<h2>Know your margin before you give any of it away</h2>
<p>Every one of these decisions comes back to one question: <em>what&#39;s my margin on this load before fees?</em> Give up 3% on a load that only nets 8% and you&#39;ve handed over more than a third of your profit. Give up 2% on a 25%-margin load and you&#39;ll barely notice.</p>
<p>You can only make that call if your numbers are in front of you. In <strong>MantleTMS</strong>, customer rate, driver pay, and attributed expenses roll up into a per-load profit and margin — so before you accept quick pay or hand an invoice to a factor, you can see exactly how much of the load you&#39;re actually trading away.</p>
<p><a href="https://mantletms.com/signup">Start free</a> and decide with your real margin, not a guess.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
