If your treasury or accounts-payable team issues cheques from ERPNext today, you already feel where the core runs out of road. ERPNext's Payment Entry handles a single disbursement well, but it has no concept of a "check run" that batches dozens of approved supplier payments into one printable job, no MICR-encoded cheque layout aligned to your bank's pre-printed stock, and no structured way to void, reissue, or track a cheque number as it moves from printed to presented to cleared. Teams end up exporting to spreadsheets, hand-numbering cheques, and reconciling clearances manually — which is exactly where duplicate payments, out-of-sequence cheque numbers, and stale post-dated cheques slip through.

This app adds a proper Check Run DocType to ERPNext that selects eligible Payment Entry and Purchase Invoice records by company, bank account, party, and due-date window, then generates a single batch of sequentially numbered cheques. Cheque numbering is driven by a per-bank-account Cheque Book DocType (start number, last-used pointer, and a uniqueness constraint), so numbers are never reused and gaps are logged. A Print Format renders each cheque with a MICR line — E-13B or CMC-7 depending on your region — computing the routing/transit, account, and cheque fields and laying them out to sub-millimetre tolerances so they register correctly on your bank-supplied cheque stock. The whole run exports as a single paginated PDF for a continuous print job, and a courtesy/legal amount-in-words converter handles your currency and language.

Under the hood it is a standard Frappe app installed on your bench. hooks.py doc events fire validate and on_submit server scripts that enforce numbering, block cheques above a role-configurable approval ceiling, and write an immutable Cheque Register ledger row for every printed instrument. Void and reissue are first-class: voiding a cheque reverses the linked Payment Entry (or cancels the GL impact), stamps the number Void so it can never be re-picked, and — on reissue — draws the next valid number while keeping a full audit chain back to the original. Post-dated cheques get their own PDC lifecycle: they sit in a Pending state, a scheduler_events daily job promotes them for deposit on their value date, and clearance automation posts the bank-clearance Journal Entry (or reconciles it against a Bank Statement import) and flips the cheque to Cleared — or Bounced, which re-opens the payable. Everything is exposed through whitelisted methods and the Frappe REST API, guarded by dedicated role profiles (AP Clerk, Treasury Approver) and permission rules, with client scripts giving in-form validation and a "Print Run" action.

Because this is build-to-order, nothing is a generic download. We start with a short scoping call to capture your bank's exact cheque stock dimensions, MICR standard, numbering rules, approval thresholds, and PDC/clearance workflow, then build the app against your Frappe/ERPNext v15 or v16 instance. You get the work on a staging site for UAT first, then a clean production install — with source code, git repo handover, and a support window so your team owns it fully.