Hello,
We recently identified a potential control gap after migrating from a legacy per diem configuration to the newer TAS Assisted Upgrade model.
Under the previous configuration, once an itinerary was submitted for a specific travel period, the associated dates were no longer available for selection when creating a new itinerary. This control helped prevent duplicate per diem claims for the same travel dates.
Following the upgrade, it appears that users may still be able to create and submit additional itineraries for travel periods that have already been claimed. As a result, there is a risk that duplicate per diem reimbursements could be submitted and approved for the same date range.
Questions for the Community
Has anyone else experienced this behavior after moving to the TAS Assisted Upgrade configuration?
If so, are there any available configurations, audit rules, or recommended controls that can:
- Prevent users from creating duplicate or overlapping itineraries.
- Identify and block duplicate per diem claims for the same travel dates.
- Replicate the date-locking functionality that existed in the legacy configuration.
We are interested in understanding both standard system capabilities and any best-practice approaches that organizations have implemented to mitigate this risk.
Thank you in advance for any guidance or recommendations.
