IRP Apportioned Plates: Who Needs Them and How They Work

IRP registration sounds simple when it is reduced to one sentence: get apportioned plates before running a heavy commercial truck across state lines.

That shortcut is useful, but it is incomplete.

The real decision has three separate parts:

1. Does the vehicle meet the IRP definition of an apportionable vehicle?
2. Will it operate in two or more IRP member jurisdictions?
3. Which jurisdiction is legally entitled to register the fleet as the base jurisdiction?

Only after those questions are answered does the carrier get to the application, mileage, fees and cab card.

This matters especially for a new authority because IRP is often discussed together with IFTA, UCR, Form 2290, insurance and operating authority. They are related to the same truck, but they are not the same registration.

A carrier can have an active MC authority and still lack valid apportioned registration.

A truck can display an IRP plate and still lack the authority, insurance, tax credentials or permits needed for the load.

The safest way to understand IRP is therefore not as another startup form.

It is the multijurisdiction registration system for the vehicle.

Start with three trucks, not with a form

The qualification rule becomes clearer when applied to actual operations.

These examples point to the first principle:

IRP qualification is not determined by one number alone.

Who actually needs IRP apportioned registration?

For a property-carrying operation, the practical federal-state framework generally points to IRP when a vehicle is used or intended for use in two or more member jurisdictions and meets at least one of the following vehicle tests:

• a two-axle power unit with gross vehicle weight or registered gross vehicle weight in excess of 26,000 pounds;
• a power unit with three or more axles, regardless of weight;
• a vehicle used in combination when the gross weight of the combination exceeds 26,000 pounds.

The exact Plan wording and the base jurisdiction’s implementation should control the filing decision.

Vehicle / operation	Typical IRP result	Reason
Two-axle power unit, 30,000 lb, interstate	Generally required	Over 26,000 lb and operates in multiple member jurisdictions
Three-axle power unit, 25,000 lb, interstate	Generally required	Three or more axles regardless of weight
Tractor-trailer combination, 80,000 lb, interstate	Generally required	Combination exceeds 26,000 lb
Two-axle 24,000-lb truck, interstate	Not automatically required by the ordinary weight test	Review optional registration, reciprocity and trip permits
Heavy truck operating only inside one state	Usually not an IRP multijurisdiction fleet	Operation is not in two or more member jurisdictions

The distinction between actual weight, gross vehicle weight and registered gross weight should not be guessed from the truck’s empty scale weight.

A tractor that weighs far less than 26,000 pounds by itself can still be part of an 80,000-pound registered combination.

That is why a new carrier should determine its registration weight from the planned equipment and operation before filing.

A one-truck owner-operator can be an IRP fleet

The word fleet causes unnecessary confusion.

IRP does not require a business to own five trucks, ten trucks or even two trucks before apportioned registration becomes relevant.

State IRP guidance expressly treats a fleet as one or more vehicles registered under the Plan.

A one-truck owner-operator can therefore have:

• one IRP account;
• one fleet;
• one power unit;
• one apportioned plate;
• one vehicle-specific cab card.

The registration obligation follows the qualifying vehicle and operation, not the size of the company.

This is particularly important for a carrier following the own-authority startup process. The business can be small enough that the owner is also the driver, dispatcher and safety manager while still being fully inside IRP, IFTA and FMCSA compliance systems.

What the International Registration Plan actually does

IRP is a registration reciprocity agreement among participating U.S. states, the District of Columbia and Canadian provinces.

Instead of buying a permanent full-year vehicle registration separately in every member jurisdiction, the registrant works through one base jurisdiction.

That jurisdiction:

• processes the fleet registration;
• calculates the apportioned fees;
• collects the amount due;
• issues the apportioned registration credentials;
• distributes the appropriate fee shares to the other member jurisdictions;
• maintains the account for renewal and audit.

The carrier receives an apportioned plate and a cab card for the vehicle.

The result is one registration system for multijurisdiction operation.

Full reciprocity does not mean free registration

Under IRP full reciprocity, an apportioned vehicle receives registration recognition throughout IRP member jurisdictions without the old process of adding each state or province individually to the cab card.

That does not mean:

• registration is free outside the base state;
• every weight is legal everywhere;
• oversize or overweight permits disappear;
• state operating authority disappears;
• fuel taxes disappear;
• the vehicle can ignore local registration restrictions.

The registration fees are still apportioned using the Plan’s distance and jurisdiction fee structure.

The advantage is administrative reciprocity, not exemption from the underlying cost of registration.

The cab card is more important than the plate alone

The apportioned plate identifies the power unit as registered through IRP.

The cab card provides the detailed vehicle-specific registration record.

Depending on the jurisdiction and format, the cab card can identify information such as:

• registrant;
• fleet;
• vehicle identification number;
• unit number;
• make and model information;
• registered weights;
• registration period;
• IRP jurisdictions.

A carrier should review the cab card immediately after issuance.

Do not wait for a roadside inspection to discover:

• wrong VIN;
• wrong unit;
• wrong legal name;
• insufficient registered weight;
• incorrect plate information;
• wrong registration period.

The cab-document system should also ensure the current cab card is available in the vehicle in the format recognized by the jurisdictions where it operates.

IRP is not the same as IFTA

The two systems are often filed at the same time because they apply to many of the same interstate heavy vehicles.

Their purpose is different.

Issue	IRP	IFTA
Main purpose	Apportion vehicle registration fees	Report and settle motor-fuel use tax
Main credential	Apportioned plate and cab card	IFTA license and decals
Core operating data	Distance by jurisdiction	Distance and fuel by jurisdiction
Typical filing cycle	Registration and annual renewal	Quarterly tax returns plus annual credentials
Does it replace the other?	No	No

Because the same trip can support both systems, carriers often use the same underlying mileage source.

But a software report labeled “IFTA” is not automatically an adequate IRP record.

Texas specifically warns that buying an ELD does not guarantee IRP or IFTA recordkeeping compliance and that there is no special “IRP-certified ELD.”

The source record must still contain enough detail to support the distance actually reported.

IRP is also different from UCR, MC authority and Form 2290

A new carrier should keep these obligations separate in its startup file.

USDOT Number identifies the motor carrier for federal safety and registration purposes when required.

Operating authority permits specified for-hire interstate operations when required. See USDOT vs. MC Number.

UCR is an annual registration for covered interstate entities.

IRP apportions vehicle registration.

IFTA apportions fuel-use tax reporting.

Form 2290 / HVUT is a federal heavy highway vehicle use tax filing that can affect registration evidence for heavy vehicles.

Insurance and FMCSA filings establish required financial responsibility and maintain authority.

No single receipt proves that the entire carrier is dispatch-ready.

That is why the first-90-day authority plan treats each credential as a separate control.

Choose the base jurisdiction before starting the application

A carrier does not simply select whichever state appears to have the lowest plate fee.

The base jurisdiction is the IRP member jurisdiction through which the fleet qualifies to register.

Current state guidance commonly looks for factors such as:

• a qualifying physical business location or residency basis;
• a connection between the registrant and the jurisdiction;
• operational records maintained there or made available there;
• fleet distance accrued in that jurisdiction when required;
• legal entity registration;
• USDOT and FEIN consistency;
• authority and insurance status for for-hire carriers.

The exact documentation is controlled by the Plan and the chosen jurisdiction’s rules.

For example, Oregon requires an Oregon-based physical address for its ordinary IRP application route and separately provides proof-of-residency procedures. Wisconsin states that a registrant may qualify through an established place of business or, for an owner-operator, through qualifying residency, while also requiring Wisconsin mileage and audit access to records.

The practical lesson is more important than memorizing one state’s list:

Do not create a paper address merely to obtain cheaper apportioned registration.

A virtual office, mailbox or unrelated address can fail a base-jurisdiction review when it does not satisfy the Plan and state requirements.

Keep the legal identity consistent

Before filing, compare the business name across:

• Secretary of State record;
• EIN / IRS record;
• USDOT registration;
• operating authority;
• insurance;
• vehicle title or lease;
• IRP application;
• IFTA application;
• UCR.

Small differences can create processing delays.

Examples:

• ABC Transport LLC versus ABC Transportation LLC;
• personal name on title but LLC on application;
• old business address on USDOT record;
• DBA used where legal entity is requested;
• different FEIN associated with the carrier record.

Correct the identity first rather than forcing the IRP application through inconsistent records.

The application sequence for a new one-truck carrier

The exact portal, form names and supporting documents vary by base jurisdiction.

The sequence, however, can be organized consistently.

A practical first-time IRP registration sequence

1. 01
   Confirm the truck qualifies

   Review axle count, gross or registered gross weight, combination weight and intended multijurisdiction operation before paying for an account or permit.

2. 02
   Confirm the base jurisdiction

   Verify that the business satisfies the jurisdiction's place-of-business or residency requirements and can maintain the required operational connection and records.

3. 03
   Clean up the carrier identity

   Make the legal name, FEIN, USDOT record, authority, insurance and vehicle ownership or lease documentation consistent.

4. 04
   Prepare vehicle and weight information

   Collect VIN, title or ownership evidence, unit number, year, make, axle configuration and the weights needed for the intended operation.

5. 05
   Determine the distance method

   Use qualifying actual reporting-period distance when it exists. A genuinely new fleet without actual distance generally uses the official Average Per Vehicle Distance method rather than self-created state estimates.

6. 06
   Provide related tax and registration evidence

   Submit Form 2290 proof, insurance, authority, UCR or other documentation when the base jurisdiction requires it for the vehicle and operation.

7. 07
   Review the invoice before paying

   Confirm vehicles, weights, distance basis and jurisdiction fees. Do not treat the first amount displayed as automatically correct.

8. 08
   Verify the issued credentials

   Match the plate and cab card to the exact truck, legal entity, weight and registration period before dispatch.

The best filing strategy is to prepare the evidence before entering the portal.

Repeatedly changing answers during an application can create inconsistent records and processing questions.

What documents should a new carrier expect to prepare?

No universal document list works for every base jurisdiction.

A new one-truck authority should nevertheless expect requests involving several of these categories:

Business identity

• legal entity record;
• FEIN evidence;
• physical address or residency evidence;
• contact information;
• authorized signer.

Federal carrier identity

• USDOT Number;
• current carrier record;
• operating authority when required;
• proof that legal names match.

Vehicle

• title or ownership evidence;
• VIN;
• year, make and model;
• unit number;
• axle information;
• purchase or lease documentation;
• registered weight.

Lease relationship

• owner-operator lease when the vehicle is operated under another carrier;
• identification of who is responsible for registration;
• USDOT Number of the responsible motor carrier where required.

Tax and registration

• Form 2290 / Schedule 1 evidence when applicable;
• UCR status where the base jurisdiction checks it;
• IFTA account information when filed together;
• prior IRP account information if the vehicle or fleet is transferring.

Insurance

• evidence required by the base jurisdiction;
• correct legal entity;
• active for-hire authority and insurance where required before processing.

The application office can ask for additional proof when the account, business address, prior registration or mileage history creates questions.

New carriers should not invent projected mileage

This is one of the most important distinctions for a new authority.

A carrier opens its first IRP account and thinks:

“I expect to run mostly Texas, Oklahoma and Arkansas, so I will estimate 60%, 25% and 15%.”

That is not how a new-fleet distance calculation should normally be created under the current IRP framework.

When a fleet has actual distance during the applicable reporting period, that qualifying actual distance is generally used.

When the fleet accrued no actual distance during the reporting period, the base jurisdiction uses Average Per Vehicle Distance, commonly abbreviated APVD, according to the Plan’s method and the official jurisdiction chart.

Texas expressly states that a fleet with no actual distance during the reporting period must use average per-vehicle distance. Nevada likewise directs first-time apportioned registrations without prior mileage history to its APVD chart.

APVD is not your business forecast

The APVD calculation does not predict where the carrier will actually haul next year.

It provides a standardized distance basis for allocating the first registration fee when the fleet lacks qualifying historical mileage.

After the carrier develops actual operations, renewal uses the applicable actual reporting-period mileage under the Plan and base-jurisdiction process.

That creates a simple lifecycle:

new fleet without qualifying history → APVD

operating fleet with qualifying history → actual jurisdiction distance

Existing mileage cannot always be erased by opening a new account

A carrier that moves its base jurisdiction, transfers an existing vehicle or reorganizes an account should not assume it can claim to be a zero-history fleet.

State guidance can require existing actual mileage to follow the operation when that mileage exists.

Nevada, for example, specifically warns relocating carriers that actual mileage from a previous jurisdiction must be used when available rather than replaced with estimated mileage.

The safe approach is to disclose the prior operation and let the base jurisdiction determine the correct treatment.

How IRP fees are calculated

There is no single national price for “an IRP plate.”

The fee is built from multiple jurisdictions’ registration schedules and the fleet’s apportionment percentages.

At a high level, the calculation works like this:

1. determine the fleet’s distance basis;
2. calculate the percentage of total distance attributable to each jurisdiction;
3. apply that percentage to the relevant registration fee in each jurisdiction, subject to the Plan and local fee structure;
4. combine the apportioned jurisdiction amounts and applicable base-jurisdiction charges.

For a simplified illustration, assume a fleet’s qualifying actual distance were:

• Texas: 50,000 miles;
• Oklahoma: 20,000 miles;
• Arkansas: 15,000 miles;
• Louisiana: 15,000 miles.

Total: 100,000 miles.

The distance percentages would be:

• Texas: 50%;
• Oklahoma: 20%;
• Arkansas: 15%;
• Louisiana: 15%.

Those percentages are then applied within the IRP fee calculation using each jurisdiction’s applicable registration fee structure and the vehicle’s registered weight.

This is why two carriers with identical tractors can receive different IRP invoices.

Their:

• base jurisdictions;
• weights;
• actual distance mix;
• fleet composition;
• registration periods;
• local fees

can differ.

Why registered weight deserves its own review

IRP is not only a mileage calculation.

The weight shown for the vehicle can materially affect:

• registration fees;
• legal operating weight;
• enforcement review;
• whether additional credentials or permits are needed.

A carrier should register the vehicle for the weight required by the actual operation rather than simply choosing the lowest number accepted by the portal.

At the same time, IRP registration does not authorize oversize or overweight operation by itself.

Jurisdiction-specific:

• axle limits;
• bridge formulas;
• oversize permits;
• overweight permits;
• route restrictions

continue to apply.

A cab card should therefore be read as registration evidence, not as a universal permit to move any weight on any road.

IRP records begin with the first mile

The first renewal should not be the moment a carrier starts thinking about mileage records.

Operational records should begin when the truck begins moving.

A defensible IRP distance system should be able to reconstruct:

• date of trip;
• trip origin;
• trip destination;
• route traveled;
• beginning and ending odometer or similar readings where required;
• total trip distance;
• distance by jurisdiction;
• unit or VIN;
• registrant or fleet identification;
• driver information where required.

State audit guidance also emphasizes an important point:

all movement matters.

That includes:

• loaded miles;
• empty miles;
• deadhead;
• bobtail;
• movement under trip permits.

The registration fee is based on vehicle movement, not on whether a broker paid for the mile.

Paid miles are not IRP miles

A rate confirmation might pay:

• 900 loaded miles.

The truck might actually travel:

• 80 miles to pickup;
• 915 miles on the route used;
• 25 miles to parking after delivery.

Operational movement:

1,020 miles

Paid loaded miles:

900 miles

Using the 900-mile commercial figure as the registration record would omit 120 actual vehicle miles.

That is why dispatch miles and settlement miles should not be treated automatically as IRP source data.

ELD data can help, but the export must be tested

Many one-truck carriers already have GPS and ELD data capable of supporting jurisdiction mileage.

The question is whether the system preserves the information needed for audit.

Before relying on a provider, export a completed month and answer:

• Does the report identify the exact power unit?
• Can it show total distance by jurisdiction?
• Can individual trips be reconstructed?
• Does total jurisdiction distance reconcile to odometer movement?
• Are empty and bobtail miles captured?
• What happens when GPS loses signal?
• Can records be downloaded after cancellation?
• How far back does the provider retain data?

Texas explicitly warns carriers that purchasing an ELD does not guarantee IRP or IFTA record compliance.

The carrier owns the recordkeeping risk even when the data is created by a vendor.

Build IRP and IFTA from one mileage control

Although IRP and IFTA are separate systems, maintaining two unrelated mileage histories creates unnecessary risk.

A better one-truck workflow is:

Trip movement

→ ELD / GPS / odometer source

→ jurisdiction mileage ledger

→ monthly reconciliation

→ IRP annual reporting dataset

→ IFTA quarterly mileage dataset

The two filings can then use the same underlying movement records while applying different legal calculations.

The carrier should investigate any period where:

• IRP mileage differs from IFTA mileage without explanation;
• ELD miles do not reconcile to odometer change;
• one state repeatedly shows zero despite routes through that state;
• fuel purchases appear in jurisdictions with no reported travel;
• total trip distance is substantially below dispatch/GPS history.

A small discrepancy can have a legitimate explanation.

An unexplained pattern is the problem.

How long should IRP records be kept?

Retention is an area where the base jurisdiction’s instructions should be followed precisely.

Several state IRP programs require carriers to retain the records supporting apportioned registration for a multi-year audit period. Oregon instructs carriers to keep the current registration year and three prior years, and Nevada instructs its carriers to maintain operational records for four years.

For a new one-truck business, the practical system is simple:

• never delete the prior year’s mileage file after renewal;
• maintain a rolling multi-year archive;
• keep raw source records as well as summaries;
• preserve the version actually used to prepare the application;
• retain audit correspondence and corrections.

A spreadsheet showing annual totals is useful.

It is not a substitute for the records that produced those totals.

IRP accounts can be audited

Apportioned registration is not a self-certification system that ends when the plate arrives.

Base jurisdictions maintain IRP audit programs to verify whether reported distance and fees were accurate.

Texas explains that each base jurisdiction must audit an average of 3% of renewed fleets annually under the Plan’s audit framework.

A one-truck carrier should therefore be able to move from an annual number back to the source trip.

For example:

Arkansas annual distance: 12,486 miles

The carrier should be able to show how that total was built from identifiable vehicle movements rather than answering:

“That is what the ELD dashboard said last year.”

Audit risk is usually a record problem before it is a math problem

Common weak evidence includes:

• annual mileage totals with no trip detail;
• screenshots instead of exportable records;
• dispatch miles rather than actual route miles;
• missing odometer continuity;
• deleted ELD history;
• driver-created spreadsheets with no source documents;
• one total combining two trucks;
• missing deadhead;
• mileage recorded only when fuel was purchased;
• unverified software summaries.

A good system can explain where every jurisdiction total came from.

What happens when the carrier adds a truck?

The second truck is not simply a duplicate insurance event.

It can change the IRP account.

Before dispatching the added unit, determine how the base jurisdiction requires the vehicle to be added to the existing fleet.

Prepare:

• title or ownership evidence;
• VIN;
• weight;
• unit number;
• lease documentation when applicable;
• Form 2290 evidence when applicable;
• insurance information;
• registration fees.

The carrier should not move the truck interstate merely because another truck in the company already has an apportioned plate.

IRP credentials are vehicle-specific.

What happens when the carrier replaces or sells a truck?

A vehicle change should trigger both registration and recordkeeping controls.

When replacing a unit:

1. record the final date and odometer of the old truck;
2. preserve its mileage history;
3. follow the base-jurisdiction transfer or supplement process;
4. register the replacement correctly;
5. verify the new cab card;
6. remove old credentials as required;
7. update IFTA, insurance, ELD and company records.

Do not erase the old vehicle from the accounting system as though it never existed.

Its distance can remain relevant to the fleet’s reporting period and later audit.

Leased-on owner-operators need to know who is the registrant

An owner-operator leased to another motor carrier can encounter a different IRP structure from an owner operating under their own authority.

State IRP manuals recognize arrangements in which:

• the owner-operator is the registrant and maintains the required IRP records; or
• the lessee motor carrier registers the vehicle and assumes the applicable registration and recordkeeping responsibility.

The exact arrangement should be documented in the lease and accepted by the applicable base jurisdiction.

Before assuming the carrier’s plate solves the issue, the owner-operator should identify:

• whose name is on the registration;
• whose IRP account contains the vehicle;
• which USDOT Number is associated as required;
• who keeps the distance records;
• who pays registration charges;
• what happens to the plate and cab card when the lease ends.

This is another example of why “owner-operator” does not describe one legal structure.

Can a carrier use trip permits instead of IRP?

A temporary trip permit can sometimes be used when a vehicle is not apportioned for an operation that requires registration in another jurisdiction.

This can make sense when interstate travel is genuinely occasional.

But trip permits are jurisdiction-specific.

The carrier must verify:

• whether the jurisdiction offers the permit;
• permit duration;
• vehicle and weight covered;
• route or operation restrictions;
• purchase timing;
• cost;
• whether separate fuel permits are also needed.

Do not treat one state’s permit as permission for the entire trip.

Compare annual IRP with repeated permit friction

Suppose a non-apportioned truck begins crossing state lines every week.

The carrier may face repeated:

• permit purchases;
• dispatch delays;
• administrative fees;
• risk of entering a jurisdiction before the permit is active;
• separate fuel-tax permit questions.

At that point, permanent apportioned registration may be operationally superior even when a particular vehicle falls within optional registration rules.

The decision should consider frequency and administrative reliability, not just the price of one permit.

A truck under 26,001 pounds needs a more careful answer

The internet often reduces IRP to:

“Over 26,000 pounds = IRP. Under 26,000 pounds = no IRP.”

That is too crude.

A two-axle power unit at or below 26,000 pounds may fall outside the ordinary mandatory weight threshold.

But the carrier still has to examine:

• axle count;
• combination weight;
• whether optional IRP registration is available;
• whether another jurisdiction requires registration for intrastate activity there;
• reciprocity agreements;
• temporary permit rules.

Pennsylvania, for example, explicitly states that certain vehicles or combinations at 26,000 pounds or less may be apportioned at the registrant’s option.

The correct question is therefore:

“What registration does this exact vehicle need for this exact multistate operation?”

not merely:

“Is the truck under 26,001 pounds?”

IRP renewal is where the first year’s recordkeeping gets tested

A new carrier’s first application can feel document-heavy.

The first renewal exposes whether the business actually maintained usable distance records.

The carrier should prepare renewal before the deadline by:

• identifying the correct IRP reporting period;
• confirming all vehicles that operated during that period;
• including applicable distance from units later sold or removed;
• totaling actual distance by jurisdiction;
• reconciling totals to source records;
• comparing IRP distance with IFTA records;
• reviewing registered weight;
• updating business and vehicle information;
• verifying current Form 2290 evidence where required;
• reviewing UCR, authority and insurance status as required by the base jurisdiction.

The renewal process is not a request to estimate where the business plans to run next year.

It is primarily a registration calculation built from the required historical reporting period and current fleet information.

A one-truck renewal example

Assume Unit 101 operated throughout the relevant reporting period.

The carrier’s records show:

• Texas: 48,200 miles;
• Oklahoma: 12,400 miles;
• Arkansas: 8,900 miles;
• Louisiana: 6,500 miles;
• New Mexico: 4,000 miles.

Total distance:

80,000 miles

The carrier should not report only the states where it picked up paying freight.

If it deadheaded 600 miles through New Mexico, those vehicle miles remain part of the operational distance record.

If it used a trip permit during a period of operation, those miles should still be captured in the underlying distance system even though the permit handled registration authority for that trip.

The annual summary should reconcile to the source vehicle movement.

The six IRP failures that matter most for a new authority

Rather than another generic checklist, the most useful way to review IRP risk is to look at the six decisions that can stop a truck or create an expensive correction.

1. Registering in a state the business cannot legitimately use as its base

A cheap address is not an IRP strategy.

Fix the physical presence, residency and operational-record question before filing.

2. Choosing the wrong weight

Under-registering the truck to reduce fees can create enforcement and permitting problems.

Register for the operation the carrier actually intends to run.

3. Treating APVD as a personal estimate

A genuinely new fleet without actual reporting-period distance should use the official average-distance method required by the Plan and base jurisdiction.

Do not manufacture a mileage forecast.

4. Treating dispatch miles as actual miles

IRP records should capture movement, including deadhead and bobtail.

The invoice paid by the broker is not the registration odometer.

5. Assuming an ELD automatically creates an audit file

Test the export before relying on it.

A dashboard that disappears after cancellation is a recordkeeping vulnerability.

6. Treating the plate as the final startup credential

IRP is one part of dispatch readiness.

Before the first regulated interstate load, separately verify:

• USDOT status;
• required operating authority;
• insurance and filings;
• BOC-3;
• UCR;
• IFTA;
• Form 2290;
• IRP;
• state permits;
• driver and vehicle compliance.

The practical IRP decision for a new carrier

For a typical one-truck interstate tractor-trailer business, the answer is usually straightforward:

• the combination operates in multiple IRP jurisdictions;
• the weight exceeds 26,000 pounds;
• the vehicle therefore belongs in apportioned registration unless a specific exemption or lawful temporary permit structure applies.

The harder questions are not whether the acronym exists.

They are:

• Which jurisdiction can legitimately be the base?
• Which entity should be the registrant?
• What weight should appear on the registration?
• Does actual reporting-period mileage already exist?
• If not, which APVD figures apply?
• Can the carrier produce the mileage records during an audit?

A carrier that answers those six questions before filing is far less likely to discover a registration problem at the scale house.