Rydoo Sandbox to Production Receipt Email Testing Runbook
A narrow runbook for testing a Rydoo receipt email route in sandbox, recording evidence, approving promotion, running one production canary, and cleaning up the test path.
By ilios Galil · Founder, Expensent
Published July 21, 2026 · Updated August 3, 2026
Last verified : July 8, 2026
Read this if…
You already have or are arranging Rydoo sandbox access and need a controlled receipt-email test before allowing production traffic.
Release gate
Rydoo documents sandbox-receipts@rydoo.com for Sandbox and receipts@rydoo.com for Production.
Prove sandbox access and sender recognition before testing the receipt route. Mobile sandbox use requires a sandbox login and locks the app to that environment until reinstall.
Run only the message shapes the live route will send, preserve route-level evidence, and promote with one reviewed production canary.
Promotion gates, canary controls, rollback steps, and cleanup steps in this guide are operational recommendations rather than Rydoo product requirements.
In This Guide
1. Environment decision table
Rydoo documents two receipt-email destinations. Choose from the environment you intend to inspect, not from the type of receipt being sent.
| Environment | Destination | Use | Gate |
|---|---|---|---|
| Sandbox | sandbox-receipts@rydoo.com | Pre-production receipt-email tests | The test user can sign in to the sandbox and inspect the result. |
| Production | receipts@rydoo.com | Live receipt forwarding and the final canary | The owner approves a real production expense to be created. |
| No sandbox access | Neither | Pause the test | Ask the Rydoo account contact how sandbox access applies to your account. |
Documented fact versus recommendation
The two addresses are documented by Rydoo. The gates in this table are operational recommendations for keeping test evidence separate from live expense data.
2. Confirm access and environment boundaries
Before testing email delivery, prove that the reviewer can enter the intended sandbox and identify the test user. Rydoo does not present sandbox access as a universal self-service entitlement in the receipt-email article. In its current Perk integration guidance, Rydoo says sandbox access may be provided during implementation when applicable and directs customers to their Rydoo Customer Success Manager to discuss access.
Rydoo requires receipt and invoice emails to come from the email address associated with the Rydoo account, or from a secondary email added in personal settings. Use the exact sender planned for production so sender recognition is part of the test.
Mobile testing has an extra boundary. Rydoo says to append +sandbox to the account email during login and use the password for sandbox-accounts.rydoo.com. The app is then locked to that environment; switching back to production requires deleting and reinstalling it.
Required before the first send: sandbox login, named reviewer, recognized sender, and a known place to inspect the result. Recommendation: use web access for the email-routing runbook unless mobile behavior is itself under test. Recommendation: do not repurpose a production mobile installation for a brief sandbox email test because returning to production requires a reinstall.
3. Run the minimum receipt-email test matrix
Keep the matrix small enough that each result has one explanation. Rydoo documents body-only, one-attachment, and multiple-attachment outcomes, but this rollout test only needs cases your live route will actually send.
Testing constraint
Rydoo publishes the email-shape outcomes but no universal processing-time SLA in the cited receipt-email article. Record observed timestamps; do not invent a pass/fail timeout from this guide.
4. Promote with one production canary
Recommendation: change only the destination required for the canary, then send one receipt whose merchant, amount, sender, and attachment are easy for finance to identify. Use receipts@rydoo.com and inspect the production account, not the sandbox account.
If Expensent will route recurring receipts, test one production receipt first. Once it reaches the intended Rydoo user and creates the expected expense, enable the recurring sender-and-subject pattern.
Record the same evidence fields used for sandbox. Confirm the result is in the production account and belongs to the intended user. Have finance review the created expense before enabling recurring traffic. Do not treat an email delivery event alone as a passed Rydoo canary.
5. Sources checked
These sources were used to verify product behavior, current terminology, and the boundaries between native workflows and Expensent.
7. Frequently asked questions
Which Rydoo address should a sandbox test use?
Rydoo documents sandbox-receipts@rydoo.com for Sandbox and receipts@rydoo.com for Production. Confirm that your user can access the intended sandbox account before sending the test.
Does a successful sandbox receipt prove production is ready?
No. Rydoo documents separate sandbox and production destinations, and its public receipt-email article does not promise that a sandbox result proves production configuration. As an operational recommendation, run one controlled production canary before enabling a live routing rule.
What should a Rydoo receipt email test record?
Record the environment, exact From and To addresses, message identifier, attachment count and type, send time, Rydoo result, resulting expense identifier, and reviewer. These fields are operational recommendations, not Rydoo requirements.
Can the Rydoo mobile app switch between sandbox and production?
Rydoo says the mobile app is locked to the environment selected during setup. To switch environments, delete and reinstall the app. Sandbox login uses +sandbox at the end of the account email and the password used for sandbox-accounts.rydoo.com.
When should a sandbox receipt route be removed?
As an operational recommendation, remove or disable the sandbox destination as soon as evidence is captured and the production canary is complete. Keep the test record, but do not leave a test route available to a live rule.
Move a tested receipt route into Rydoo production
Test one receipt in the sandbox, confirm one production receipt, then automate recurring inbox-to-Rydoo matches with Expensent.
Get Started