Key takeaways
- Federal travel is governed by the Federal Travel Regulation (FTR), which limits lodging and meals and incidental expenses (M&IE) to GSA-published maximum rates by locality; many state and local agencies adopt the same rates.
- Agencies must validate every travel claim against the current GSA schedule to avoid improper payments flagged by inspectors general and external auditors.
- Staff who travel across several localities on one trip require tracking different GSA rates for lodging and meals by day and location.
- Non-compliance results in improper payments, repayment demands, audit findings and scrutiny of the appropriation or grant that funded the trip.
- Vergo proposes coding by inference from your own accounting structure and history and applies per diem policy flags at submission, so travelers see GSA caps before claims are processed.
Where should you go next?
- Learn more about Vergo Employee Reimbursements
- Learn more about Vergo Expense Management
- Learn more about Vergo AP Invoice Automation
Why federal per diem rules exist
Per diem and travel reimbursements follow strict rules because agency travel is paid from appropriated public funds, and the Federal Travel Regulation (FTR), issued by GSA, sets what federal travelers may be reimbursed. The FTR limits lodging to the GSA maximum rate for the location and pays M&IE at a flat daily locality rate, with first and last travel days paid at 75 percent. GSA publishes daily lodging and M&IE rates by locality, updated each federal fiscal year. These rates ensure travel is reimbursed consistently and reasonably across programs, regardless of which office approves it. Many state, county and municipal agencies adopt GSA rates in their own travel policies, and grant-funded travel usually has to follow them too. Every claim that doesn't align with the published thresholds risks being flagged as an improper payment at audit. Vergo flags claims above your configured thresholds at submission, so finance staff don't process non-compliant claims unknowingly.
Why government agencies face unique challenges
Agencies face structural complexity that magnifies compliance risk. An inspection program might send staff across three counties with different GSA locality rates in one week. A multi-office agency might send employees from several regions to the same training, each with different home-station rules. Unlike a small office with a few travelers, a department with dozens of inspectors, auditors or program staff on the road faces many per diem claims weekly — each one charged to a fund, program and sometimes a grant with its own allowability rules. Contributing factors include GSA locality rates that change each fiscal year and vary by city and county, travelers moving between localities mid-trip that trigger partial-day M&IE calculations, and grant-funded travel that must also meet the grantor's cost principles. Supervisors often approve reimbursements without visibility into the applicable rate, creating compliance gaps that only surface at audit or grant close-out.
The real impact of non-compliance
Non-compliance with per diem rules has direct financial and operational consequences for agency finance teams. Auditors can classify any travel cost above the GSA rate as an improper payment, and the agency must seek repayment from the traveler or absorb the finding. Overstated reimbursements charged to a grant inflate reported expenditures, creating discrepancies between allowable costs and amounts drawn down — triggering reconciliation work at grant close-out. Tracking down whether each reimbursement was charged to the right fund, department, object code and program, and validated against the correct locality rate, slows every close. Unused encumbrances for travel that was approved but reimbursed at a lower amount must be released, or budget-to-actual reports stay wrong. Repeated audit findings on travel can lead to corrective action plans, tighter oversight and questions from the legislative body or grantor that funds the program. Vergo flags claims that exceed configured thresholds at submission, before overages reach a fund or grant.
A practical example
A state inspector submits a $320 hotel receipt for a trip to a GSA locality capped at $178. In a manual process, the finance office processes the reimbursement against the travel authorization without checking the applicable GSA schedule. The $142 overage is paid and charged to a federally funded program. Six months later, the single audit flags the excess $142 as an unallowable grant cost, which must be repaid from general funds. The grant's expenditure report no longer matches allowable costs, delaying close-out. In a compliant process, the overage is flagged at submission, the approver is alerted, and only the allowable $178 is charged to the grant. The exception is documented with justification if an actual-expense authorization applies, or the traveler is notified of the cap and reimbursed only the compliant amount.
How leading agencies prevent overages
The most effective approach agency finance teams use is enforcing per diem compliance at the point of submission — not during back-office review. This means building current GSA rate tables into the reimbursement workflow so that when a traveler submits a claim, lodging and M&IE amounts are checked against the applicable locality rate before the claim is processed. This replaces the audit-after-the-fact model with a preventive control. Claims that exceed GSA thresholds are flagged for review or capped, with documentation captured to support any justified exceptions. Every reimbursement is tied to its fund, department, object code, program and grant, giving finance a clean audit trail without manual reconciliation at month-end or grant close-out. Vergo handles this by checking each reimbursement against your configured per diem policies and creating a documented audit trail at the point of submission.
How Vergo handles this
Vergo is an AI-native, card-agnostic expense management platform that handles card spend, employee reimbursements, and AP invoices through one coding model — same coding, same review, one reconciliation. Employees submit receipts by text or from their phone, with no portal login, and Vergo chases missing receipts itself. Transactions are ready to code the moment they happen, and once they clear, they sync into your ERP, such as Tyler Munis, CGI Advantage, Workday or Oracle. Vergo proposes coding by inference from your own accounting structure and history, so new vendors, funds and grants are handled on first sight without maintaining keyword lists. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule, such as per diem claims above GSA thresholds. Connecting your existing cards involves no card applications, no re-issuing, and no banking change.
Related questions
Frequently Asked Questions
What does the Federal Travel Regulation say about per diem for government travelers?
The FTR limits lodging reimbursement to the applicable GSA per diem rate for the destination and pays M&IE at the locality's daily rate, with first and last travel days at 75 percent. Amounts above these limits are not reimbursable unless an exception, such as actual-expense authorization, is approved and documented.
How do GSA per diem rates apply to travel in rural or multi-county locations?
GSA rates are set by locality — typically by county or metropolitan area. When a trip covers several counties, the applicable rate is determined by where the employee is on official business and staying overnight. Locations that are not specifically listed default to the standard CONUS rate, which is lower than most metropolitan locality rates.
Do per diem rules apply to grant-funded travel?
Usually, yes. Federal grant cost principles require travel charged to an award to be reasonable and consistent with the recipient's written travel policy, and many grantors expect GSA rates. If an agency reimburses above those rates and charges the cost to a grant, the agency bears the audit exposure and may have to repay it.
How does non-compliant per diem reimbursement affect grant and budget reporting?
Overstated travel reimbursements charged to a grant or program inflate expenditures to date. When auditors disallow those costs, the agency must correct reported amounts, which creates discrepancies in budget-to-actual and grant expenditure reports and can trigger repayment to the grantor or a draw-down correction.
Can reimbursement software automatically enforce GSA per diem limits by fund or grant?
Yes. Platforms like Vergo let finance teams configure per diem policies and apply GSA locality limits at the point of employee submission. This keeps non-compliant amounts from reaching AP processing and creates a documented audit trail for any approved exceptions — a critical control for audited funds and federal grants.
How often do GSA per diem rates change, and how does that affect agency travel processes?
GSA updates per diem rates annually, effective October 1 at the start of the federal fiscal year. Locality rates for high-cost areas can change significantly from one year to the next. Finance and AP teams that rely on static internal policies rather than current GSA schedules will accumulate compliance gaps across multi-year programs.
