Received Cheque Management in ERP: From Due Date to Collection and Bounce

Received Cheque Management in ERP: From Due Date to Collection and Bounce

Introduction: Why Cheque Management Is a Strategic Issue, Not a Side Accounting Task

In Iran's commercial transaction economy, the cheque remains the most widely used settlement instrument between companies. According to official Central Bank statistics, billions of cheques worth enormous sums are exchanged across the country every year, and a significant portion of them face delayed collection or bounce. For a manufacturing, trading, distribution or services company, this simple fact means that received-cheque management is no longer a side accounting task; it is directly tied to liquidity, working capital, customer credit assessment, the ability to purchase from suppliers, and ultimately the survival and growth of the business.

Imagine a nationwide distribution company that receives more than two thousand cheques from its customers every month. If even two percent of these cheques are forgotten, deposited late, or bounce without follow-up, the company faces a substantial monthly cash-flow blockage: money that counts as an "asset" in the books but never reaches the bank account. A forgotten cheque means revenue that was not deposited on time; a bounced cheque without follow-up means receivables that slowly turn into dead debt; and an error in recording the cheque number means a document that effectively loses its validity for inquiry and legal action.

Manual cheque management with Excel files, classic ledgers, or the treasurer's memory works at small scale and with limited documents; but as the number of customers and documents grows, errors and risk rise exponentially. Excel has no status control, issues no automatic accounting entries, sends no reminders, and every copy left on an employee's laptop is an inconsistent version of reality. This is precisely where the cheque and treasury management module of an ERP system such as Sayar Soft comes in: cheques are tracked in a fully integrated way from the moment they are recorded on the sales document through collection, endorsement or bounce, and every stage automatically reflects its financial effect in the ledgers, reports and management dashboards.

What Is a Received Cheque and How Does It Differ from Other Treasury Documents?

A received cheque is a document taken from a customer in exchange for credit sales of goods or services, and until it is collected it is treated as a current asset of the company. But not everything with "paper, an amount and a signature" has the same nature, and the system must distinguish between them:

• Received cheque: a document for collecting a receivable from a customer; by custom and banking practice it is expected to clear on its due date, and the company typically relies on it when planning purchases and payments.
• Guarantee (security) cheque: received as surety for performance, good execution or fiduciary deals, and must not be spent or collected until the contract ends; holding it requires tracking the contract number, project, return date and return status. Confusing a guarantee cheque with a received cheque is one of the most common treasury errors, and ERP prevents it at the root by separating document types.
• Promissory notes and bills of exchange: receivable instruments with a different legal structure and collection process that require their own registration and follow-up path.
• Joint (co-signed) cheque: a cheque issued by two or more persons and dependent on the collection of another cheque; its risk is higher and it must be flagged in the system as a high-risk document.

Unlike cash, a received cheque is not "money" by nature; it is an instrument for collecting money that can meet one of three fates:

• Collection: paid by the bank on the due date and converted into the company's cash balance.
• Endorsement (spending): endorsed and transferred to a supplier or another creditor before the due date.
• Bounce: returned by the bank due to insufficient funds, lack of cover, a stop-payment order, signature mismatch or document defects, turning into a customer debt and a past-due receivable.

In the third scenario, legal issues arise alongside the financial problem: issuance of a certificate of non-payment by the bank, registration of the bounce in the Central Bank system and banking restrictions imposed on the issuer, and action through execution or the courts. A system that sees a bounced cheque merely as a "suspended ledger item" has effectively taken part of the company's receivables management — and even its legal risk — out of control.

The New Cheque Law and the Sayad System: What Changed and How Does It Affect Your Business?

The rollout of the Sayad system and the amendments to the Cheque Issuance Law have changed the nature of cheque management from "keeping a paper document" to "managing an electronic identifier tied to the issuer's identity". The key points every company must build into its processes:

• The 16-digit Sayad cheque number: every cheque has a unique identifier tied to the issuer's identity. Without recording this number correctly, inquiry into the cheque's status, bounce follow-up and enforcement action become practically impossible; that is why validating the length and structure of the cheque number at entry is a mandatory system requirement, not an optional extra.
• Cheque status inquiry: before accepting a cheque, the issuer's status can be queried (bounce history, banking restrictions, stop-payment orders); the result of this inquiry must be stored in the customer file and next to the cheque record in the ERP to serve as the basis for the sales decision.
• SMS notifications: the issuer is notified by text message when a cheque is deposited or bounces; by reconciling this notification with the status recorded in the system, the receiving company can control human error.
• Bounce restrictions: with each new bounce, the issuer's banking services are restricted; meaning the probability of collecting that customer's future cheques drops, and the system must automatically lower their credit level.
• Account-holder registration and bank account linkage: old cheques not registered in Sayad cannot clear through the normal process; the system must be able to identify and flag these cheques for special handling (replacement, alternative settlement).

The practical outcome of these changes is that "correct entry at receipt" and "status tracking across the cheque's lifetime" can no longer be left to people's memory and diligence; that is exactly the job an ERP automates for you.

The Lifecycle of a Received Cheque in an Integrated System

In a standard ERP, a received cheque is not a "simple cash document"; it is an entity with a status and a complete history. Its lifecycle typically looks like this:

1. Initial registration: when the sales or credit-receipt document is recorded, the cheque is entered into the system with its Sayad number, cheque and serial numbers, amount, due date, drawee bank, branch and issuer details, and is debited to the "Cheques Receivable in Collection" account. If a cheque image or contract attachment exists, it is linked to the record.
2. In-collection status: the cheque appears in the list of cheques in collection and shows up in the aging report and liquidity forecast; in this state it can be planned for endorsement or collection.
3. Endorsement (spending): if the cheque is spent with a supplier, settlement occurs between the receivable and payable documents accounts, and the trail of the transfer, its date and the counterparty remain in the system; from this moment the cheque is no longer directly collectible by the company, and if it bounces, responsibility for follow-up between you and the endorsee is clearly defined.
4. Deposit at the bank: close to the due date, the cheque is presented to the bank for collection and its status changes to "at bank"; in this state the cheque must not be endorsable at all, and the system enforces this control.
5. Collection: deposit into the company's bank account is recorded, the cheque leaves the collection pipeline and becomes cash; the collection entry debits the bank account and credits cheques in collection simultaneously, and is recorded as reconciled in the bank reconciliation.
6. Bounce: if payment fails, the cheque returns to the debtor's (customer's) account, the receivables follow-up file and enforcement actions begin, and bank charges or penalties are recorded in the system. The certificate of non-payment is stamped and attached to the cheque file.

The key point is that at each of these stages the accounting entry must be issued correctly and completely only once, then updated automatically in subsequent steps — something almost impossible in manual bookkeeping given the volume of documents. Every status change must also be logged with the user's name, time and a description, so each cheque's history is always a single, documented, citable narrative.

Accounting for Received Cheques: From Entry to Settlement

From an accounting perspective, every change in cheque status is a transaction. The table below shows the simplified relationships between accounts:

In a good ERP, these entries are generated automatically based on "posting rules" defined in the system, and the accountant merely confirms the result. The advantages of automated cheque accounting in an ERP include:

• Subsidiary detail at the individual cheque level: by breaking accounts down (subsidiary and detail ledgers) to each individual cheque, the exact balance of every cheque in any status can be viewed at any moment, with full traceability in the trial balance.
• Consolidated collection entry: instead of dozens of scattered postings, the day's collections are recorded in a single consolidated entry with traceable detail.
• Three-way document linking: the accounting entry, the sales document and the cheque record are linked to one another; one click takes you from any of them to the others, making bank reconciliation and internal audit far faster.
• Elimination of parallel bookkeeping: when treasury and accounting record the same cheque in two separate systems, inconsistency is inevitable; in an ERP there is one record that everyone sees.
• Statutory and tax reporting: amounts in the cheques-in-collection pipeline at period end are reflected in the financial statements precisely and with full traceability.

Common Challenges in Managing Received Cheques

• Forgotten due dates: without automatic reminders, cheques that should go to the bank next week are presented late, and collection delays damage cash flow; in some cases the cheque even leaves the presentation window and the collection path becomes more complicated.
• No status tracking: knowing at every moment which cheque is in collection, which has been endorsed, which is at the bank and which has bounced is practically impossible without a unified system.
• Errors in the Sayad number: a mistyped 16-digit number makes inquiry and follow-up in the banking system impossible and leaves the file incomplete at the legal-action stage.
• Bank reconciliation: without linking cheques to actual bank transactions, month-end reconciliation becomes a nightmare; cheques collected but still "in collection" in the system (or vice versa) break the balance of the books.
• Scattered information: when cheques live separately in the treasury's Excel, the accounting ledgers and the sales team's notes, no one has the true picture of receivables and liquidity, and every report builds a different version of reality.
• Uncontrolled endorsement: if anyone can endorse a cheque that is in collection, the same cheque may simultaneously go to the bank for collection; the result is a bounce, loss of credibility with the supplier, and damage to the company's commercial reputation.
• Weak bounce follow-up: a bounced cheque without a recorded enforcement date, responsible person and inquiry result is an opaque process that creates legal and financial risk; in many companies bounced cheques sit in a folder for years.
• Handing cheques to collection agents: when a cheque is given to a collection agency or factor, without recording "delivered to agent" and tracking its return, the company's money disappears into ambiguous line items and settlement with the agent cannot be verified.
• No link between sales and treasury: without seeing the customer's bounce history, the sales team sells to them on credit again, repeating the bad-debt cycle.
• Dependence on individuals: when only one person "knows" where each cheque is, their leave or departure halts the treasury; the system must keep knowledge in the structure, not in people's heads.

Received Cheque Management in Sayar Soft ERP

The treasury and cheque management module in Sayar Soft ERP is designed to answer these challenges and covers the entire cheque lifecycle, integrated with accounting, sales, purchasing and banking:

• Smart entry with Sayad validation: the Sayad number, bank, due date and amount are validated at the moment of entry to eliminate typographical errors at the root; full cheque details are linked to the sales document, customer and contract.
• Document-type separation: received cheques, guarantee cheques, promissory notes and other instruments are each registered and managed with their own process and reports, never mixed together.
• Due-date dashboard: the treasury calendar shows how much is due for collection on each day and week; supplier payment planning is based on this, and the finance manager always has the picture of incoming cash for the coming weeks.
• Automatic reminders: a set number of days before each cheque's due date, an alert is sent to the treasurer and the sales team so the cheque is presented to the bank on time; the reminder lead time is configurable per cheque.
• Status change with automatic entry: with one click, a cheque's status changes from "in collection" to "at bank", "collected" or "bounced", and the corresponding accounting entry is issued instantly.
• Endorsement of cheques: a received cheque can be spent directly on a purchase or payment document to a supplier; with its "one cheque, one status" control, the system prevents double endorsement or sending the same cheque for collection at the same time, and keeps both sides of the cycle connected.
• Bounce management and follow-up file: on recording a bounce, the cheque transfers automatically to the customer's account, the certificate of non-payment and inquiry date are recorded, the enforcement action (execution notice, lawsuit, replacement-cheque agreement, instalment settlement) is defined with an owner and deadline, the follow-up result is logged in the customer file, and the past-due receivables report is updated.
• Guarantee cheques and collection-agent handover: guarantee cheques are kept linked to the contract, project and return date, and cheques delivered to a collection agent are tracked with an independent status (delivered, collected, not yet returned).
• Integrated bank reconciliation: by connecting to the bank account statement, actual collections are matched against recorded cheques, discrepancies are identified, and the bank balance in the books is reconciled with reality.
• Analytical reports: receivables aging report, bounce rate by customer and category, forecast of collections into liquidity over the next 30, 60 and 90 days, and the performance of each cheque depositor.
• Access levels and event logging: every status change is recorded with the user's name and time; only authorized personnel can collect, bounce-declare or endorse a cheque, and each cheque's full history is always viewable.
• Document attachments: the cheque image, contract, certificate of non-payment and correspondence are attached to the cheque record, so all documents are in one place at audit or litigation time.

Customer Credit Assessment: Before the Cheque Bounces

The best bounce management is preventing it from happening. In an integrated ERP, historical cheque data is a valuable input for the sales team's decisions:

• Customer payment-behavior history: each customer's bounce rate, average collection delay and outstanding cheque amounts are visible in their file; the salesperson sees this picture before accepting an order.
• Credit check at order entry: the system can flag customers with a bounce history, block credit sales above the defined limit, or route them for manager approval.
• Credit limits and settlement terms: setting debt ceilings and payment terms (cheque tenor, guarantees, down payment) based on real data rather than personal impressions; reliable customers get better terms and high-risk customers are restricted.
• Sayad inquiry in the sales flow: the result of the inquiry into a new cheque's status is stored beside the document, and if a warning exists, acceptance requires higher-level approval.
• Sales–treasury interaction report: salespeople can see which customers' cheques collect easily and which generate follow-up costs; this transparency changes the next sales negotiation and commission design.

Bounced Cheque: From the Moment of Bounce to Legal Action

A bounced cheque is not the end of the road; it is the start of a process. In Sayar Soft ERP, the post-bounce path is managed as follows:

1. Recording the bounce and transferring to the customer's account: when the bounce is recorded, the balance moves from cheques in collection to the customer's accounts receivable, bank charges are posted, and the customer's credit history is updated immediately.
2. Recording the certificate of non-payment: the stamped certificate of non-payment is attached to the cheque file and its date recorded; this document is the primary basis for enforcement action.
3. Defining the action and its owner: for every bounced cheque, the type of action (execution office, lawsuit, replacement-cheque agreement, instalment settlement), the follow-up owner and the deadline are defined, and the system keeps reminding until a result is achieved.
4. Logging correspondence and agreements: every call, letter or new agreement with the customer is recorded in the file, so if the case goes to court or execution, the history is documented and complete.
5. Return to the cycle or taking a replacement: if the customer provides a new cheque or alternative settlement, the new cycle is recorded linked to the previous file, preserving the full history of the customer's behavior.
6. Receivables allowance: old, uncollectible bounced cheques are identified in the aging reports according to company policy and form the basis for recording the allowance for doubtful receivables at fiscal year-end.

Liquidity Forecasting: The Biggest Management Gain of Integrated Cheque Management

When all incoming and outgoing cheques are recorded in one system, you gain a tool no ledger or Excel file can build: forecasting future cash flow. The liquidity dashboard in Sayar Soft ERP shows you:

• How much money will enter the company's bank accounts in the coming week, month and quarter from cheques in collection.
• How much you owe in payment cheques and endorsed commitments in the same periods, and whether the net cash flow for each week is positive or negative.
• If a large cheque bounces, which weeks will face a shortfall, so financing or facility arrangements can be planned now.
• If a major purchase is ahead, whether payment can be made relying on maturing cheques or not.

This means purchasing, investment and settlement decisions shift from "guesswork" to "data-driven" — and that is the greatest strategic value of the cheque module in an ERP.

Key Reports Every Treasury Manager Should Have

• List of cheques in collection by due date, amount, drawee bank and customer; the core document of the treasury's daily planning.
• Daily/weekly collection report: what was collected and how far it deviated from forecast; the variances themselves are an analytical report.
• Bounced cheque report: amount, cause, enforcement status and outstanding balance.
• Endorsed cheque report: which cheque was endorsed to which supplier and its current status.
• Cheques-held-by-agent report: delivered, collected and not yet returned; for transparent settlement with the agent.
• Guarantee cheque report: by contract date and return deadline, so no guarantee cheque is lost or wrongly endorsed.
• Liquidity forecast: total cheques in collection for coming weeks and months, plus payment and endorsed cheques, to compute net cash flow.
• Management KPIs: bounce rate, average interval from due date to collection, share of bounced cheques in total receivables, and their trend over time.

A Practical Checklist for Implementing Cheque Management in Your Organization

For the cheque module in an ERP to deliver real results, follow this implementation checklist:

1. Design the account structure: set up the cheques-in-collection accounts, held-by-agent accounts and per-cheque detail accounts correctly from the start; restructuring accounts after thousands of entries is very costly.
2. Define automatic posting rules once, correctly: so every status change issues the right entry without manual intervention.
3. Formalize the status workflow: specify who may endorse, collect and declare a bounce, and when and for which amounts a second approval is required.
4. Migrate legacy data: enter existing balances of cheques in collection, bounced and guarantee cheques with full detail, so the starting point is clean.
5. Activate reminders and make reviewing them a daily habit: the treasury's morning dashboard must show "today's and this week's cheques".
6. Tie the customer credit policy to the system: define debt ceilings, settlement terms and the approval path for high-risk customers inside the ERP itself.
7. Keep bounce files alive: every bounced cheque must have an active owner and deadline until collection or case closure.
8. Bring the reports into management meetings: review the future liquidity and cheque KPIs monthly in the management meeting.

Conclusion

The received cheque is the main carrier of your business's future cash, and managing it poorly means turbulent liquidity, growing past-due receivables, unanswered legal risk, and reports that always run one step behind reality. With the cheque management module in Sayar Soft ERP, from the moment a cheque is recorded through its due date, collection, endorsement or bounce, everything remains in one integrated, traceable flow: entries are issued automatically, due dates are reminded, customer credit is measured on real data, bank reconciliation becomes transparent, and every bounced cheque gets a defined follow-up file with an owner and a deadline. The result is an orderly treasury, discrepancy-free accounting, risk-aware sales, and a management team that always knows where the company's money is and when it will arrive. If your company's cheques are still scattered across Excel files and ledgers, today is the time to move to an integrated system.

-end close and dependable reports.