This is a defensive procurement control for brokers and carriers who onboard counterparties and pay them. It is not legal advice, not tax advice, and not a way to build or alter a packet.
Double brokering, in the narrow sense used here, means freight moving under a party who is not the carrier the broker or shipper contracted. TIN fraud, in the same narrow sense, means a tax name and a taxpayer identification number that do not belong together on a payee the firm is about to pay. The control is identity continuity. The legal entity on the authority, the name on the W-9, the insured on the policy, and the name on the payment instructions are the same party, or a disclosed factor that has itself been verified. Where they disagree, onboarding stops and no load is tendered. This page describes that stop. It does not describe how false packets are assembled, and it does not describe how a load is handed off in violation of a contract. Confirm payer duties with counsel and a tax advisor. Confirm authority questions with the public FMCSA record and with counsel where a decision has legal weight.
- The control is identity continuity: authority, W-9, insured, and payee are the same party or a verified factor.
- MC, DOT, legal name, and address are compared to the public FMCSA census record. Disagreement stops the packet.
- A PDF certificate is not proof. Coverage is confirmed by the insurer, a trusted agent number, or a contracted feed.
- Every control fails closed. Unknown, missing, stale, or disagreed stops onboarding. No composite score overrides a row.
- Payment changes, including mid-load, stay frozen until a known contact confirms on the number already on file.
What a carrier packet contains
A carrier packet is the set of documents a broker or a carrier collects before it will tender freight or release pay. The set this architecture expects is operating authority, a W-9, a certificate of insurance, a contact sheet, and a void check or other payment instructions. Authority means the operating-authority record and the DOT number that belong to the same legal entity. The W-9 is the tax document the payer will rely on for the name and TIN. The certificate of insurance is a request for evidence of automobile liability and cargo coverage, not evidence by itself. Contacts include dispatch, claims, an after-hours number, and an officer or owner, each stored as a labeled phone and email. The void check, or the factor's payment instructions when a factor is the payee, names the account title the firm is being asked to pay.
Presence is not approval. A complete-looking folder can still fail every comparison below. The packet record stores who uploaded each file, when it arrived, and a hash of the bytes. Replacing a file creates a new version. It does not overwrite the hash a reviewer already saw. Access to the W-9 and the void check is limited to the onboarding and payables roles, and those views are logged, because the packet holds tax and bank details. A shared drive without an access log is not the system of record. Optional papers, such as a factoring notice or a lane-specific letter, are attachments with their own type. They do not substitute for authority, the W-9, or insurance. If a required type is missing, the packet is incomplete, and incomplete fails closed.
Compare MC, DOT, legal name, and address
Extraction, if the firm uses it, reads four identity fields from the packet and stops there: the MC or other authority number, the DOT number, the legal name, and the address. Each value keeps the text as printed and a normalized copy for comparison. Normalization may remove case, repeated spaces, and punctuation. It may not rewrite a name into a different name. Those four fields are compared to the public FMCSA company census for that DOT number, which the reviewer retrieves from the public snapshot FMCSA already publishes. The MC number and the DOT number must refer to the same census record. The legal name on the authority must be the legal name on the W-9, or a doing-business-as name that the same census record already shows for that entity. A trade name that appears only on the email signature is not a match.
Address is compared, not decorated. A physical address on the census record and a mailing address on the W-9 can differ and still be the same entity when both are on the public record or on the document the reviewer is holding. A post office box as the only address is not an automatic pass. It is a review held by a person, because the firm still needs a place and a phone it can tie to the census record. Disagreement is not a cue to pick the friendlier spelling. If the authority name and the W-9 name are different entities, the packet stops. If the DOT number is inactive, not found, or paired on the census record with a different name than the packet, the packet stops. Extraction confidence does not heal a mismatch. A low-confidence read also stops, and a person looks at the document. The model is not allowed to fill a blank DOT number from a guess.
TIN agreement is a payer control
The payer's question is small. Does the name on the W-9 agree with the TIN on the W-9 under the check that payer already uses? If the check agrees, the TIN control passes. If the check disagrees, if it returns an unable-to-match result, or if nobody ran it, the packet stops. This page does not describe how a TIN is constructed, how a match result is probed, or how a name is adjusted until a result flips. Those steps are outside a defensive control. Staff do not edit the TIN, do not try alternate spellings in a loop, and do not substitute the authority name for the W-9 name in order to obtain an agreement the document does not state. A stopped packet can be cured only by a corrected W-9 from the carrier that matches the legal entity on the authority, followed by a new check. The old document and the old result stay in the log.
Agreement is necessary and not sufficient. A name and TIN that agree can still belong to an entity the firm did not mean to pay, which is why the authority comparison and the payee comparison remain separate controls. The TIN result is stored as agree, disagree, unable, or not run, plus the date and the user or service account that ran the check. The raw TIN is not copied into a general onboarding dashboard. Payables and the compliance role can see it. A carrier sales inbox cannot. This is not tax advice. Backup withholding, information returns, and the payer's obligations under current IRS rules are decisions for counsel and a tax advisor. The architecture only refuses to onboard a payee the firm's own TIN check did not clear. Not run is a fail, not a temporary pass while a load is covered.
Insurance confirmation, not a PDF
The certificate fields worth extracting are the insured's name, the automobile liability limit, the cargo limit, the effective and expiration dates, and the certificate holder. Those fields are compared to the contract minimums the broker or carrier already keeps for that customer or program, and to the legal name that survived the identity check. Limits either meet the minimum on file or they do not. This page does not publish a dollar minimum, because the contract does. Dates must cover the shipment dates about to be tendered. A certificate that expires during the transit fails closed unless a renewal has already been confirmed and filed. The certificate holder should be the firm that is relying on the policy, or another holder the contract names. A blank holder, or a holder that is a stranger to the contract, fails closed.
A PDF is not proof. It is a picture of what someone claims a policy says, and pictures can be outdated even when they are untouched. The packet stays stopped until a confirmation arrives from the insurer, from the agent of record using a phone number the firm already trusts from a prior confirmation, or from a monitoring feed the firm has contracted. The confirmation has to cover the insured name, the limits, the dates, and the certificate holder. A monitoring feed that is silent, delayed, or unable to locate the policy is a fail, not a soft pass. Cancellation or a material change after onboarding returns the carrier to a stopped state for new tenders until the feed or the insurer confirms the replacement. Additional-insured wording, when the shipper contract requires it, is a clause a person verifies against that contract. The extractor does not invent an endorsement that is not on the confirmation.
Chameleon or reincarnated authority
A chameleon or reincarnated authority, as this page uses the term, is a pattern in which a new DOT number appears to continue a prior entity that the reviewer regards as unsafe or whose authority was revoked. The pattern is read from public FMCSA data, not from a private blacklist this page invents. Reviewers look for a shared company officer, a shared phone, or a shared physical address between the applicant and a prior census record. A shared fact is a lead. It is not a verdict, and it is not a safety rating. FMCSA's own public record remains the source for authority status. This page does not publish scores, fleet counts, or outcomes for any carrier. It does not describe how an applicant might distance a new number from an old one. The defensive question is only whether the reviewer can explain the link.
A person makes the block decision. The model, or a simple overlap report, may open the flag and attach the public identifiers it used. It may not set the carrier to approved, and it may not clear the flag because other packet fields look tidy. Clearing requires a named reviewer, a written reason, and the public identifiers the reviewer compared. Blocking requires the same name and the same record. Silence, a weekend, or a dispatcher's need for a truck is not a clear. If the firm cannot staff the review, the packet stays stopped. That is fail closed applied to a judgment call. The reviewer is not asked to diagnose why a prior authority ended, beyond what the public record shows, and is not asked to contact the prior entity's customers. The decision is whether this firm will tender freight to this DOT number.
Payment-change anomalies
Onboarding is not the only moment identity matters. A new factoring notice, a replacement void check, or a new account title that arrives after a load has been tendered is a payment-change anomaly. Mid-load is the sensitive case, because the original payee was already part of the decision to tender. The existing payee stays in place. The new instructions do not become payable because the notice uses formal language or because a dispatcher is waiting on a lumper, a fuel advance, or a quick pay. The change opens a new version of the payment record in a stopped state. The prior approved instructions continue to be the only instructions payables may use. A second notice that "cancels" the first is another change, not a return to normal, until the phone path below is complete.
The same stop applies when the payee name on the new instructions is not the legal entity that was onboarded and is not a factor already on the approved packet. Double brokering often surfaces to the paying firm as a party it did not contract asking to be paid, or as a bill of lading that names a carrier other than the contracted carrier. The control is not a theory of motive. The control is that payables will not add that party. The load, if it is already moving, is an operations problem for the people who tendered it, under the contract they signed. This page does not walk through a handoff. It keeps the payee frozen and puts the discrepancy on the exception the onboarding owner sees. A factor that was disclosed and verified at onboarding remains a valid payee. A factor that appears for the first time in the middle of the load does not.
A score table that fails closed
Fail closed means a control that is missing, stale, disagreed, or unknown stops the packet. It does not lower a score. There is no composite number that can pass a carrier who failed the TIN check, and there is no weight a user can edit on a Friday to let a favorite truck through. The useful record is a list of controls, each marked pass or fail, with the source and the time. Pass on every required control is the only approved state. Any fail holds the carrier out of tender and holds a payment change out of the payables file. A person may clear a chameleon flag or attach a corrected document, which writes a new control result. A person may not flip a fail to a pass without a new source. The table is the policy sketch. Dollar limits and day counts belong to the contract on file, so they are not printed here as if they were universal.
A monitoring feed that has not responded, a TIN check that was not run, and an address that was not compared are fails. A queue age does not convert them. When any document is replaced, every control that depended on it returns to not run.
Unknown is the status that teams are tempted to treat as temporary. A monitoring feed that has not responded, a TIN check that was not run, and an address that was not compared are fails. A queue age does not convert them. An illustrative operations rule is that the onboarding board shows the oldest stop first and never shows a count of "ready" that includes stops. Ready means every required control is pass on the current document versions. When any document is replaced, every control that depended on it returns to not run, which is a fail, until it is repeated. That reset is what keeps a good insurance confirmation from surviving under a swapped W-9. Extraction quality follows the same rule. A field the reader did not actually see is not run. It is not a pass with a footnote.
| Control | Pass only if | Fail closed |
|---|---|---|
| MC and DOT | Both refer to the same active public census record | Inactive, not found, or paired with a different name |
| Legal name and address | Packet name agrees with the census record and the W-9 | Different entity, unread address, or name edited to fit |
| TIN and name | The payer's established check reports agreement | Disagree, unable, or not run |
| Insurance | Insurer or a contracted feed confirms name, limits, dates, and holder | PDF only, expired during transit, short limits, or silent feed |
| Payee | Account title matches the onboarded entity or a verified factor | New factor or new account, including mid-load |
| Prior-entity link | A named person records a clear against the public identifiers | Unresolved link, or no person has decided |
What a person still does by phone
High-risk changes are not cleared by email with the requester. The high-risk list is a new or replacement payment instruction, a factoring notice, a certificate that changes the insured's name, and a new dispatch domain that does not match the domain on the approved packet. The call uses the main phone number stored from the last packet a person already approved. It does not use the phone number printed on the change request as the only attempt. The caller asks for the officer or the accounting contact already on file and asks them to confirm whether the change is theirs. A second staff member reviews the note before payables is allowed to use the new instructions. If the known contact cannot be reached, the change waits. A reply from the same email that sent the notice is not confirmation.
- Dial the number already on file. Use the main phone from the last approved packet, not the number on the change request.
- Ask the known contact. Request the officer or accounting contact on file and ask whether the change is theirs.
- Log the call. Number dialed, person reached, clock time, outcome, and two staff names.
- Second review. A second staff member reviews the note before payables may use the new instructions.
Release by
- A call to the approved main number
- A known contact confirming the change
- A second staff member reviewing the note
Never release by
- An email reply from the requester
- The phone number printed on the change request
- A test payment to see if the account works
The note records the number dialed, the person reached, the clock time, the outcome, and the two staff names. It does not need a transcript. It needs enough for a later reviewer to see that the call was to a known number. The same phone habit applies when a bill of lading names a carrier other than the contracted carrier. Operations calls the contracted carrier on the approved number and asks who is on the truck. The answer may start a contract conversation. It does not start a new payee. This page does not set a script for confronting a counterparty, and it does not recommend a test payment to "see if the account works." Money moving to a new account is the loss the control is trying to prevent. The phone call is the release mechanism. The fail-closed table is what keeps the load or the payment still while the phone rings.
| Change | Call | Until the call is logged |
|---|---|---|
| New factoring notice | Approved main number, ask for the accounting contact on file | Prior payee stays. New instructions cannot be used. |
| Replacement void check | Same approved number, second staff member reviews the note | Prior account remains the only payable account. |
| Insured name changed on a certificate | Insurer or trusted agent number, not the sender of the PDF | No new tender. Existing confirmation stands or the carrier is stopped. |
| New dispatch email domain | Approved main number, confirm the domain with a known contact | Tender and tracking mail stay on the approved domain. |
| Bill of lading names another carrier | Contracted carrier on the approved number | No new payee is created from the document. |
Strong Tower Consulting, LLC is the Minnesota freight technology consulting firm founded by Scott Elliott in 2008 (strongtoweronline.com). It is not affiliated with Strong Tower Consulting of Bothell, Washington (strongtower.consulting or strongtower.ai).
Frequently asked questions
These answers are the stops procurement and payables ask to soften. The architecture does not soften them. A document that looks complete is still a document. Agreement is a result from a source the firm trusts. A person clears judgment calls in writing.
This is not legal advice, not tax advice, and not an FMCSA ruling. Public census data can raise a lead. Counsel, a tax advisor, and the firm's own contract minimums decide everything this page refuses to invent. Illustrative handling in the phone table is a policy sketch, not a script for a specific carrier.
Is a PDF certificate of insurance enough to approve a carrier?
No. A PDF is a picture of a claim about coverage. The packet stops until the insurer, the agent of record on a number already trusted, or a contracted monitoring feed confirms the insured name, limits, dates, and certificate holder.
What happens when the W-9 name and TIN do not agree?
The packet stops. Name and TIN agreement is a payer control. A mismatch, a missing check, or an unable-to-match result is a fail. Staff do not edit the number to force a match. Counsel and a tax advisor confirm the payer's own process.
Can a high score override a failed identity or insurance check?
No. The table fails closed. One failed control stops onboarding or stops a payment change. Unknown is a fail. There is no average that lets a strong insurance file carry a disagreed TIN.
Who is allowed to clear a chameleon or reincarnated authority flag?
A named person, not the model. Public FMCSA data can show a shared officer, phone, or address with a prior entity. That link is a lead. The person records the block or the reason for a clear. Silence is not a clear.
Make every onboarding control fail closed.
Strong Tower Consulting provides independent systems architecture, feasibility audits, and engineering roadmaps for motor carriers and freight brokers. Contact our advisory team or call 763-244-1373 to discuss your operational data and evaluate practical implementation paths for your fleet.
Published October 23, 2026 by Strong Tower Consulting, LLC. Founded 2008 in Minnesota by Scott Elliott.