Ana səhifə

1-Way ofx and Microsoft Money Microsoft Corporation June 3, 2005 What is 1-Way ofx?


Yüklə 0.76 Mb.
səhifə1/13
tarix18.07.2016
ölçüsü0.76 Mb.
  1   2   3   4   5   6   7   8   9   ...   13


1-Way OFX and Microsoft Money

Microsoft Corporation

June 3, 2005

What is 1-Way OFX?

1-Way OFX, also referred to as Active Statements or Web Connect, refers to a mechanism that allows Financial Institutions to deliver transaction history (or statement data) from Internet banking websites to customers who are using Microsoft Money. Statements are delivered to the Money client via a file that is created using the OFX data format. The OFX file is typically delivered to the user via the financial institution's secure web site. For example, a financial institution web site could include a “Download to Money” button or link on their statement detail web page to allow users to send the information to their Money file.

Microsoft Money allows the user to import the OFX file that has been downloaded, reconciling each transaction and allowing the user to assign categories to each transaction as required, just as if a request had been initiated from Money. In some cases, Money will also attempt to intelligently assign default categories to transactions.

1-Way OFX File Format

The 1-Way OFX file is created using either the OFX 1.0.2 or 2.0 data format for Money 2004 and 2005 or OFX 1.0.2, 2.0, or 2.02 data format for Money 2006 and later. The file must be a valid OFX response file, including OFX header information, with the extension .ofx. Valid response files include:



  • SONRS

  • STMTTRNRS

  • CCSTMTTRNRS

  • INVSTMTTRNRS

  • SECLISTTRNRS

Banking

The following is an example of a valid 1-Way OFX file in OFX 1.02 (SGML) format for a checking and savings account. It has been indented for readability.


OFXHEADER:100

DATA:OFXSGML

VERSION:102

SECURITY:NONE

ENCODING:USASCII

CHARSET:1252

COMPRESSION:NONE

OLDFILEUID:NONE



NEWFILEUID:NONE








0

INFO



20050803155648[-5:EST]

ENG



SYNERGYBANKS

WOODGRV











0



0

INFO





USD



BankRTN

AcctNum

CHECKING





20050706120000

20050803120000



CHECK

20050706120000

-1099.24

48397293

1633

Home Insure Mortgage Company

Loan 67392938





PAYMENT

20050713120000

-49.65

48397294

City Electric Company

Automatic Payment





DIRECTDEP

20050722120000

450.00

48397299

ABC Manufacturing Inc

Direct Employer Deposit







701.11

20050803120000









0



0

INFO





USD



BankRTN

AcctNum

SAVINGS





20050706155648

20050803120000



INT

20050712120000

12.89

484534

Woodgrove Savings







8012.89

20050803120000










The following is an example of the same Active Statement file in OFX 2.0 (XML) format.
It has been indented for readability.













0

INFO



20050803155648[-5:EST]

ENG



SYNERGYBANKS

WOODGRV











0



0

INFO





USD



BankRTN

AcctNum

CHECKING





20050706120000

20050803120000



CHECK

20050706120000

-1099.24

48397293

1633

Home Insure Mortgage Company

Loan 67392938





PAYMENT

20050713120000

-49.65

48397294

City Electric Company

Automatic Payment





DIRECTDEP

20050722120000

450.00

48397299

ABC Manufacturing Inc

Direct Employer Deposit







701.11

20050803120000









0



0

INFO





USD



BankRTN

AcctNum

SAVINGS





20050706155648

20050803120000



INT

20050712120000

12.89

484534

Woodgrove Savings







8012.89

20050803120000











Investment

The following is an example of an investment active statement file in OFX 1.02 format. It has been indented for readability.

OFXHEADER:100

DATA:OFXSGML

VERSION:102

SECURITY:NONE

ENCODING:USASCII

CHARSET:1252

COMPRESSION:NONE

OLDFILEUID:NONE



NEWFILEUID:NONE








0

INFO

SUCCESS



20050201120000

ENG









0



0

INFO

SUCCESS





20050131120000

USD



2

40219634





19000101

20050131120000







40025098200011111050

20050102120000

WOODGROVE MONEY MARKET FUND





808515100

CUSIP



-8345.00

1.0000

0.00

8345.00

CASH

CASH



SELL









40001239200101085866

20050101120000

FrogKick Scuba Gear





293562104

CUSIP



300.0000

27.7500

20.00

-8345.00

CASH

CASH



BUY







40025098200010157523

20050115120000

Dividend





808515100

CUSIP



DIV

51.28

CASH

CASH









40025098200008029240

20050116120000

WOODGROVE MONEY MARKET FUND





808515100

CUSIP



51.2800

1.0000

0.00

-51.28

CASH

CASH



BUY







40025098200010157524

20050117120000

Dividend





918005109

CUSIP



DIV

35.00

CASH

CASH









40025098200008029241

20050118120000

WOODGROVE MONEY MARKET FUND





808515100

CUSIP



35.0000

1.0000

0.00

-35.0000

CASH

CASH



BUY










808515100

CUSIP



OTHER

LONG


1977.65

1.0000

1977.65

20050131120000

WOODGROVE MONEY MARKET FUND



1977

Y





293562104

CUSIP



OTHER

LONG


300.0000

30.45

9135.00

20050131120000

FrogKick Scuba Gear



300

Y





918005109

CUSIP



OTHER

LONG


100.0000

71.8400

7184.00

20050131120000

Contoso LTD



100

Y




0.00

0.00

0.00



















808515100

CUSIP



WOODGROVE MONEY MARKET FUND

WGMXX



OPENEND









293562104

CUSIP



FrogKick Scuba Gear

FKSG



COMMON









918005109

CUSIP



Contoso LTD

CLTD



COMMON







The following is an example of the same investment active statement file in OFX 2.0 format. It has been indented for readability.















0

INFO

SUCCESS



20050201120000

ENG









0



0

INFO

SUCCESS





20050131120000

USD



2

40219634





19000101

20050131120000







40025098200011111050

20050102120000

WOODGROVE MM FUND





808515100

CUSIP



-8345.00

1.0000

0.00

8345.00

CASH

CASH



SELL









40001239200101085866

20050101120000

FrogKick Scuba Gear





293562104

CUSIP



300.0000

27.7500

20.00

-8345.00

CASH

CASH



BUY







40025098200010157523

20050115120000

Dividend





808515100

CUSIP



DIV

51.28

CASH

CASH









40025098200008029240

20050116120000

WOODGROVE MM FUND





808515100

CUSIP



51.2800

1.0000

0.00

-51.28

CASH

CASH



BUY







40025098200010157524

20050117120000

Dividend





918005109

CUSIP



DIV

35.00

CASH

CASH









40025098200008029241

20050118120000

WOODGROVE MM FUND





808515100

CUSIP



35.0000

1.0000

0.00

-35.0000

CASH

CASH



BUY










808515100

CUSIP



OTHER

LONG



1977.65

1.0000

1977.65

20050131120000

WOODGROVE MONEY MARKET FUND



1977

Y





293562104

CUSIP



OTHER

LONG



300.0000

30.45

9135.00

20050131120000

FrogKick Scuba Gear



300

Y





918005109

CUSIP



OTHER

LONG



100.0000

71.8400

7184.00

20050131120000

Contoso LTD



100

Y




0.00

0.00

0.00



















808515100

CUSIP



WOODGROVE MONEY MARKET FUND

WGMXX



OPENEND









293562104

CUSIP



FrogKick Scuba Gear

FKSG



COMMON









918005109

CUSIP



Contoso LTD

CLTD



COMMON









FIELD NOTES:

NEWFILEUID: “NONE” is correct since 1-Way OFX doesn’t involve synchronization.

STATUS: This aggregate is required for the OFX file to be processed but it does not apply to OFX file import. It is correct to set these required field values to 0 and INFO.

FI: This tag is used if the financial institution is part of a larger organization that supports OFX for all of those institutions. Independent institutions will omit this aggregate. Money does not require this aggregate.

CURDEF: See the OFX spec for appropriate values if support for International applications is required.

SIGNONMSGSRSV1: The message set containing the SONRS is required for a successful import into Money.

FITID: Use of this field prevents duplicate entries in Money, which is one of the key benefits 1-Way OFX. This value must be unique within the account and persistent.

Optional Fields: The OFX specification includes both required and optional fields. A minimal number of optional fields have been included in these examples where they provide the greatest benefit to the end user and financial institution.

LEDGERBAL: Money expects the BALAMT in the LEDGERBAL to be signed from the perspective of the user. For CHECKING, SAVINGS, and MONEYMRKT account types, this should be a positive value, unless the account is overdrawn. For CREDITLINE account types, and for Credit Cards, the BALAMT should be a negative value when the user owes money on these debts.

NAME/PAYEE: If possible, it is best to avoid generic NAME/PAYEE tags. Money will recall any payee changes made by the customer during the Statement Matching process. The next time the same payee is presented, Money replaces the downloaded payee with the remembered payee, and auto completes the category field. This "alias"ing causes problems when the payee is generic - such as Purchase or Deposit. If available, Active Statement servers should add any information available regarding the payee to the NAME/PAYEE tag, rather then adding it all in the MEMO tag. For example, the following transaction:



DEBIT

20051230120000

-26.49

1336

PURCHASE

12-28-98 BORDERS BOOKS & MUSIC 94 BRIDGEWATER TNJ 98189


Would be less confusing to Money customers if it were formatted as follows:


DEBIT

20051230120000

-26.49

1336

BORDERS BOOKS & MUSIC

12-28-98 94 BRIDGEWATER TNJ 98189



CONTENT-TYPE: Microsoft Money can work with either Content-type text/ofx or application/x-ofx

CONTENT-DISPOSITION: Money work best with Inline rather than Attachment. This allows MNYIMPRT.EXE to open an OFX file automatically. However, if you want to give your users the option of opening or saving, then use Attachment.

FILE EXTENSION: If Money is installed and the users opens a file with ofx file extension, Money will copy the file to the local machine's temp directory and add a reference to the file in the registry. The user is then given the option to run Money and import the file immediately or wait until a later time. If the user chooses to wait, they will be prompted to import the file the next time Money is run.

FILE/IMPORT: If an OFX files is saved locally, the user can import it in Money from the File menu to manually load the file.

ACCTFROM: The aggregate is used to help match the account in the OFX file with the user's accounts in their Money file.

Testing 1-Way OFX Files

Testing your 1-Way OFX implementation will have three focuses:



  • Ensuring that the data in the OFX file accurately represents the statement transactions for the user’s accounts.

The burden here is on the Financial Institution to validate that the correct data is being extracted and translated from the backend legacy system where the data is stored.

  • Ensuring that the OFX file is in the correct format so that it may be read correctly by the Money client.

If the data in the OFX file is not formatted according to the OFX specification (and OFX DTD), the user’s attempt to read the statement data will fail. Money adheres to the OFX specification in this regard. Any problem with the format of the file that causes Money to be unable to parse the file will cause the entire file to be rejected as invalid. Any data issues that do not agree with Money’s implementation will be dropped and the user will not see the transaction.

In order to help in this effort, Microsoft provides troubleshooting documentation and utilities on our Financial Institution Tools site at http://www.microsoft.com/money/fi/tools.mspx.

To validate the user experience the Money client should be used in testing as much as possible. The Money client contains strong algorithms for reconciling the users transactions in the Active Statement file, but these algorithms rely on the data that is in the file.


  • Ensuring that the file is interpreted correctly by the Money client.

Your testing should include importing your files into Money and verifying that the data is interpreted correctly. One of the common questions received by the Money team regards Money's interpretation of dates. If you do not include a time zone, Money assumes base GMT. To ensure that your dates are interpreted correctly, you will want to include time zone information with your dates or convert to GMT on the server. Microsoft recommendation is to use the time of Noon GMT, which is the same day in almost all areas of the world.

OFX Specification for 1-Way OFX

1-Way OFX files are implemented using the OFX data specification. It was designed to support a variety of transactions and communications between a financial institution and client. Only small sets of these are required to support Active Statements for Microsoft Money.

The document that follows is a significantly modified version of the OFX specification. Many sections were removed that are not required to support Active Statements. While this greatly aids in learning the requirements for Active Statements, it is strongly recommended that the published version of the OFX specification be referenced for any implementation of OFX.

The OFX specification is available on the web at http://www.ofx.net.

Some sections of the spec that are not directly related to 1-Way OFX files have been left in the document where they provide a better understanding and background of OFX.

For more information about the way Money implements this specification, please review the OFX_Message_Support.doc found at http://www.microsoft.com/money/fi/ofxdoc.mspx.



Open Financial Exchange
Specification 1.0.2


May 30, 1997

Errata from September 16, 1997
NOTE: This is an incomplete version of OFX 1.0.2 modified specifically for financial institutions developing Active Statements web sites. Refer to the complete OFX specification before implementation, available at http://www.ofx.net.
© 1997 CheckFree Corp., Intuit Inc., Microsoft Corp. All rights reserved

Open Financial Exchange Specification Legend

Open Financial Exchange Specification © 1996-97 by its publishers: CheckFree Corp., Intuit Inc., and Microsoft Corporation. All rights reserved.

A royalty-free, worldwide, and perpetual license is hereby granted to any party to use the Open Financial Exchange Specification to make, use, and sell products and services that conform to this Specification.

THIS OPEN FINANCIAL EXCHANGE SPECIFICATION IS MADE AVAILABLE "AS IS" WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT, INTUIT AND CHECKFREE ("PUBLISHERS") FURTHER DISCLAIM ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT, ALL OF WHICH ARE HEREBY DISCLAIMED. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS SPECIFICATION REMAINS WITH RECIPIENT. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE PUBLISHERS OF THIS SPECIFICATION BE LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, DIRECT, INDIRECT, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF ANY USE TO WHICH THIS SPECIFICATION IS PUT, EVEN IF THE PUBLISHERS HEREOF HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.



Contents

1. Overview 5

1.1 Introduction 5

1.1.1 Design Principles 5

1.2 Open Financial Exchange at a Glance 6

1.2.1 Data Transport 6

1.2.2 Request and Response Model 7

1.3 Conventions 8

2. Structure 10

2.1 HTTP Headers 10

2.2 Open Financial Exchange Headers 10

2.3 SGML Details 11

2.3.1 Compliance 11

2.3.2 Valid SGML Characters 11

2.3.3 Comments Not Supported 11

2.4 Open Financial Exchange SGML Structure 12

2.4.1 Overview 12

2.4.2 Case Sensitivity 12

2.4.3 Top Level 12

2.4.4 Messages 12

2.4.5 Message Sets and Version Control 13

2.4.6 Transactions 15

2.5 The Signon Message Set 16

2.5.1 Signon 16

2.5.2 USERPASS Change

19

2.5.3 Signon Message Set Profile Information 19



2.5.4 Examples 19

2.6 External Data Support 19

2.7 Extensions to Open Financial Exchange 19

3. Common Aggregates, Elements, and Data Types 20

3.1 Common Aggregates 20

3.1.1 Identification of Financial Institutions and Accounts 20

3.1.2 Format of User-Supplied Numbers 20

3.1.3 Balance Records 20

3.1.4 Error Reporting 21

3.2 Common Elements 22

3.2.1 Financial Institution Transaction ID 22

3.2.2 Server-Assigned ID 22

3.2.3 Client-Assigned Transaction UID 22

3.2.4 Token 22

3.2.5 Transaction Amount 23

3.2.6 Memo 23

3.2.7 Date Start and Date End 23

3.2.8 Common Data Types 24

3.2.9 Amounts, Prices, and Quantities 25

3.2.10 Language 26

3.2.11 Other Basic Data Types 26



4. Open Financial Exchange Security 27

5. International Support 28

6. Data Synchronization 29

7. FI Profile 30

8. Activation & Account Information 31

9. Customer to FI Communication 32

10. Recurring Transactions 33

11. Banking 34

11.1 Consumer and Business Banking 34

11.2 Credit Card Data 34

11.3 Common Banking Aggregates 34

11.3.1 Banking Account 34

11.3.2 Credit Card Account 35

11.3.3 Bank Account Information 35

11.3.4 Credit Card Account Information 35

11.3.5 Transfer Information 35

11.3.6 Transfer Processing Status 35

11.4 Downloading Transactions and Balances 36

11.4.1 Bank Statement Download 36

11.4.2 Credit Card Statement Download 38

11.5 Statement Closing Information 42

11.6 Stop Check 42

11.7 Intrabank Funds Transfer 43

11.8 Interbank Funds Transfer 43

11.9 Wire Funds Transfer 43

11.10 Recurring Funds Transfer 43

11.11 E-Mail and Customer Notification 43

11.12 Data Synchronization for Banking 43

11.13 Message Sets and Profile 43

11.13.1 Message Sets and Messages 44

11.13.2 Bank Message Set Profile 45

11.13.3 Credit Card Message Set Profile 45

11.13.4 Interbank Funds Transfer Message Set Profile 45

11.13.5 Wire Transfer Message Set Profile 45

11.14 Examples 45

11.14.1 Statement Download 45

12. Payments 47

13. Investments 48

13.1 Types of Response Information 48



A. Status Codes 49

B. Change History 50

B.1 OFX 1.0 to 1.0.1 50

B.1.1 Specification Changes by Chapter 50

B.1.2 General Specification Changes 57

B.1.3 DTD Changes 57

B.2 OFX 1.0.1 to 1.0.2 59

B.2.1 Specification Changes by Chapter 59

B.2.2 General Specification Changes 61

B.2.3 DTD Changes 61

C. Errors and Omissions 63




  1   2   3   4   5   6   7   8   9   ...   13


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət