Designed to surface historical duplicates and credits that may still be recoverable.
Find the same economic obligation paid twice.
Duplicate payments do not always look identical. InnRecon normalizes vendor and invoice data, compares distinct payment records and applies exclusion rules before a potential duplicate becomes a recovery case.
How duplicates survive normal controls
A duplicate can cross accounting periods, use a slightly different invoice number, sit under a vendor-name variation, originate from an emergency manual payment, or move through a different payment method. Each entry can be posted correctly while the underlying obligation was still paid twice.
What InnRecon tests
- Exact vendor, invoice, amount and distinct-payment matches.
- Controlled invoice-number and vendor-name variants.
- Same-amount patterns supported by purchase-order, date, GL or payment-reference evidence.
- Selected valid credits that remain unapplied when the available records support the conclusion.
False positives have to be designed out
- Voids and reversals.
- Correcting entries.
- Legitimate split payments.
- Recurring purchases with valid repeated obligations.
- Same-dollar transactions with insufficient corroboration.
The core screen can begin with the ledger your hotel already uses.
A monthly AP payment ledger or check register provides vendor, invoice, payment amount, payment date and separate payment reference. The first historical review uses a deeper lookback, while ongoing monthly monitoring can use an overlap window to catch late entries and corrections.
Monthly monitoring looks for new anomalies while keeping prior open recoveries alive.
Supported cases move through vendor communication, follow-up and refund or credit confirmation.
Let us find the money your hotel is losing.
See the recovery opportunity in your own financial data before deciding whether to authorize InnRecon to pursue it.