Monarch Receipts Not Showing Up: Intake Troubleshooting

Open Transactions > Receipts and search for the message you sent. If no receipt record exists, the failure is in intake: sender identity, destination, processing, message contents, size, spam handling, or batch volume. Do not spend time on pending transactions or merchant matching yet.

If the receipt exists in this tab but is not attached to the expected transaction, intake worked. Move to the separate Monarch receipts not matching guide. Resending an imported receipt can create a duplicate receipt record without solving the match.

Monarch says a normal import usually takes a few minutes and can produce import, match, and import-error notifications. Use those states as evidence. “Sent” proves only that the mailbox attempted an outbound message; it does not prove Monarch accepted or processed it.

Not in Receipts: continue with this intake checklist. In Receipts but unattached: switch to matching troubleshooting. Matched to a transaction: review the downstream receipt, notes, and categories.

The Monarch account email and household-member emails are documented as already verified. Every other sending address must be added under Transactions > Receipts > Settings > Add new email. Monarch sends that inbox a six-digit code; enter the current code in Monarch before testing again.

Monarch currently says codes expire after 24 hours and provides Resend. If you receive an address-is-not-recognized reply, do not confuse it with Gmail's forwarding-destination blocker. This reply means Monarch rejected the From address at intake. Verify that sender or resend from an already accepted mailbox.

Check the actual From header, not just the inbox where you read the email. Shared mailboxes, aliases, send-as identities, and connected tools can use a different address. If Expensent sends from a connected mailbox, that exact mailbox must be accepted by Monarch.

Monarch says an email added to a different Monarch account is associated with the most recently added account, with notice to the previous member. If imports seem to disappear into another household, review recent sender-verification changes across accounts.

The current address is receipts@my.monarch.com. Copy it from Monarch's live documentation and compare every character with the outbound message. A saved contact, autocomplete entry, or prior draft can preserve a typo after the visible copy has been corrected elsewhere.

Do not send a Gmail forwarding-verification message to this address and expect Monarch to confirm it. Google's verification link is part of Gmail's automatic-forwarding setup, not a receipt. Monarch's ingestion mailbox is not a user-accessible inbox and does not provide a way to return that link.

When using Expensent, store the address as the configured software destination and send a reviewed test from the connected mailbox. This is ordinary authorized outbound sending, not Gmail forwarding configuration. It still depends on Monarch accepting the sender.

Monarch says receipts typically appear within a few minutes. Network delivery, importer load, and document complexity can make a specific message slower. Wait for the first result before sending another copy. Repeated sends make it harder to tell which message imported and can leave duplicate receipts.

An import notification means the receipt record should be available. A match notification means Monarch also attached it to a transaction. An import-error notification identifies an intake failure. An unrecognized-address reply points back to sender verification. Preserve the notification and original message when escalating to support.

If no response arrives, check the sending mailbox for a bounce, spam folder, and Sent folder. A message absent from Sent may never have left the mailbox. A message in Sent with no Monarch result needs the content, size, spam, and batch checks below.

Compare the test with a receipt that imported successfully from the same sender. A change in attachment type, message size, forwarding chain, or source template is stronger evidence than a general assumption that Monarch is down. Keep one variable at a time: changing the sender, destination, and file together makes the result impossible to interpret.

Monarch currently documents JPG, PNG, WEBP, HEIC, HEIF, and PDF for native receipt-email attachments, with 10 MB per attachment and 30 MB per email. It also accepts body-only receipt messages. Those limits belong to Monarch's native importer and can change, so recheck the live source.

A listed extension is not a guarantee. Monarch calls out hard-to-read or unusual formats as possible failure causes. Use the original unencrypted file where possible, make sure the merchant, date, and total are legible, and remove unrelated images or files that inflate the message.

If Expensent is upstream, use its actual support boundary: PDF, JPG, and PNG for attachments. Monarch accepting HEIC or WEBP natively does not make those files universally forwardable through Expensent. Use a supported conversion or Monarch's native upload route for an unsupported source.

For body-only messages, confirm the email contains a genuine receipt rather than a delivery update or portal notice. Expensent body-as-proof is an opt-in preference and does not silently change existing rules. Test the exact pattern before automating it.

Monarch treats one forwarded email as one receipt. A daily digest, marketplace order history, or thread containing several confirmations will not be separated into several receipt records. Even if the message imports, it may not represent the evidence you intended.

Split separate receipts into separate outbound messages. Keep statements, account summaries, and multi-order emails in review unless one document clearly represents the transaction. A forwarding system should not convert every email containing the word receipt into an ingestion candidate.

If the source email contains one receipt plus logos, tracking images, and signatures, preserve the actual receipt evidence and avoid adding more thread history. The goal is one clear receipt envelope, not merely one Gmail conversation.

Monarch recommends smaller batches because only a limited number of receipts process concurrently. It does not publish a universal safe batch count. Send a few, wait for notifications and receipt records, then continue. Large historical dumps can produce delays or missing imports that are difficult to reconcile.

Monarch also identifies spam handling as a troubleshooting factor. Avoid sending repeated duplicates, oversized threads, or large bursts that look unlike normal receipt traffic. If a legitimate message is classified unexpectedly, keep the original and the send timestamp for support.

Historical catch-up deserves more review than future routing. Old email often contains refunds, portal notices, bundled confirmations, and documents already attached through another method. Review candidates upstream and send only the records that still belong in Monarch.

Google officially says dots do not change delivery for personal Gmail accounts. A community report says Monarch may have treated dotted and undotted forms differently during sender verification or import. Monarch's Help Center does not currently document address normalization, so this is not a product fact.

When the visible address and the verified Monarch entry differ only by dots, inspect the exact From header and add that exact form in Monarch if the UI permits it. Record the result and contact Monarch support if the behavior remains inconsistent. Do not promise that removing or adding a dot will fix every case.

Launch-week users also reported silent errors or missing attachments. Current Monarch documentation now describes import-error notifications and receipt imagery, so rely on the current official behavior and use isolated reports only as symptoms to investigate.

After one controlled retry, collect the sender address, destination, send time, file extension and size, total email size, screenshot of Monarch sender verification, Sent-folder evidence, and any bounce or Monarch notification. Remove sensitive card or personal details that support does not need.

If a small, readable, supported receipt sent from an accepted address still does not create a receipt record, contact Monarch support with that evidence. If the message never left the connected mailbox, troubleshoot the upstream mail sender instead.

Stop using this guide the moment the receipt appears in the Receipts tab. From there, pending status, date windows, merchant text, amount, retries, and Find match belong to matching troubleshooting. Keeping that stop condition prevents duplicate imports.