Automate Monarch Receipts When Gmail Cannot Verify the Address

Gmail's built-in automatic forwarding cannot be completed for receipts@my.monarch.com when Google asks the destination to open a verification link. The destination is Monarch's shared receipt-ingestion mailbox, not an inbox the Monarch user can open. Without destination confirmation, Gmail will not make that address available for automatic forwarding or a forwarding filter.

Monarch publicly confirmed this Gmail limitation shortly after launching receipt email imports and did not provide a resolution timeline. Check the current Monarch and Google help pages before setup because either workflow can change.

Two supported choices remain clear. For low volume, manually forward receipts from a sender Monarch accepts. For an email-heavy workflow, use a connected-inbox sending path that creates an authorized outbound message rather than configuring Gmail's automatic-forwarding destination.

Monarch sender verification answers: “May this email address submit receipts to my Monarch household?” Current Monarch documentation says the account email and household-member emails are already verified. A different sender is added under Transactions > Receipts > Settings > Add new email. Monarch emails that sender, and the user enters a six-digit code in Monarch.

Gmail forwarding-destination verification answers: “May Gmail automatically forward messages to this external destination?” Google emails a verification link to receipts@my.monarch.com and requires the destination to open it. The user controls the sender inbox but not Monarch's ingestion mailbox, so the second check cannot ordinarily be completed.

The direction matters. Monarch sends its code back to the sender. Google sends its link forward to the destination. Completing Monarch sender verification does not make Gmail's destination selectable, and solving the Gmail routing path does not automatically verify a new sender in Monarch.

Monarch check: code arrives in the sender inbox; user enters it in Monarch. Gmail check: link arrives in the destination inbox; destination must open it. Expensent path: authorized outbound send; Gmail forwarding settings are not configured. Remaining requirement: the outbound From address must still be accepted by Monarch.

Manual forwarding is the shortest supported path. Open the receipt email, choose Forward, enter receipts@my.monarch.com, and send from an address Monarch accepts. Gmail's destination-verification setting is not involved because the user is composing an outbound message, not configuring automatic forwarding.

Start with one clear receipt and confirm it appears in Transactions > Receipts. Monarch treats one forwarded email as one receipt, so avoid bundled confirmations. Wait for its import or error notification before retrying. If it imports but does not match, move to matching troubleshooting instead of resending.

Manual forwarding remains a good fit for a handful of monthly receipts, paper-heavy workflows, or situations where the sender and document shape vary too much for a repeat rule. The cost is repeated inbox searching, no upstream review queue, and no automatic historical catch-up.

Expensent connects to Gmail or Outlook through OAuth and sends selected messages from the connected mailbox. The outbound message appears as activity from that authorized mailbox. Because the workflow is a send rather than Gmail's native forward-to-destination configuration, Google's destination-verification screen is not part of the path.

That difference is architectural, not a security bypass. Expensent does not receive the Google verification message, click a link inside Monarch's mailbox, or change Gmail forwarding settings. It uses the mailbox access the user authorized to perform an ordinary outbound send to the destination the user configured.

Monarch still checks sender identity. If the connected mailbox is not the Monarch account email or a household-member address, add that exact From address in Monarch's receipt settings and complete the six-digit code. Test one receipt before creating any recurring rule.

Expensent is strongest before the Monarch handoff: finding likely receipts, presenting current and historical candidates for review, routing supported evidence, and creating rules from a reviewed email pattern plus subject pattern. Monarch owns receipt import, matching, categories, and notifications after arrival.

Connect the mailbox that actually receives and will send the receipts. Verify that exact sending address in Monarch when required. Set receipts@my.monarch.com as the software destination. Review and send one test; confirm intake and matching separately. Create a narrow sender-plus-subject rule only after the pattern succeeds.

Google says Gmail filters apply to new messages. Even if the destination-verification issue disappeared, a newly created filter would not process the months of receipts already sitting in the inbox. Historical catch-up is therefore a different job from future routing.

Use an inbox scan to surface older receipt candidates, then review them before sending. Old mail is more likely to include duplicate confirmations, portal notices, expired download links, refunds, statements, and receipts for transactions already documented elsewhere. A catch-up queue should make those exceptions visible instead of forwarding every keyword match.

Monarch recommends smaller batches because only a limited number of imports process concurrently, but it does not publish a universal safe batch number. Send a small group, wait for import and error notifications, confirm the Receipts tab, and continue only when the previous group is understood.

A useful receipt rule combines a stable email pattern with a stable subject pattern and a predictable document shape. A dedicated merchant receipt sender with one receipt per message is a better candidate than a marketplace sender that mixes receipts, shipping notices, returns, promotions, and account alerts.

Keep body-only patterns out of automatic rules until the Expensent body-as-proof preference is intentionally enabled and the exact template has been tested. The setting surfaces detected body-proof items and changes the attachment requirement only for newly created rules; it does not silently rewrite existing rules. Recreate or edit rules whose evidence requirements need to change.

Keep unsupported attachment formats, several receipts in one message, portal-only notices, ambiguous refunds, and unreadable files out of an automatic path. Monarch's native format list is broader than the PDF, JPG, and PNG attachments Expensent currently supports.

A sent state is not a matched state. Review Monarch notifications and downstream records. If a receipt arrives but remains unmatched because its transaction is pending, forwarding the same message again only adds noise.

Google Workspace administrators can apply different organizational routing policies, and Apps Script can send mail under specific account permissions. Neither fact establishes a supported solution for Monarch's receipt destination. Current primary Monarch documentation does not recommend these routes, and organization-specific controls can change their behavior.

Avoid any method that claims to intercept, fake, or complete the destination verification. Manual forwarding composes a message, and a connected-inbox tool sends an authorized message; neither configures Gmail's native forwarding destination.

The connected-inbox path is also not a native Monarch integration. It uses Monarch's documented receipt email interface. There is no Monarch account API connection, receipt-status webhook, or ability for Expensent to force a match inside Monarch.

Choose a recent receipt whose transaction is already posted. Confirm the sending address in Monarch, send one message, and wait for Monarch's import notification. Open the Receipts tab and confirm the receipt exists. Then confirm whether Monarch attached it to the expected transaction.

If the receipt does not appear, troubleshoot intake: sender, address, processing delay, import error, attachment size or clarity, spam, and batch volume. If it appears but does not match, troubleshoot posted status, merchant, amount, date, retry, and Find match. Those two branches should never be merged into a vague “automation failed” diagnosis.

After a successful test, create one narrow rule and observe several future examples before expanding coverage. Maintain a review route for vendor-template changes and body-only or portal exceptions. Repeat the controlled test after any sender, rule, or mailbox-permission change. The goal is controlled reduction of inbox work, not invisible forwarding at any cost.

Record the first test as a small runbook: connected mailbox, exact From address, Monarch destination, source pattern, send time, import result, and match result. That evidence makes later failures diagnosable. It also prevents a teammate from “fixing” the workflow by turning on Gmail native forwarding or changing the sender without completing Monarch verification.