Post-dated cheques are a cornerstone of B2B payment practice in Nepal. A Kathmandu trading company delivering goods on 60-day credit terms typically collects a post-dated cheque at the time of delivery - the buyer hands over a cheque dated 60 days forward as a commitment to pay. The seller holds the cheque, deposits it on the due date, and the transaction settles. This works when both parties track the cheque lifecycle properly. When tracking fails, the consequences range from a missed deposit (the cheque date passes without being presented to the bank) to depositing a cheque that has already been replaced or cancelled, creating a banking relationship problem on top of the payment dispute.
A mid-sized trading company in Nepal typically handles 50-200 cheques per month in both directions: cheques received from customers and cheques issued to suppliers. Tracking these manually - in a register, a spreadsheet, or a physical envelope system - works at low volume but breaks down as the business grows. The most common failures are: missing a PDC deposit date, depositing a cheque without first confirming the replacement arrangement with the customer, and issuing a cheque without checking whether the bank account has sufficient balance for the date it will be presented.
Cheque management software integrates with the accounting system to turn cheque tracking from a manual exercise into an automated process. Every cheque issued or received is recorded with amount, bank, cheque number, and due date. Deposit alerts trigger before PDC due dates. Issued cheques link to the bank account to flag approaching clearance dates against available balance. Returned cheques trigger automatic reversal workflows. The entire cheque lifecycle - from issue or receipt to bank clearance to accounting entry - runs through one system.
The Post-Dated Cheque (PDC) Lifecycle in Nepal
Understanding the PDC lifecycle is essential for building proper controls. When a seller receives a PDC, the accounting entry depends on the company's policy: some businesses record the receivable when the cheque is received and mark it as "PDC received" with the due date; others wait until the cheque date arrives and the cheque clears. The first approach gives better receivables visibility; the second is more conservative. Whatever policy the business follows, it must be consistent and the PDC status must be trackable in the accounting system.
PDC deposits require a specific process. The cheque should be reviewed before deposit: confirm the date is current (not future-dated), confirm the cheque has not been replaced with a fresh cheque or a bank transfer that has already settled the same amount, and confirm the cheque details match the receivable it is being deposited against. Depositing an old PDC after the debt has been settled through other means creates a double-collection situation that damages customer relationships and creates an accounting error.
When a business issues PDCs - commonly done when paying suppliers with future-dated cheques - the cash flow implication is immediate: the bank account must have sufficient balance when the cheque is presented. A post-dated cheque issued for Kartik 15 creates a cash requirement for that date, regardless of whether the supplier will present it on exactly that date or a few days later. The issued PDC register must feed the cash flow forecast so the obligation is visible in advance.
A PDC received is not the same as cash received - it is a promise that may or may not honor on the due date. A PDC issued is a commitment that must have cash backing on the clearance date. Both types need separate tracking registers, and both must feed the cash flow position.
Tracking Received Cheques and PDCs
A cheque received register captures: cheque number, issuing bank and branch, amount, date on cheque, customer name, the receivable it relates to, deposit date, and status (in hand, deposited, cleared, returned). When a cheque is deposited, the status updates. When the bank confirms clearance (typically 1-3 banking days), the status updates again and the receivable marks as collected. If the cheque returns (bounces), the status triggers the return workflow.
Nepal's banking system processes cheques through Nepal Clearing House Limited (NCHL). Cheques drawn on banks within the same clearing zone are typically processed within 2-3 banking days. NCHL's online system means most clearing happens faster than the formal 3-day window. When a cheque bounces (is returned unpaid), the presenting bank returns the physical cheque with a return memo stating the reason (insufficient funds, signature mismatch, account closed, stop payment instruction). The payee has 7 days from receiving the return notice to file a complaint with the relevant court under the Negotiable Instruments Act. Acting within this window is critical - missing the 7-day window forfeits the legal protection for cheque bounce cases.
PDC deposit alerts are the most operationally critical feature. A PDC for Kartik 20 needs a deposit reminder no later than Kartik 18 or 19 - allowing time to physically present the cheque to the bank before the close of business on the due date. Most Nepali banks process same-day clearing for cheques deposited before their daily cutoff (typically 3:00 PM). Cheques deposited after cutoff enter the next day's clearing cycle, effectively making the clearing date one day later than the cheque date. The alert should account for this timing.
PDC deposit alerts must be set 2-3 days before the cheque date to account for bank processing cutoff times. A cheque date alert set for the same day as the date on the cheque will miss same-day clearing windows and push clearance to the following day.
Managing Issued Cheques and Cheque Books
The issued cheque register mirrors the received cheque register from the payer's perspective. Every cheque issued to a supplier or payee is recorded with cheque number, payee name, amount, cheque date, bank account, and the payable or expense it settles. When the bank statement import shows the cheque has cleared, the issued cheque status updates to cleared and the outstanding cheque reconciliation removes it from the reconciliation list.
Cheque book management is a related requirement. Each bank account has one or more active cheque books. The system should track which cheque leaves are used, which are void, and how many remain. When a cheque book approaches exhaustion - say, fewer than 10 leaves remaining - an alert prompts ordering a new cheque book from the bank. Running out of cheque leaves during a supplier payment cycle is a preventable operational failure.
Stop payment instructions - formally requesting a bank to not honour a specific cheque - are sometimes needed when a supplier dispute arises after a cheque has been issued but before it is presented. Nepal's banks typically charge a fee for stop payment instructions and require the instruction to be submitted with sufficient notice before the expected clearance date. The cheque management system should support recording a stop payment instruction against a specific cheque, with the status changing to "stop payment placed" and a note of the reason. This creates an audit trail for the payment dispute without removing the original cheque record from the system.
Cheque signing authority is another internal control dimension. Most businesses require two signatories above a certain amount - say, one authorized signature for cheques below rū 1 lakh and two signatures above that threshold. The cheque management system should flag when a cheque above the threshold is recorded with only one signatory indicated, prompting the second authorization before the cheque is handed to the payee.
Issued cheque management is as much about internal control as about payment tracking. Cheque signing limits, stop payment recording, and cheque book stock management are all control points that prevent fraud and operational failures. Software makes these controls automatic rather than relying on individual discipline.
Returned Cheque Handling and Legal Process
A returned cheque (cheque bounce) requires immediate action on both the accounting and relationship fronts. On the accounting side: reverse the receipt entry that was posted when the cheque was deposited, post a bank charge entry for the return fee charged by your bank, and create or reinstate the receivable from the customer. On the relationship side: contact the customer immediately, understand the reason, and determine whether re-presentment is possible or whether a replacement payment is needed.
The legal process under Nepal's Negotiable Instruments Act is triggered if the customer does not resolve the payment within 7 days of being notified of the bounce. The payee files a complaint with the court in the jurisdiction where the bank branch is located. The court summons the cheque issuer, and penalties can include fines and imprisonment. Maintaining accurate records of the original cheque, the bounce date, the bank return memo, and the notification to the customer is essential documentation for any legal proceedings.
From a credit management perspective, a bounced cheque is a signal that warrants a credit review for that customer. A first bounce in a long relationship might be treated as an isolated incident. A second or third bounce, or a pattern of PDCs being replaced at the last minute, suggests a credit risk that the cheque management system's history should make visible. The system's cheque return history per customer, visible alongside the receivables ageing, gives credit managers the data to make informed decisions about future credit terms.
A bounced cheque triggers both an accounting reversal and a legal clock. The 7-day window under Nepal's Negotiable Instruments Act means the accounting team and the credit team need to coordinate immediately when a cheque return notice arrives. The cheque management system should log the return date automatically to ensure the legal deadline is not missed.
Frequently Asked Questions
Technically, Nepal's banking regulations permit banks to process a cheque presented before its date, but most banks in practice return early-presented PDCs or advise the customer to wait for the date. Some banks have internal policies against processing future-dated cheques. The safe practice is to never deposit a PDC before its date - the risk of it being returned (which damages the relationship and creates a bank charge) outweighs any benefit from early clearance. The cheque management system should warn the user if they attempt to deposit a PDC before its recorded date.
A stale cheque is one that is presented more than 6 months after its date (3 months in some bank interpretations). Nepal's banks typically return stale cheques unpaid. If your PDC register shows a cheque that is approaching its 6-month stale date without having been deposited, this requires urgent action: contact the customer to understand why the cheque was not deposited, get a replacement cheque with a current date, or confirm the debt has been settled through other means. The cheque management system should flag cheques approaching their stale-date threshold.
PDC replacements happen when a customer realizes their bank account will not have sufficient funds on the original PDC date and requests to replace it with a new cheque for a later date. The process should be: physically return the original cheque to the customer in exchange for the new cheque, record the replacement in the cheque management system (marking the original as replaced, entering the new cheque with its new date), and confirm the accounting entry reflects the new expected receipt date. Never accept a replacement arrangement verbally or via WhatsApp without the physical exchange of the new cheque - the original cheque is the only security you hold until the new one is in hand.
PDC and Cheque Management Integrated With Accounting
MISAC's cheque management is not a standalone module - every cheque is linked to an accounting entry from the moment of recording. A received PDC links to the receivable it settles. An issued cheque links to the payment voucher and the supplier's payable. When the bank statement is imported, MISAC matches cheque clearances against the outstanding cheque register automatically. The bank reconciliation and cheque management work from the same data, eliminating the reconciliation exercise between two separate systems that many businesses currently manage.
Nepal's specific PDC culture is reflected in MISAC's cheque workflow. The PDC deposit alert system generates reminders per the schedule you configure - 3 days before, 2 days before, on the day. Cheque return handling automatically posts the reversal journal, records the bank charge, and reinstates the receivable in one action. The 7-day legal window counter is logged from the return date, and the customer's cheque return history is visible alongside their receivables ageing for credit management decisions. For issued cheques, the integration with the cash flow projection means PDC obligations appear in the forward cash position from the day the cheque is issued.
MISAC Intelligence Pvt. Ltd. has implemented cheque and PDC management for trading companies across Nepal where cheque volume runs into the hundreds per month. The combination of automated deposit alerts, integrated accounting entries, and return workflow handling has eliminated the manual tracking burden that previously occupied accounting staff time and created recurring errors. Start with cheque management alone if that is the immediate need - the module activates within the existing accounting setup without re-implementation.
Ready to See MISAC in Action?
Contact us to see how MISAC handles PDC management, cheque tracking, and bank reconciliation for Nepal businesses like yours.