Cheque and Promissory Note Tracking: Due Dates and Status

Cheque and promissory note tracking software shows, in one place, where every cheque and note you received from customers or gave to suppliers is, when it is due and what its latest status is. Short answer: the real gain is not a list of instruments, but recording every movement of each one, from portfolio to bank, from endorsement to collection, and reading the coming weeks of cash in and out straight from the due date calendar.

What is wrong with tracking cheques in a ledger or Excel?

A business with few instruments can live with a folder in the safe and a spreadsheet. As the number of instruments and banks grows, the same questions stop having answers: where is this cheque right now, who was it endorsed to, if it went to the bank which slip was it on, is it overdue?

• Only the latest status is written down; when, by whom and where it was sent is lost.
• An endorsed cheque is deleted from the list, and when it comes back unpaid nobody knows where it came from.
• Instruments sent to the bank for collection are not tracked per deposit slip, so an uncollected item slips through.
• Due dates of issued cheques live in a separate file, and the cash need is noticed on the last day.
• When an instrument is collected, the customer balance is corrected by hand and the two records drift apart.

What good cheque and note tracking software must have

The core record is not the instrument alone but the instrument plus its movement history. Number, drawer, bank, due date and amount are entered once; every later action (sending to the bank, endorsement, collection, bounce, return) is added as a new movement row and old rows are never changed. That way the question "who held this instrument on that date" can always be answered.

• Received and issued instruments in separate portfolios, but on one due date calendar.
• Instrument card: number, drawer or debtor, bank and branch, due date, amount, currency, photos of front and back.
• A fixed list of statuses and a table of allowed transitions; an instrument not in the portfolio cannot be endorsed.
• Deposit slips for collection or collateral: which instrument went to which bank on which day.
• For endorsed instruments, who they were given to; the instrument leaves the portfolio but not the tracking.
• A daily list and reminder for instruments due soon and for overdue ones not yet collected.
• Amounts as integers in minor units, with the currency stored on foreign currency instruments.

A cheque you endorse leaves your hands, but your risk does not end: if it is not paid on its due date it can come back to you. That is why an endorsed instrument is never deleted; it keeps being tracked with an "endorsed" movement.

Status transitions and a due list: a small example

In the example below, the statuses an instrument can move to come from a fixed table: a collected instrument cannot go to the bank again, and a bounced one can be taken back into the portfolio. Each transition is stored as its own movement with who did it and when. The second function lists instruments waiting in the portfolio or at the bank that fall due in the coming days, ordered by date.

type Status = 'portfolio' | 'atBank' | 'endorsed' | 'collected' | 'bounced' | 'returned';
type Instrument = { no: string; dueDate: string; amountMinor: number; status: Status };

// Allowed moves come from a fixed table; anything else is rejected.
const NEXT: Record<Status, Status[]> = {
  portfolio: ['atBank', 'endorsed', 'collected', 'returned'],
  atBank: ['collected', 'bounced', 'portfolio'],
  endorsed: ['bounced'],
  collected: [],
  bounced: ['portfolio', 'collected'],
  returned: [],
};

function move(i: Instrument, to: Status, by: string, at: Date) {
  if (!NEXT[i.status].includes(to)) throw new Error(`${i.status} -> ${to} not allowed`);
  return { instrument: { ...i, status: to }, movement: { no: i.no, from: i.status, to, by, at } };
}

// Open instruments due within the next N days, oldest first.
function dueSoon(list: Instrument[], today: Date, days: number) {
  const limit = today.getTime() + days * 86_400_000;
  return list
    .filter(i => ['portfolio', 'atBank'].includes(i.status) && Date.parse(i.dueDate) <= limit)
    .sort((a, b) => a.dueDate.localeCompare(b.dueDate));
}

Which systems should cheque tracking be connected to?

Cheques and notes should not be an island. An instrument received from a customer should appear as a payment in your accounts receivable software, together with the invoice it settled; if it bounces, the balance should reopen by itself. Collected or paid instruments flow into the official books through accounting software integration. Due date reminders are produced by a scheduled job (cron job) that runs every morning, and who may send an instrument to the bank or endorse it is limited with role based access control.

Off the shelf or custom software?

If you handle few instruments and work with a single bank, the cheque and note module of a bookkeeping package is usually enough. Custom software makes sense when instruments move between branches, when cheque tracking must run on the same data as sales, orders and credit limit checks, or when the field team should record an instrument with a photo on mobile at the moment of pickup. Before deciding, count how many times in recent months nobody could immediately say where an instrument was or what its status was; that shows the size of the problem best.

Conclusion

Cheque and promissory note tracking software pays off when every instrument keeps its movement history, endorsed instruments never drop out of tracking and received and issued instruments sit on the same due date calendar. This article is a general software guide, not legal or financial advice. If you want to look at your cheque process together with your existing systems, see our corporate solutions page or write to us through the get a quote form.