Invoice Overpayment

Overview

Invoice overpayment occurs when the total value received and applied to an invoice exceeds the amount due under the merchant’s calculation and tolerance rules. It can result from customer error, duplicate transfers, wallet fee assumptions, quote changes, or intentional additional payment. The excess should not be recognized automatically as revenue without a documented contractual or customer decision. Within Invoice Overpayment, and especially at the boundary with Overpayment Handling, the invoice should remain distinct from its payment sessions so late transfers, refunds, credits, and exchange-rate changes do not rewrite the original commercial document.

Crypto invoices can receive an amount slightly above the target because wallets or exchanges round quantities. A tolerance can accept the invoice while recording the exact received amount and excess separately.

A materially duplicated payment should be checked against replacement invoices and other customer obligations before refund. The transaction sender may not be a safe refund destination.

The merchant can return the excess, hold it as customer credit, apply it to another authorized invoice, or accept it as a tip or donation only when policy and customer intent support that treatment.

Risks include refund fraud, duplicate fulfillment, tax misstatement, lost customer credit, conversion losses, and fees exceeding the small excess.

Systems should store amount due, amount received, accepted tolerance, excess, valuation, customer decision, refund address verification, transaction, fees, and accounting treatment.

Implementations should link Invoice Overpayment to Crypto Invoice and Overpayment Handling through auditable references. Although the records can share a customer or transaction, Invoice Overpayment retains its own authority, lifecycle, and recovery rules.

For Invoice Overpayment, the invoice and the payment used to settle it should remain separate records. When Invoice Overpayment interacts with Crypto Invoice, the invoice defines the commercial obligation, parties, amount, denomination, tax, due date, and revision history; payment records hold quotes, addresses, transaction identifiers, confirmations, fees, refunds, and settlement. In the relationship between Invoice Overpayment and Overpayment Handling, keeping these layers separate prevents a late payment, repricing event, or refund from silently changing the document originally issued to the customer.