The workbook contains seasons, not one row per destination
A destination with seasonal lodging rates appears in several master-file rows. Each period has start and end dates, a lodging amount and M&IE. Our importer verifies that the periods cover the whole fiscal year without overlap or gaps before producing the twelve-month table.
The month order is October through September. Reading the first number as January would shift an entire fiscal year’s seasonal schedule.
Use identifiers and coverage together
The official ZIP files carry GSA DestinationID. We use that identifier to join a spelling change across editions while preserving each year’s source name. Matching the identifier is not enough for a geographical comparison: the changes analysis also requires identical coverage text.
The downloadable JSON retains source filenames and row numbers. Each original workbook has a checksum in the source manifest so a reviewer can identify the exact version used.
Choose the export for the task
Use the full-edition CSV for a spreadsheet reference, the search-result CSV for a filtered destination list, and the trip CSV for dated calculations with meal selections. The JSON is useful when importing the complete nested data into another tool.
These are published snapshots, not a live connection to GSA. A file’s retrieval date is separate from its rate validity. Check GSA for revisions before relying on an older download, and do not treat a new browser visit as a fresh source review.
Official sources
This guide explains a general method. Your travel authorization and applicable policy determine the claim. Report a correction.