Perk can create an expense from an email sent to a dedicated inbox.
Requirements
- You must send the email from the same address as registered in Perk.
- The email must contain the receipt as a PDF attachment, as JPEG or PNG images, or in the email body.
How Perk processes emailed receipts
You can upload new receipts by sending an email to send@receipts.perk.com.
Perk creates an expense from every email sent by a verified sender. What Perk reads from the email depends on what is attached:
| What the email contains | What Perk does |
|---|---|
| One or more PDF attachments | Perk uses the PDF. If there are several PDFs, Perk joins them into one file before using that file to create the expense. Perk ignores all other attachments, including images. |
| No PDF attachment | Perk creates a PDF from the email body and adds any attached JPEG or PNG images. Perk ignores all other attachments. |
Perk reads only PDF, JPEG, and PNG files. It ignores every other attachment, such as XML, XLS, or HEIC files, and forwarded emails attached as files. Perk doesn't reject the email because of them.
Tip: If you want to use a HEIC file to create an expense, upload it manually in the web or mobile app.
Note: The format of a PDF can affect whether Perk processes it. Perk recognizes a PDF by its MIME type, application/pdf. Perk also accepts a PDF sent as application/octet-stream or binary/octet-stream, but only if the file name ends in .pdf in lowercase.
Some email programs and tools send attachments as application/octet-stream. In that case, a file named receipt.PDF is ignored. To avoid this, save the receipt as a PDF with a lowercase .pdf file name and attach it to a new email.
If Perk finds no receipt details in what it reads, it still creates the expense, but the fields are empty. Complete them in Perk.
Perk does not upload email attachments as supporting documents. Perk ignores every attachment that it doesn't read as the receipt. To add supporting documents, upload them in the web or mobile app.
How Perk verifies senders
Perk verifies the sender of every email sent to send@receipts.perk.com before it creates an expense. This stops anyone from sending receipts in someone else's name by typing their address in the From field. Use this section to understand what Perk checks and how to fix emails that don't create expenses.
Sender verification: how it works...
Sender verification checks that the domain in the From address is the same domain that signed or sent the email. Perk accepts the email when one of these standard email checks passes:
| Check | What it confirms | Passes when |
|---|---|---|
| DomainKeys Identified Mail (DKIM) | The email carries a digital signature from your company's domain. | The signing domain is the same as the From domain. |
| Sender Policy Framework (SPF) | The server that sent the email is on the approved list for your company's domain. | SPF passes and the email's bounce address (also called the return-path or envelope sender) uses the same domain as the From address. |
One passing check is enough. DKIM is the more dependable of the two because its signature usually stays valid when an email is forwarded, while SPF often fails.
What sender verification means for you
Sender verification in Perk usually needs no action from you:
- Emails from Microsoft 365, Google Workspace, and similar providers pass when your company's email is set up in the usual way.
- Perk checks the address that sends the email to Perk. If you forward a receipt from your own mailbox, Perk checks your own domain. Forwarding often breaks SPF but usually keeps a DKIM signature valid, so DKIM is more likely to pass.
- Perk creates an expense only when the From address belongs to exactly one active Perk user.
When sender verification fails, Perk doesn't send an error message. The email doesn't arrive and you don't get a reply.
Troubleshooting emails that don't create expenses
Use this section if you sent a receipt to send@receipts.perk.com and no expense appeared in Perk, or the expense has no details. Check the sender first, then the contents of the email.
Checking the sender
- Make sure you send from the email address in your Perk profile. Perk only recognizes that exact address, not aliases.
- Send the email from your own mailbox, not from a shared inbox or a tool that sends on your behalf.
- Make sure that email address belongs to only one active Perk account. Ask your Perk admin if you're not sure.
- If the email still doesn't create an expense, ask your IT admin to check your company's email setup.
What your IT admin needs to check...
Check:
- Every service that sends email for your domain, such as a ticketing tool, marketing platform, or mail relay, is listed in the domain's SPF record.
- Outgoing email is signed with DKIM for the domain in the From address.
- The domain in the From address is exactly the same as the domain that signs the email. A subdomain, such as mail.acme.com, doesn't match acme.com.
- If you rely on SPF, the bounce address (return-path) uses the same domain as the From address. Many relays use their own domain here, so DKIM is the better choice.
For example, Sarah sends a receipt from sarah@acme.com, but her email goes through a relay that signs with its own domain and uses its own bounce address. Perk can't verify the email, so it doesn't create an expense. Her admin turns on DKIM signing for acme.com on the relay, and her next email passes.
Checking the receipt email
If sender verification isn't the problem, check these causes:
| What happened | What to do |
|---|---|
| The email has attachments other than PDF, JPEG, or PNG, such as XML, XLS, or HEIC files. | Perk accepts only PDFs, JPEGs, and PNGs. It ignores the rest. Send the receipt as a PDF, JPEG, or PNG attachment, or paste it in the email body. If you want to use a HEIC file or add XML or XLS files as supporting documents, upload them manually in the Perk app. |
| The receipt came from a forwarded email. | Perk ignores a forwarded email that is attached as a file. Attach the receipt as a PDF, JPEG, or PNG to a new email, or paste the receipt in the email body. |
| A receipt file is larger than 10 MB. | Reduce the file size. Keep it well below 10 MB, because some email providers struggle with large files. |
| The expense was created, but its fields are empty. | Perk reads only a PDF, or the email body plus JPEG and PNG images. If the receipt was in another kind of attachment, Perk couldn't read it. Complete the fields in the expense. Next time, attach the receipt as a PDF, JPEG, or PNG, or paste it in the email body. |