Pierre , all details you are giving from business point of view makes sense. In context of this task, what we want to conclude is that is it making sense to introduce new table for check. And you are not answering that question's answer .
What I said above and what Swapnil again said here : " if there is indeed any real time need of electronically transferring Check details to different financial institutions like Bank etc., (similar to what we mostly do for Credit Card/EFT), then we could add Check as new entity to store all relevant details as discussed above. Although, we haven't came across any real requirement around that from our clients so far who are dealing inbound/outbound payments through checks." . So our discussion is around whether to add new table or not ?
It will be great if you help us to conclude that. I think that we don't need to add new table for Check . Also as Swapnil mentioned we have not seen any such requirements so far , where clients who deals with outgoing and incoming payments with Check, send check details electronically to financial institutions like Bank . So its not making sense to add new table for Check.
But if you have some use case where it will make sense to add new table, we can definitely do that. I hope your next reply will help us to conclude this discussion.