Date-Matching Space Sensitive?

Was just curious to know if my problem was a problem with anyone else's, but had to make two rules with date matching. The situation was the dates on some of the scanned files came out with a space "January 1, 2013" between the comma and the year, and some of the dates "January 1,2013", without a space after the comma. The only way I found this out was by copying the date of the scanned files that were not renaming according the rule, and pasting it into word and realizing that the space was the issue, I then made a separate rule to compensate for the spacing issue. Was wondering if this was the normal procedure for this issue, if anybody else has had this issue, or if I should be doing something different on my end, I guess this is the normal with some scanners, I have a fujitsu scansnap s1300i.

That is normal procedure. You can alternatively use the "anything" token instead of a space which will match a space, or nothing, or any other random characters that aren't a year.