The AutoEntry duplicate check with File Matching is a great feature that gives you full control over how you manage duplicate transactions between AutoEntry and your integrated accounting software.

File Matching is presently available for AutoEntry companies integrated with SBCA, Xero and QuickBooks Online. Our standard duplicate check still exists for all other integrations.

In this article:


AutoEntry will flag invoices/bills that appear to have duplicate transactions within your integrated accounting software, and if those matching transactions do not already have a file attached (e.g. receipt image). File Matching will then allow you to attach the AutoEntry document file to the accounting software transaction.

The duplicate invoice checking is set to 'check for duplicates' by default. This function can be turned on and off on your company's Integrate page.

The Duplicate Check

Once an invoice has been processed within AutoEntry, and you attempt to publish it through to your accounting software, AutoEntry will do a check of the existing invoices/bills in your software. This automatic check looks for exact matches between your accounting software and AutoEntry based on:

  • Supplier/Vendor Account

  • Invoice Date

  • Invoice Number

  • Gross Total

If a duplicate invoice is found, a warning symbol will appear beside the invoice in AutoEntry. Clicking on the warning will display the summary details of both invoices:

This window shows that a duplicate has been found and the invoice details present in Sage/Xero/QuickBooks and the matching invoice details in AutoEntry along with 3 options on what you want to do next:

  • Attach - Where no invoice image exists in the accounts package, e.g: it was previously manually entered, then you can attach the image in AutoEntry to the data already present in your accounts updating the data there. If an image already exists with the invoice data then this option will not appear.

  • Publish - This will overwrite the duplicate check and force the invoice through to your accounts, creating a duplicate transaction.

  • Reject - This will send the invoice to your rejected folder where you can delete it from AutoEntry if required.

When the image is attached to the existing data in your accounts package, AutoEntry only attaches the image there. No edits or updates are made to the existing data. We simply attach the missing image to your data.

When AutoEntry attaches an image in this way, the Published icon is replaced with the attached image below to show that AutoEntry only attached the image and did not create or publish the invoice data.

Additionally, to improve the duplicate check you can set the duplicate check threshold (see here) to aid the duplicate check for any invoice that may have been entered using a different date.


This feature only works with Purchase invoices/Bills as Sales invoices are created in Sage based on your invoice template there. Sales invoice images are not published through from AutoEntry for Sales invoices in Sage Accounting.

For Sage Accounting, the user can also choose that the invoice number should not be part of the duplicate checking.


Duplicate Sales invoices are not permitted for Xero users. Therefore, the only option available for a duplicate Sales invoice is to reject it (although another option would be to adjust the invoice number).

QuickBooks Online

Matches will be suggested for Expenses without a reference number if all other conditions are met (this is to facilitate File Matching of Expenses added directly from the Bank Statement via QuickBooks' Banking module).

For QuickBooks Online users, if the duplicate AutoEntry invoice is marked as paid by cheque and the 'Duplicate check warning' advanced setting is defaulted to 'On' (the default setting), then a 'duplicate document number' error message will display when attempting to publish the invoice as a duplicate from AutoEntry - this can be resolved by simply turning off the 'Duplicate check warning' in QuickBooks Online.

Last edited:

Dec 7, 2022, 11:47 AM

Did this answer your question?