Transportation
The most valuable thing this integration does is refuse to answer a question.
Written for freight factors and the underwriters who look at both ends of a load. FMCSA lookup on the carrier you are funding and on the broker who owes the money, and Tessera Network claim verification for the load itself.
What it will not do is tell you that a carrier’s authority is current, that their insurance is in force, or what their safety score means. It captures. It does not verify, and it says which is which.
Party · Kestrel Logistics · FMCSA
Captured 09:02- Registration
- Matched
- Legal name
- Matched
- Role
- Carrier, client side
- Also seen as
- Debtor on 0 files
Not asserted
- Operating authority currency
- Insurance currency
- Safety score interpretation
This gate is forbidden from asserting these. Captured identity only, with the date it was captured.
Why this exists
Freight fraud does not usually involve a fake carrier. It involves a real one.
A registration that exists, a load that was really moved, and an invoice that has already been paid to somebody else. The screens that look most reassuring are the ones that were never asked to be right.
The refusal
A gate that is not allowed to guess, and is not allowed to be made advisory.
Somewhere in every transportation lending stack there is a screen with a tick on it, and somewhere downstream there is an underwriter who has learned to read that tick as a verified assertion. Nobody decided this would happen. It happened because the interface offered certainty that the data behind it never supported.
FactorFox refuses to produce that tick. The relevant gate is explicitly forbidden from asserting authority currency, insurance currency or safety scores, and it states its refusal on screen rather than quietly omitting the field. A refusal an operator can see is a control. An omission is a gap they will fill with an assumption.
The reason is liability, and it is yours rather than ours. An advance made against a load moved by a carrier whose authority had lapsed is a conversation with your insurer, and the strength of your position in that conversation depends on what your own systems told your own people. A system that said nothing leaves your officer’s judgement intact. A system that said fine has quietly transferred the error to you.
This is the same asymmetry that governs money in the platform. Automation may stop something. It may not wave something through. A gate that protects a decision is either enforced or it is not present, and there is no configuration that turns this one into a suggestion during a busy quarter.
What the gate is forbidden from saying
- That operating authority is current
- That insurance is in force
- What a safety score implies about a carrier
It is captured data, presented as captured data, with the date it was captured. An underwriter can act on it. Nobody can point at it afterwards and say the software said it was fine.
The rows
What is connected here, and what each one is entitled to claim
Two integrations and one sibling product. The third is not a connector and is not described as one.
| Row | Status | What moves | What it does not claim |
|---|---|---|---|
| FMCSA | Available | Registration identity in, on the carrier client and on the broker debtor, attached to the party file with the date it was captured. | Operating authority currency, insurance currency and safety scores are not asserted, and the gate that would assert them is forbidden from guessing. |
| Tessera Network | Available | A claim goes out for verification. A verdict comes back with the provenance behind it, captured at run time. | A verdict without provenance does not count as verification, and a run is never re fetched underneath the decision that used it. |
| FactorEvo | Ecosystem | A shared intelligence layer, not a connector. The transportation specialty finance sibling with its own product surface. | Separate product, separate tenancy. It is not an integration and is not counted as one. |
TriumphPay is not a current integration. It is named here because it is asked about often enough that silence would be its own kind of answer, and because a buyer deserves to know that before an implementation rather than during one.
Verification
What corroboration looks like when the only witness is the party being paid
Freight has one advantage over most receivable classes: a load involves several parties, and they do not all have the same interest in what you believe.
Cross validation
A claim is verified against parties other than the one submitting the invoice. That is the entire value. A document supplied by the client corroborates the client.
Provenance or nothing
The verdict carries the provenance behind it. A verification result you cannot trace back is a rumour with a timestamp, and it will not survive a dispute.
Pinned at run time
Verification runs capture their evidence when they run and are never re fetched. A load verified in March still shows March, next to the decision March produced.
Both parties resolved
Carrier and broker each become a party with an exposure, so the broker funding four of your clients is one concentration rather than four unrelated names.
Duplicate paper caught
Near duplicate detection blocks at verification, across the portfolio rather than within one client, which is where the same load invoiced twice actually shows up.
Exceptions reach the briefing
A verification exception is a signal, so it arrives in the morning brief with its severity, its reason and the actions available, rather than waiting in a queue somebody opens on Thursday.
Straight answers
What a freight underwriter asks about these checks
Does FactorFox tell us whether a carrier's authority is active?
No, and it will not pretend to. Registration identity is captured and attached to the party file. Operating authority currency, insurance currency and safety scores are not asserted, and the gate that would assert them is explicitly forbidden from guessing. It says so on screen rather than producing a green tick that an underwriter would reasonably read as a verified fact.
Then what is the FMCSA lookup for?
Identity, on both sides of the load. Confirming that the party in front of you corresponds to a registration, that the broker your client is invoicing is the broker they say it is, and that the same registration is not appearing under two client names in your portfolio. Identity is a genuinely useful answer. It is simply a smaller answer than the one most software implies it is giving you.
Why does the debtor side matter as much as the client side?
In transportation the client is the carrier and the debtor is usually the broker, so a check offered only on the client throws away half of what you needed. Broker payment behaviour is the risk in freight factoring far more often than carrier registration is, and the broker is the party whose conduct across your whole portfolio you can actually observe.
What does Tessera Network verification add that a rate confirmation does not?
Corroboration from a party other than the one asking to be paid. A rate confirmation is a document the client supplied. A verified claim carries the provenance behind the verdict, and the verdict without its provenance does not count. Verification runs capture their evidence at run time and are never re fetched, so a load verified in March still shows what was known in March.
Is TriumphPay a FactorFox integration?
It is not a current integration. Not partially, not through a partner, not by an import built once for one customer. If it matters to your operation, raise it during the evaluation and you will get a straight answer about what building it would involve, which is a better position for you than finding out after signing.
Where does FactorEvo fit?
It is a sibling product in the FactorEvo network rather than a connector: the transportation specialty finance surface, built on the same intelligence layer, with separate product and separate tenancy. Operations that need a dedicated freight management surface run there. Operations that fund freight alongside other industries run FactorFox.
Related
Ask what the carrier screen refuses to tell you.
Bring a real MC number to the demonstration. The instructive moment is the field that stays empty and explains why, next to the ones that are filled in and dated.