RE: Fraudulent Orders or creating a Bad address list
I don't know your particular environment or processes, but you could have a stop list of partial addresses in a SQL table, add bad ones in there.
Then set up a SQL job to compare the addresses in there to ones on your SOP10100/SOP10200, if they match "enough" then insert a record into the SOP holds table for that order to put a process hold on the order.
You can report on holds.
You can go even further if you need to. There are online services (a whole service sector) that allow you to submit details for checking, some services come from the debtor credit worthiness, others check for online fraud patterns. They cost and cause false positives and negatives, its a balancing game between "acceptable" losses and tying up your processes in checking.