This section contains a listing of common issues seen in Money and Investor. Taking these issues into consideration when developing an OFX server can prevent support calls.
Synchronization
Synchronization is defined in the OFX 1.02 specification section 6. Current versions of Money use full-synchronization for error recovery and multi-client support.
TOKENs
All Tokens specified in OFX and sent in their respective specified aggregates are stored in the Money database and returned in subsequent requests.
-1
Money supports the data synchronization TOKEN=-1 as specified in the OFX Errors and Omissions document referencing specification 6.4. This document states:
Servers should return TOKEN=-1 in the event they must respond with an error, but there is no XXXTRNRS wrapper inside the SYNCXXXRS wrapper.
Money will process a SYNC response with -1 to find an expected response. However, if the XXXTRNRS is not present, Money will reject the OFX response as invalid.
REFRESH
Current versions of Money use REFRESH rather than 0. On a first call, Money sends Y, requesting the current state of all SYNC data, rather then the entire history. In subsequent calls, Money returns the value received in the previous call. If you do not connect for more than 30 days, Money will send 0, instead of the last value.
Money will accept and handle several unsolicited items (unknown TRNUID) when received in the appropriate sync wrapper.
XXMAILSYNCRS
All versions of Money accept and display items received in the various mail sync wrappers.
INTRASYNCRQ/RS
Money 2003 and 2004 will send INTRASYNCRQ and will process the following responses when received in the SYNC response:
-
INTRARS
-
INTRACANCRS
-
INTRAMODRS
Money matches INTRATRNRS with unknown SRVTID values received in an INTRASYNCRS with existing transactions if AMOUNT, DTPOSTED, and BANKACCTTO/BANKACCTFROM agree with transaction in register.
Money 2005
Due to problems processing unrecognized INTRARS in Money 2005, this request has been turned off in Money 2005, but will be re-enabled in future versions. If a transfer request fails to complete in Money 2005, customers will need to check their financial institution’s website to see if the transfer request was processed. Likewise, for customer’s who’s financial institution offers future dated transfers will need to watch their financial institution website to see when the transfer takes place.
PAYEESYNCRS
Money accepts and handles unsolicited payee updates when returned in a PAYEESYNCRS wrapper.
PMTSYNCRS -
PMTRS
Money discards any PMTTRNRS data with unknown SRVRTID that is older than the DTSTART of an accompanying bank statement response STMTTRNRS, or today less seven days for bill-payment only responses. For new payment sync data within date range, Money will match transactions in the register based upon DTPMTPRC, TRNAMT, and CHECKNUM (if present).
-
PMTCANCRS
-
PMTMODRS
-
RECPMTSYNCRS
Current versions of Money handle the following unsolicited transactions, whether the TRNUID or RECSRVRTID is known or unknown:
-
RECPMTRS
If the RECSRVRTID and TRNUID are unknown, then Money creates new Apay models in the Bills area. Money does not match existing recurring transactions in Bills.
-
RECPMTCANCRS
-
RECPMTMODRS
Money 2006 and above will ignore Apay modifications.
 For more information on how Money handles specific unsolicited items returned in sync wrappers, review the OFX Message Support Document which can be found at http://download.microsoft.com/download/a/3/d/a3da081d-333e-4c5b-8029-815a932e5b19/OFX_Message_Support.doc. After reviewing this information, contact the Microsoft OFX Certification Team at certteam@microsoft.com if you need further clarification.
Current versions of Money process PMTSYNC data and INTRASYNC data before processing statement data. Refer to the Synchronization section above for descriptions of the matching process used for these transactions.
After processing Sync data, Money processes statement data and uses the following statement matching process:
-
Money first matches guaranteed transactions. Guaranteed matches can be one of the following:
-
Transactions already downloaded with an FITID assigned to it.
-
Epay or Xfer transactions that match by SRVRTID or RECSRVRTID, if downloaded from the financial institution.
-
Check number and amount are identical
NOTE: These will not match if the amounts are different or the sign is different (deposit versus withdrawal)
-
Money then matches remaining items with existing transactions based on the following criteria:
-
Posting date (from bank)
-
Check number
-
Amount
NOTE: For withdrawals, Money only matches on EXACT amounts. For deposits, Money matches if amount is within a small percentage. This allows for slight variations in paychecks.
NAME Values and Payee Aliasing
Money aliases payees, such that if you manually change a value to something else during reconciliation, or match a statement to an existing register item with a different name, Money stores the new value as an alias for the NAME value. The next time Money receive that same NAME value in a STMTRNRS, we replace it with the alias.
To avoid problems with incorrectly aliasing some of the more common NAME values, Money does not alias the following names.
-
cash
-
check
-
atm
-
withdrawal
-
debit
-
credit
-
deposit
-
purchase
-
point of sale
-
atm debit
-
atm deposit
-
ach debit
-
ach credit
Instead, current versions of Money drop these NAME values when entering into the register, but do include a feature to allow users to manage this aliasing more directly.
Microsoft agrees that this is not ideal for these transactions, but better than the alternative of every "atm debit" downloading as "Gift for Grandma" or whatever else the user used during the first download. Some servers have chosen to put this data in the MEMO tag, so that it is still available for viewing.
|
Yüklə 293.5 Kb.