OFX File Invalid/Corrupt

[Jeff Feit]

While trying to download/import a OFX from a bank that I have been using for some time I got an error that the file was Invalid/Corrupt. After some experimenting I was able to narrow the issue down to transactions from a single day, then to 2 of the 4 transactions from that day.

I looked in this group and found the OFX file analyzer and ran the file through it. This is the first time that I have used it and I can't find any documentation, but it seems there are no errors. This was the output:

*** All line number references do not include header lines ***
***OFX 1.02 Add ~10
***OFX 2.0 Add ~2
Running Data Through Parser
No Parse Errors

Reading Data Into Buffer
Tokenizing Data
Initializing Data Structures
Analyzing Data
Verifying Security Types
Verifying Security Uniqueness
Verifying FITID Uniqueness
Verifying Sign Correctness
Verifying Total Calculations
Verifying Other
Done Analyzing File

These are the 4 transaction from that day. The first 2 work, the second 2 do not. Is there anything obviously wrong with them? 

<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20250819120000
<TRNAMT>-373.94
<FITID>63140954021202508190000004
<NAME>CAPITAL ONE      CRCARDPMT
<MEMO>Preauthorized Debit
</STMTTRN>

<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20250819120000
<TRNAMT>-1116.29
<FITID>63140954021202508190000003
<NAME>CAPITAL ONE      CRCARDPMT
<MEMO>Preauthorized Debit
</STMTTRN>

<STMTTRN>
<TRNTYPE>DIRECTDEBIT
<DTPOSTED>20250819120000
<TRNAMT>-27.31
<FITID>63140954021202508190000002
<NAME>WAWA 7408         INDIANAPOLIS I
<MEMO>DBT Purchase
</STMTTRN>

<STMTTRN>
<TRNTYPE>DIRECTDEBIT
<DTPOSTED>20250819120000
<TRNAMT>-51.36
<FITID>63140954021202508190000001
<NAME>AVIAN & EXOTIC    INDIANAPOLIS I
<MEMO>DBT Purchase
</STMTTRN>

[Cal Learner]

If only the bottom one had the problem, I would suspect the ampersand could be the problem. An ampersand in OFX should show up as these 5 characters: &amp;

You could try replacing that ampersand with those five characters, or maybe use a plus sign or something else.

See if that gets rid of one of the errors.

[Jeff Feit]

I must have made a mistake in my test. Fixing the ampersand did it, the other one was OK. Should the OFX analyzer pick that up?

[Cal Learner]

I tested, and the OFX Analyzer did not pick up the test cases I tried.

So should have picked it up in the initial Analyzer design, but the existing version does not pick that up.

I am working on a different scrubber right now, but this is the kind of thing that I would think I should incorporate into a scrubber.

[Ameridan (microsoftmoneyoffline.wordpress.com)]

scrubber.py has this function already?

#14-Apr-2018*rlc
#   - Replace ampsersand "&" symbol w/ &amp; code when not part of valid escape code. see _scrubGeneral()

[Cal Learner]

Thanks!  I think that  scrubber can be used only as a PocketSense scrubber.  Jeff may want to use PocketSense to polish off his file today.

[Doris Tomlin]

I guess I'm a little late to this discussion. 
I can confirm that the ampersand in an OFX file has given me that error message in the past. After homing in on the offending transaction, I edited the file to remove the ampersand and the following text. I believe it was a Reader's Digest subscription charge on my credit card that caused the problem, and the &apos was used to indicate the apostrophe in Reader's. 
<MEMO>Check 3628 Tracer 021000029229665 Processed Check - Reader&apos;
I edited it in Notepad to read: 
<MEMO>Check 3628 Tracer 021000029229665 Processed Check - Readers;
... and I had no further problems

I have never tried PocketSense or the OFX Analyzer

--
You received this message because you are subscribed to the Google Groups "Microsoft Money" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microsoft-mon...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/1270e0cf-51c1-417c-b11b-3a5e5774c15fn%40googlegroups.com.