Rydoo: per diem rate not found for this destination
Fixes Rydoo's missing per-diem rate by selecting a valid rate table entry or having an admin add the destination. Use when Rydoo reports no per diem rate found for the destination. Not for wrong-rate calculations on destinations that do have rates.
TL;DR
Rydoo cannot compute the allowance because the destination has no rate in the active per-diem table (unlisted city, new country entry, or a table that has not been updated for the year). Check the spelling of the destination and pick the closest listed city or country rate; if none exists, ask an admin to add the destination to the rate table. The expense cannot be valued until the table has a rate.
Error
Rydoo: per diem rate not found for this destinationSteps
- Open the per-diem expense in Rydoo and confirm the destination as entered. Expected: you see the exact destination string that failed the lookup.
- Open the per-diem rate table in Rydoo settings and search for the destination or its country. Expected: the search shows whether any rate covers it.
- If a country-level or nearby-city rate exists, change the expense destination to the listed entry. Expected: Rydoo computes the allowance immediately.
- If no rate exists, ask a finance admin to add the destination with the correct daily rate to the table. Expected: the admin confirms the new rate entry.
- Re-open the expense and resubmit. Expected: the per-diem amount calculates and validation passes.
When to use
- Rydoo reports "per diem rate not found for this destination".
- Travel to a new country or city not yet in the rate table.
- The destination was typed with a spelling the table does not recognize.
When not to use
- A rate exists but the calculated amount looks wrong (a rate-value problem).
- The failure is on travel dates rather than the destination.
- The per-diem policy itself is under review.
Tool compatibility
Rydoo expense management with per-diem tables (current 2026 releases). Admin role required to edit rate tables.
Variant phrasings
rydoo "no rate for destination"
Same lookup failure in short form. Verify the destination string against the table.
per diem failed for a new country in rydoo
The table predates travel to that country. An admin adds the country rate.
city misspelled and per diem failed in rydoo
The table keys on exact names. Correct the spelling to the listed entry.
Why it happens
Per-diem tables are finite lists maintained by finance, usually updated yearly from government or company schedules. New destinations, renamed cities, and spelling variants miss the list, and the lookup fails closed rather than guessing a rate. The design is deliberate: paying an allowance requires an authoritative rate, so a missing entry blocks instead of estimating.
Provenance
Resolved from the public thread: https://vectle.com/posts/pstuG0UarOdydbGvJXWkM-ZQ