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.
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.
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.
- Sandbox | Destination: sandbox-receipts@rydoo.com | Use: pre-production receipt-email tests | Gate: the test user can sign in to the sandbox and inspect the result.
- Production | Destination: receipts@rydoo.com | Use: live receipt forwarding and the final canary | Gate: the owner approves a real production expense to be created.
- No sandbox access | Destination: neither | Use: pause the test | Gate: 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.
- S1, direct sender: send one clean JPEG, PDF, or PNG attachment from the Rydoo account email to sandbox-receipts@rydoo.com. Expected documented shape: Rydoo uses the attachment as the receipt.
- S2, production sender path: repeat S1 from the exact added secondary email or upstream route planned for production. Expected result: one sandbox expense attributable to that sender path.
- S3, exception shape: run only if the live route permits it. With no attachment, Rydoo says it converts the email body into a receipt; with multiple attachments, Rydoo says it creates a separate expense for each attachment.
- P1, production canary: after promotion approval, send one identifiable receipt through the production path to receipts@rydoo.com. Expected result: one expense in the intended production account.
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. Record evidence that identifies the route
A screenshot that says only "it worked" is not enough to distinguish sandbox from production or one sender path from another. Use a compact test record that lets a second reviewer trace the message to the resulting expense.
- Test ID and reviewer.
- Environment and account or company label visible to the reviewer.
- Exact From and To addresses, email Message-ID, and send timestamp.
- Attachment count, filename, type, and a non-sensitive test marker.
- Resulting Rydoo expense identifier or URL, observed timestamp, and result screenshot.
- Pass, fail, or blocked outcome with the reason and any configuration change made afterward.
Operational recommendation
These evidence fields are a proposed finance control, not a Rydoo product requirement.
5. Apply promotion criteria
Sandbox completion is a decision point, not automatic permission to go live. The following criteria are operational recommendations for the route owner and finance reviewer.
- Every required sandbox case has a complete evidence record and an unambiguous result.
- The tested From address and message shape match the planned production route.
- The production destination is stored separately from the sandbox destination and has been reviewed character by character.
- A named owner can disable the upstream route without changing Rydoo.
- The finance reviewer has approved one identifiable production canary and knows where to find it.
6. 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 is the upstream routing layer under test, keep the rule disabled and route the canary as a reviewed message first. Enable recurring routing only after the production evidence matches the approved canary criteria.
- 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.
7. Rollback and clean up the test path
Recommendation: if the canary fails or creates an unexpected result, disable the upstream route first. Preserve the message and Rydoo expense identifiers, record the failure, and return the destination configuration to its pre-test state before investigating.
Cleanup is part of the test. Remove temporary sandbox destinations, disable test-only rules, revoke temporary reviewer access according to your company process, and label or remove test expenses according to instructions from your Rydoo administrator. Rydoo's public receipt-email article does not define a universal test-expense deletion procedure, so this guide does not prescribe one.
- Stop: disable the upstream forwarding or routing rule.
- Preserve: retain the email Message-ID, route configuration, resulting expense identifier, and screenshots.
- Restore: return destinations and rule state to the documented pre-test configuration.
- Clean: remove test-only access and destinations; handle test expenses under your Rydoo admin's process.
- Close: record the decision to retry, narrow the route, or remain manual.
8. Sources checked
These sources were used to verify product behavior, current terminology, and the boundaries between native workflows and Expensent.
10. Frequently asked questions
Which Rydoo address should a sandbox test use?
Does a successful sandbox receipt prove production is ready?
What should a Rydoo receipt email test record?
Can the Rydoo mobile app switch between sandbox and production?
When should a sandbox receipt route be removed?
Test the upstream route before enabling a rule
Use Expensent to send a reviewed sandbox sample and a reviewed production canary before enabling recurring inbox-to-Rydoo routing.
Get Started