The OFX specification includes lists of appropriate Status CODE values for each XXXTRNRS. Often, OFX server developers use any OFX STATUS code in the OFX Specification Status Code Appendices, without verifying that the CODE is appropriate for the particular transaction response. Servers should send only appropriate Status CODEs.
Current versions of Money do not reject a response that contains an inappropriate Status CODE. Instead, Money displays the error message for a 2000 in the Call Summary if it receives a CODE that is not supported for the transaction.
Apay Support
Current versions of Money allow users to send Apays to any server that supports bill payment. This includes servers that do not support Apays. Servers that do not support recurring payments should include error handling for any it receives. We recommend returning an error 2008 and a value that explains why the payment request failed. For example:
(value matches what Money sends)
2008
ERROR
Automatic payments are not supported by (FI name). Change the Automatic payment into a series of individual electronic payments. Submit each payment at the appropriate time. You can submit each payment up to one year in advance of the due date. <BR><BR> We are sorry for this inconvenience.
Note: The <BR> characters inserts an extra line break. You need two sets to provide a blank separation line.
Money 2005 FAQ
Based on early feedback from users, we released an updates to Money 2005 in mid-November which addressed issues that had been reported to us. While this page does not cover all the updates included in this release it identifies several fixes we believe to be particularly relevant to our online financial institution partners. For the latest information regarding Money 2005 updates please visit our website at http://www.microsoft.com/money/fi/update.mspx. The content of our updates page include a description of all relevant issues addressed in the updates and how to determine whether or not your installation of Money has received all available updates.
Error When Attempting to Open Money 2005 Data File
If you are experiencing issues opening your Money 2005 file it may be due to a release version difference as we have released an update for Money 2005. Once a user has updated their Money file they can no longer open that data file in installations of Money which have not installed the update. This KB article may be used to determine whether or not that is causing an issue if you receive an error when opening your data file. http://support.microsoft.com/default.aspx?scid=kb;en-us;890393.
Special Characters in Account Info DESC Field
The OFX specification supports any value in the field. However, Money 2005 uses the value to create account names does not allow the following characters in the tag:
[ - left bracket
] - right bracket
: - colon
Payment Mail
Money 2005 does not send any payment information in the PMTINFO aggregate when sending payment mail.
Common Brokerage Issues
This section discusses some of the more common issues seen only with downloads from Brokerage servers.
COMMISSION, TAXES, FEES, and LOAD
The Commission recorded in the Money register is the sum of the COMMISSION, TAXES, FEES, LOAD, and WITHHOLDING. As indicated above, these values must always be positive. Current versions of Money drop any transactions that contain negatively signed values for these tags.
Calculation Tolerance
Money calculates the expected TOTAL for most security types as UNITS * PRICE +/- Total Commission. For DEBT transactions, the Price is defined as percent of par. The TOTAL calculation for DEBTs is UNITS * (PRICE/100) +/- Total Commission. For Options, the calculation is (UNITS * SHPERCTRCT) * PRICE +/- Total Commission.
For Mutual Funds, the TOTAL value returned in Investment transactions must compute to within 5¢ of the value Money calculates. All other investment types must compute to within 2¢.
Rather than rejecting the entire response, Current versions of Money drop individual transactions that do not compute.
DEBT Securities How Money Calculates for Bonds
OFX 1.02 spec section 13.9.2.4.2 defines as "Price per commonly-quoted unit.... Percentage of par for bonds" and as "For security-based actions other than stock splits, quantity.... Face value for bonds."
is defined as "Transaction total. Buys, sells, etc.:( (quan. * (price +/- markup/markdown)) +/- (commission + fees + load + taxes))."
Based upon this, Money was written to calculate bond TOTAL as follows:
((UNITS/PARVALUE) * ((price*PARVALUE/100) +/- markup/markdown)) +/- (commission + fees + load + taxes))
The Par Value in Money is always considered to be 100, no matter what the PARVALUE is downloaded in the DEBTINFO. For that reason, we recommend that UNITS and UNITPRICE be sent appropriately for a PARVALUE of 100. Since Par Value is presumed to be 100, and most brokers do not download MARKUP/MARKDOWN, this can be simplified to:
((UNITS/100) * price) +/- (commission + fees + load + taxes).
PARVALUE
Money ignores the downloaded PARVALUE and presumes that the PARVALUE is always 100. For this reason, Microsoft recommends that Brokerage servers use 100 as PARVALUE.
ACCRDINT
for a or is included as a separate cash transaction in the associated cash account. should be less than or equal to zero for . Conversely, should be greater than or equal to zero for . If the signage of with respect to and is incorrect Money will not enter the transaction into the cash account.
MARKUP/MARKDOWN
Current versions of Money TOTAL calculations take MARKUP/MARKDOWN into consideration as specified in OFX spec 1.02 section 13.9.2.4.2 Transaction Aggregate Elements:
Transaction total. Buys, sells, etc.:( (quan. * (price +/- markup/markdown)) +/- (commission + fees + load + taxes)). Distributions, interest, margin interest, misc. expense, etc.: amount. Return of cap: cost basis; amount
TRANSFERs of SHORT Positions
Even though UNITPRICE is not a required tag, Money skips transactions that result in Add Shares for a short position if there is no price. Money displays something similar to the following in Call Summary:
A Transfer transaction of -1.0000 shares on Thursday, August 24, 2004 has been downloaded but could not be entered into the register because the investment information was invalid.
If Money received enough information, it will automatically adjust. (CUSIP: 000000000) Server could modify code to always send a non-zero value in UNITPRICE, but this is not required, as server behavior is correct according to OFX spec.
SECNAME
Money can store 70 characters for the Security name. Money does not allow two different securities with different ticker symbols in the file to share the same name.
Money will display a dialog asking customers to disambiguate two securities with the same name and different TICKER values. However, it is easy for the customer to be confused and to make the wrong decision here.
For this reason, Microsoft suggests that each UNIQUEID have a SECNAME that is unique within the first 70 characters.
Brokerages are required by OFX spec to always send UNITPRICE in INVPOS. However, Money does not always use this feed to update price history. Money only updates price history with price from INVPOS when it makes an adjustment, an add or remove shares, based upon this position information. This is by design.
Money expects that security prices will be kept up to date by our quote feed. On a first call known securities that need no position update will have price as of last transaction. Future calls will update to current price from quote feed. What this means, however, is that Money never updates prices for securities without known TICKERs, such as Bonds, or brokerage funds that are not publicly traded. Users will need to update these manually.
The first time Money receives INVBANKTRAN transactions for an account and processes the statement, Money can adjust the Opening Balance of the account to agree with the if not 0, else the . However, this only occurs if there are no other transactions in the associated cash account, such as transfers of cash caused by Investment transactions. If any Investment BUYs, SELLs, etc. has an affect on the Cash account exist in the account, Money does not adjust the balance.
Option TICKER Format
The quote feed used by Microsoft for stock quotes expects Options to be formatted with a leading period. For example, a TICKER for a Call option on Microsoft at 150 on 1/18/2002 would be .IWUAJ.
If we receive TICKER values without the leading period, Money displays error messages during any quote call, similar to the following: Money was unable to retrieve a quote for MSFT Call 150 Jan 02. The symbol US:IWUAJ is unrecognized. To get more information on how to disable downloads for this symbol see, "Deactivate a ticker symbol from online downloads." Likewise, server should not download invalid or expired TICKER values.
Since 401(k) and 403(B) accounts are not taxed based upon capital gains but as income, Money 2003 and 2004 simplify the manual and online reconciliation of securities in accounts designated as one of these types of retirement accounts. When these versions receive a statement for an account that is handled as a 401K or 403B Money processes the positions and clears out any cash in the contributions (cash) account. Money ignores any transactions in the OFX response.
Money 2005 asks when setting up a new investment account of any type for online services whether or not you care to see transactions. Showing transactions is the default choice. If you only want to see your positions, you can select that option and Money 2005 will ignore any transactions downloaded from the server.
In Money 2003 and 2004, there is a work around if you want Money to process statement data for 401K and 403B accounts. You can change the account type from a retirement account to an Investment account in Account Details. Then set it back as a retirement account so that Money features in the Financial Planner and other tools handle the account appropriately. However, instead of setting it as a 401K or 40sB account, set it as another type of retirement account, such as Other (For Employee).
NOTE: Money 2003 and 2004 will process statements in any other type of retirement account. This behavior only affects 401(K) and 403(B) designated accounts in Money 2003 and 2004. For information which can be shared with customer, please see the Microsoft Knowledge Base article at http://support.microsoft.com/default.aspx?scid=KB;EN-US;822766.
Money 2003 Handling of Options
Versions of Money prior to 2003 handled Options actually as security type STOCK. Money 2003 added the OPTION security type, and therefore behavior of OFX statements for Options is different in Money 2003 than in earlier versions. There are a few issues with this change.
Security Type Not Converted on Upgrade
Once a security is created, Money is unable to change it from one security type to another. When earlier versions of Money received OPTINFO they created a Stock security. Money 2003 first began creating Option securities. However, if a customer had imported data for an Option in earlier versions, then upgrades, Money cannot convert the Stock security to an Option security. Instead user must create a new security, with a new name. Money will then create a new position, not clearing out the old one.
Money 2003 Cannot Handle Some BUYTOCLOSE Transactions for Options
If Money 2003 receives a BUYTOCLOSE transaction for any security, and the file does not already have a short position to cover the closure, Money 2003 displays the following message:
This is a Buy To Close transaction, but you do not have a Sell to Open transaction for this investment in your account. Please go to the Account Register and manually enter a Sell to Open transaction to cover this option, and then read your statement again.
The user must note the security, number of shares, and date, then click OK and go to the account register and manually create a transaction to open the position before the closure date. Then they can proceed with processing this transaction and subsequent transactions.
NOTE: Just as in the OFX response, when manually entering a Sell To Open transaction for options, user must enter the number of contracts, not the number of shares. So if 4.03.1-1240.0, user would need to create a Sell To Open transaction for 4 contracts on or before the transaction date. Price can be Zero.
Money 2004 and above automatically create a zero price Sell To Open transaction for the necessary number of shares on the date of the transaction that will close the position.
Option Created as PUT Even If SECINFO Indicates a CALL
Options are created by Money 2003 as PUTs, even when SECINFO indicates that it should be a CALL. The only way to successfully import a CALL option is to create the Call Option manually first. Then import the OFX file or make your first connection to the server. Later versions of Money handle this correctly. For this reason, we do not recommend Money 2003 for customers with Call Options.
Money Loops When Importing a Short Position
When importing positions which contain short option positions which do not exist in file, Money 2003 cannot proceed. The only work around is to step out of processing the positions, and manually create the short position by entering a Sell To Open transaction. So for example:
...
SHORT -50.00000 0.10 ... 20030414120000…
would need to be entered as a Sell to Open transaction on or before 4/14/03 of quantity 50.
Money 2004 and 2005 automatically create a zero price Sell To Open transaction for the necessary number of shares.
Margin Interest Transactions in Money 2005
Money 2005 skips all margin interest transactions and will not display them in the account register. This functionality will be added in the next version of Microsoft Money.
Money 2005 Sends DTEND When Requesting Positions
Money has historically used the current date for DTASOF when requesting positions. Money 2005 uses the DTSTART value instead. If server responds correctly, Money 2005 will post positions BEFORE investment transactions. Money 2006 returns to using the current date for DTASOF. Microsoft suggests that servers always return positions with current information.
Money 2005/2006 skips option TRANSFER transactions
Money 2005/2006 skip transactions for option security types. However, Money will add or remove the appropriate shares when processing the position information. This issue has been addressed for the next Money release.
Money 2005/2006 loops when encountering OTHERINFO
When importing security types, Money will ask the user to select a security type. If the users selects “Other”, Money will notify the user that a security of that name already exists and cannot proceed. The only work around is to select a different security type besides “Other”.
Invalid Error When Calculating OFX 2.0 Investment TOTAL
Money 2005 and earlier ignored the WITHHOLDING, STATEWITHHOLDING, and PENALTY tags when computing the value of an OFX 2.0 formatted investment statement. Since the OFX analyzer uses the Money 2004 parser, the Analyzer tool may report computation errors that do not apply to Money 2006 and above.
Enterprise and Support Training June, 2016
|
Yüklə 293.5 Kb.