How can receipts get into QuickBooks Online automatically without duplicates?

What does each automatic route create?

Intuit's "Upload your receipts to QuickBooks" page says QuickBooks extracts a receipt's details and creates a transaction for you to review, which you can add to an account or match to an existing transaction. A captured receipt is staged, not posted: it reaches your books only when someone adds it, recording a new transaction, or matches it to one already there.

QuickBooks Online's own capture has three routes, all of which stage:

• Upload. Intuit's upload page covers uploading from your computer or Google Drive, one receipt at a time.
• Mobile capture. The same page has you install the QuickBooks mobile app on an iOS or Android device to upload receipts from it.
• Forwarding address. Intuit's "Email receipts and bills" page has you create an address ending in @assist.intuit.com and turn forwarding on user by user. One email can carry several receipt images, so it doubles as the batch route, and what arrives waits in Receipts for review.

Intuit's upload page says the feature is limited for QuickBooks Online Free and QuickBooks Online Lite.

Two more routes can post:

• The bank or card feed. Intuit's "Match your bank and credit card transactions" page says downloaded transactions wait for review and don't affect your books until you match or categorize them: match one if you already entered a record for it, or categorize it if you have none, which creates a brand-new record. Intuit's bank-rules page says a rule with auto-post on posts each downloaded transaction it applies to immediately, with no chance to review it.
• A connected capture app. For example, Dext's undated page "How to publish documents from Dext to QuickBooks Online" says a paid item appears in Expenses in QuickBooks Online as a paid transaction and an unpaid one as a bill waiting to be paid, that Dext attaches the original image or PDF, and that automatic publishing sends items once they are marked Ready.

Why does one purchase arrive twice?

The feed reports the payment; capture reports the document. They are independent sources for one purchase, so on a connected account every captured receipt is a duplicate candidate. Intuit's matching page says matching links bank transactions to records you already created, like receipts and bills, and prevents duplicate entries. Intuit's undated page "Fix duplicate transactions in QuickBooks Online Desktop bank feeds", whose text addresses QuickBooks Online, names the core failure: adding a downloaded transaction instead of matching it.

Duplicates arise in four ways:

• Two routes post one purchase. A connected app publishes a paid expense and the feed line is categorized or auto-posted.
• A receipt posts before its charge. The receipt is added because the charge has not downloaded, and the charge is later posted separately instead of matched.
• One document is captured twice. A receipt snapped at the counter is also forwarded, or a mailbox rule delivers a message twice, leaving two copies waiting for review.
• A connected app publishes again. Whether a re-sync or reconnection can publish one item twice is answered only by that app's own documentation, so look it up for yours and rely on the reconciliation checks below until you have.

Is it a duplicated transaction or a duplicated document?

Only the first misstates your books, and each needs a different remedy:

What does QuickBooks match by itself, and what waits for you?

Intuit's upload and matching pages describe matching in both directions as a suggestion that a person confirms:

• From a receipt. Intuit's upload page says that if QuickBooks finds existing transactions matching an uploaded receipt, it shows the number of matches, and you choose the matching expense and select Match. If it finds none but you know one exists, the page says to select Search manually.
• From the feed. Intuit's matching page says QuickBooks suggests matches for transactions with the same amount within a date range of 90 days before to 20 days after the transaction date, and gives no suggestion when fees or discounts change the total, payments were deposited together, the record is outside that range, or it is already reconciled (exclude the charge then, the page says, so it doesn't create a duplicate). So no suggestion never proves no record: before categorizing, search with Find match, as Intuit's duplicate-transactions page advises.

Two settings let items post without anyone confirming a match: a bank rule with auto-post on, and a connected app's automatic publishing, such as Dext's. Your judgment is load-bearing in three places:

• Before you select Match. Intuit's matching page bases feed suggestions on amount and dates, and the upload page doesn't say what receipt suggestions rest on, so two same-amount purchases can be offered for each other. Compare vendor, date, amount and the card's last four digits, which Intuit's email-receipts page says QuickBooks pulls from the receipt image.
• When you leave a suggestion unselected. It links nothing, and whoever next acts on the receipt or the charge can post a second transaction.
• Where auto-post is on. It removes the review in which you would see that a charge already has a record.

How do you give each payment method one posting route?

Write down, for every card, bank account and cash fund, the one route allowed to post. Every other route may only match to what that route posted. Which route posts depends on the account:

Where a connected app attaches its own image, as Dext's page says it does, do not also send those receipts to QuickBooks' capture, or one transaction gets two copies. If the app publishes unpaid bills, match the later feed payment to the bill. Intuit's matching page says matching a transaction to a bill marks it paid, and to verify you actually sent the payment first. Categorizing the payment instead would record a second expense and leave the bill open, so the vendor balance stays too high. Keep auto-post rules off on any account whose receipts are captured or published by an app.

A completed route map, with invented accounts, looks like this:

Where the last column says procedure, no setting enforces the rule, so the reconciliation checks are what catch a slip. Date the map each time you check its settings.

What happens to a receipt captured before its charge appears?

Leave it waiting for review. Intuit's upload page says swiping a receipt with no match label in the mobile app creates an expense; on a card whose feed posts, don't swipe it. Then work in this order:

1. When the charge downloads, review it in the bank feed. If Find match turns up nothing that records it, categorize it.
2. Open the waiting receipt, choose the transaction the feed just created from its suggested matches or with Search manually, and select Match.
3. Open that transaction and confirm the receipt image is on it.

If a receipt was added early by mistake, QuickBooks can suggest its charge as a match to that record when the amounts agree and the dates fall within the range above. In the bank feed, verify the suggested match, then select Post (if it's wrong, select Find other match): Intuit's matching page reserves categorizing for charges with no existing record, and categorizing this one as well is how the duplicate is made. If the charge has not arrived within your card's usual delay, still do not add the receipt; a feed that is not downloading is a separate problem to fix first.

On a connected card with receipts snapped at the point of purchase, this applies to every purchase: the feed transaction is the posting, the receipt is the attachment, and each match is checked as above before you select Match.

How do you handle receipts from people who don't work in the books?

Intuit's email-receipts page says you can give standard users permission to forward receipts and that each must send from the email address they use to sign into QuickBooks. The same page says a sender needs standard user permissions with Vendor access at a minimum. What they send waits for review, but their role decides whether they could also post it: Intuit's "User roles and access rights" page says the Standard all access role can do everything related to vendors and purchases.

Three controls keep these submissions under review:

• Decide who submits. Turn forwarding on only for the people named in your route map, and compare that list with Manage forwarding email whenever you review the map.
• Check each submitter's role. Where it lets them add purchases or categorize bank feed lines, as Intuit's roles page says Standard all access does, tell them to send only and let the reconciliation checks catch a slip.
• Keep one reviewer. The bookkeeper adds or matches every submitted receipt, against the route map.

Where staff send receipts through a connected app, the app decides whether they post: Dext's page says standard users need publishing permissions enabled and, where approval workflows are set up, items must complete approval before publishing. Record on the map who can publish.

How do you control automatic forwarding from a mailbox?

Because forwarded receipts must come from a permitted user's sign-in address, a mailbox rule that forwards them automatically has to run in that user's mailbox. Three habits keep its output clean:

• Control what is forwarded. Base the rule on the specific senders of your receipts rather than a broad keyword, so newsletters and shipping notices stay out.
• Recognize a repeated delivery. Two waiting items with the same vendor, date and amount may be one receipt delivered twice or two real purchases. Treat them as one only if both images show the same document (same receipt or order number and time); otherwise handle each on its own, expecting two charges on a card with a feed.
• Never post a non-receipt item. Anything waiting for review that is not a receipt is never added or matched. Log it as settled on the route map, since Intuit's upload and email-receipts pages don't document removing it.

What do you check at each reconciliation?

Run these checks every time you reconcile a bank or card statement, not at year end. Each starts from a complete list rather than from the receipts you remember:

• Extra transactions. Intuit's "Learn the reconcile workflow in QuickBooks Online" page has you compare each transaction in QuickBooks with your statement. A QuickBooks transaction with no statement line of its own, carrying the same amount as one that has a line, is a likely duplicate, so resolve it before you finish.
• Doubled expenses. Run the General Ledger report for the period (Intuit's ledger-report page has you search for it in Reports) and look across all expense accounts for the same payee and amount twice, and confirm each pair as in removal step 1 before treating it as a duplicate. This catches a duplicate charged to cash or to the wrong card, which no statement comparison shows.
• Vendor balances that are too high. Intuit's vendor-balances page points to the Vendors list for your balances with vendors. Because matching a payment marks its bill paid, an open balance on a bill you know is paid means its payment was either recorded some other way or not yet recorded: find the payment in the bank feed before you change anything.
• Stale receipts. Anything waiting for review longer than your card's usual delay is waiting on a charge that should have arrived, belongs to a method with no feed and should be added from review, or is a second copy or non-receipt item to log as settled. Settle it now.

How do you remove a duplicate without losing the receipt?

The IRS's "What kind of records should I keep" page lists receipts among supporting documents and says it is important to keep these documents because they support the entries in your books and on your tax return. The same page says all requirements that apply to hard-copy records also apply to electronic records. Intuit's "Void or delete transactions" page says deleting removes a transaction everywhere except the audit log. So check before you remove anything:

1. Confirm the two record one payment. Intuit's duplicate-transactions page says to check your statement: a charge that appears there twice really happened twice, so change nothing in your books. For cash, open both receipts: two different receipts are two purchases.
2. Decide which transaction survives: the one your route map says posts.
3. Open both. If the receipt image is on the one you will remove, download it from the Attachments list under Settings, which Intuit's attachments page says lets you edit, download and remove attachments.
4. Open the survivor, select Attachments, browse to and select the downloaded file, then save and close.
5. Reopen the survivor and confirm the image opens.
6. Only then remove the other transaction. If it was created from the feed, as when a connected app's transaction should have been matched, remove it as the related question on duplicate bank transactions describes rather than deleting it here.

What does one purchase look like before and after the fix?

Say the owner snaps a hardware-store receipt for 86.40 on card 4417 on 3 March and, because the charge has not downloaded, adds it as an expense. On 6 March the charge downloads and a colleague categorizes it instead of matching it. The books look like this before the fix:

Office supplies shows 172.80 for an 86.40 purchase, and at reconciliation the statement's single 86.40 charge leaves one of the two as an extra. The map says the feed posts for card 4417, so B survives: download the image from A, attach it to B, confirm it opens on B, then delete A. Undoing B and matching it to A, as Intuit's duplicate-transactions page does for feed-added transactions, also works, but that is bank-transaction cleanup, which the related question on duplicate bank transactions covers. After the fix, one transaction remains:

Office supplies now shows 86.40, and the one transaction both agrees with the statement and carries the receipt.

How do you know the setup is still working?

The reconciliation checks are the test: if the four checks find nothing (apart from items logged as settled), the map held for that period. Separately, re-check every setting in the map's last column (forwarding users, submitters' roles, auto-post rules, each connected app's publishing settings) at each reconciliation, and again after any update to QuickBooks or a connected app, a new card or a new user. Intuit's bank-rules page says the All transactions dropdown in Bank transactions filters for Auto-post rules, and an auto-posted transaction carries an AUTO badge. Where a connected app runs beside QuickBooks' own capture, test it after an update to either: send one real receipt through and confirm it ends up in exactly one place, on the transaction your map says posts.