Cash application

The matching workflow compares customer evidence, amount and invoice references. A repeated bank event resolves to its existing source identity. A processor settlement can link to an already recognized receipt only through a confirmed mapping; similar memo text is a clue for review, not permission to discard a deposit. Lower-confidence items remain visible to the clerk. Check the source transaction, proposed invoices, currency and remaining receipt amount together before accepting the distribution.

Only accepted invoice payment allocations consume receipt cash and reduce the corresponding open invoices. A discount or short-pay suggestion requires its own approved credit or write-off rather than pretending the missing amount was received. An unapplied remainder remains on the customer account for later work. Enforce the receipt total and each invoice’s remaining balance before committing allocations. Proposed match and Draft records do not reduce receivables, and a repeated application request must return the existing result instead of creating another allocation.

Recognize the receipt’s cash effect once. When cash has already been booked with an unapplied balance, a later allocation moves that balance to the relevant receivable and does not debit cash again. Keep the ledger request and confirmed result attributable to the same source. A returned or refunded receipt restores only its prior accepted effects and preserves the correction history. For project-billing references, request application from the owning system and update the displayed balance only from its confirmed outcome.

• Auto-Match Proposals. Open the related records within your assigned scope.
• Unapplied Cash. Open the related records within your assigned scope.