Trace a Missing Receipt Through Rydoo

Rydoo's email-forwarding help says receipts and invoices need to be forwarded from the email address associated with the Rydoo account. If the receipt came from a personal address, assistant mailbox, shared AP inbox, scanner address, or vendor forwarding alias that is not tied to the user profile, the first suspect is the sender relationship, not OCR.

Rydoo also documents a secondary email option. The secondary-email article says a user can add another address to the profile by going to Personal settings, editing the expense settings section, clicking add email, and saving. The article does not describe a broader shared-inbox authorization model, so avoid assuming that any teammate mailbox can send on behalf of any Rydoo user.

For a controlled test, resend one known-good receipt from the primary Rydoo account email or from a secondary email already added in the user's personal settings. If that creates the expected expense and the shared mailbox did not, the missing receipt is a sender-setup issue.

Confirm the From address on the original message, not only the mailbox where someone found it. Check whether that address is the Rydoo account email or an added secondary email. Do not describe secondary emails as verified unless your Rydoo account or support team confirms that wording.

Rydoo's forwarding article lists receipts@rydoo.com for Production and sandbox-receipts@rydoo.com for Sandbox. That matters when a test message appears to vanish. A receipt sent to the sandbox address should be diagnosed in the sandbox context; a production expense list may not be the right place to look.

Do not infer more sandbox behavior than the official forwarding article states. The article documents the sandbox address, but it does not publish a universal guarantee that sandbox processing mirrors production, avoids production effects, or behaves the same for every account. If your company uses a sandbox for workflow testing, confirm the expected account behavior with the Rydoo administrator or support team.

For production troubleshooting, copy receipts@rydoo.com directly into a new test message and send from the allowed sender. For sandbox troubleshooting, run the same test with sandbox-receipts@rydoo.com, but label the test clearly so no one checks the wrong environment.

Production destination: receipts@rydoo.com. Sandbox destination: sandbox-receipts@rydoo.com. If production and sandbox tests are mixed, record the recipient address before judging whether Rydoo created the expected expense.

Rydoo documents three email shapes. With one JPEG, PDF, or PNG attachment, Rydoo uses the attachment as the receipt. With multiple attachments, Rydoo creates a separate expense for each attachment in the email. With no attachment, Rydoo converts the email body into a receipt.

That means the expected result should change based on attachment count. If someone forwarded a vendor email with three receipt PDFs and expected one expense, the correct place to check is separate expenses. If someone forwarded a single attachment and got multiple items, inspect whether email signatures, inline images, or duplicate files were also present as attachments in the original message.

If there was no attachment, do not troubleshoot it as a failed PDF upload. Look for a body-based receipt result and inspect whether the body contained enough receipt information for a useful expense. A body-only email with real receipt details is different from an email that merely says "view receipt" and links to a portal.

One attachment: expect one attachment-based receipt expense. Multiple attachments: check for multiple expenses before resending. No attachment: check whether Rydoo converted the email body into a receipt.

Body-only receipt handling is useful, but it is not the same as logging into a vendor portal. Rydoo says it converts an email without an attachment into a receipt. That supports emails where the receipt details are present in the email body. It does not prove that Rydoo can retrieve a receipt hidden behind a login button, expiring link, or account-specific download page.

If the email body contains merchant, amount, currency, date, and line details, check whether Rydoo created a body-based receipt expense and whether required fields remain incomplete. If the email only contains a payment notification plus a link, download the actual receipt first, confirm it is a supported file for the path you are using, and send a cleaner message.

This distinction is also important for automation. Broad mailbox rules often forward the entire vendor message, including signatures, marketing images, and portal links. A reviewer should decide whether the email is ready to send, needs a download, or needs manual review before creating a recurring rule.

Body contains receipt details: check for a body-based receipt result. Body contains only a portal link: download the actual document before resending. Body has clutter plus attachments: isolate the file or content Rydoo should process.

A receipt can show up in Rydoo without being ready to submit. Rydoo's status article defines Processing as the system reading amount, merchant, currency, and date from the receipt. It defines To be verified as a receipt that was read automatically but still needs required fields filled manually. It defines Unreadable as a case where the system could not read receipt details and asks the user to try snapping a picture again.

For uploaded receipts, Rydoo's upload article says mobile scanning creates a new expense after saving, OCR extracts date, merchant, amount, and currency, and feedback such as Audit in progress or Duplicate detection is shown. On web upload, Rydoo describes processing receipts and then possible statuses such as To be verified or To submit. AI Autofill can prefill country, tax rate, and category if enabled for the account.

So a missing OCR result can be a normal review state, an unreadable document, or a configuration question. Avoid saying that Rydoo is down or that the email failed until you have checked whether an expense row exists with Processing, To be verified, Duplicate, Unreadable, To submit, or another visible status.

Processing: Rydoo is reading amount, merchant, currency, and date. To be verified: OCR read the receipt, but required manual fields remain. Unreadable: improve image quality or file clarity before another attempt.

Sometimes the receipt is present but the expected card match is missing. Rydoo says that once a receipt has been uploaded, it automatically looks for a match to the corresponding corporate card feed. If it finds a match, a green credit card icon appears on the expense and the expense and transaction are linked and reconciled.

Rydoo also documents several reasons a transaction may not match automatically: basic information such as amount differs between the transaction and expense, the transaction is older than two months, the payment method is incorrect, or the user needs to link one transaction to several expenses using a split approach. In those cases, manual matching may be the next step.

The corporate card feed itself is provider and account dependent. Rydoo says transaction data must be sent from providers or card companies to Rydoo in a specific format, and customers should verify provider agreements and possible fees. If no transaction feed is present, late, incomplete, or configured differently from the expense, a good receipt can still lack the card match you expected.

Receipt present, no green card icon: check amount, date, payment method, and transaction age. Transaction missing: check whether the corporate card feed is configured and receiving provider data. Several expenses for one transaction: review Rydoo's split and manual matching guidance.

Expensent searches current and historical email for the source receipt and sends selected documents from the eligible mailbox to the correct Rydoo environment.

Confirmed sender-and-subject patterns can route new recurring receipts automatically. Rydoo then creates the expense, reads the receipt, and attempts card matching.

If the receipt arrived but the expense or match is missing, continue the diagnosis inside Rydoo using the stages above.