Trace a Missing Receipt Through Rydoo

A Rydoo receipt that is "not showing up" can mean several different things. The email may not have reached the right Rydoo address. It may have come from a sender Rydoo does not associate with the user. It may have created more than one expense because the email carried multiple attachments. It may have created a body-based receipt rather than an attachment-based receipt. Or the expense may exist, but still be in Processing, To be verified, Duplicate, Unreadable, To submit, Submitted, Approved, Controlled, Reported, or another status.

The fastest diagnosis is to identify where the trail broke. Start with the original email: sender address, recipient address, sent time, whether it had one attachment, several attachments, or no attachment, and whether the receipt was in the body, in a file, or behind a portal link. Then compare that trail with Rydoo's expense list, transaction match state, and admin settings.

This guide follows those stages in order. It is written for the common case where someone forwarded or uploaded a receipt to Rydoo and expected a new expense, OCR result, body-only receipt, multi-attachment split, or card match that did not appear where expected.

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.

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.

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.

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.

Do not mix file rules from different Rydoo paths. The email-forwarding article names JPEG, PDF, and PNG for a one-attachment emailed receipt. The upload article separately describes mobile scanning and web upload. The additional-attachment article separately says users can add up to five additional attachments to an expense, accepts JPG, PNG, and PDF files at 20 MB or less, and does not support password-protected PDFs.

Those official notes are useful, but they apply to the path they document. A failed additional attachment is not always evidence that email submission failed. A web upload that creates a processing receipt is not the same as an emailed vendor thread. A mobile scan that creates a new expense immediately has a different first screen from a forwarded email.

When troubleshooting, write down the path first: forwarded email, mobile scan, web upload, or additional attachment on an existing expense. Then use the matching Rydoo guidance. If the file is password protected, corrupted, not a clear receipt image, or a non-standard format for the path used, rebuild the file package before resending.

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.

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.

Not every missing-receipt complaint is an email-forwarding failure. Rydoo documents several admin or module-controlled behaviors around expenses. Additional attachments can be enabled or disabled by an admin. AI Autofill can be enabled for an account. Smart Audit checks can be activated, configured, shown to selected roles, and used to block auto-approval or control for flagged expenses.

Smart Audit can also make a receipt look "stuck" when the real issue is review. Rydoo's Smart Audit article lists receipt validation checks such as AI-generated receipt, card transaction receipt, invalid receipt, blurry receipt, photo of screen, screenshots, handwritten amount, VAT number, advanced duplicate detection, and receipt-expense match. These checks do not mean the receipt failed to arrive; they can mean the expense needs the configured review path.

Ask an admin for the exact setting only after naming the symptom. "I cannot add a second file to an existing expense" points to additional attachments. "The country, tax rate, or category did not prefill" points to AI Autofill or advanced expense prefilling. "The expense is flagged after upload" points to Smart Audit, expense rules, or policy settings. "The receipt exists but is not reimbursed" points much later in the approval, reporting, accounting, or reimbursement flow.

Rydoo processes receipt emails after they arrive. Expensent helps one step earlier: finding receipt and invoice emails in the connected inbox, separating items that are ready to forward from items that need a download or review, and routing selected supported documents toward the Rydoo destination your team uses.

That upstream checkpoint is useful for the exact failure modes in this guide. It lets a reviewer catch a portal-only message before it is sent to Rydoo, split a multi-attachment vendor thread, avoid sending from the wrong mailbox pattern, and create recurring rules only from sender and subject patterns that were already reviewed. It is also useful for historical catch-up when receipts are already buried in a mailbox.

Expensent does not replace Rydoo Expense, receipt upload, OCR, AI Autofill, Smart Audit, corporate card feeds, transaction matching, approvals, reimbursements, exports, accounting integrations, or company policy. Keep Rydoo as the system that owns expense processing and use Expensent to make the inbox-to-Rydoo handoff more visible and controlled.

Escalate with evidence, not a vague "missing" report. For an email issue, include sender, recipient, sent time, subject, attachment count, attachment names, whether there was a body-only receipt, and whether production or sandbox was used. For an upload issue, include upload path, file type, visible status, and whether the issue is OCR, attachment display, or submission readiness.

Contact an email administrator when a forwarding rule did not send, an attachment was stripped, or a shared mailbox sent from the wrong address. Contact a Rydoo administrator when secondary email setup, additional attachments, AI Autofill, Smart Audit, card feeds, payment methods, approval rules, or role visibility need review. Contact Rydoo support when the documented path was followed but the account behaves differently from the current help guidance.

Before resending the same receipt repeatedly, search for separate expenses, body-based receipts, Processing rows, Duplicate or Potential Duplicate indicators, Unreadable rows, and unmatched card transactions. Duplicate resends can make reconciliation harder when the original document was already in Rydoo under a different state.