A factor’s funding cutoff is three deadlines stacked on each other: the last moment a submission can still clear verification, the last moment your staff can still process it, and your bank’s own deadline for the rail you are sending on. The published time is whichever of those three is earliest. Most shops publish the number without having worked out which one it actually is.
Four of our own guides lean on this day and none of them describes it. The onboarding guide puts first funding in one sentence: the system “applies the approved advance and holds the reserve, and the money moves to the account you confirmed in Step 1.” The pricing guide names ACH charges and wire fees as a transparency point. The fuel advance guide owns card-versus-ACH delivery for that one product, and the cash application guide owns the money coming in. Nobody owns the day money leaves.
Search it and you get speed marketing written to carriers, or factoring-software vendors explaining that their platform handles it. The tooling question is real and it is not this page. This page is how the outbound day is designed, where it breaks, and what a published cutoff actually commits you to.
What a complete funding request is
Everything downstream depends on whether the batch that arrived is fundable, so define that before you define anything else.
A complete request is the invoice, the rate confirmation, the signed bill of lading, and proof of delivery, on a load for a debtor with available credit under an approved limit, from a client whose account is current. Anything missing one of those is not a late funding. It is an incomplete submission, and the distinction matters because the two have different owners. A late funding is your problem. An incomplete submission is a conversation with the client, and if you handle it as the former you will absorb the cost of their intake sloppiness indefinitely.
So publish what complete means, per client, at onboarding. And track the bounce reasons. A client whose batches come back three times a week for the same missing document is not a funding problem, it is a training problem, and it will not fix itself while your desk quietly repairs the files.
Where verification sits in the day
Verification is the gate, and where you put it in the day decides your real cutoff more than anything else.
Our collections guide treats verification as the first act of collections and covers how to set its depth by risk: a proven broker with clean history may warrant a light check, a new or shaky debtor gets call-and-confirm on every load. That page owns the standard. The funding-day question is narrower and harder: call-and-confirm depends on somebody at the debtor answering the phone, which is a constraint you do not control and which collapses on Friday afternoons, holidays, and month-end.
Design for that instead of hoping. Know which of your debtors verify through a portal that is available all day, which need a human, and which need a human who is only reliably reachable in the morning. Then set your submission deadline behind the slowest verification path you will actually fund on, rather than behind the fastest. A cutoff set behind the best case is a cutoff you miss on your busiest days, which are precisely the days a carrier remembers.
The other half of this is staffing, and it is the half nobody plans. If one person runs verification, your funding cutoff is that person’s calendar. A single unplanned absence moves the whole day, and there is no software fix for it.
The cutoff, and what “same day” actually binds
Here is where operators get themselves into trouble, because a published cutoff is a commitment and the thing it commits you to is partly outside your building.
For an ACH credit, the outside constraint is the network’s schedule. Nacha’s own Same Day ACH rule page states “A morning submission deadline at 10:30 AM ET, with settlement occurring at 1:00 PM” and “An afternoon submission deadline at 2:45 PM ET, with settlement occurring at 5:00 PM.” The same page carries the availability obligation on the receiving side: “For a credit Same Day Entry, an RDFI must make the amount of the credit Entry available to the Receiver for withdrawal no later than 5:00 p.m. in the RDFI’s local time on the Settlement Date of the Entry,” a requirement effective March 16, 2018.
Read those as network deadlines, not as yours. Your bank has its own earlier cut-off for handing you access to each window, and it may differ by product, by channel, and by whether a file needs review. Windows and bank schedules also change. Get your own bank’s current deadlines in writing for every rail you use, confirm them annually, and set your published cutoff behind the earliest one, not the latest.
Then say what you actually mean. “Submitted complete and verified by 11 a.m. Central funds the same business day by ACH” is a statement an operator can keep. “Same-day funding” with no conditions attached is a statement your desk will break, and the client who gets broken on is the one who told three other carriers about you. We are not going to tell you any design holds under volume. What we will say is that the shops with the fewest funding complaints are the ones whose published promise is the most boring.
Rail choice is a cost and a clock
Every payment method trades money against time against reversibility, and the funding desk should choose deliberately rather than by habit.
Standard ACH is the cheapest and the slowest, and it is the right default for a client on a predictable weekly rhythm who does not need the money at 2 p.m. Same-day ACH buys you the windows above at a higher per-item cost. A wire is the fastest conventional option, costs materially more per payment, and is generally final once sent, which is the part that matters operationally. We are deliberately publishing no cost figures here, because every number available in public is vendor marketing without primary attribution. Get your own bank’s schedule of charges and do the arithmetic on your own volume.
The design question is not which rail is best. It is which rail each client is on by default, who may override it, and what the override costs. A desk where any client can request a wire on any day, approved by whoever is at their computer, has an unpriced cost center and a control gap in the same place. Our pricing guide covers how those charges should appear to the client, and the principle is the one we apply to every fee: the client should be able to read what they were charged and recognize what they were told.
One dated change worth putting in your calendar rather than your process today. Nacha has announced that the Same Day ACH per-payment limit will rise to $10 million effective Sept. 17, 2027, up from $1 million since March 2022 and $100,000 since 2020. If your funding controls, approval thresholds, or dual-authorization rules were built around the current ceiling, that is a dated reason to revisit them before it moves rather than after.
The payee control comes before the money, always
The single most expensive failure on a funding desk is not a late payment. It is a correct payment to the wrong account.
Bank details for a client are set at onboarding and confirmed there, and the discipline that matters is what happens when they change. A change request that arrives by email, is actioned by the person who received it, and takes effect on the next funding is the exact shape of the most common fraud in this business. The control is dull and it works: bank-detail changes are verified by outbound call to a number already on file, never to a number in the request, are actioned by somebody other than the person who received them, and take effect on a stated delay rather than immediately. Record who approved it and when.
The same discipline belongs on the account itself. Who can release a payment, at what size, and with how many approvals, should be a written matrix rather than a habit. And the release list should be reconciled to what actually left the bank, daily, by somebody who did not release it. Our cash application guide makes the inbound version of that argument, and the outbound version is if anything more urgent, because outbound errors move real money out of the building.
None of this prevents fraud. It changes how fast you find out, and on an outbound rail, speed of discovery is most of what you have.
Exceptions are the job, not the interruption
A funding desk that only handles clean batches is not designed, it is lucky. Three exceptions come up constantly and each needs a decided answer.
Partial funding is the first. When six invoices in a batch of ten verify and four do not, you fund six and the batch is not held. That sounds obvious and plenty of shops hold the whole submission because their process has no partial state. Decide it once, build it, and tell the client what they will see.
The held invoice is the second. An invoice pulled from funding needs a reason code, an owner, and an age, exactly as an unapplied payment does. What breaks shops is not holding invoices, it is holding them silently: the client finds out when the funding is short, and nobody can say who is working it. A held-invoice report on the funding desk every morning, with the oldest item at the top, closes that.
The third is the reserve interaction, and it is the one that generates the most client confusion. A held invoice does not just reduce today’s advance, it also delays the reserve release that invoice would eventually have produced, so the client feels it twice at different times. Our pricing guide covers how advance, fee, and reserve work as one design. The funding-desk obligation is to explain both effects at once, in the same message, rather than letting the second one arrive as a surprise three weeks later.
Month-end, and what your lender reads
Two audiences look at the funding day from outside your desk, and neither of them is the client.
The first is the calendar. Volume is not flat, and a desk sized for an average Tuesday fails on the last business day of the month, on the day after a holiday, and in the week your largest client has a good run. Look at your own funding volume by day of week and by position in the month before you decide the desk is adequately staffed. Our metrics guide covers funding capacity as one of the five numbers worth reporting monthly, and peak-day volume is the version of it a funding desk actually feels.
The second is your lender. Our funding-stack guide covers the borrowing base, the field exam, and the question a field examiner asks about whether your system aging reconciles to the report you certified. Outbound funding sits underneath that: advances are what the borrowing base is measured against, and a desk that funds off a spreadsheet and posts to the system later is generating a reconciliation problem on purpose. Fund in the system, then move money, in that order.
What instant payments change
Instant-payment rails are real and in production in the United States, and the operational consequence for a funding desk is more interesting than the speed.
On a batch rail, the window between release and settlement is where a mistake gets caught. Somebody notices the duplicate, the wrong amount, the payee that changed last week, and the file can be pulled. Instant payment removes that window entirely. Every control has to sit before release, because there is no batch to recall and no return process to lean on.
That is not a reason to avoid it. It is a reason to know, before you enable it, that your payee verification, your duplicate check, and your approval matrix are all pre-release controls rather than end-of-day catches. Most funding desks discover which of their controls were secretly relying on the delay only after the delay is gone.
Where this stops being operational
FRC works on process, and there are two lines here.
How you account for payment fees, how float is treated in your financial statements, and the tax treatment of any of it are questions for your CPA. FRC is not an accounting firm and gives no accounting opinion. Our operations audit is an operational read of how the work runs and is not a financial-statement audit.
Your agreements with your bank, your obligations under the network rules you send on, and your liability when a payment goes wrong are legal questions. Read the Nacha rules for what they say, and take your position under them to qualified counsel rather than to a web page.
Where an outside read fits
Funding-day problems are almost never speed problems. They are a cutoff set behind the best-case verification path, a verification function that is one person’s calendar, a bank-detail change process that runs on email, no partial-funding state, and held invoices nobody reports. Each is small. Together they are why the desk has a bad last week of every month.
Operations and technology are two of the six domains in FRC’s 90-Day Operational Audit, alongside collections, onboarding, risk, and financial reporting, and the funding day runs across most of them. The output is a written assessment and a prioritized 12-month roadmap, with no long-term commitment.
FRC’s founder, Renee Williams, built a freight factoring company from the ground up over 25+ years, leading credit and underwriting operations and building the funding and back-office infrastructure the desk runs on. The operators we have worked with, MinWest Financial and MyFactor among them, came in understanding finance and not the operational realities of transportation factoring. We cannot promise you a funding speed. We can help you design a day your desk can actually keep. Call 800-648-5450 and Renee picks up directly.