Ramp Receipts vs Reimbursements vs AP Inbox: Where to Send Each Document

A Ramp receipt, a reimbursement receipt, and a supplier invoice may all look like proof of spend, but they belong in different Ramp workflows. The right destination depends on what you want Ramp to create or complete after the document arrives.

Use receipts@ramp.com when the document is proof for a Ramp card or Ramp fund transaction. Use the reimbursement workflow when the employee paid out of pocket and needs to be paid back. Use Ramp Bill Pay or the account-specific AP forwarding address when the document is a supplier invoice or vendor credit that should become a draft bill or vendor credit. Use mailbox integration or receipt auto-capture when Ramp can collect the receipt natively from a supported source.

The mistake is treating receipts@ramp.com as the universal Ramp inbox. It is not. Sending the wrong document to the wrong destination can create a missing receipt, an unsubmitted reimbursement, or a vendor invoice that never enters AP review. Start with the document outcome, then pick the Ramp path.

For Ramp card and fund transactions, receipts@ramp.com is the core email destination. Ramp also lists other native submission channels: SMS, Ramp.com upload, mobile app capture, Slack, WhatsApp, Chrome extension, employee mailbox integration, and supported merchant receipt capture. Those routes all point toward the same general outcome: completing the receipt requirement for a Ramp transaction.

This path works best when the receipt can be matched to a posted Ramp transaction. Ramp currently lists JPG, JPEG, PNG, and PDF as supported receipt file types for receipt submission, with a 60 MB maximum receipt upload size, a 10 MB limit for web submissions, and a 50-page maximum for PDFs. Ramp receipt verification compares amount, plus either date or merchant, before marking a receipt as auto-verified.

Use this path for card receipts from travel, SaaS subscriptions, online purchases, meals, ride services, and other spend made on a Ramp card or fund. If the employee paid with a personal card or cash, do not assume receipts@ramp.com is correct. That usually belongs in reimbursement, not the card receipt inbox.

A reimbursement receipt proves an employee spent personal funds for the company. It should not be treated like a Ramp card receipt because there may be no Ramp card transaction to match. Ramp documents reimbursement submission as a separate workflow for out-of-pocket expenses, mileage, and per diem requests, depending on company setup.

Ramp says employees can send or forward reimbursement receipts to reimbursements@ramp.com, which creates draft reimbursements. That is only the intake step. The employee still needs to add required details and submit the draft in Ramp, and the reimbursement still follows the company approval and payment process.

Use this route when an employee paid with a personal card, cash, personal bank account, or another non-Ramp funding source and expects to be paid back. If the receipt is for a company card charge, route it back to the card receipt workflow. If the receipt is really a vendor invoice that the company should pay directly, route it to Bill Pay/AP instead.

Supplier invoices are accounts payable documents. They are usually asking the company to pay a vendor, not proving an employee card charge. In Ramp, that means Bill Pay, not receipts@ramp.com and not the employee reimbursement queue.

Ramp Bill Pay AP email forwarding gives a company a dedicated @ap.ramp.com inbox for vendor emails. Ramp says the generated format is based on the company name, and the address is visible in Bill Pay under New Bill, then Forward invoices to pre-fill drafts. In multi-entity setups, Ramp can provide entity-specific AP inboxes plus a shared cross-entity inbox. Because those addresses are account-specific, readers should copy the destination shown in their own Ramp account.

AP forwarding is stricter than a normal email inbox. Ramp says it processes forwarded emails only when sender, company domain, vendor contact domain, or recipient conditions are met. When the email qualifies, Ramp reviews supported attachments and creates draft bills for invoices or draft vendor credits for vendor credit memos. Other files can be attached as supporting documents, filtered out, or left unprocessed if unsupported, encrypted, password-protected, duplicated, or not relevant.

Memos and accounting fields are not a separate document destination. They are details that complete a Ramp transaction, reimbursement, or bill. For card transactions, Ramp supports adding a memo by putting Memo: followed by the memo text in the body of an email sent with the receipt, and Ramp also supports memo and accounting entry through web, mobile, SMS, Slack, and other submission prompts.

For reimbursements, the employee completes the reimbursement draft with memo, merchant, amount, date, trip, attendees, accounting categories, and any company-required fields. For Bill Pay, the AP team reviews the draft bill, invoice document, vendor details, line items, payment details, approval route, and accounting fields before moving it forward.

This distinction matters because a receipt can arrive without completing the expense. Ramp documentation notes that receipts, memos, and accounting fields can be separate requirements. If a card or fund remains locked after a receipt is submitted, the missing item may be a memo, accounting field, review task, repayment request, or another independent requirement.

Ramp has native ways to collect some receipts without a manual forward. The employee mailbox integration lets a user connect a work Gmail account when the finance team allows it. Ramp says the connection can identify receipt-like emails, match them to Ramp card transactions, attach matched receipts, and look back approximately seven days on first connection. Ramp also says the employee Gmail integration is different from the company-wide Gmail integration.

Ramp receipt auto-capture is another native path. Standard auto-capture can retrieve receipts from select merchants using transaction details, while merchant receipt collection requires the employee to connect supported merchant credentials. Ramp currently describes merchant receipt collection as available for US-based businesses, with Amazon as the supported merchant for that specific credential-based flow.

Use these native paths when the receipt source is supported and the desired outcome is a Ramp card transaction attachment. Do not treat them as a replacement for AP invoice intake, reimbursement drafts, or finance review. A travel booking, merchant receipt, and AP invoice may all arrive by email, but they still need different Ramp outcomes.

The fastest way to route a Ramp-bound document is to name the document type before touching the forward button. A card receipt, reimbursement receipt, AP invoice, and portal notice can all come from the same mailbox. The sender is useful context, but the destination should be chosen by the work Ramp needs to do next.

Use this table as a practical routing checklist. It is intentionally conservative: when the document is ambiguous, keep it in review and confirm the destination in Ramp before creating an automatic rule.

Expensent is useful before Ramp when the hard part is not Ramp processing, but inbox routing. Finance teams may have receipt emails, reimbursement receipts, vendor invoices, travel confirmations, portal alerts, and supporting documents spread across one or more inboxes. Ramp can process documents after they reach the right path. Expensent helps users find and route the right email before that handoff.

That role is deliberately narrower than Ramp. Expensent does not replace Ramp Expense Management, Ramp reimbursements, Ramp Bill Pay, receipt verification, AP approvals, policy enforcement, payment release, or accounting sync. It helps with the upstream decision: should this email go to receipts@ramp.com, reimbursements@ramp.com, the account-specific AP inbox, a manual upload path, or review?

The strongest workflow is review first, then rules. Use Expensent to find historical and current receipt emails, inspect the attachment and subject pattern, forward the reviewed item to the right Ramp destination, and create a recurring email-pattern plus subject-pattern rule only after the first examples land correctly. That keeps automation tied to real inbox evidence instead of broad guesses.

Start with one document class. For example, route SaaS card receipts to receipts@ramp.com, route personal-card employee receipts to reimbursements, and route supplier invoices to the AP inbox shown in Ramp Bill Pay. Confirm the result in Ramp before adding more senders or older emails.

Then document the exceptions. Some vendor emails contain a receipt and marketing content. Some portals email only a notification, not the invoice. Some invoices are encrypted or password-protected. Some vendors send credits, statements, and invoices from the same address. Those are not good candidates for broad rules until you know how Ramp handles each class of attachment.

Finally, keep ownership clear. Employees should know where to send their own reimbursement receipts. Cardholders should know the authorized sender rules for card receipts. The AP team should control the AP forwarding address and vendor inbox rules. Expensent can sit before those destinations to help route inbox documents, but Ramp account settings and company policy still decide what is accepted.