So, we really cant tell a client what they are doing but if the machine transmitted something running on DOS with a fax modem on a reboot two contracts of the same amount, same currency and same rate in 24-48 hours, then it is likely to be a duplicate. But, what does the customer think?

So, we really can't tell a client what they are doing but if the machine transmitted something running on DOS with a fax modem on a reboot two contracts of the same amount, same currency and same rate in 24-48 hours, then it is likely to be a duplicate. But, what does the customer think? They have to agree and you go through it on the recorded line and they pull their fx Quenta dough folder and then they confirm at Nutella Credit Union or at Converse City Credit Union.   In loss prevention, if the report is generated once a day of outstanding contracts, you will see the unprocessed duplicate one day after but the client does know its a duplicate but they might see that the machine transmitted the report twice but they also presume we have a way of knowing what is a duplicate since it is the biggest Mcdonalds Bank in the world; innit?  But back office processing cannot say it is a duplicate.  It is not their job. The rate goes down and the contract is processed twice but the trader is only paid for one rate booking; right Pauley?    Once processed twice, the bank needs payment twice but the customer only sends payment once but their credit facility is booked twice.  I propose here at Cyberdyne Genysis a filter for Bank of Mcdonalds that will pend a second contract that meets the  variables of same amount, same currency and same rate in 24-48 hours. Right Pauley?  There is one person who knows the contract is a duplicate.  He works for Cyberdyne Genesys.