Duplicate bills, and vendors that send a bill plus a receipt

Some suppliers send one transaction twice: an invoice, then a payment receipt for the same charge. TALISK_HQ watches for that so the expense is never counted twice.

What TALISK_HQ does on its own

When a new bill arrives (by email scan, upload, or receipt scan), TALISK_HQ compares it to what is already in the book:

• Strong evidence (the identical file, or the same invoice number from the same supplier): the copy is filed straight into the Duplicates bucket on Ledger › Expenses. It keeps its document and points at the original, and it can never be approved or reach your books. If it was filed wrongly, open it and use "Not a Duplicate" to return it to review.
• Weaker evidence (the invoice numbers share a core but differ by a prefix, like CWS5320979 on the bill and 5320979 on its receipt, or only the amount and date agree): the bill stays live in your review queue with a "Possible duplicate" banner, and you decide.

Answering a "Possible duplicate" banner

Open the flagged bill from Ledger › Expenses. The banner names the bill it may duplicate and offers two answers:

• It's a duplicate: files this copy into the Duplicates bucket. The original stays live and is the one you approve and pay.
• Not a duplicate: clears the flag, and the bill proceeds as an ordinary payable.

A flagged bill is never auto-approved, even by a recurring-bill rule: TALISK_HQ waits for your answer first.

When the two documents name different suppliers

A bill and its receipt sometimes carry two names for one company (for example a courier that bills as one company but sends receipts under its brand name). After you confirm such a pair as a duplicate, TALISK_HQ offers to merge the two vendors. Merging teaches the book that the two names are one supplier, so the next bill-plus-receipt pair from them is caught automatically, and bank charges under either name match their bills. You can also merge vendors any time from Ledger › Expenses › Vendors.