Carrier Onboarding Packet: Authority, Insurance and Payment Setup

A new carrier is booked for Monday's 06:00 pickup because the lane is short of trucks. The broker-supplied certificate of insurance shows a $1,000,000 auto limit, so the load goes out. On Thursday the carrier's invoice arrives with a different legal name from the one on the certificate, a bank letter from a personal email address, and no tax form. Accounts payable stops the payment, the carrier stops answering, and nobody can say which document was ever checked against its source.

A carrier onboarding checklist fixes that only when every line names the document, the place it is verified, the person who signs it off, and the point in the clock by which it must be done. Built that way, a clean US carrier or Indian transporter can be tender-ready within two business days, and the first invoice pays without a hold, a backup withholding surprise or a reverse-charge argument.

• What this guide covers: the US federal filings behind operating authority and insurance, Form W-9 and the freight exception for information returns, and the Indian GSTIN, PAN, vehicle RC, GTA tax option and TDS declaration.
• What it adds: an owner and deadline for each packet item, a worked setup in dollars and rupees, a JSON readiness record, and an evaluation list for tools or services that run the packet.

Five evidence blocks that make a carrier packet complete

A complete packet holds five blocks: legal identity, operating authority, insurance, tax status and remittance details. Each block is proven by a record held somewhere other than the carrier's own email, and the packet is complete only when every block has been compared with that outside record.

Most failed onboarding files hold the right paper but no comparison. A PDF of operating authority, a certificate of insurance and a bank letter all prove that someone produced a document. They do not prove that the federal register, the insurer's filing or the bank agree with it. The table below sets the outside record for each block, the person who checks it, and who may release the carrier for tendering.

The release owner column matters more than the checker column. If the person who invited the carrier can also approve its bank details, a single compromised inbox can redirect every payment. Keep the release for remittance with accounts payable, and keep the release for authority and insurance with whoever answers for cargo claims and safety.

Operating authority and the BOC-3: confirming the federal filings

For an interstate for-hire carrier in the US, check three things in FMCSA's own records: an active USDOT registration, active for-hire authority for the docket the carrier quotes, and a process agent designation on file. A PDF of the authority grant is not evidence that the authority is still active today.

The process agent filing is easy to overlook because carriers rarely send it. Under 49 CFR 366.2, carriers, brokers and freight forwarders designate agents for service of process on Form BOC-3, only one current form may be on file, and it must cover every state where a designation is required. A carrier that cannot be served in the state where a claim arises is a slower counterparty when cargo goes missing.

• Entity type check: confirm the docket is carrier authority, not broker-only. A broker presenting itself as a carrier will hold a $75,000 surety bond or trust fund under 49 CFR 387.307, filed on Form BMC-84 or BMC-85, not the carrier's liability filing.
• Name match: the legal name on the authority, the insurance filing, the W-9 and the invoice must be identical. 49 CFR 387.313(c) requires insurance filings to be issued in the full and correct name of the carrier.
• Address and contact: compare the phone number and email the carrier gave you with the registration record, and log any difference for the remittance callback later.
• Recheck date: store the date each record was viewed, because authority can be revoked after onboarding and the packet should show what was true on the day of release.

Reading insurance evidence beyond the emailed certificate

A certificate of insurance shows what an agent typed on a form; the FMCSA filing shows what the insurer has certified to the regulator. Check the filing for public liability, check the policy or insurer for cargo cover, and set the cargo requirement from the value of your freight, because federal rules do not set one for general freight.

The federal floor for public liability comes from 49 CFR 387.9. A for-hire carrier of non-hazardous property in vehicles of 10,001 pounds GVWR or more needs at least $750,000. Oil and listed hazardous materials need $1,000,000, and the bulk hazardous categories in the table need $5,000,000. Under 387.303(b)(1)(i), a fleet made up only of vehicles under 10,001 pounds carrying non-hazardous property needs $300,000.

Carrier onboarding for US interstate freight should confirm the insurer's BMC-91 or BMC-91X filing on FMCSA records, not only the certificate, because 49 CFR 387.313(d) bars cancellation until 30 days after notice on Form BMC-35, and 387.9 sets a $750,000 floor for non-hazardous property in 10,001-pound vehicles.

The filing forms tell you what kind of cover sits behind the carrier. Under 387.313(a)(3), Form BMC-91 certifies the full security limit and BMC-91X certifies full coverage or a layer of an aggregated limit. Separately, 387.7(d) requires the carrier to keep proof at its principal place of business, usually the MCS-90 endorsement or an MCS-82 surety bond. Ask for the MCS-90 page when the certificate looks unusual.

Cargo cover is where shippers most often assume a rule that does not exist. The cargo filings in 387.303(c), at $5,000 per vehicle and $10,000 per occurrence on Form BMC-34, apply to household goods carriers. For general freight, the cargo limit, deductible and exclusions are a contract matter, so the packet should record the limit and the exclusions that bite on your commodities.

US tax setup: Form W-9, backup withholding and the freight exception

Collect a signed Form W-9 before the first payment, match the name and TIN, and start backup withholding at 24% if the carrier fails to provide a correct TIN. Do not assume every carrier payment needs a Form 1099-NEC, because the IRS instructions list freight among the excepted payments.

The W-9 gives three facts the vendor master needs: the legal name as the IRS holds it, the federal tax classification, and the taxpayer identification number with a certification about backup withholding. The IRS states that payers must withhold at the current rate of 24 percent when a payee has failed to provide a correct TIN, so a missing form converts directly into a deduction from the first invoice.

• Classification field: record whether the carrier is a corporation, partnership, LLC or sole proprietor. The Form 1099-NEC instructions say payments to corporations are generally not reportable, with stated exceptions such as legal services.
• Freight exception: the same instructions list payments for merchandise, telegrams, telephone, freight, storage and similar items among the payments not reported, so linehaul paid to a carrier is not routinely a 1099-NEC item.
• Threshold change: for tax years beginning after 2025 the instructions set the nonemployee compensation threshold at $2,000. That matters for non-freight services a carrier may also bill, such as yard labour or consulting.
• Name control: a sole proprietor's W-9 may show a personal name with a business name on a second line. Map the invoice name to line 2 and the TIN owner to line 1, or the TIN match will fail.

Indian transporter documents: GSTIN, PAN, RC and the GTA option

For an Indian transporter, verify the GSTIN on the GST portal, confirm the PAN embedded in it, check vehicle registration certificates against VAHAN, and record whether the transporter is a goods transport agency that has opted to pay GST itself. That last flag decides who pays the tax on each freight bill.

The GSTIN carries the transporter's PAN, so a PAN card copy that does not match characters three to twelve of the GSTIN means the two documents belong to different persons. The GST portal's taxpayer search shows the legal name, trade name, status and registration date. A cancelled or suspended GSTIN found here should stop onboarding, because the transporter cannot issue a valid tax invoice for your credit claim.

• VAHAN check: compare each registration number with VAHAN for owner name, vehicle class, fitness validity and insurance validity before the vehicle is added to the vendor's approved list.
• Vehicle owner, not GTA: a truck owner who hires out a vehicle without issuing a consignment note is not a GTA, so the packet should record which role the vendor plays.

A goods transport agency issues a consignment note and is taxed under a choice it makes once. Notification 06/2023-Central Tax (Rate) lets a GTA opt to pay GST itself by filing Annexure V between 1 January and 31 March of the preceding financial year, and that choice continues for later years unless it files Annexure VI to revert to reverse charge. Ask for the filed Annexure V where the transporter claims forward charge.

• Reverse charge default: if no Annexure V is on file, set the vendor's tax code so the recipient pays GST under reverse charge, and the payable system does not accept GST charged on the invoice.
• Forward charge option: if Annexure V is on file, the transporter charges GST on its invoice and you claim credit subject to the usual conditions.
• Annual review: because the option carries forward until Annexure VI is filed, ask each GTA in April whether it reverted for the new financial year.

Income-tax deduction at source is the other India packet item. Payments to a contractor in the business of plying, hiring or leasing goods carriages are exempt from contractor TDS when the transporter owns ten or fewer goods carriages during the year and gives a declaration with its PAN. That rule sat in section 194C(6) of the Income-tax Act, 1961 and continues in section 393 of the Income-tax Act, 2025 from 1 April 2026.

Bank details and payment terms that survive a fraud attempt

Treat bank details as a separate approval with its own evidence: a bank letter or cancelled cheque, a callback to a number you found independently, and an account validation before the first payment. Payment terms belong in the same block, because an Indian micro or small transporter registered under Udyam has a statutory payment ceiling.

Payment diversion usually arrives as a polite email asking you to update remittance details, sent from a lookalike domain days after onboarding. The defence is procedural: the only phone number used for verification comes from the registration record or an earlier signed contract, never from the email requesting the change. Accounts payable makes the call and records who answered, the time and the last four digits confirmed.

• Bank document: a letter on bank letterhead or a cancelled cheque showing the account holder's name exactly as on the W-9 or GSTIN record.
• Account validation: a zero-value or small test credit confirmed by the carrier before the first full payment run.
• Change freeze: any bank change in the first 60 days after onboarding goes to the AP manager with a second callback, because a newly created vendor record has no payment history to compare against.

In India, section 15 of the Micro, Small and Medium Enterprises Development Act, 2006 caps any agreed payment period at 45 days from acceptance of the goods or services, and section 16 adds compound interest at three times the Reserve Bank's bank rate on late payment. Record the transporter's Udyam number at onboarding, so the payable system can set terms of 45 days or less for that vendor.

{
  "carrier_packet_id": "CP-2026-11-0418",
  "market": "US",
  "legal_name": "Ridgeline Freight LLC",
  "usdot_number": "verified_active",
  "authority": { "type": "for_hire_carrier", "status": "active", "viewed_on": "2026-11-09" },
  "boc3_on_file": true,
  "liability_filing": { "form": "BMC-91X", "limit_usd": 1000000, "required_usd": 750000 },
  "cargo_cover": { "limit_usd": 100000, "exclusions_reviewed": true },
  "w9": { "tin_match": "pass", "classification": "LLC_partnership", "backup_withholding": false },
  "remittance": { "callback_number_source": "registration_record", "validated": true, "approved_by": "ap.manager" },
  "release_rule": "tender_allowed = authority.status == 'active' AND boc3_on_file AND liability_filing.limit_usd >= liability_filing.required_usd AND cargo_cover.limit_usd >= max_load_value_usd",
  "payment_rule": "pay_allowed = tender_allowed AND w9.tin_match == 'pass' AND remittance.validated"
}

The record separates the right to tender from the right to pay. A carrier may be cleared to haul on Monday while its bank validation finishes on Wednesday, provided the first invoice will not fall due before then. Splitting the two rules lets operations move without letting finance pay an unverified account.

A first load released before the packet closed

Most onboarding failures are timing failures: the tender goes out before a block closes, and later steps are skipped because the freight has already moved. The trace below shows one illustrative case and the control that would have held the load.

1. Mon 07:12, invite sent: the carrier relations analyst invites a carrier for lane CHI-IND; the packet portal opens record CP-2026-11-0391 with authority and certificate uploaded, W-9 pending.
2. Mon 09:40, tender accepted: the TMS releases load L-552870, valued at $186,000, because the tender screen checks only that the carrier record exists, not that the packet is complete.
3. Tue 15:05, cargo limit found: the insurance coordinator reads the certificate and finds a $100,000 cargo limit with an unattended-vehicle exclusion, $86,000 below the load value.
4. Thu 11:20, payment held: accounts payable receives invoice INV-7741 under a different legal name, no W-9 and a bank letter from a free email domain; the invoice is parked with block code BW-TIN.
5. Controlled version: with the release rule above in the TMS, the tender on Monday fails the cargo check, the load goes to the next carrier in the routing guide, and the new carrier finishes its packet without freight at risk.

The fix was not a better checklist. It was moving the release test into the transaction that commits the freight, so the tender screen reads the packet status instead of the vendor master's existence flag.

Setting up one US carrier and one Indian transporter, in dollars and rupees

The two markets hold the first invoice for different reasons: in the US, a missing TIN triggers backup withholding; in India, a missing transporter declaration triggers contractor TDS and a missing Udyam flag risks a late payment. The figures below are illustrative and show how each packet gap changes the amount and date of the first payment.

The arithmetic is small per invoice, but the cost compounds in disputes. A carrier that is short $576 on its first payment calls dispatch, not accounts payable, and the next tender is declined. Closing the tax block before the first tender is cheaper than explaining a deduction afterwards.

Transporter onboarding in India should capture a ten-vehicle declaration with PAN before the first freight payment, because the contractor TDS exemption formerly in section 194C(6) and now in section 393 of the Income-tax Act, 2025 applies only with that declaration; without it, a ₹48,000 bill to a company loses ₹960.

Checks the onboarding portal enforces and calls a reviewer must make

Comparisons between two records can be enforced by the system every time; interpreting a document that does not match a pattern needs a person. Software, including AI document readers, earns its place by extracting fields from carrier uploads and flagging mismatches, with a named reviewer accepting or rejecting each flag.

Keep the reviewer column small. Every row there costs minutes per carrier, and most carriers should pass on rules alone. If more than one carrier in five needs a reviewer for the same row, the portal is asking for the wrong document or reading it badly.

Carrier packet release in a transportation management system should block tendering until the authority status, BOC-3 designation under 49 CFR 366.2 and liability filing all pass, while bank details clear separately through an accounts payable callback, keeping new-carrier release within two business days for at least 80% of complete packets.

Choosing a tool or service to run the carrier packet

Pick the onboarding tool by whether it reads outside records and writes a release flag your TMS and payable system obey; a polished upload portal alone changes nothing. Ask each vendor or service to run your own sample carriers through the packet during the demo.

The packet sits beside the controls that follow it. Our freight audit checklist starts after the carrier has hauled, testing whether each invoice is valid and correctly priced; this packet decides whether the carrier should be paid at all and in which name. Ongoing service quality belongs in a carrier performance scorecard, and Indian payable matching against LR and POD is covered in freight accounts payable automation. More transport guides are on the logistics and supply chain hub.

Run the pilot on the carriers you will onboard next month rather than on a clean demo set. If you want help writing the packet rules, tender integration or payable controls into a request for proposal, you can send us your requirements and we will map them to your carrier mix and markets.