PCS per diem: authorized travel days vs actual travel days

Eight travel days authorized, but your move takes five? For a straightforward military PCS by privately owned vehicle, with five actual travel days and no leave, TDY, or special delays, the rule is to use five days for en route per diem—not automatically all eight.

The Joint Travel Regulations (JTR), section 0503, base en route per diem on the shorter of authorized and actual travel time. The daily rate and the number of payable days are separate parts of the calculation. See JTR section 0503 and paragraph 050301, Table 5-4.

Source review: October 30, 2026. Policy sources: JTR editions effective October 1, 2024 and August 1, 2025, and DTMO's computation example dated September 4, 2025. Check the current JTR and updates from DTMO for the rules effective on your travel dates, and confirm unusual itineraries with your servicing finance office.

Authorized, actual, and payable days

These terms answer different questions:

• Authorized travel days: the travel-time allowance calculated for the ordered journey and transportation mode.
• Actual travel days: the time used for the official journey, supported by your departure and arrival details. This is not simply a count of days until you choose to sign in.
• Payable days: the days that qualify for travel per diem after applying the travel-time rules and any relevant restrictions or approvals.

DTMO's Service Member Permanent Duty Travel—Elapsed Time Is Less than Authorized example illustrates the distinction. Its member has a five-day maximum for a 1,500-mile journey but departs June 1 and checks in June 4. The result is four travel days. The example applies JTR paragraph 050205-A and compares the maximum with elapsed time.

Worked example: eight days allowed, five used

Assume a member is moving between authorized duty stations within CONUS by privately owned vehicle. Their authorized limit is eight days. They depart November 2 and complete the official journey and report at the new station November 6. There is no leave, TDY, approved additional travel time, or separate dependent travel in this example.

This applies the comparison in DTMO's example to a different itinerary. Eight days is the limit in this scenario, not a guaranteed eight-day payment. If a journey involves leave or other travel statuses, have finance determine the qualifying days before multiplying by a rate.

Does arriving early or delaying sign-in change the answer?

For the simple example above, completing and reporting after five days means the shorter period applies. An instruction to claim eight days merely because eight were permitted leaves out that comparison.

Where physical arrival, leave, and reporting dates differ, provide all of those facts to your finance office. Do not treat delayed sign-in or a voucher's acceptance of an entry as proof of entitlement. JTR paragraph 050205, Table 5-2, addresses shorter elapsed time and travel involving leave; ask your reviewer to apply it to your actual itinerary. JTR paragraph 050205 and Table 5-2

Keep your orders, amendments, itinerary, and supporting documents. The DFAS PCS travel-voucher guide describes the supporting information needed for an Army PCS claim and recommends retaining expense records. Other services should use their servicing travel-pay office's submission process.

Are the mileage rules a daily driving maximum?

JTR paragraph 050205-A uses official distance to calculate an allowance: one day for a journey of 400 miles or less; for longer journeys, divide the official distance by 350 and add a day when the remainder is at least 51 miles. This is a travel-time computation, not by itself a statement that driving farther on a particular day is illegal. Follow applicable safety instructions and your command's travel requirements. The DTMO computation example shows how the mileage calculation works.

Which daily rate should you multiply?

For the member's straightforward PCS drive between authorized locations, JTR paragraph 050301, Table 5-4, provides MALT Plus using the standard CONUS per diem rate. MALT is the mileage component; the “Plus” is per diem. A destination's higher locality TDY rate should not simply be substituted into this example. JTR paragraph 050301, Table 5-4

This example leaves R symbolic rather than using a dollar figure that may be wrong for your travel dates. It also does not import a TDY first/last-day reduction. DTMO explains that first/last-day treatment for PCS depends on the traveler and circumstances and directs service members to section 0503. DTMO per diem guidance

When this example does not cover your move

TDY is temporary duty and has its own calculation rules. Temporary Lodging Expense (TLE) and Temporary Lodging Allowance (TLA) concern temporary accommodation around a move; they are separate benefits, not unused driving days. Military OneSource explains that TLE cannot be paid for the same day as PCS travel per diem.

Civilian relocation also has separate rules: JTR section 0539 covers civilian PCS per diem. Do not apply a military POV example to civilian lodging reimbursement. JTR section 0539

Ask finance to review mixed air/vehicle travel, overseas legs, dependent travel, leave, TDY en route, or delays beyond your control separately. Bring your orders and actual dates and ask which provision supports the payable-day calculation.

For developers and travel operations teams

A published daily rate does not determine the number of payable days. Keep the rate lookup separate from the application's determination of travel status, entitlement, and payable quantities. Preserve the travel dates and the rule assumptions alongside your calculation so someone can explain the result later.

Allowances API provides normalized published rate data and effective-date history, subject to subscription access. Your application must separately determine entitlement and payable days; the API does not validate a PCS voucher or provide a PCS entitlement engine. Explore the API reference and our guide to automating government allowance lookups for the rate-data part of your workflow.