Reference · built on requestOperator by FibricFinance & billing

Duplicate Invoice

Vendor invoices that repeat an amount, number, or document already entered, with a hold proposed before payment.

Request accessPricing ↗

About

The exact repeat is the easy case. Duplicates that get paid change a hyphen, a prefix, or the vendor record. This operator reads every new vendor bill and every invoice file that arrives, and compares them with what the ledger already holds: same vendor, same amount, same date, a number that differs only in punctuation, or the same document under two vendor records.

For each likely duplicate it proposes a hold on the later bill, with the original beside it. For two vendor records that look like one supplier it proposes a review. A person approves the hold, and the receipt keeps both documents and the fields that matched.

This is a reference listing. It documents what Fibric would read from Duplicate Invoice and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • New purchase invoices in Business Central with vendorInvoiceNumber, vendorNumber, invoiceDate, and totalAmountIncludingTax
  • ACCPAY invoices in Xero with InvoiceNumber, Contact, Date, and Total, and bills in QuickBooks Online, NetSuite, or Sage Intacct
  • Coupa invoices by invoice-number and supplier, including those in ap_hold or on_hold
  • Invoice files arriving as Gmail attachments or in a SharePoint, Google Drive, or Amazon S3 folder, compared by content hash
  • Vendor records with taxRegistrationNumber, email, and bank details, to spot the same supplier entered twice
  • Payments scheduled or posted against each bill, so a hold is proposed before the money moves

Proposed actions

  • Target capability: propose a hold on a bill whose number matches an earlier bill for the same vendor after punctuation and prefixes are removed
  • Target capability: propose a review of a bill matching an earlier one on vendor, amount, and date inside your window, under a different number
  • Target capability: propose flagging a file whose content hash matches an invoice already entered, before anyone keys it
  • Target capability: propose merging or marking two vendor records that share a tax registration number or bank details
  • Target capability: propose a message to the AP clerk or the vendor asking which of the two documents stands

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold before the payment run

    A Business Central purchase invoice whose vendorInvoiceNumber repeats an earlier one after normalization is proposed for hold, with both invoices and the scheduled payment shown.

    With Microsoft Dynamics 365 Business Central

  • Catch it in the inbox

    An attachment arriving in the AP Gmail mailbox with the same content hash as a file already entered in Xero is flagged before a clerk keys it.

    With Gmail API, Xero

  • Same supplier, two vendor records

    NetSuite vendors sharing a tax registration number are proposed for review, and bills split across them are compared as one vendor.

    With NetSuite

  • Coupa holds with the reason attached

    A Coupa invoice matching an approved one on supplier, amount, and date is proposed for ap_hold, with the earlier invoice number posted to the AP channel in Slack for the clerk to approve.

    With Coupa, Slack

Requirements

  • A ledger connector with vendor bills and vendor records: Business Central, Xero, QuickBooks Online, NetSuite, Sage Intacct, or Coupa
  • Where invoices arrive as files, a mailbox or folder connector: Gmail API, SharePoint, Google Drive, or Amazon S3
  • A date window and an amount tolerance for near matches, and the recurring vendors whose repeated amounts are expected
  • A hold mechanism in the ledger: an on-hold status, an approval step, or a blocked payment flag
Authentication
It holds no ledger login. Bills, files, and vendor records are read through the ledger, mailbox, and file connectors you attach, with the roles you assign.

Limits

  • It flags and holds. Voiding or deleting the duplicate stays with a person in the ledger.
  • Invoices that repeat an amount by design, such as rent, belong on the list you keep. Otherwise they are reviewed each period.
  • Files are compared by content hash and extracted text. Two scans of the same paper with different noise are not one file.
  • A duplicate keyed and paid before the operator saw it is reported, not recovered.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Duplicate Invoice ↗

Questions and answers

What does approving a hold look like?
Each hold is one proposal showing the new bill, the earlier one, and the fields that matched: vendor, number after normalization, amount, date, or file hash. Approve the hold, mark it not a duplicate, or send it to the vendor for an answer.
What is kept for each pair it raised?
A receipt per pair: both documents, the matching fields, the decision, who made it, and when. Pairs marked not duplicates are remembered so the same pair is not raised again.
Will it block a payment on its own?
No. A hold is placed only after approval, once, and lifted only by a person. Bills it has not matched are untouched.
Ask about Duplicate Invoice

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy