Other languages

Optional machine translation through Google Translate. Wording may be inaccurate; consult the reviewed Arabic or English edition for precise information. This is not a Zawid-reviewed translation.

The page address is sent to Google only when you press the button. More languages are available in Google Translate. It opens a new tab under Google’s privacy policy. Google privacy policy

Account Management

Entered a Payment Twice? Find the Duplicate and Correct the Customer Balance

A repeated payment entry can make a customer balance look lower than it should. Learn how to verify the actual receipt, identify the duplicate, correct the record, and issue an updated statement.

Our editorial and review policy · About the product developer

You received a payment and recorded it. Later that evening, you returned to the customer's messages, could not remember whether you had saved it, and entered it again. The next day, the balance looked lower than expected. Even a small duplicate can affect follow-up: you might request less than you are owed or mistakenly interpret a balance as credit belonging to the customer.

Before deleting any transaction, establish what happened in reality. Two identical amounts are not sufficient evidence of duplication: the customer may have made two payments of the same value. Connect each saved transaction to a separate actual receipt, then correct the entry that has no corresponding real event.

Start by asking how many times the money arrived

Gather the available evidence of receipt: a receipt, a transfer statement, or a documented collection note. Compare the transaction reference, date, customer, and currency. Two messages about one transfer do not mean two payments, and similar dates alone do not establish a duplicate.

Search the account and transaction history for the amount and note. Open the details of each suspect transaction instead of relying on a shortened row. One may record an amount due while the other records a payment, or one may belong to another currency or account.

If you cannot establish how many receipts actually occurred, leave the record unchanged until you can. Removing a valid entry may create another discrepancy that is harder to resolve than the original question.

A worked example of one extra entry

Assume a customer account in one currency with a zero opening balance. You recorded 1,500 due, then received 400 once. The correct balance is 1,100. Entering that payment of 400 twice, however, produces a balance of 700.

ItemCorrect recordRecord containing a duplicate
Amount due recorded1,5001,500
Total payments shown400800
Balance owed by the customer1,100700

The difference between the balances is 400, the value of the extra entry. Correcting the record restores one documented payment; it does not change the fact that the customer paid 400. Do not fix the mistake by adding a new debt of 400: no new sale or amount due has arisen.

A checklist before making a correction

  • Do both entries belong to the same account and currency?
  • Are both actually payments, or does one represent something else?
  • Do they share one reference, or are there two separate transfers?
  • Was the money actually received, or was a payment promise recorded by mistake?
  • Does either entry originate from a transaction in another financial center?
  • Have you shared a statement containing the error that now needs replacing?

Keep a brief note of what you found and which transaction you will retain. For example: “Transfer reference 82 appears in two entries; the money was received once.” This is a review note, not a third financial transaction.

Back up your records before correcting a manual entry

Create a current backup before changing important records and verify that it was saved. The backup guide explains the process. The default portable backup file is unencrypted: protect access to it and do not send it publicly with a support request.

If a manual transaction represents a real event but has the wrong amount or date, open its details and edit it after confirming the correct information. If it is a confirmed duplicate of an existing entry, retain the correct version with the appropriate details and attachment. Delete the extra version through the transaction actions, reading the confirmation message carefully.

Do not delete both entries and rebuild the record from memory. Do not assume that a permanent undo button will let you recover any deletion later. Check your selection before confirming and keep a backup when needed.

A transaction may be identified as originating from a financial center. In that case, the app may direct you to that center rather than allow it to be edited as a manual entry. Review the original source instead of adding an arbitrary opposite entry to the customer's ledger to conceal its effect.

Reconcile again after the correction

Reopen the customer account and confirm that only the valid payment remains. In the example, it should show 1,500 due, 400 paid, and a balance of 1,100. Also check the date and note: a correct total is not enough if the transaction still belongs to the wrong day or account.

Create a new statement for the same period and compare it with the original evidence. If you previously sent a statement, tell the customer that the replacement corrects a duplicated entry and clearly state the correct amount. Do not imply that the correction creates an additional payment obligation beyond the real balance.

Follow the PDF account statement review steps to choose the period and recipient. A file sent previously does not update automatically when you edit your records. Generate a new version and share it when needed.

A simple habit that prevents a repeat

After saving a payment, return to the account and confirm that it appears before closing the app. Use a clear reference in the note, especially when entering several similar transfers at the end of the day.

If the process was interrupted or you are unsure whether saving succeeded, search the record first. Repeatedly pressing a button or creating a second entry just because you are uncertain can turn a quick check into a duplicate that needs investigation. When importing data, compare a sample of payments with entries you already made manually before adding more.

If the problem is that a known payment is missing from your file, review how the statement period affects the account statement before entering it again.

Frequently asked questions

Should I delete any two entries with the same amount and date?

No. They may represent two valid receipts. Compare them with actual payment references and the details of the transaction before deciding that one is a duplicate.

Should I change the opening balance to correct a duplicate?

Do not use it to hide an error in a recent transaction. Review and correct the entry causing the discrepancy so the account history remains understandable.

Does the old PDF disappear after the correction?

A saved or sent file remains as it was when created. Generate a new statement after your review and identify it as the corrected version when sharing it.

Make every payment explainable

Start with one account and match each payment to money actually received. Download Zawid Accounts from Google Play to organize transactions and review balances and statements on Android, with a free plan and an optional Pro plan.

Useful for someone you know?
Share on WhatsApp