Review the Original Check and Its Status
In Sage 100, begin by locating the payment in the relevant Accounts Payable check history or payment records. Verify the vendor account, check number, cash account, and invoice or invoices paid. If the original check has already cleared the bank, coordinate with the accounting team before reversing it, since the bank activity and ledger may require additional reconciliation.
For a lost or damaged check that has not cleared, confirm that the payee has not deposited it and follow your organization's stop-payment or bank-confirmation procedure when appropriate. A replacement should not be issued until the status of the original payment is understood. This protects the vendor relationship and helps prevent duplicate disbursements.
Void the Check in Sage 100
Use the Accounts Payable payment or check-reversal function appropriate to the original transaction. Menu names and available options can vary by Sage 100 version, module configuration, and payment status, so confirm the procedure in your version's documentation before posting. Select the original check, verify the details, enter the required void date, and review the accounting period that will receive the reversal.
Review the effect on the vendor's open invoices and cash account before completing the transaction. A properly recorded void generally reverses the payment's accounting impact and makes the related payable available for settlement again, where applicable. Retain the original check reference and reason for the void in the transaction notes or supporting records.
Strong payment controls should also govern who can initiate, review, and post a void. A documented Payment Approval process helps ensure that the reversal is authorized and that the replacement amount and payee details are independently checked.
Reissue the Replacement Check
After the void is posted and the invoice balance is available for payment, use the appropriate Accounts Payable payment workflow to select the outstanding invoice or invoices and prepare a new check. Confirm the vendor name, remittance address, bank code, payment amount, payment date, and check form before printing. If the original payment covered several invoices, verify that the replacement settles the intended invoices without paying any invoice twice.
For example, suppose a vendor was paid $2,450 by check number 10482, but the check was damaged before delivery. After confirming it has not cleared, the accounting team voids the original and issues check number 10517 for $2,450. The payment register should clearly show the voided check and the replacement, while the vendor's net payment obligation remains settled only once.
Check Posting, Reconciliation, and Audit Records
After the replacement is issued, review the payment register, vendor activity, general ledger cash account, and open invoice status. The original check should appear as voided according to the selected process, and the replacement should appear as the active payment. When the replacement clears the bank, match it to the bank statement through Bank Reconciliation. Confirm that the original check is not incorrectly treated as a cleared payment.
Keep the reason for the void, approval evidence, original and replacement check numbers, supporting correspondence, and bank confirmation together. A Check In Software Finance workflow can be understood as the broader use of check-related records and controls to document payment activity. Similarly, a Budget Check helps verify spending against an approved budget; it does not replace payment authorization or bank reconciliation.
Coordinate Controls Across Finance Systems
When finance teams extend payment workflows across ERP platforms, integration design should preserve payment identifiers, posting dates, approval status, and reversal history. For example, Sage Intacct Integration describes connecting Sage Intacct with other systems so financial information can move between applications; it is a separate integration concept rather than a Sage 100 voiding function. For Sage 100, review the configured integration and posting rules before changing payment records.
Finance automation can support standardized review steps around check corrections. The Hyperbots Platform can be configured for company-specific workflows, ERP connections, roles, and general-ledger structures. Its Process Specific Capabilities support finance tasks through process-focused AI, while Ready to Deploy Capabilities provide pre-trained agents and ERP connectors for supported workflows. Self Learning Capabilities use human actions to refine workflow behavior, and Human in the Loop keeps human review involved in approvals and exceptions. These capabilities should complement, not replace, the authorization and posting controls established for Sage 100.
When connecting finance automation to an ERP, review ERP Security Best Practices for Finance Teams (2026) for guidance on permissions and integration controls. For teams comparing educational resources across Sage products, AI Copilots for Sage 300 addresses AI-supported finance workflows in Sage 300, which is distinct from Sage 100. For invoice-related automation, Straight-Through Invoice Processing: Reality Check explains how capture, validation, matching, and posting affect processing accuracy. Procurement controls also matter when a payment originated from a purchase order; Procurement Freedom vs. Financial Guardrails: A Practical Guide explores the balance between purchasing flexibility and financial oversight.
Summary
To void and reissue a check in Sage 100, verify the original payment and its bank status, use the appropriate void or reversal process, confirm the invoice balance is available, and issue a replacement with validated payment details. Reconcile the replacement when it clears, preserve the original and replacement references, and document approvals. Following these steps maintains reliable vendor balances, accurate cash reporting, and a traceable payment history.