How to Void a Check in Sage 100
how to void a check in Sage 100
Also searched as
- Sage 100 void check after bank reconciliation
- Sage 100 MAS 90 reverse a vendor payment
- void AP check Sage 100 closed period
Short answer
Sage 100 voids checks through Accounts Payable > Main > Check and Payment Voiding. Select the bank code, choose the check number, and Sage reverses the Cash Disbursements Journal entry and reopens the invoice it paid. A check that already cleared in Bank Reconciliation or falls in a closed period needs an extra step before it can be voided cleanly.
Applies to: Sage 100 2021 through 2025, Standard, Advanced, and Premium
Void a check in Accounts Payable
- 1Back up the company data first - Sage recommends a backup before any financial reversal.
- 2Go to Accounts Payable > Main > Check and Payment Voiding.
- 3Select the Bank Code the check was written from.
- 4Enter or select the Check Number; Sage 100 displays the vendor, amount, and original check date.
- 5Confirm the Void Date - it defaults to today but can be backdated to the check date if the accounting period is still open.
- 6Click Accept/Proceed to reverse the Cash Disbursements Journal entry; the original invoice reopens as unpaid unless you also choose to void the invoice itself.
- 7Print and update the Check and Payment Voiding Journal, then run the register Update.
- 8If the check was already marked reconciled in Bank Reconciliation, remove it from the reconciled transactions first, or Sage will warn that the check has already cleared.
- 9Reissue payment or re-post the corrected invoice as needed once the void is updated.
Voiding an unposted vs an already-posted check
If a check was printed but the Accounts Payable register has not yet been updated, void it directly from the check printing/reprint routine or reverse it before Update - no separate voiding transaction is needed. Once the check has gone through Update and posted to the General Ledger, Check and Payment Voiding is the correct path, since it creates its own reversing entry rather than trying to edit a posted transaction.
What happens in the General Ledger
Voiding posts a reversing entry dated on the Void Date: it debits Accounts Payable (or the clearing account used) and credits Cash for the check amount, mirroring the original disbursement in reverse. The vendor's open item history shows both the original payment and the void, and the invoice it paid returns to an open, unpaid status so it can be reprocessed.
Voiding a check in a closed period
If the check date falls in a period that has already been closed in General Ledger, Sage 100 will either block the void or post it with a Void Date in the current open period instead, which creates a timing difference between the AP subledger and GL if not handled carefully. The safer route for a closed period is a manual adjusting journal entry that reverses the cash and AP impact in the current period, referencing the original check number, rather than forcing a backdated void.
Voiding a check that already cleared the bank
Check and Payment Voiding checks whether the check is flagged as reconciled in Bank Reconciliation before letting you proceed. If it is, unreconcile the transaction in Bank Reconciliation first (or your next bank statement reconciliation will not balance), then void the check, then reconcile the reversing entry against the bank statement in the period it actually cleared as a reversal.
Common pitfalls
- !Voiding a check with a backdated Void Date into a period that is already closed in General Ledger, causing subledger-to-GL mismatches.
- !Forgetting to unreconcile an already-cleared check in Bank Reconciliation before voiding it, which breaks the next reconciliation.
- !Not printing and updating the Check and Payment Voiding Journal, leaving the void half-processed.
- !Voiding the check but also selecting to void the invoice when the invoice actually still needs to be paid, requiring it to be re-entered.
- !Skipping the data backup before a bulk void when correcting several checks at once from a bank error.
How an ERP-grounded AI assistant handles this
Most of the friction in voiding a Sage 100 check is not the screen itself but the judgment call around it - is the period open, has it already cleared, should the invoice reopen or stay closed. An assistant like Netray's ERPray, grounded in the live Sage 100 AP and GL data, can check a check's period status, reconciliation flag, and linked invoice before the user opens Check and Payment Voiding, and flag in plain language when a manual journal entry is the safer route instead of a backdated void.
Frequently asked questions
Can I void a check from a prior fiscal year in Sage 100?
Only if that year's period is still open in General Ledger. If it is closed, Sage 100 will either prevent the void or post it into the current open period, which is usually not what you want financially - a manual adjusting entry dated in the current period is the more accurate fix for prior-year checks.
Does voiding a check automatically reopen the invoice it paid?
Yes, by default the invoice returns to an open, unpaid status once the void is updated, unless you explicitly choose to void the invoice as well during the voiding process, in which case both the payment and the invoice are removed from open items.
What if the check number was never actually printed or used?
Use Check and Payment Voiding the same way, selecting the unused check number, so Sage records it as void in the check register and skips the gap in numbering cleanly rather than leaving it unexplained.
Can I void a check that was part of a manual check entry rather than a printed check?
Yes. Manual checks post through the same Cash Disbursements Journal and appear in Check and Payment Voiding by bank code and check number exactly like a system-printed check, so the same voiding steps apply.
Related
How to Create a Generic Inquiry in Acumatica
Generic Inquiries (GI) are Acumatica's no-code query builder for joining tables, adding filters, and exposing the result as an inquiry screen, dashboard data source, or API endpoint. Open System > Customization > Generic Inquiry, add your base table, define joins and conditions, then run and save. No SQL or customization project is required.
Error fixFix Odoo AccessError: You Are Not Allowed to Access Records
Odoo raises AccessError when a user's security groups do not grant a CRUD right on a model through ir.model.access.csv, or when an ir.rule record rule filters the specific record out for that user or company. Fix it by adding the user to the group named in the error, editing the model's access rights, or reviewing the record rule's domain under Settings > Technical > Security.
How-toHow to Run Requirements Planning (MRP) in SYSPRO
SYSPRO's MRP engine lives under Planning and Scheduling > Requirements Planning. Set planning parameters per warehouse, run the Requirements Calculation to net demand against supply, then review and release the resulting suggestions as purchase requisitions or work orders. A full regenerative run typically runs on a schedule, with net change runs in between to pick up new activity.
Error fixFix Fishbowl Error: MySQL Server Has Gone Away
This error means the Fishbowl Server lost its connection to the underlying MySQL database, usually because a session sat idle past MySQL's wait_timeout, MySQL itself restarted, or a large import or report exceeded max_allowed_packet. Raise the relevant MySQL timeout and packet settings, confirm the MySQL service is actually running, and restart both MySQL and the Fishbowl Server service.
Error fixQAD Says "Unable to Connect to the Application Server": How to Fix It
This error almost always means the Progress OpenEdge AppServer broker behind QAD is stopped, unreachable over the network, or out of licensed connections, not a database problem. Confirm the broker process is running and healthy in OpenEdge Explorer, check the port and firewall path from the client, then restart the broker with clean agent settings.
How-toHow to Close a Job in JobBOSS2
A job in JobBOSS2 will not close cleanly until every routing operation is marked complete, all material has been issued or returned, and all labor and cost transactions are posted. Review the job's Work In Process detail first, clear any open items, then change the job status to Complete and run final job costing before it is locked.
AI for ERPAI for Sage X3, Grounded in Your Own Ledgers and Stock Data
Add AI to Sage X3 finance and stock data without exporting it to a public model. On-prem and private-cloud LLMs for Sage X3 in the UK and France.
AI for ERPNatural Language Query for ERP Data: Ask SAP, Infor, or Oracle a Question in Plain English
See how natural language query over SAP, Infor, Oracle, and NetSuite data works: grounded text-to-SQL, role-based permissions, and a visible audit trail.
Stuck on Sage 100 (formerly MAS 90/200)?
Talk to engineers who work inside Sage 100 (formerly MAS 90/200) every week, and who build private AI that answers these questions from your own ERP data.