• valid()</PRE>

valid()</PRE> <P>Ask if the MICR code is valid Returns true or undef Valid means the string argument was matched as a business check MICR or a personal check MICR. That is, the fields are there and in the *right order*. NOTE that if your code is deemed invalid, you *may* still get field values. But your string as a whole should be considered invalid. You should always use <CODE>valid()</CODE> before taking the output as gospel.</P> <P> <H2><A NAME=``status()''><CODE>status()</CODE></A></H2> <P>Returns a summary string including original string argument to constructor, ``clean_run'' pass count for the string, string after those clean runs, if the module gave up, etc. Useful for logging and find out if you have any problems.</P> <P>Typical usage:</P> <PRE> $micr-&gt;valid or print STDERR $micr-&gt;status;</PRE> <P> <H2><A NAME=``is_business_check()''><CODE>is_business_check()</CODE></A></H2> <P>Returns true or false. Presently a business check has the fields;</P> <PRE> AUXILIARY_ON_US TRANSIT ON_U/PRE <P>In that order. Furthermore, the check number is extracted from AUXILIARY_ON_U/P <P> <H2><A NAME=``is_personal_check()''><CODE>is_personal_check()</CODE></A></H2> <P>Returns true or false. Presently a business check has the fields;</P> <PRE> TRANSIT ON_U/PRE <P>In that order. Furthermore the check number is extracted from ON_US, digits after the on us symbol.</P> <P> <H2><A NAME=``is_unknown_check()''><CODE>is_unknown_check()</CODE></A></H2> <P>Means that we have matched one or more main fields (aux on us, on us, transit) but some are missing or in unexpected order. This should be taken *very* seriously. It means any strings that return <CODE>is_unknown_check()</CODE> *must* be checked for correctness.</P> <P> <H2><A NAME=``get_check_type()''><CODE>get_check_type()</CODE></A></H2> <P>Returns (u)nknown, (b)usiness, (p)ersonal, or undef.</P> <P> <H2><A NAME=``clean_runs()''><CODE>clean_runs()</CODE></A></H2> <P>How many times the string has been been ``cleaned''. This does not tell you that the string is a valid MICR code. Just how many times it was cleaned. The higher the number, the more you should inspect the output by a human being.</P> <P> <H2><A NAME=``original_string()''><CODE>original_string()</CODE></A></H2> <P>String passed to constructor.</P> <P> <H2><A NAME=``micr()''><CODE>micr()</CODE></A></H2> <P>MICR string without spaces of extraneous garble. If you passed a MICR string *with* garble, this is different from the <CODE>original_string()</CODE> Returns undef if the string is invalid. NOTE: a string which is not <CODE>valid()</CODE> will not return a <CODE>micr()</CODE> code.</P> <P> <H2><A NAME=``micr_pretty()''><CODE>micr_pretty()</CODE></A></H2> <P>Returns the <CODE>micr()</CODE> code somewhat formatted for human eyes. That is.. If your original string argument to the constructror is</P> <P>3 12 U0000011135U T052000113T 984U0837166 _ 23 1</P> <PRE>

Then this returns somethign like</PRE> <P>U0000011135U_T052000113T_984U0837166</P> <P>NOTE: a string which is not <CODE>valid()</CODE> will not return a <CODE>micr_pretty()</CODE> code.</P> <P> <H2><A NAME=``giveup()''><CODE>giveup()</CODE></A></H2> <P>Returns true or false. Think of this also as 'gave up'. NOTE: A string that ended up not <CODE>valid()</CODE> could still return 0 here. This is because by default, Finance::MICR::LineParser attempts to match at least one of the main MICR fields before giving up.</P> <P> <HR> <H1><A NAME=``micr specific methods''>MICR SPECIFIC METHOD/A</H1> <P>There are five major fields on a MICR line. Two of the five major fields (transit and ``on us'') are broken into multiple fields- here called ``sub fields''. First are the five major fields...</P> <P> <H2><A NAME=``auxiliary_on_us()''><CODE>auxiliary_on_us()</CODE></A></H2> <P>contains check number if present; bracketed by 'on us' symbols returns undef if not found.</P> <P> <H2><A NAME=``epc()''><CODE>epc()</CODE></A></H2> <P>one character located to the left of the transit field if present returns undef if not found. This needs work.</P> <P> <H2><A NAME=``transit()''><CODE>transit()</CODE></A></H2> <P>Always 9 digits including check digit. Opens and closes with a transit symbol. (Some papers refer to this field as having 11 chars because they are counting the open and close symbols as characters.) returns undef if not found.</P> <P> <H2><A NAME=``on_us()''><CODE>on_us()</CODE></A></H2> <P>variable length 19 digits max between transit and amount fields (to the right of transit.) returns undef if not found.</P> <P> <H2><A NAME=``ammount()''><CODE>ammount()</CODE></A></H2> <P>10 digits zero filled; bracketed by two amount symbols returns undef if not found. This needs work.</P> <P> <HR> <H1><A NAME=``transit sub field methods''>TRANSIT SUB FIELD METHOD/A</H1> <P>Transit has 9 digits. It is croken into multiple fields:</P> <P> <H2><A NAME=``routing_number()''><CODE>routing_number()</CODE></A></H2> <P>return routing number. (digits 1-4) returns undef if not found.</P> <P> <H2><A NAME=``bank_number()''><CODE>bank_number()</CODE></A></H2> <P>return bank number (digits 5-8) returns undef if not found.</P> <P> <H2><A NAME=``check_digit()''><CODE>check_digit()</CODE></A></H2> <P>return check digit (one digit) returns undef if not found</P> <P> <HR> <H1><A NAME=``on us sub field methods''>ON US SUB FIELD METHOD/A</H1> <P> <H2><A NAME=``check_number()''><CODE>check_number()</CODE></A></H2> <P>returns check number, Located in various places in the on us field. returns undef if not found</P> <P> <H2><A NAME=``tpc()''><CODE>tpc()</CODE></A></H2> <P>max 6 characters; Located to right of account number returns undef if not found TODO: This needs some thought, on a personal check this would be the check number, what gives?</P> <P> <H2><A NAME=``account_number()''><CODE>account_number()</CODE></A></H2> <P>Variable length; always followed by the On Us symbol returns undef if not found</P> <P> <HR> <H1><A NAME=``bugs''>BUG/A</H1> <P>Please report bugs to developer.</P> <P>Notice: this module is under development. It is being used for production, but it *is* under development.</P> <P>Please notify with hany questions or concerns. I've seen very little on MICR and open source out there. If you have any recommendations, please don't hessitate on letting me know how to make this module better.</P> <P>This module helps me a lot, and I am hoping it may be of use to others and they may contribute criticism, patches, suggestions, etc.</P> <P> <HR> <H1><A NAME=``todo''>TODO</A></H1> <P>Not yet implemented:</P> <P>If you want to get *your* symbols output back, here's an example:</P> <PRE> my $micr = new Finance::MICR::LineParser({ string =&gt; $string_from_gocr, on_us_symbol =&gt; 'CCc', transit_symbol =&gt; 'Aa', dash_symbol =&gt; 'DDd', ammount_symbol =&gt; 'XxX', return_my_symbols=&gt;1, });</PRE> <P> <HR> <H1><A NAME=``author''>AUTHOR</A></H1> <P>Leo Charre &lt;<A HREF=``mailto:leo@leocharre.com''>leo@leocharre.com&gt;</P> <P>This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.</P> <P> <HR> <H1><A NAME=``bugs''>BUG/A</H1> <P>Address bug reports and comments to: Leo Charre &lt;<A HREF=``mailto:leo@leocharre.com''>leo@leocharre.com&gt;</P> <P> <HR> <H1><A NAME=``see also''>SEE ALSO</A></H1> <P><A HREF=``http://en.wikipedia.org/wiki/Magnetic_ink_character_recognition''>http://en.wikipedia.org/wiki/Magnetic_ink_character_recognition</P> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR=``#cccccc''> <FONT SIZE=+1><STRONG><P CLASS=block>&nbsp;Finance::MICR::LineParser - validate and parse a MICR code from a string</P></STRONG></FONT> </TD></TR> </TABLE>

</BODY>

</HTML>