The corporate-cheque deadline is an operations change, not just a banking announcement. Every invoice, deposit, refund, dual-signature practice and post-dated payment that assumes a cheque must move to a replacement with an equally clear approval and audit trail before 1 January 2027.
This guide is for a Singapore SME finance manager still issuing or receiving SGD corporate cheques. The decision is to replace cheque-dependent payables, receivables and deferred-payment controls before banks stop processing corporate cheques from 1 January 2027.
Two dates control the migration
The Association of Banks in Singapore says banks stopped issuing new SGD corporate cheque books from 1 January 2026 and will cease processing SGD corporate cheques from 1 January 2027. A business that still has unused cheques therefore has a shrinking runway, not a stockpile that remains usable indefinitely. ABS e-payments guide.
Map use cases before choosing rails
PayNow Corporate, FAST, GIRO and MEPS+ solve different speed, value and identifier needs. Electronic Deferred Payment and EDP+ are intended to address some future-dated or richer payment use cases. The correct replacement depends on whether the business is paying, collecting, scheduling, requiring confirmation or transmitting remittance information.
Preserve approval separation
A handwritten dual-signature rule should not collapse into one person creating and approving a bank transfer. Map preparer, verifier, approver, payment limit and beneficiary-change control for each electronic rail. Use bank entitlements, not a shared login or a screenshot forwarded for informal approval.
Counterparties need a controlled change
For suppliers and customers, verify the legal entity, bank or UEN-linked PayNow identifier, effective date and test method through a known contact. A payment-detail change received by email is a fraud event until independently confirmed. Keep the old and new instruction plus callback evidence.
The FAQ sets practical boundaries
ABS’s corporate-cheque FAQs explain the sunsetting scope and transition. Use them with the firm’s own bank notices because product availability, cut-off time and fees can differ. The control sheet should record the chosen bank product and tested transaction, not merely the generic rail name. ABS corporate cheque FAQs.
The two working tools
The first original unit is a use-case matrix that refuses to name one rail as the universal replacement. The second is a counterparty migration ledger recording owner, old cheque purpose, new rail, bank setup, independent verification, test transaction and first live settlement. It exposes the exceptions before the deadline.
| Cheque use | Candidate route | Control to retain |
| Routine supplier payment | FAST, PayNow Corporate or GIRO | Beneficiary verification and dual approval |
| Large time-critical payment | MEPS+ where suitable | Cut-off, value limit and callback |
| Recurring collection | GIRO or agreed digital collection | Mandate, rejection and reconciliation |
| Future-dated instruction | EDP or EDP+ where offered and suitable | Date, payee evidence and cancellation rule |
Keep the decision usable after today
A first check can go stale before the task is finished. Put two dates control the migration, map use cases before choosing rails and preserve approval separation on separate dated lines instead of combining them into one “done” box. Attach the authority page or document beside the line it supports, record the person who checked it, and write the exact event that will force another check. That event may be a changed account, amended filing, new appointment, revised timetable, altered access route, later test run or updated dataset. The format matters because a future reader must be able to see which fact changed without repeating every part of the exercise.
Next, give the two original tools different owners. The person maintaining a payment-use-case matrix comparing PayNow, FAST, GIRO, MEPS+, EDP and EDP+ should preserve the inputs and arithmetic or branch logic. The person maintaining a counterparty migration ledger covering mandate, approval, payee verification and cut-off risk should confirm that the final action followed the chosen route. One person may perform both roles, but the evidence should still distinguish calculation from execution. This prevents a correct plan from being mistaken for proof that the payment, filing, trip, report, repair, training or release actually happened.
Before relying on the result, ask a second reader to reproduce the conclusion from the saved material without being told the preferred answer. They should be able to match the right person, entity, account, property, route, service or software version; identify the controlling date; and explain the strongest stop condition. If they reach another branch, do not average the two answers. Reopen the disputed source, definition or input. A decision that cannot be reproduced is not ready for a consequential step.
Worked example
An SME writes cheques for rent, one-off suppliers and customer refunds. Rent moves to GIRO, suppliers to bank-approved FAST with dual authorisation, and refunds to a verified PayNow or bank-transfer workflow. One landlord cannot accept the proposed rail, so that exception is escalated months before the cheque cut-off rather than during a missed payment.
The example is a calculation or decision illustration, not a report of an interview, purchase, visit, transaction, taste test or personal outcome. Replace its inputs with the reader’s own current evidence.
Where this can go wrong
- Assuming unused cheque leaves will be processed after the deadline.
- Replacing two signatures with one shared online-banking credential.
- Accepting changed bank details without an independent callback.
- Moving payment but not remittance, reconciliation and rejected-payment handling.
Before acting
- Inventory every issued and received cheque use.
- Assign a replacement rail and control owner.
- Verify counterparties through known channels.
- Test approvals, limits, cut-offs and reconciliation.
- Retire cheque stationery and update contracts, forms and procedures.
Limits and useful next reading
Banks and counterparties control the products available to a particular business. This article does not recommend one payment rail or override contractual payment terms. High-value, cross-border and regulated payments may need additional controls.
For the next related decision, keep invoice and payment dates aligned for GST. It is also useful to build another deadline-based company control.
