Cheques are grouped into cheque books. Cheques are written, cashed or void (I made a mistake when writing it, so ripped it up). When all cheques in a book are cashed or void, that book becomes less important to me.

When cheques are written they have a created date of the date they are written (actually there could be two different dates here - the date I wrote it and the date it's for, in case I write a future-dated cheque). They have a cheque number (that relates them to other cheques in the same book), plus a description field - relying on part of the description field to be the cheque number is probably not good enough for the link to the book.

A written cheque will have a transaction date that is always today i.e. an extra date that floats later and later. The transaction date stops moving later when it matches with a transaction that I enter or import. At this point its status changes to cashed. Or I could give up on a cheque and mark it as void (or some other status like stopped or abandoned).

I'd like to see easily all written but not cashed cheques, and which books still have written but not cashed cheques. Manually bumping the transaction date later and later is possible but code could easily do that for me.

Cheques are real world entities that users expect to see reflected in their finance system (like statements, which is the subject of another request).