When Should a Payment Be Voided?
A void should reflect a confirmed business reason and the actual status of the payment. Before proceeding, the accounts payable team should establish whether the payment has been printed, transmitted, cleared by the bank, or applied to the supplier's account. A check that has not been presented may follow a different procedure from an electronic payment that has already reached the bank.
- Incorrect payment details: A check or payment record contains an incorrect amount, payee, date, or other required information.
- Lost or damaged check: A physical check needs to be canceled and replaced under company policy.
- Duplicate payment: Review confirms that the same supplier obligation was paid more than once and the appropriate correction process is required.
- Payment reissue: A payment must be canceled before a replacement can be prepared and authorized.
- Supplier or invoice change: A documented correction requires the original payment to be canceled and the obligation reviewed again.
When an electronic payment has already been transmitted or settled, a bank recall, return, or recovery process may be necessary instead of treating the transaction as an ordinary void. The finance team should follow the applicable bank procedure and Epicor workflow.
How the Void Payment Process Works
The process usually begins by locating the original payment using its payment number, supplier, invoice reference, date, amount, or payment batch. The user checks the transaction details and confirms that the payment qualifies for voiding under the organization's accounting controls. Depending on the configured Epicor application, the action may be available through a payment-entry, payment-processing, or related accounts payable function.
After selecting the appropriate void action, the user reviews any confirmation details and records the reason for cancellation where the workflow supports it. Epicor may update payment status and accounting records based on the transaction type and posting state. The user should then verify the result rather than assume that selecting a command completes every required accounting or bank action.
Payment Approvals and segregation-of-duties controls should govern who can request, authorize, and execute a void. A documented Payment Approval workflow helps ensure that the cancellation has a valid business reason and that a replacement payment receives the required authorization.
Accounting Impact and Reissuing Payments
The accounting result depends on whether the original payment was posted, whether it has cleared the bank, and how the Epicor environment handles void transactions. A void may reverse or offset the payment's accounting effect and restore the invoice to an open or payable status when appropriate. The team should inspect the invoice balance, supplier ledger, payment history, and general ledger entries to confirm the outcome.
For example, suppose a supplier invoice for $4,800 was paid by check, but the check contains an incorrect payee name and has not been cashed. If the check is eligible for voiding, the team cancels the original payment, verifies that the invoice is available for settlement, and creates a replacement payment after correcting the supplier details and obtaining authorization. The invoice remains $4,800 unless another approved adjustment changes the amount; the void and reissue should not create an unintended duplicate liability or expense.
Teams should also consider whether an eligible early payment discount remains available when a replacement is issued. The payment date, supplier terms, and accounting treatment should be checked before the replacement is released.
Controls, Fraud Checks, and Cash Visibility
A controlled void process protects the integrity of supplier records and supports reliable cash flow reporting. Before cancellation, confirm the original payment reference, payee, amount, invoice allocation, and bank status. Fraud Prevention procedures should include reviewing unexpected requests to cancel payments, changes to supplier bank details, and requests to issue a replacement to a different account.
Payment controls should connect the original invoice to its purchase order, receipt, approvals, and payment history where applicable. Procurement practices such as Fraud Prevention in Purchase Orders | Secure Automation help maintain traceable authorization from purchasing through settlement. Teams processing electronic disbursements, including Payment Processing By ACH, should also distinguish between a payment that can still be canceled in the ERP and one that requires bank intervention.
Reconciliation and Audit Documentation
After voiding a payment, review the supplier account and accounting entries, then compare the recorded result with the bank's actual activity. Reconciliation Of Bank Statements helps match recorded payments, reversals, and bank transactions. In the broader Bank Reconciliation process, an outstanding check that has been voided should be treated consistently with its actual status so the cash balance and outstanding-payment records remain accurate.
Keep the original payment reference, void date, reason, approver, related invoice, replacement payment number, and bank confirmation where relevant. The Accounts Payable Payment record should provide a traceable link between the supplier obligation and its settlement history. Payment reports should distinguish voided transactions from completed payments, returned transfers, and replacement payments. This gives finance managers clearer information for reporting and treasury forecasts, including the payment timing considerations discussed in Optimize Cash Flow with AI: Insights from a CFO.
Summary
Epicor Void Payments supports the controlled cancellation of payment transactions while preserving the history needed for accounts payable and financial reporting. The essential steps are to verify the payment's status, follow the configured void workflow, confirm the accounting effect, authorize any replacement, and reconcile the result with bank activity. Since the available commands and accounting behavior vary by Epicor version and transaction status, finance teams should follow their documented procedures and verify each result in the relevant records.