Reconcile Payments in an AR Automation Platform

When an accounts receivable (AR) automation platform flags a payment mismatch, it means the payment record does not agree with the invoice, bank activity, or customer account data the platform expected. Reconciliation helps you identify the cause, apply or correct the payment accurately, and preserve a clear audit trail without forcing a match that could misstate a balance.

What You’ll Need

• Access to the AR platform and the relevant customer account, invoice, remittance advice, and payment record.
• The bank statement, payment processor settlement, or other reliable source showing the amount received, date, currency, and payment reference.
• Permission to review or update cash application records. If you cannot edit a record, identify the person or team who can approve the correction.
• Your organization’s procedures for fees, foreign currency, short payments, write-offs, refunds, and approval limits.

Step-by-Step

1. Pause before accepting a suggested match. Open the mismatch alert and note the customer, payment, affected invoice or invoices, amount, currency, and date. Do not post an adjustment or mark the item resolved simply to clear the alert. First establish what actually happened using source records.
2. Confirm the cash received. Compare the payment record with the bank statement or processor settlement. Check the settled amount rather than relying only on an email, payment notification, or amount entered by a customer. Confirm whether the platform displays gross or net proceeds; a processor may deduct fees before depositing funds.
3. Check the payment identity and customer. Compare the payer name, account, payment reference, invoice number, and remittance advice. A parent company, payment service, or shared bank account may pay on behalf of a customer. Use documented evidence to identify the payer; do not assign funds based only on a similar name or a convenient amount.
4. Compare dates and status. Check the payment date, bank posting date, settlement date, and the date range used by the platform. A payment initiated near a cutoff may appear in a later bank period. Also check that the transaction is settled rather than pending, reversed, or duplicated. A timing difference may require waiting for a feed update, not editing the amount.
5. Review the invoice balance and prior activity. Open the invoice ledger and look for earlier payments, credit notes, discounts, write-offs, reversals, and unapplied cash. Confirm the invoice is still open and that another user or automated rule has not already applied some or all of the payment. This helps prevent duplicate application.
6. Identify the kind of mismatch. Compare the received amount with the amount due and classify the difference: partial payment, overpayment, combined payment, deduction, fee, currency difference, duplicate, or missing reference. Check the platform’s alert details and matching rules, but treat them as clues rather than proof.
7. Apply the payment only to supported invoices. If remittance information identifies multiple invoices, verify that their amounts add up to the payment, accounting for any documented deductions. Apply the cash to those invoices using the platform’s allocation screen. If the customer paid less than the balance, leave the remainder open unless an approved policy says otherwise. If a payment covers several invoices, split it rather than applying the full amount to one invoice.
8. Handle deductions and currency differences according to policy. For a bank or processor fee, confirm the fee on the settlement record and use the designated fee or clearing account if your procedures permit it. For a short payment, identify whether it is a customer deduction, dispute, discount, or unexplained difference; do not silently write it off. For foreign currency, verify the transaction currency, exchange rate source, and any realized gain or loss treatment specified by your accounting process.
9. Leave uncertain funds unapplied and escalate. If you cannot reliably identify the customer or invoices, keep the payment in the appropriate unapplied-cash or suspense workflow. Add a concise note describing what you checked, attach supporting documents where allowed, and route it to the cash application or accounting reviewer. Avoid creating a new customer or invoice just to force a match.
10. Save, verify, and document the resolution. Review the proposed allocation and remaining invoice balances before posting. After saving, confirm that the payment status, invoice balance, and bank reconciliation are consistent. Record the reason for any adjustment, the source evidence, and any approval in the platform’s audit trail or designated notes. Reopen the alert or reconciliation view to make sure it cleared for the correct reason.

Common Mistakes

• Matching on amount alone: Several invoices or customers can have the same amount. Verify references and account history too.
• Ignoring gross-versus-net settlement: A deposit smaller than the customer’s payment may reflect a documented processor fee. Confirm the settlement breakdown before treating the difference as a short payment.
• Applying a partial payment as full settlement: This can leave an inaccurate zero balance or hide an outstanding amount. Apply only the cash received and handle the remainder under policy.
• Posting an unsupported write-off: A small mismatch is not automatically immaterial or eligible for write-off. Follow approval rules and retain evidence.
• Editing source transactions to silence an alert: Changing a payment amount, date, or customer without evidence can damage the audit trail and create downstream errors.
• Forgetting duplicate or reversed entries: Check bank activity and transaction status before applying cash that may already have been recorded.

Tips

• Use remittance advice and structured payment references when available; they often explain multi-invoice payments and deductions.
• Set a consistent review routine for unapplied cash and unresolved mismatches, with clear ownership and escalation paths.
• Keep an audit note factual: state the amount, evidence checked, allocation made, and approval received. Avoid putting unnecessary sensitive information in notes.
• When a mismatch repeats, review the cause at its source, such as customer reference formatting, bank-feed mapping, currency settings, or a matching tolerance that does not fit your process.
• Use automation suggestions to prioritize review, not as a substitute for confirming cash and customer intent.

Troubleshooting

The payment is not visible in the bank feed: Check whether the transaction has settled, whether the feed has refreshed, and whether the correct bank account and date range are selected. Compare with the bank’s online transaction detail. If it remains absent, follow your bank-feed or integration support process rather than entering a duplicate payment.

The amount differs by a small value: Look for documented fees, currency conversion, a discount, or a deduction on the remittance and settlement records. If the difference is unexplained, leave it unresolved or unapplied and ask the appropriate reviewer. Do not invent an adjustment.

The customer says the invoice was paid, but no remittance is available: Ask for a payment confirmation that identifies the amount, date, payer, and invoice references. Verify receipt independently before applying it. Until the funds are identifiable, retain them in the approved unapplied-cash workflow.

The platform shows a duplicate or already-applied payment: Inspect the transaction history and bank activity to determine whether there are two real deposits or one payment imported twice. Do not delete or reverse a posted transaction without following the correction and approval process.

The mismatch remains after saving: Refresh the reconciliation view, confirm the allocation was posted rather than left as a draft, and check whether the alert is tied to another invoice or period. If the figures still disagree, capture the transaction reference and relevant evidence and send them to your platform administrator or accounting support team.

Frequently Asked Questions

Should I force a match if the amount is close?
No. A close amount is not enough evidence. Confirm the payer, reference, settlement, and invoice allocation; otherwise keep the cash unapplied and escalate.

What should I do with a payment that covers several invoices?
Use remittance advice or other reliable customer instructions to split the payment across the listed invoices. Check that the allocations, plus any documented deduction, reconcile to the received amount.

Can I write off a small difference?
Only when your organization’s policy permits it and the required approval is documented. Otherwise, keep the balance open or route the difference for review.

Why can the bank deposit be lower than the customer payment?
A payment processor may deduct fees, or currency conversion may affect the deposited amount. Confirm the settlement breakdown and use the accounting treatment your organization has approved.

When should I leave a payment unapplied?
Leave it unapplied when the customer, invoice, amount, or payment status cannot be established confidently. Document the checks made and send it through the designated review process.

What evidence should I keep?
Retain the relevant bank or settlement record, remittance information, invoice details, allocation explanation, and approval where required, following your organization’s recordkeeping rules.

Related

• Increase Dedicated Video RAM: What You Can Actually Change
• Evaluate AI Agent Monitoring Tools for Production
• How to Spot a Fake GTA 6 Leak or Insider Account