2026 U.S. business trips: $40.27 ESTA, denial, 72-hour rule

The deadline is the one that changes the trip: file the waiver request before departure, not at the gate. The fee follows the filing, and the denial cost follows the fee. For 2026 U.S. business travel, the worksheet should carry lines for approved entry, denial exposure, fallback visa, and validity.

The worksheet is the control

• Set the approved-entry budget line at $40.27.
• Reserve $10.27 for denial exposure.
• Require submission at least 72 hours before departure.
• Price the visitor-visa fallback at about $435.
• Check validity against two years or passport expiry and 90-day stays.

Each line is a control, not a decoration. Timing protects the filing from a gate-side gamble. The approved-entry figure keeps the expected case from being underbudgeted. Denial exposure prevents a refused request from becoming an unexplained expense. The fallback line stops improvisation when the waiver is unavailable. Validity prevents the budget from treating the authorization as a trip-only cost.

Assign the worksheet to the person who owns the trip budget, not the traveler. The traveler should see the filing deadline and the fallback trigger, but the budget owner should keep the cost lines current. The worksheet should be visible in the booking record, so the next reviewer can see what was budgeted and what was approved. When a trip is booked, the worksheet should be checked against the passport, the departure date, and the purpose of the visit. When the trip changes, the details should be rechecked before the booking is made.

The timing item protects the trip

The border agency has stopped real-time approvals, so the request needs lead time. That changes travel policy from a last-minute form to a pre-departure filing. The rule should attach to the booking, not the traveler's memory. If the request is not in, the trip is not ready. The mobility team should treat the filing as a required step in the approval chain, the same way it treats a flight confirmation or a hotel hold.

The paperwork should be completed before the traveler is told the trip is set. If the request is delayed, the team should flag the risk to the business owner and the traveler. If the request is refused, the team should move to the fallback line before the traveler books the next flight.

The fee items keep the budget honest

The approved fee combines travel promotion, a budget-law add-on, and border system operations. That split matters because the operational piece is the part that survives a refusal. The budget should carry the approved-entry line and the denial line separately, even when the traveler expects a smooth approval. The approved-entry line covers the normal case. The denial line covers the case where the request is refused and the trip still incurs a cost.

The expense report should show the line, not just the total. Approved and refused cases should land on their own lines, while visa cases go to the fallback line. Keeping the lines separate makes the audit trail easier and the policy review faster.

The fallback and validity items close the loop

When the waiver is unavailable, the fallback is a visitor visa. The budget should treat that as a separate line, not as an afterthought. The backup option should be visible to the traveler before the trip is set, because travel requirements can change the timing and the cost of the journey. The validity item matters because the authorization is not tied to a single trip. It also sets the limit for business stays, so the travel policy should check the passport and the trip length before the traveler departs.

The passport check should happen at booking, not at the airport. Flag a passport close to expiry before the waiver request is submitted. Confirm the purpose and the return plan when the trip length is near the allowed stay. The same check should happen again before departure.

The worksheet should be reviewed after the trip, not only before it. The actual cost should be matched to the line that was budgeted, and any variance should be noted for the next policy update. The note should say what changed, not just that it changed.