Why Revolut Business Did Not Match a Receipt

Start with one question: did the document reach Revolut Business at all? A receipt that is absent from both the expense and My receipts is an intake problem. A receipt visible in My receipts but not on the expected card expense is a matching problem. A receipt attached to a different expense is a correction problem. These states look similar to the cardholder, but each has a different fix.

Do not immediately forward the same message again. Repeated sends can make the evidence harder to follow without resolving sender, permission, file, or expense-status problems. Record the cardholder, sender address, destination, sent time, merchant, amount, transaction date, and current expense status first. Then stop at the first failed stage in this guide.

This article focuses on documents intended to support an existing Revolut Business card expense. A personal-card purchase belongs in the reimbursement workflow, while a supplier invoice may belong in a bills or accounts-payable process. Confirm the object you are trying to document before diagnosing a card receipt match.

For an emailed receipt, check the sender mailbox for delivery failure or an incorrect-address notification, then open My receipts in the cardholder account. Revolut documents a dedicated Expenses email address found in the user profile under My receipts. It instructs the user to forward from the email address used to log in to Revolut Business.

If the receipt is not present, verify the current intake requirements rather than treating the issue as matching. Revolut says Expenses must be enabled, the user needs the Enrolled in Expenses permission, and an emailed receipt must have an accepted attachment or an HTML body. Its current UK help page also says only the first attachment in a multi-attachment email is processed.

For a manual upload, open the expected expense directly and check whether the file is visible there. Revolut documents mobile photo/gallery upload and web file upload as native attachment paths. A successful direct upload proves the document can be attached to that expense; it does not prove the earlier email was accepted or matched.

Receipt forwarding is user-specific. Revolut tells users to send from their Revolut Business login email to the unique Expenses address shown in My receipts. That makes the actual From address important. A display name, alias, shared finance inbox, delegated mailbox, or assistant account may not be the same address as the cardholder uses to log in.

Ask the employee who made the card purchase to open their own My receipts view and confirm both addresses. Then inspect the raw sender on the sent message. If a finance team forwarded the document on the employee's behalf, do not assume Revolut will infer the cardholder from the merchant, subject line, or attachment.

Permissions are a separate gate. Revolut tells users who cannot find an emailed receipt in-app to check for the Enrolled in Expenses permission. Admins and expense managers may be able to review broader company activity, but that does not turn a shared sender into the cardholder's login identity.

Matching cannot attach a receipt to an expense that is absent from the Expenses view. Revolut says card payments normally appear in Expenses, but an older transaction can be missing if it falls before the configured expense-tracking starting date. A card can also have expense tracking disabled.

Search for the card transaction by employee, date, merchant, and amount. If it is missing, check the Expenses starting date and the card's expense-tracking setting. This is an expense-record problem, not a document-processing problem, so forwarding the receipt again will not create the missing card expense.

Also verify that you are looking for a Revolut Business card payment rather than a reimbursement request, transfer, direct debit, or invoice workflow. Different records can appear in Expenses, but the troubleshooting path and responsible person may differ.

Revolut gives one specific reason for an unmatched receipt: the expected expense may already have been submitted. Its help documentation says matching considers non-submitted expenses, and its editing guidance says a submitter cannot edit an expense after submission.

Open the expected expense and check its current state before changing the receipt. If the expense is still editable, continue to manual matching. If it was submitted, ask the appropriate expense admin to review it. Revolut documents Revert decision for a completed expense when an admin needs to move it back to Info required and make a correction.

Do not use a missing-receipt declaration as a shortcut when the real receipt exists. Those declarations are part of the company's expense-control process. The cleaner fix is to restore editability where appropriate and attach the actual supporting document.

When the receipt has arrived and the target expense is eligible, use Revolut's native fallback. Open your profile, choose My receipts, select the unmatched receipt, click Match manually, and select the expense to attach it to. This resolves an ambiguous match without changing how the document entered Revolut.

Before confirming, compare the receipt with the card expense yourself. Check the final charged amount, currency, merchant identity, purchase date, employee, and any signs of split shipments, tips, refunds, or repeated same-vendor purchases. Revolut does not publish a field-by-field matching formula in the help articles used for this guide, so these are review checks, not a claim about its algorithm.

If the receipt attached to the wrong expense, first identify both the current and intended expense. Correct the attachment through the editable expense workflow or involve an admin if the record has already progressed. Avoid adding another copy before locating the first attachment.

After identifying the likely failure, run one clean test instead of changing several variables at once. Use an expense that is visible, non-submitted, and owned by the employee doing the test. Use the employee's Revolut Business login mailbox and the dedicated Expenses address shown in that employee's My receipts view.

Choose one clear receipt or invoice that satisfies the current document requirements. If the original email had multiple attachments, an unsupported file, no usable HTML body, or a long forwarding chain, prepare a clean message that removes that ambiguity. Keep the original evidence as well so the team can explain what changed.

After sending, check both locations separately: first My receipts for document arrival, then the target expense for attachment. If the document arrives but does not attach, use Match manually rather than sending it again. If it never arrives, the remaining problem is sender, permission, destination, or document intake, not expense matching.

Record the result as a small decision table for the team. A clean cardholder test that succeeds while a shared-mailbox test fails points to the upstream sender path. A clean test that arrives but stays unmatched points to matching or expense eligibility. A clean test that never appears points back to intake. This evidence is more useful than a folder of duplicate forwards.

Escalate after you can describe the broken stage precisely. For an intake failure, collect the sender, dedicated Expenses destination, sent timestamp, subject, attachment count, file type, file size, permission state, and any delivery notification. For a matching failure, add the unmatched receipt view, cardholder, target expense, current status, merchant, date, amount, and whether the target appears in manual matching.

Give that record to the company's Revolut Business expense admin first. The admin can verify expense settings, card tracking, permissions, and whether a submitted record needs to be reverted. If the configuration looks correct, use Revolut's in-app support path with the same evidence.

Keep API questions separate. Revolut Business documents API retrieval of expenses and receipts already related to expenses. That can help an internal system inspect receipt IDs and transaction relationships, but it is not evidence that Expensent or a read-oriented retrieval workflow can force an unmatched emailed document onto an expense.

Expensent is useful when the failure starts before Revolut: a receipt is buried in an employee inbox, historical emails need catch-up, recurring vendor messages are easy to overlook, or a team wants review before anything is forwarded. It connects to inboxes through OAuth, identifies likely receipt and invoice emails, and keeps uncertain or link-only messages visible for review.

After a person confirms a clean recurring pattern, Expensent can create a rule from the reviewed email using sender and subject patterns. That is narrower than a broad mailbox filter and keeps ambiguous invoices, portal notices, and non-card documents out of automatic routing until someone decides where they belong.

The boundary is exact: Expensent helps discover, review, and deliver an email receipt from the connected mailbox. Revolut Business controls whether the sender and document are accepted, whether an eligible expense exists, how scanning and matching behave, who can edit or approve the expense, and whether manual intervention is required.