How to Record a Customer e-Transfer Overpayment

To record a customer e-Transfer overpayment, record the full amount that reached the bank, apply only the amount actually due to the invoice, and leave the excess visible as a separate customer credit or overpayment. Then document whether the customer authorized the credit for a future invoice or the business returned it in a new payment. Never reduce the incoming transfer to force it to equal the invoice.

An e-Transfer notification can document the payer, amount, date, status, and reference. It cannot decide why the extra money was sent, whether the customer has a valid credit, or how GST/HST should be adjusted.

Is an Overpayment the Same as a Deposit or Refund?

No. Start with the obligation that existed when the money arrived:

• A customer overpayment is more than the amount currently due.
• A partial payment is less than the amount due and leaves an open balance.
• A customer deposit or advance is money intentionally paid under an agreement before the final sale or invoice is settled.
• A refund is a new outgoing payment that returns money after the original receipt completed.
• A duplicate payment repeats an amount the customer already paid and normally needs the same overpayment review.

Do not choose among these labels from the e-Transfer message alone. Compare the completed deposit with the invoice, contract, existing credits, and customer instructions. If the customer intentionally prepaid under agreed terms, use the customer-deposit workflow. If several transfers are settling one invoice, use the partial-payment workflow.

What Should a Customer-Overpayment Record Include?

Keep the incoming payment intact and connect it to an overpayment record containing:

• Customer and displayed payer names
• Invoice, order, contract, or account number
• Amount due immediately before the payment
• Existing credit already on the account
• Full e-Transfer amount and completed-deposit date
• Interac reference, when available
• Amount applied to the invoice
• Excess left as a customer credit
• Reason, such as a typing error or duplicate payment
• Customer instruction, decision date, and approver
• Future invoice to which a credit was applied, if any
• Refund date, recipient, status, and new reference, if any
• GST/HST review and related document, when required

A simple control is:

overpayment = completed payment - amount properly applied

The customer account, payment register, and bank deposit should all preserve the original amount. The allocation explains what happened to the excess.

How Do You Record an e-Transfer Overpayment?

1. Confirm that the full payment was deposited

Open the financial institution through its known app or website. Match the notification to the completed deposit using the amount, payer, date, and reference.

Do not refund money based only on a screenshot, sent notice, or unexpected email. Interac explains that email or text carries the notification while financial institutions move the money. If the transfer is pending, declined, cancelled, or expired, keep the invoice open and use the e-Transfer status workflow.

2. Recalculate the customer balance

Review the original invoice total, valid credits, earlier completed payments, and any written payment plan. Calculate the balance immediately before the new payment.

Apply only that balance. If a customer owes $860 and a completed e-Transfer is $900, preserve the $900 receipt, apply $860 to the invoice, and show $40 as unapplied. Do not change the invoice to $900 or edit the bank receipt down to $860.

If the invoice itself is wrong, correct it using the business's normal invoice, credit-note, or debit-note process. A payment allocation should not disguise a pricing or tax correction.

3. Confirm why the extra amount was sent

Contact the customer through a trusted method already on file. Confirm whether the amount was accidental, a duplicate, an intended advance, or payment for another invoice.

Preserve the answer. A vague message is not enough to allocate money across accounts when several balances are possible. If someone other than the customer sent the transfer, keep both names and confirm the relationship before applying or returning the excess.

4. Document one outcome

The usual outcomes are:

1. Refund the excess: approve a separate outgoing payment for the exact excess.
2. Keep a customer credit: obtain clear authorization and leave it visible until used or returned.
3. Apply it elsewhere: identify the other invoice or agreed advance and record the allocation.

Do not silently treat an unexplained excess as a tip, additional sale, or income. The contract, refund policy, applicable law, and accounting method may affect what the business can do with the money. Get professional advice when the customer disputes the balance or the right to retain it.

5. Review GST/HST separately

The payment method does not determine the tax result. If the invoice and tax were correct and the customer simply sent too much, do not invent additional taxable sales to match the bank deposit.

If the business actually adjusts, refunds, or credits GST/HST it previously charged or collected, the CRA's current guidance describes when a credit or debit note is used and what it must contain. If tax was collected in error, the CRA directs the supplier to refund or credit the customer and issue a credit note before making the related net-tax adjustment.

An unapplied credit used for a future taxable supply can raise different timing questions from a prompt refund. Keep the invoice, customer instruction, credit record, and payment evidence together, and have a qualified accountant confirm an unclear entry.

6. Record a refund as a second payment

If the business returns the excess, independently verify the recipient details. Send the approved amount and create a new outgoing transaction with its own date, amount, status, and reference.

Do not delete the incoming payment or reuse its reference. The customer-refund workflow explains how to link the receipt, approval, credit document, outgoing transfer, and bank withdrawal.

Be cautious if someone asks for the refund to go to a different person, email address, or mobile number. Pause and verify the request through established customer details; contact the financial institution about suspected fraud.

7. Reconcile the customer and bank records

At month-end, review the invoice, full incoming payment, amount applied, remaining credit, later application or refund, any tax document, and the matching bank activity.

Investigate credits with no customer instruction, refunds with no completed receipt, unexplained negative customer balances, duplicate notification rows, and refunds that do not match the bank. Do not backdate a refund or erase the original receipt when the overpayment crosses a reporting period.

Which Overpayment Edge Cases Need Extra Care?

One transfer pays several invoices

Keep one payment record, then allocate the completed amount across the identified invoices. Only the remainder after all authorized allocations is the overpayment.

The customer pays twice

Keep both completed transfers and references. Apply the first valid payment, then place the duplicate in the overpayment workflow. Do not mark the second transfer cancelled if it reached the account.

The customer wants a future credit

Record the authorization, amount, date, and customer account. When the credit is used, link it to the new invoice instead of recording a second cash receipt.

How TransferLog Helps Organize Overpayment Records

TransferLog organizes details found in supported incoming and outgoing Interac e-Transfer notification emails from connected Gmail, Outlook, or iCloud inboxes. You can search and filter transactions, assign categories, and export CSV or PDF on the Pro plan.

Categorize the original receipt as a customer payment with an overpayment note, and categorize any outgoing transfer as a customer refund. Then reconcile the export with invoices, customer credits, tax documents, and the bank account.

TransferLog does not calculate customer balances, hold credits, issue invoices or credit notes, approve refunds, access bank accounts, determine GST/HST, or resolve disputes. It organizes the notification side of the audit trail.

Official Sources

• CRA: Business records
• CRA: General Information for GST/HST Registrants
• CRA: Amounts collected as GST/HST in error
• Interac e-Transfer Help Topics
• Interac e-Transfer Terms of Use

This article provides general record-keeping information, not tax, accounting, legal, or fraud-recovery advice.

Organize supported customer-payment notifications with TransferLog. Start free, then reconcile the export with invoices, customer credits, and bank records.