Cash application links receipts to customer invoices and related adjustments. Deduction review explains differences between what was billed and what was paid. Keep those two tasks connected so a payment can be applied without losing the unresolved reason for a short payment.
Start with the receipt and remittance.
Identify the customer, amount, date and references on the incoming payment. Use the remittance to understand how the customer allocated it. X12’s supply-chain guidance describes the 820 as a payment and remittance transaction. Electronic remittance information is useful context; it should still be matched to the receipt and relevant invoice records.
Preserve the residual question.
When payment is below the invoice balance, record the deduction reference and reason. Do not make the financial difference disappear simply to mark an invoice as paid. The accounting treatment belongs to an authorized accounting owner. The operating record should preserve which amount is explained and which amount still needs review.
Avoid counting the same outcome twice.
An approved credit may later appear in another remittance or arrive as a separate repayment. Link that settlement to the original case. Check whether a later credit has already reduced an open balance before treating a receipt as additional recovery. Keep the references that support the conclusion, not just the final status.
Handle partial and combined payments explicitly.
One payment can cover many invoices, and one invoice can be settled through several payments and adjustments. Preserve the allocation and remaining balances. When the source information is incomplete, route the question to the owner instead of forcing a match based only on the closest amount.
Reconcile at the appropriate level.
Review the case, customer account and accounting records together. Confirm the financial effect, settlement date and any remaining amount. A closed operating task should not mask an unreconciled balance. Use clear reconciliation ownership and retain the evidence that explains why the case is considered complete.
Sources and scope
Safa editorial framework. Reviewed October 23, 2026. Examples are illustrative; confirm account-specific requirements with the trading partner.