This specification describes the ofc data format and details how Microsoft ® Money uses ofc for online home banking and online bill payment features

Intrabank Transfer response

Notes on

0. 
   If DTPOSTED is not returned by the server, Money will assume that the funds are immediately available to the destination account.
   
1. 
   Unless a STATUS of “0” is returned in an INTRARS, Money will assume the transfer happened and that funds are available in the destination account.
   
2. 
   Money does not allow users to inquire on a transfer. If the server returns STATUS of 0, Money assumes the transfer occurred.
   

If STATUS is 0

0. 
   If STATUS is 0, it is assumed that the transfer happened and the funds are available in the account described in ACCTTO.
   

If STATUS is 1

0. 
   If STATUS is 1, it is assumed that the transfer did not happen. No funds should move between accounts.
   
1. 
   Include CLTID element.
   

If STATUS is 100

0. 
   If STATUS is 100, it is assumed that the transfer did not happen. No funds should move between accounts. The ERROR should explain the cause of the failure.
   
1. 
   Include CLTID element.
   
2. 
   Include explanation in ERROR element.
   

If STATUS is 104

0. 
   If STATUS is 104, it is assumed that the transfer did not happen. No funds should move between accounts. A STATUS of 104 means that the account specified in the ACCTFROM aggregate in the INTRARQ was not found on the server.
   
1. 
   Include CLTID element.
   

Interbank Transfer request

This transaction will not be used in US releases of Microsoft Money.

Notes on INTERRQ:

0. 
   This record can contain an ACCTTO or PAYEEID but not both.
   
1. 
   If ACTION is 1 or 2, Money will include a SRVRTID element.
   

Interbank Transfer response

This transaction will not be used in US releases of Microsoft Money.

Online Bill Payment Records

Tags displayed in bold are required by Microsoft Money.

Payee request

Notes on

0. 
   Money will always send a complete PAYEE aggregate even if a PAYEEID is included.
   
1. 
   If the user is paying the payee for the first time, a complete PAYEE aggregate will be sent
   
2. 
   If the user enters an electronic payment to a payee for the first time (the user has not entered a payment to the payee previously) then Money will generate a PAYEERQ and a PAYMTRQ (Payment request). Both records will be sent to the server in the same session.
   
3. 
   It is possible that Money will send a PAYEERQ to the server without a PAYMTRQ. For example, if the user schedules an electronic payment in the future, Money will send a PAYEERQ to the server on the next call.
   

If ACTION is 0

0. 
   An ACTION of 0 means that the user has entered an electronic payment to a payee who does not exist in the user’s Money file.
   
1. 
   A PAYEEID will not be included.
   
2. 
   A complete PAYEE aggregate will be included.
   

If ACTION is 2

0. 
   An ACTION of 2 means that the user has changed the details of the payee in Microsoft Money.
   
1. 
   A user can not change the payee’s name. A user can change the payee’s address, city, state, zip code, phone number and their account number with the payee.
   
2. 
   A PAYEEID or complete PAYEE aggregate will be included.
   

Payee response

Notes on

0. 
   Reference the section of this document on Online Bill Payment with Microsoft Money and OFC for details on the DAYSWITH and DAYSREQD elements.
   

If STATUS is 0

0. 
   STATUS of 0 means that the payee has been added to the payment processing host system.
   
1. 
   If a PAYEEID is available for the payee, it must be present in the PAYEEID element.
   

If STATUS is 1

0. 
   STATUS of 1 means that the payee was not added to the payment processing system.
   
1. 
   The server should echo the CLTID value sent in the Payee request.
   

If STATUS is 4

0. 
   STATUS of 4 means that the PAYEERS is sent “unsolicited” to Money. This means that there wasn’t a corresponding PAYEERQ sent to the server.
   
1. 
   CLTID must be zero (0).
   
2. 
   A complete PAYEE aggregate or PAYEEID must be included.
   
3. 
   DAYSREQD and DAYSWITH must be included.
   

If STATUS is 100

0. 
   STATUS of 100 means that the that the payee was unable to be added to the payment processing system.
   
1. 
   CLTID should echo the CLTID in the PAYEERQ.
   
2. 
   An explanation of why the problem occurred should be in the ERROR element.
   

Payment request

Notes on

0. 
   In Microsoft Money, users can enter 256 character memos for each transaction.
   Note: If the bill payment processor will not print this memo on the user’s checks, it should make the customer aware of this before they sign up for online bill payment.
   
1. 
   If Money has a PAYEEID for the payee, it will be included. If not, Money will send a complete PAYEE aggregate.
   
2. 
   PAYACCT will be included in every PAYMTRQ record.
   
3. 
   Money will send the payment’s due date in DTDUE. This value will be sent regardless of the payment model used by the payment processor (withdraw funds on the due date or withdrawn funds before the due date.)
   

If ACTION is 0

0. 
   An ACTION of 0 means that the user has entered an electronic payment in Money and is sending it to the server to be processed.
   
1. 
   Money will assign a CLTID value.
   
2. 
   The ACCTFROM aggregate will describe the account the user is using to pay the bill.
   
3. 
   TRNAMT will be the amount of the check.
   
4. 
   If Money has a PAYEEID, it will send it. If not, a complete PAYEE aggregate will be sent.
   
5. 
   PAYACCT will be the user’s account number with the payee.
   
6. 
   DTDUE will be the due date of the payment.
   
7. 
   MEMO will be the memo a user entered in the Money account register.
   

If ACTION is 1

0. 
   An ACTION of 1 is a request to delete the pending payment request from the bill payment server.
   
1. 
   An ACTION of 1 means that the user has sent the payment to the bill payment server, but the bill payment has not yet been processed.
   
2. 
   Money will assign a CLTID value.
   
3. 
   The ACCTFROM aggregate will describe the account the user is using to pay the bill.
   
4. 
   TRNAMT will be the amount of the check.
   
5. 
   If Money has a PAYEEID, it will send it. If not, a complete PAYEE aggregate will be sent.
   
6. 
   PAYACCT will be the user’s account number with the payee.
   
7. 
   DTDUE is the due date of the payment.
   
8. 
   MEMO will be the memo a user entered in the Money account register.
   
9. 
   A SRVRTID will be included. It will be the SRVRTID sent back to Money in the PAYMTRS when the payment was originally sent in for processing.
   
10. 
    If the payment has already been processed, Money will not allow the user to send a PAYMTRQ with ACTION of 1 to the server.
    

Payment response

Notes on

0. 
   The SRVRTID is used when inquiring about a payment. It is displayed in the Money user interface as a “Confirmation #.” It is assumed that a user can use this number when contacting a customer service representative about the status of the payment.
   

If STATUS is 0

0. 
   A STATUS of 0 means that the payment referenced in the PAYMTRQ has been accepted by the bill payment server and will be processed by the date in DTDUE.
   
1. 
   The CLTID should echo the CLTID sent in the PAYMTRQ.
   
2. 
   A SRVRTID must be returned.
   
3. 
   If a PAYEEID was sent in the PAYMTRQ, the server should echo it back in the response.
   

If STATUS is 1

0. 
   A STATUS of 1 means that the payment referenced in the PAYMTRQ has not been accepted by the bill payment server and will not be processed by the date in DTDUE.
   
1. 
   The CLTID should echo the CLTID sent in the PAYMTRQ.
   

If STATUS is 100

0. 
   A STATUS of 100 means that the payment referenced in the PAYMTRQ has not been accepted by the bill payment server and will not be processed by the date in DTDUE.
   
1. 
   The server should include as explanation why the payment was rejected in the ERROR.
   
2. 
   The CLTID should echo the CLTID sent in the PAYMTRQ.
   

Payment inquiry request

Notes on

0. 
   Money will send the same SRVRTID that was returned in the PAYMTRS for the transaction. A SRVRTID will always be included in the PAYIQRQ.
   
1. 
   The MEMO element will contain the user’s question about the payment. A MEMO element will be generated for each line the user types in followed by a carriage return.
   
2. 
   Money will including the following MEMO elements by default: