2026 Guide to DCAA Per Diem Compliance for Government Contractors

Meta description

A practical 2026 guide to DCAA per diem compliance for government contractors. Learn how to document travel costs, preserve historical rates, and support GSA, DTMO, and State Department per diem calculations during audits.

Government contractors often know which per diem table applies after checking a source finder or internal travel policy. The harder part is proving that the rate used in a proposal, expense report, invoice, or incurred cost submission was correct for the trip date.

This guide focuses on compliance and audit support. It is designed to complement our Federal Allowance Source Finder, which explains when to use GSA, DTMO, or Department of State rate sources.

Who this guide is for

This guide is for:

• Proposal managers pricing travel in federal bids
• Finance teams reviewing travel claims
• Project controllers building travel budgets
• Accounting teams preparing incurred cost submissions
• Small businesses setting up DCAA-ready travel documentation
• ERP, HRIS, and expense-system administrators automating rate lookups

The focus is contractor travel cost support, especially when per diem rates are used as the basis for lodging, meals, and incidental expenses.

The compliance issue: using the right rate is only step one

For federal contractors, per diem compliance is not only about finding a rate. The audit question is usually broader:

Can you show which rate applied, when it applied, where it came from, and how it was used?

A compliant travel record should answer these questions:

GSA publishes CONUS per diem rates, DTMO explains that per diem rate responsibility is shared across GSA, DoS, and DTMO, and the Department of State publishes foreign per diem rates under DSSR 925. :contentReference[oaicite:0]{index=0}

2026 per diem compliance checklist

Use this checklist before submitting a proposal, approving an expense report, or preparing audit support.

1. Classify the destination

Identify whether the trip is:

• CONUS
• Non-foreign OCONUS
• Foreign

This classification determines the rate source. CONUS rates generally come from GSA. Non-foreign OCONUS rates generally come from DTMO. Foreign per diem rates come from the Department of State. DTMO describes federal per diem rate calculation as a shared responsibility of GSA, DoS, and DTMO. :contentReference[oaicite:1]{index=1}

2. Match the rate to the travel date

Use the rate that was effective for the date of travel, not the rate visible on the website today.

For FY 2026 CONUS travel, GSA states that rates are effective October 1, 2025, through September 30, 2026. GSA’s rate tool also allows users to select travel dates for rate lookup. :contentReference[oaicite:2]{index=2}

3. Separate lodging from M&IE

Do not store only the total per diem if your accounting or audit process needs the components.

Track:

• Lodging rate
• Meals and incidental expenses rate
• Total per diem, if used
• Lodging nights
• M&IE days
• First-day or last-day adjustments, when applicable
• Any company-policy reductions

4. Keep the source and effective date

Each travel calculation should preserve:

• Rate source
• Location name
• Rate effective date
• Lookup date
• Travel date
• Lodging amount
• M&IE amount
• Any season or locality identifier
• Screenshot, PDF, export, or system-generated rate record

This is especially important for historical trips because rate tables can change.

5. Reconcile company policy with federal ceilings

FAR 31.205-46 allows contractor travel costs for lodging, meals, and incidental expenses to be based on per diem, actual expenses, or a combination, provided the method produces a reasonable charge. The same section places limits on allowable costs, including the applicable maximum per diem rates except in special or unusual circumstances. :contentReference[oaicite:3]{index=3}

Your company policy may be stricter than the federal ceiling. A stricter internal cap can reduce reimbursable amounts, but it should be documented and applied consistently.

6. Preserve support for exceptions

If a trip includes an exception, retain the approval and explanation.

Examples include:

• Actual lodging above the standard ceiling
• Conference hotel requirements
• Remote or limited lodging availability
• Long-term travel adjustments
• Customer-directed travel rules
• Contract-specific travel clauses
• Special or unusual circumstances under the applicable cost principle

GSA per diem compliance for CONUS travel

Use GSA for travel within the continental United States. For 2026 planning, GSA’s FY 2026 CONUS rates are effective from October 1, 2025, through September 30, 2026. :contentReference[oaicite:4]{index=4}

What to retain for GSA-based travel

Common GSA compliance issues

• Using a nearby major city instead of the correct locality
• Applying the current fiscal-year rate to a prior-year trip
• Mixing lodging and M&IE without retaining component detail
• Failing to document first-day and last-day treatment
• Pricing proposals using outdated spreadsheet copies

DTMO per diem compliance for non-foreign OCONUS travel

Use DTMO for non-foreign OCONUS destinations such as Alaska, Hawaii, and U.S. territories.

DTMO describes per diem as a set allowance for lodging, meal, and incidental costs incurred during official government travel. It also explains that per diem rate responsibility is divided among GSA, DoS, and DTMO. :contentReference[oaicite:5]{index=5}

What to retain for DTMO-based travel

Common DTMO compliance issues

• Treating Hawaii or Alaska as CONUS
• Using State Department foreign rates for U.S. territories
• Missing monthly or interim rate updates
• Ignoring locality footnotes
• Losing the rate table version used for a historical trip

Department of State per diem compliance for foreign travel

Use Department of State foreign per diem rates for foreign destinations. State publishes foreign per diem rates by location under DSSR 925. :contentReference[oaicite:6]{index=6}

Foreign rates may include seasonal date ranges. For audit support, the date range matters as much as the country and city.

What to retain for State Department foreign travel

Common State Department compliance issues

• Using “Other” when a specific post exists
• Missing a seasonal rate change
• Applying a current foreign rate to a historical trip
• Confusing foreign per diem with post allowance or COLA
• Using State Department rates for non-foreign OCONUS locations

DCAA audit support: what auditors usually need to see

DCAA audit support often centers on whether the cost is allowable, allocable, reasonable, and supported. For travel, the per diem rate is only one piece of the support package.

A strong travel file usually includes:

• Travel authorization or approval
• Expense report or voucher
• Travel dates and destination
• Business purpose
• Contract, project, or cost objective
• Receipts where required
• Per diem source and effective date
• Calculation worksheet or system output
• Approval for exceptions or over-ceiling costs
• Evidence that company policy was followed

FAR 31.205-46 states that lodging, meals, and incidental expenses may be based on per diem, actual expenses, or a combination, provided the method results in a reasonable charge. It also limits allowable costs to applicable maximum per diem rates except for special or unusual situations. :contentReference[oaicite:7]{index=7}

Historical per diem rates: the audit trail problem

Historical travel creates a common compliance gap. A finance analyst may be able to find today’s rate in minutes, while the correct rate for a trip from a prior fiscal year or prior rate cycle may be harder to reconstruct.

This creates risk when:

• Travel is audited months or years later
• Proposal models use stale rates
• Expense systems overwrite current rate tables
• PDF rate tables are saved without effective dates
• Spreadsheets do not preserve the data source
• Foreign or OCONUS rates changed during the trip period

Recommended historical-rate controls

Proposal pricing: per diem compliance before the trip happens

Proposal teams often use per diem rates before travel occurs. The compliance goal is different from an expense report, but the documentation still matters.

For proposal pricing, retain:

• Assumed destination
• Assumed travel dates or period of performance
• Rate source
• Rate effective date
• Lodging and M&IE assumptions
• Number of travelers
• Number of trips
• Number of lodging nights
• M&IE days
• Escalation or update assumptions
• Any solicitation-specific travel instructions

Proposal pricing tips

• Use the rate effective for the expected travel period when known.
• If future rates are not available, document the current rate and update assumptions.
• Keep a copy of the rate table used in the pricing file.
• Revalidate travel rates before final proposal submission when timelines change.
• Check whether the solicitation limits travel reimbursement or requires a specific method.

Expense reimbursement: per diem compliance after the trip

Expense processing should confirm that the reimbursed amount matches the approved method.

For each trip, review:

• Was the correct source used for the destination?
• Was the correct date or rate period used?
• Were lodging and M&IE calculated separately where required?
• Were first and last travel days handled according to policy?
• Were receipts collected where required?
• Were exceptions approved before payment?
• Was the cost charged to the correct contract or cost objective?

A consistent review process is easier to defend than ad hoc manual checks.

ERP and spreadsheet compliance risks

Many per diem errors start in systems rather than in policy.

Common system issues include:

• Rate tables updated without version history
• Location names typed manually
• Missing effective-date fields
• Old spreadsheets reused for new trips
• GSA, DTMO, and State data stored in separate formats
• Manual copy-and-paste errors from public websites
• No audit log for rate changes
• No automated validation against travel dates

Recommended system fields

At minimum, store these fields for every per diem calculation:

2026 per diem compliance workflow

Use this workflow for repeatable travel compliance.

Step 1: Identify the travel destination

Capture the exact destination before looking up a rate. Avoid broad labels such as “OCONUS” or “international” in the calculation file.

Step 2: Select the source

Use your source finder, travel policy, or system rules to select GSA, DTMO, or State.

Step 3: Lookup the rate by date

Query the rate using the travel date, not only the current date.

Step 4: Calculate lodging and M&IE

Keep the components separate, even if your report also displays a total.

Step 5: Apply policy rules

Apply company policy, contract clauses, customer instructions, and any first-day or last-day rules.

Step 6: Save the evidence

Preserve the rate source, effective date, calculation output, and approval record.

Step 7: Lock the record

Once the claim, invoice, or proposal file is finalized, keep the supporting rate version attached to the record.

Practical examples

Example 1: Trip to Atlanta in February 2026

A contractor employee travels to Atlanta for a customer meeting in February 2026.

Compliance file should show:

• Source: GSA
• Fiscal year: 2026
• Destination: Atlanta locality used in lookup
• Travel dates
• Lodging rate
• M&IE rate
• Calculation method
• Expense approval

Example 2: Trip to Honolulu in May 2026

A contractor employee travels to Honolulu for official project work.

Compliance file should show:

• Source: DTMO
• Destination: Honolulu or applicable locality
• Effective date of the rate table
• Lodging rate
• Meals and incidentals components
• Travel dates
• Support for any lodging exception

Example 3: Trip to Nairobi in July 2026

A contractor employee travels to Nairobi for an international project.

Compliance file should show:

• Source: Department of State
• DSSR 925 foreign per diem rate
• Country and post
• Applicable season or rate period
• Lodging rate
• M&IE rate
• Travel dates
• Source snapshot or system lookup record

Example 4: Historical audit for travel from 2024

An auditor requests support for travel costs incurred in 2024.

The team should be able to produce:

• The original expense report
• The travel approval
• The rate source used at the time
• The rate effective for the travel date
• The calculation worksheet or system record
• Any exception approval
• Evidence that the cost was charged to the correct project or contract

Red flags in a per diem audit

Review these before an incurred cost submission or internal audit:

• Current rates used for old trips
• Missing effective dates
• Missing source names
• No distinction between CONUS, non-foreign OCONUS, and foreign
• Lodging and M&IE stored only as a combined total
• Manual spreadsheet rates with no source snapshot
• Multiple location names for the same destination
• Unapproved lodging above the ceiling
• No record of first-day or last-day treatment
• Proposal rates that cannot be tied to an effective source table

How Allowances API helps

Allowances API helps teams automate per diem and allowance lookups across GSA, DTMO, and Department of State data.

Common use cases include:

• ERP travel modules
• Expense report validation
• Proposal pricing spreadsheets
• Historical rate audits
• Incurred cost support
• Contract travel budgeting
• Payroll and global mobility workflows
• Rate change monitoring

The goal is to make each calculation traceable:

• Source
• Location
• Effective date
• Travel date
• Lodging rate
• M&IE rate
• Historical rate version
• Calculation output

That structure gives finance, proposal, and compliance teams a stronger audit trail than manual downloads and copy-paste spreadsheets.

Related resources

• Federal Allowance Source Finder
• Post Allowance / COLA Calculator
• Temporary Quarters Subsistence Allowance Calculator
• Federal per diem lookup
• Historical allowance and per diem rate lookup

Disclaimer

This guide is for general informational purposes and planning support. Per diem allowability, reimbursement, billing, and audit outcomes depend on FAR clauses, contract terms, company policy, travel approvals, agency guidance, and the facts of each trip. Always confirm requirements with your contracting officer, auditor, finance team, or legal advisor when needed.