How to Email Receipts to Monarch

Monarch currently documents receipts@my.monarch.com as its receipt-import address. Forward one receipt per email from an address Monarch recognizes; Monarch can use a supported attachment or receipt information in the email body.

After delivery, the receipt appears in Monarch and may be matched to a posted transaction. A missing receipt is an intake problem, while an imported but unattached receipt is a matching problem.

The Monarch account email and household-member emails are documented as already verified. For another address, open Transactions > Receipts > Settings > Add new email, then enter the six-digit code Monarch sends to that inbox.

This sender check is separate from Gmail's forwarding-destination verification. A mailbox connected to Expensent must still be accepted by Monarch, even though the Expensent route does not configure Gmail forwarding.

Forward one recent, readable receipt from the accepted mailbox and leave its useful subject, body, and attachment intact. Avoid a bundled message containing several purchases.

Confirm that the receipt appears in Transactions > Receipts before adding recurring automation. Monarch notifications help distinguish an import result from a matching result.

Monarch currently lists JPG, PNG, WEBP, HEIC, HEIF, and PDF, with a 10 MB limit per attachment and 30 MB per email. Expensent's current attachment route supports PDF, JPG, and PNG, so use the narrower shared set when routing through Expensent.

Monarch can also turn a body-only receipt email into a receipt image. Expensent's body-as-proof preference makes those candidates visible and affects newly created rules; it does not rewrite existing rules.

Monarch matches imported receipts using amount, date, and merchant information, and only posted transactions are eligible. A receipt can arrive correctly while its card charge is still pending.

If the expected transaction has posted and the receipt remains unmatched, open the receipt and use Find match. Treat sent, imported, and matched as separate states.

Manual forwarding works well for occasional receipts. Gmail's native automatic-forwarding setup is blocked when Google asks Monarch's shared destination to open a verification link.

Expensent uses OAuth-connected Gmail or Outlook access to find receipt emails and send them from the connected mailbox. This route supports historical catch-up and recurring rules built from a proven sender and subject pattern.

The mailbox still must be accepted by Monarch, and Monarch remains responsible for import and matching after each message arrives.

If the receipt is absent from Transactions > Receipts, check the destination, sender verification, notification, and file limits. If it appears but is not attached, check posted status and the receipts amount, date, and merchant evidence.

Keeping intake and matching separate avoids duplicate sends and gets the reader to the relevant troubleshooting guide faster.