Per Diem Request Form

This form is used to request per diem reimbursement for a business trip. It captures the information needed to calculate eligible lodging, meals, and incidental expenses using the applicable rate reference. It also creates a clear record of the trip purpose and any meals provided. That makes review faster and reduces back-and-forth with finance.

The traveler or requesting employee should complete it, since they know the trip details and what expenses were actually incurred. A manager or finance reviewer can then validate the request against policy and the rate reference. If your process requires pre-approval, the form can be routed before travel and again after the trip for final reimbursement. Keep the owner of each step clear to avoid duplicate submissions.

It is typically submitted once per trip, either before travel for approval or after travel for reimbursement, depending on your policy. Some organizations use the same template for both stages by adding conditional logic for pre-trip estimates versus actual expenses. If the trip spans multiple days or locations, the form should be completed for the full travel period. Avoid using one form for multiple unrelated trips.

At minimum, you need the requester, trip dates, destination, trip purpose, trip type, and the per diem components being claimed. Lodging, meals provided, and incidental expenses should be marked required only when they apply, using conditional logic rather than forcing every field on every request. Supporting receipts can be optional or required based on policy and expense type. The goal is to collect only what you will actually use for approval and reimbursement.

The GSA rate reference field records the source used to determine the applicable per diem rate for the destination and travel dates. That helps reviewers confirm the request was calculated against the correct standard and supports an audit trail. If your organization uses a different rate table or internal policy, you can replace this field with your own reference source. The template is flexible as long as the calculation basis is documented.

Common mistakes include entering trip dates that do not match the destination stay, claiming lodging nights that exceed the actual trip length, and forgetting to note meals that were already provided. Another frequent issue is attaching receipts without explaining why they are needed when per diem is being used. Reviewers also see errors when the rate reference is missing or outdated. Clear validation and required-field rules prevent most of these problems.

Yes. You can add conditional logic for domestic versus international travel, different trip types, or department-specific approval rules. You can also rename fields to match your policy language, add a manager approval step, or include a calculation field for estimated reimbursement. If your policy treats lodging and meals differently, separate those sections so reviewers can see the basis of the claim at a glance.

It can, depending on how your workflow is set up. Many teams route approved requests into an expense platform, accounting system, or payroll workflow after review. The key is to keep the form structured so fields like employee ID, trip dates, destination, and rate reference map cleanly to downstream systems. That reduces manual re-entry and helps preserve the audit trail.

Start with a small group of frequent travelers and finance reviewers to confirm the fields match your policy and approval process. Then publish a short guide that explains when to use the form, what receipts are needed, and what happens after submission. If possible, include examples for common trip types so employees know how to complete the form correctly. A simple rollout usually works better than a broad launch with unclear rules.