Docstoc

Quickbooks Extensions

Document Sample
Quickbooks Extensions Powered By Docstoc
					Intuit ®

Payment Processing Options: Good Funds

Version 1.1




              Revision Date: September 13 2006

              Quicken for Windows, Quicken for Mac, Quickbooks for Windows
Table of Contents


1.    OVERVIEW ................................................................................................................................ 3

2.    PAYMENT PROCESSING OPTIONS ...................................................................................... 4

3.    USABILITY RESULTS ............................................................................................................... 7

4.    USER EXPERIENCE ............................................................................................................... 10

5.    IMPLEMENTATION ...............................................................................................................23

6.    Q & A ..........................................................................................................................................24

7.    SAMPLE BANK LETTERS TO CUSTOMERS .......................................................................25

8.    SUMMARY OF PAYMENT PROCESSING OPTIONS ..........................................................28

9.    INTUIT PRIVATE EXTENSIONS TO OFX SPECIFICATION: PROFILE CHANGES.....30




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                                                                      PAGE 2
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
1. OVERVIEW

This document details the options that financial institutions (FI’s) have for supporting payment
processing in Quicken for Windows, Quicken for Macintosh, and QuickBooks. Please note that
this document is confidential and should not be shared with any external parties.

Both Quicken and QuickBooks support two general options for payment processing: The Delivery
Date model and the Good Funds model. Financial institutions and their processors have the
option to choose the Delivery Date model or Good Funds model for online payment processing.

The Delivery Date model is the current payment model supported in all versions of Quicken and
QuickBooks. With the Delivery Date model, the delivery date is both the date that a payment will
be delivered to a payee, and the earliest date that funds may be withdrawn from a customer’s
account. The Delivery Date is the payment model preferred by customers.

With Good Funds, the delivery date (if available) is the date that payments will be delivered to a
payee, while the processing date is the earliest date that funds may be withdrawn from a
customer’s account. The three Good Funds models supported in Quicken and QuickBooks are
described in this document.

We have worked extensively with customers to present Good Funds in a manner most
understandable to them, but it is important to note that while customers understood how payment
processing occurs as a result of Good Funds, they expressed two main concerns with Good
Funds:

   The absence of a delivery date in the Procdate1 model.

   The concept of funds being withdrawn from their account prior to the delivery date.

As each option is discussed in this document, we will share the customer feedback we received
in testing the Good Funds payment models with our Quicken customer base.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                      PAGE 3
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
2. PAYMENT PROCESSING OPTIONS

Regardless of which processing model an FI chooses, Quicken, and QuickBooks OFX online
payment will display an appropriate screen to accommodate the FI’s online payment choice. The
appropriate fields and dialog boxes will be enabled depending on the payment processing option
and platform selected. This is important to ensure that customers that use online banking with
multiple FI’s are aware of the payment processing model they use with each FI. Quicken and
QuickBooks online payment screens will support the appropriate model chosen by the FI by
utilizing the FI profile information hosted by the FI or their processor (see: Intuit Private
Extensions to OFX Specification: Profile Changes).

DELIVERY DATE

Financial Institutions may wish to continue to process payments using the Delivery Date model.
Customers will enter the date they want the payment delivered in the delivery date field, just as
they do today. Customers may notice additional fields in Quicken, Online Banking Center that
accommodate Good Funds models; however, those additional fields will be disabled for Delivery
Date customers.

GOOD FUNDS

For FI’s that choose to implement Good Funds, each of the processing options is described
below. Screen shots may vary depending on the product version and how the user schedules
online payments.

For each model we have described the processing scenario and identified key Usability findings
from customers. In general, our Usability testing showed that customers strongly preferred the
Delivery Date model to Good Funds.

With Good Funds, customers may have funds withdrawn before the date the payment is delivered
to the payee. And in some cases, the customer will only be told the date when the payment will
be processed – they will not be told the date the payment will arrive at the payee. The most
frequent customer reactions are described below:

   Customers disliked switching from Delivery Date to Good Funds. They said the most
    important element in scheduling a payment was the delivery date, and knowing that the
    payment would arrive at the payee by that date.

   Customers did not like the fact that funds would come out of their account before the
    payment arrived at the payee. They felt that their bank was gaining float on the money.

Procdate1




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                      PAGE 4
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
In the Procdate1 model, customers schedule payments based on the processing date: the date
funds are withdrawn from their account and payment processing begins. In this model, the
processor does not provide payment leadtimes nor does the processor accept the delivery date;
therefore, customers must submit payments using the processing date. Since payment leadtime
is not available to customers, they have no way of knowing when payments will be delivered to
their payees.

If the FI’s profile indicates support for the Procdate1 model, this alerts the product to display a
processing date field, and disable the delivery date field. The customer enters a date in the
processing date field for each payment. This date will be sent to the processor to use to process
the payment (i.e. initiate an ACH payment or send a draft). When the customer sets up a
payment and enters the processing date, a pop-up message will appear and indicate that this is
the earliest possible date that funds may be withdrawn from their account and payment
processing will begin.

Customers expressed the following comments with this model of Good Funds processing:

   Customers said that it’s very important to them for Quicken to tell them when payment will be
    delivered to the payee and that this model did not provide that information.

   Customers did not like the fact that funds would come out of their account before the
    payment arrived at the payee. They felt that Quicken or their bank was gaining float on the
    money.

   Customers did not like having to figure out when to set up the payment in order to get it to the
    payee by their payment due date.

   Customers like using processing leadtime to determine when to schedule payments. They
    don’t want to have to determine when to process the payment in order to get it to the payee
    by the payment due date.

Procdate2

For FI’s choosing this option, the product displays both the processing and delivery date fields.
The customer enters the delivery date that is then sent to the processor. The product calculates
the processing date based on a value provided by the payment processor indicating how long it
takes to process payments for this payee. This calculated processing date is displayed to the
customer in a pop-up message. The message indicates that the processing date is the earliest
date that funds may be withdrawn from the account and the date payment processing will begin.
Since the processor provides leadtimes, the product is able to display this information to the
customer.

Customer feedback on this option follows:

   If the customer had to move to Good Funds, they strongly preferred the Procdate2 or
    Procdate3 model. This is because they were able to see a delivery date (when their payment
    would arrive at the payee) and a processing date (when funds would be withdrawn from their
    account).

Procdate3



PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                      PAGE 5
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
This model mirrors the Procdate2 model in all respects except that the product sends the
processing date, not the delivery date to the FI or the processor. For FI’s choosing this option, the
product displays both processing and delivery date fields. The customer enters the delivery date
and the product uses this date in conjunction with the server-provided leadtime to calculate the
processing date. The processing date is sent to the processor. Both the delivery and the
processing date are displayed to the customer. A pop-up message appears, indicating that the
processing date is the earliest date that funds may be withdrawn from the account and the date
payment processing will begin. Since the processor provides leadtimes, the product is able to
display this information to the customer.

Below is a matrix of payment options enabled by product and version:



                      Product /        ALL        2004       2005        2006
                      Version

                                     Delivery             Good Funds
                                      Date

                   Quicken for             X        X          X           X
                   Windows

                   Quicken for             X        X          X           X
                   Macintosh




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                       PAGE 6
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
3. USABILITY RESULTS

In order to ensure that the OFX implementation of Good Funds provides customers with the
information necessary to properly execute online payments, usability tests were conducted over a
period of several weeks to test the various Good Funds processing models. The areas that were
tested include:

   Customer understanding of the changes in payment processing following their FI’s switch to
    Good Funds.

   Customer understanding of actions to take following the switch to Good Funds to enable
    payments to be processed as intended.

   Customer understanding of the differences between the current Delivery Date model and
    processing under Good Funds.

   Customer reaction to the various models and their preferences.



On a more detailed level, testing was done to find:

   Customer reaction to using either the delivery date or the processing date field to enter
    payments dependent on which Good Funds processing model their FI had selected.

   Customer reaction to the Good Funds notification dialog to ensure they understood:
        1.   The change in payment processing.
        2.   The steps they need to take to enable their payments to be processed as they
             requested.
        3.   The change in the date on which funds are withdrawn.

   Customer reaction to the implementation of Good Funds:
        1.   Display of both the delivery date field and processing date fields with one of these
             fields potentially disabled.
        2.   Display of pop-up dialogs during bill payment transaction entry.
        3.   Understanding of processing date signifying the date funds will be withdrawn.
        4.   Understanding of how to obtain assistance with Good Funds via online help and/or
             phone calls to the FI.

KEY USABILITY FINDINGS




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                        PAGE 7
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
Customers were uncomfortable with the fact that the FI was changing to payment models where
they were not always given a delivery date (Procdate1), and where funds were deducted from
their account before the payment was received by the payee. However, customers did
understand the changes that were made to support the new methods of payment processing.
They understood how to use the new models to enable payments to be processed according to
their instructions.



Key findings relative to customers understanding of the changes follow:

   Customers’ preference was to stay with the current Delivery Date model rather than moving
    to the new models associated with Good Funds.

   Customers were introduced to the new processing model either by reading the sample FI
    letter (see: Sample Bank Letters to Customers) and then seeing the appropriate notification
    dialog; or, by seeing only the notification dialog. The most typical reactions to these changes
    are listed below:
        1.   Customers strongly disliked switching from Delivery Date to Good Funds. They
             emphasized that the most important thing was the delivery date and the knowledge
             that payment would arrive by that date.
        2.   Customers did not like the fact that funds would come out of their account before the
             delivery date. They felt that Intuit or their bank was gaining the float on the money.
             They also were uncertain when they would need to have funds available in their
             account. With the Delivery Date model, they knew when they would need to fund
             their account. This issue is of particular concern with future scheduled payments,
             where customers must remember to fund the account before the date shown in the
             register.
        3.   Customers understood that today, the product prevents a user from scheduling
             payments which cannot get to the payee by the date requested. This was very
             important to customers in managing the scheduling of payments, and they were
             concerned with losing this functionality.

   Of the three options for Good Funds, the customers strongly preferred the Procdate2 or
    Procdate3 models. Customers were more comfortable with the Procdate2 or Procdate3
    models than with the Procdate1 model in that they were able to see both a delivery date
    (when payment would arrive at the payee) and a processing date (when funds would be
    withdrawn from their account).

   The notification dialogs helped customers understand the changes occurring in payment
    processing and the steps they needed to take as a result of this change.

   The implementation of both the processing date and delivery date on payment screens was
    understood by customers:
        1.   In general, customers gained understanding of how these dates related to each
             other. The notification dialog in conjunction with the information in the pop-up
             messages facilitated this learning.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                        PAGE 8
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
        2.   Customers understood which date field applied to them given the payment
             processing option their FI was utilizing.
        3.   Customers were able to learn and work around the fact that one payment field
             (processing or delivery date) was disabled, depending on the model.
        4.   In general, most customers knew where to go for help, whether through calling their
             FI or looking up the new payment model in online help.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                    PAGE 9
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
4. USER EXPERIENCE

SWITCH TO GOOD FUNDS

The FI’s move to Good Funds is made in the FI Profile. When the user starts an online banking
session and the product detects the change in the FI Profile, the switch to Good Funds begins.
Before the session continues, a Good Funds notification will be displayed to the customer. This
notification will differ depending on the processing option selected.

4 A. QUICKEN FOR WINDOWS: USER EXPERIENCE

Good Funds Notification: Procdate1

For the Procdate1 model, the user will see the message displayed below. The user will be
prompted to review all scheduled payments. With the assistance of the More Info button, the user
will be able to see the steps that must be taken to ensure that payments are made on time.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                  PAGE 10
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
Good Funds Notification: Procdate2 or Procdate3

For the Procdate2 or Procdate3, the screen below will appear. The user has the option to
continue the session or to cancel out of the session to review pending payments.




Alerts

On the default Quicken Home page at the startup of Quicken, there is an Alerts section where the
user will see:

“{Financial Institution name} has changed its method of processing online payments.”

The user can click on this reminder to display the dialog with the notification that they previously
received. This reminder line will appear in the Cash Flow Alerts section until the user turns it off
by checking the box: “Don’t show this message again” or delete this alert.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                      PAGE 11
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
CREATING PAYMENTS

After the Good Funds switch, when the user schedules payments, pop-up messages will appear
to ensure the customer understands the meaning of the date entered. Following are the pop-up
messages that will appear for each Good Funds processing model. In some cases, the dialog will
differ depending on whether the customer enters online payments from the Online Center,
Register, Write Checks screen, Financial Calendar payment screen, Pay Bills screen, or the
Scheduled and Repeating Payments screen. In some cases, the customer will have the option to
turn off this dialog so it is not displayed on an ongoing basis.

Note to Financial Institutions:

Once a payment is debited from the account, if the transaction is later reversed, the financial
institution should credit to the account and explain the credit either in the transaction memo or in
an email. The Financial institution should not update the payment status using a payment
modification.




Online Center Payments Tab: Procdate1

In this scenario, the user sees both processing date field and delivery date field on the entry
screen. The delivery date field however, is disabled, and only the processing date field is active.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                      PAGE 12
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
Payment Dialog: Procdate1

In this model, the following dialog will appear whenever the customer sets up a payment from the
Online Center or Financial Calendar online payment screen.




For payments made from the Register or Write Checks screen, the following dialog appears:




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                 PAGE 13
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
Online Center Payments Tab: Procdate2 or Procdate3

In the Procdate2 and Procdate3 models, the user will see both the processing date field and the
delivery date field on the entry screen. Both fields are active. However, only the delivery date field
is allowed for entry. The processing date field will be filled by a date calculated by Quicken (using
the lead-time provided by the processor) when the delivery date is entered.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                       PAGE 14
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
Payment Dialog: Procdate2 or Procdate3

In the Procdate2 or Procdate3 models, the dialog varies depending on where the customer sets
up their online payment. For payments made from the Online Center or Financial Calendar online
payment screen, the following dialog appears:




For payments made from the Register or Write Checks screen, the following dialog appears:




In the Procdate2 and Procdate3 models, the customer enters the delivery date when creating an
online payment instruction. In the Register, Write Checks screen, Financial Calendar online
payment screen, Bills screen, and the Scheduled Transaction List screen only one date is
displayed. Prior to sending the payment, these screens display the delivery date. Once the user
sends the payment instructions, these screens are updated with the processing date.

The Online Center displays both the processing date and the delivery date at all times.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                  PAGE 15
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
When a customer creates a scheduled online payment under Procdate2 or Procdate3, Quicken
automatically generates payment instructions, but these instructions, like one-time payments,
must be sent to the processor. Like one-time payments, the delivery date is displayed in Quicken
before the payment is sent. Once the payment is sent, all dates in Quicken will be updated to
reflect the processing date.

When a customer creates a repeating online payment model under Procdate2 or Procdate3, the
user enters the delivery date when first creating the model. The delivery date will continue to be
used when displaying the Next Date. Once the model has been sent to the processor, the
processor will return individual payments that are added to the Register. Any payments added to
the register will reflect the processing date. This implementation ensures that the customer knows
when payments are scheduled to be delivered to their payees (in the Repeating Online Payments
screen) and when funds will be withdrawn from the account (in the Register).

ONLINE PAYEE LIST

The Online Payee list will display lead times if available. Leadtimes are not available with the
Procdate1 model.

Online Payee List: Procdate1




Online Payee List: Procdate2 or Procdate3




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                      PAGE 16
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
ONE STEP UPDATE, INSTRUCTIONS TO SEND, AND TRANSMISSION SUMMARY

After users select the One Step Update button from any screen or the Update/Send button from
the Online Center, they are shown a list of instructions that will be sent when they go online. This
allows users the opportunity to review the instructions before sending them.

Instructions To Send: Procdate1




Instructions To Send: Procdate2 or Procdate3




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                     PAGE 17
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
        Once the payment instructions have been successfully sent to the processor, Quicken
        displays the Transmission Summary and indicates that the register has been updated to
        reflect the processing date.

4 B. QUICKEN FOR MACINTOSH: USER EXPERIENCE

The first time the user goes online to their bank they will receive the following dialog:

In the Statement Download session, the message is displayed at the end of the session to
inform the user of the changes in the payment model.




The user simply clicks OK to dismiss the dialog and it will not reappear in subsequent sessions.



PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                    PAGE 18
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
In a Payment session, each time the user issues a payment from a ProcDate2 account, the user
will get an alert prior to entering the PIN which informs them of the processing date and delivery
date of this payment.




The user has the opportunity to cancel the payment and contact the bank if they have any
questions regarding the change in the payment model.

4 C. QUICKBOOKS: USER EXPERIENCE

The customer can setup payments for all processing models from the Pay Bills Screen or Write
Checks Screens. Following are the pop-up messages that will appear for each processing model.
In some cases, the dialog will differ depending on the payment model. The customer will have the
option to turn off this dialog so it is not displayed on an ongoing basis.




Pay Bill Screen




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                   PAGE 19
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
Write Checks Screen




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS   PAGE 20
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
In the Delivery Date Model, to ensure the customer is aware of the date entered, the following
warning message will appear if the payment date is earlier than the next possible delivery date.




In the ProcDate1 model, the customer will be notified of the date the funds are withdrawn from
the account.




In the ProcDate 2, and ProcDate 3 models, the customer will get a warning if the payment date
is scheduled earlier, and will be notified of the date the payment will be delivered.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                   PAGE 21
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
The customer has to click OK and the following pop-up screen will show up.




The customer has to send the payments from the Online Banking Center for processing. The
customer is able to see the change in payment processing in the Items Received from Financial
Institution.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                PAGE 22
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
5. IMPLEMENTATION

Quicken, and QuickBooks OFX will accommodate FI requirements for Delivery Date model or
Good Funds support. The support for Good Funds will be implemented on an FI by FI basis, and
Quicken, and QuickBooks OFX will display the new user interface according to the FI’s profile.
FI’s have the flexibility to decide which payment method they want to implement.

In order to implement Good Funds, FI’s need to do the following:

   Notify Intuit of your desire to support Good Funds. Please note if your institution is
    implementing Good Funds in conjunction with the launch of your OFX server (rather than
    after the launch of your OFX server) additional changes will need to be made to your
    information on Intuit’s branding server. Therefore, it is important that you alert QuickInfo of
    these changes.

   Notify your OFX service processor of your decision so that your processor can make the
    appropriate changes to your Profile (see: Intuit Private Extensions to OFX Specification:
    Profile Changes).

   Notify your customers of your change in payment processing methods prior to switch to Good
    Funds. The user interface in Quicken and QuickBooks presume that you have already
    notified your customers of your change in payment processing methods.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                       PAGE 23
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
6. Q & A

Are all FI’s required to move to Good Funds?
 No, each FI has the option to remain on the customer preferred Delivery Date model of
    payment processing.



When can my FI switch to Good Funds?
 Intuit will support Good Funds in Quicken and QuickBooks. FI’s will need to work with their
    OFX server provider to determine implementation timeframes.



When does my FI have to make this choice?
 Please inquire with your OFX server provider.


What changes does my FI need to make to the branding and profile server?
 Your FI’s profile information will need to be changed in order to move to Good Funds. Please
    refer to Intuit Private Extensions to OFX Specification: Profile Changes. Branding server
    changes are only required if you are simultaneously implementing an OFX server; please
    notify Intuit if this applies to you so that these changes can be made.



If my FI is not moving to OFX, can we still move to Good Funds?
 No, you must implement OFX in order to implement Good Funds.


When should communication go out to customers in relation to the time we move to Good
Funds?
 We recommend that you give your customers ample notice before you move to Good Funds
    since the Quicken and QuickBooks OFX user interface presume that you have notified them
    before they see the changes within the software.



Does Intuit provide a template letter that our FI can use to notify customers of this
change?
 To assist in your move to Good Funds, sample letters are provided that you may use to
    communicate your change in payment processing models (see: Sample Bank Letters to
    Customers).




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                  PAGE 24
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
7. SAMPLE BANK LETTERS TO CUSTOMERS

Sample letters are created for Quicken customer base. Reference to repeating payments
should be excluded for the QuickBooks customer base.
 Note: All customer communications regarding online banking services need to be reviewed
    by Intuit.


{date}



{customer}

{address 1}

{address 2}

{city}, {state} {postal code}



Dear {name}:

{Financial Institution} is changing its payment processing for Quicken online payment customers.

Beginning {start date}, the date you enter will no longer be the delivery date, the date the
payment arrives at the payee. Instead, you will enter the date on which you want funds withdrawn
from your account and {bank} to begin processing your payment.

{Financial Institution} will start processing online payment transactions using the new method
beginning {start date}.

The dates on your previously scheduled and repeating payments may need to be changed to
ensure that funds are available and that there is sufficient time for payments to arrive at your
payees. To check those transactions, choose Scheduled Transaction List from the Banking menu
in Quicken. Each scheduled and repeating transaction is listed, along with the date of the next
occurrence.

For more help, visit our web site at {URL} or phone us at {phone number}.

Because you are a valued online banking customer, we want to make sure this transition is as
convenient for you as possible, and give you plenty of assistance to make the transition.



Warm regards,




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                    PAGE 25
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
{Financial Institution representative}

{position}




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS   PAGE 26
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
Sample Bank Letter to Customer – Procdate2 or Procdate3

{date}



{customer}

{address 1}

{address 2}

{city}, {state} {postal code}



Dear {name}:



{Financial Institution} is changing its payment processing for Quicken online payment customers.

Beginning {start date}, when you enter the date on which you would like a payment delivered,
Quicken calculates a processing date for you. The processing date is the earliest date that funds
may be withdrawn from your account and {Financial Institution} begins processing your payment.

The dates on your previously scheduled and repeating payments may need to be changed to
ensure that funds are available and that there is sufficient time for payments to arrive at your
payees. To check those transactions, choose Scheduled Transaction List from the Banking menu
in Quicken. Each transaction is listed, along with the date of the next occurrence.

For more help, visit our web site at {URL} or phone us at {phone number}.

Because you are a valued online banking customer, we want to make sure this transition is as
convenient for you as possible, and give you plenty of assistance to make the transition.



Warm regards,




{Financial Institution representative}

{position}




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                   PAGE 27
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
8. SUMMARY OF PAYMENT PROCESSING OPTIONS


                          Delivery Date     Good Funds –       Good Funds –         Good Funds –
                                            Procdate1          Procdate2            Procdate3

Quicken Date Field        Delivery Date     Processing         Both Processing      Both Processing
Displayed in Online       only -            Date only -        Date and             Date and
Center                    Processing date   Delivery date is   Delivery Date        Delivery Date
                          is grayed out     grayed out
QuickBooks Date           Delivery Date     Processing         Both Processing      Both Processing
Field Displayed in        only –            Date only -        Date and             Date and
Online Center             No Processing     Delivery date is   Delivery Date        Delivery Date
                          date field        not available
Date Field Entered by     Delivery Date     Processing         Delivery Date -      Delivery Date –
Customer                                    Date               Processing Date      Processing Date
                                                               is calculated        is calculated
Pop-up Message            No                Yes                Yes                  Yes

Message in                Pay amount by     Processing pmt     Processing pmt       Processing pmt
Instructions to Send      [delivery date]   on [processing     on [processing       on [processing
window                                      date]              date] for delivery   date] for delivery
                                                               on [delivery         on [delivery date]
                                                               date]
Date sent to              Delivery Date     Processing         Delivery Date        Processing Date
Processor: Client                           Date
<DTDUE>
Date received from        Delivery Date     Processing         Delivery Date        Processing Date
Processor: Server                           Date
<DTDUE>
Date received from        N/A               N/A                Processing Date      N/A
Processor: Server
<DTPMTPRC>
Message in                “Due Date”        “Process On”       “Due Date”           “Due Date”
Transmission              (server           only (server       (server              (server
summary                   <DTDUE>) and      <DTDUE>)           <DTDUE>) and         <DTDUE> + lead
                          “Process On”      [no lead time      “Process On”         time including
                          (server           information, so    (server              PROCDAYSOFF
                          <DTPMTPRC>)       no “Due Date”]     <DTPMTPRC>)          as calculated by
                                                                                    Quicken OFX)
                                                                                    and “Process On”
                                                                                    (server
                                                                                    <DTDUE>)
Date in Online Center     Delivery Date     Processing         Both Processing      Both Processing
status                    only              Date only          Date and             Date and
                                                               Delivery Date        Delivery Date




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                    PAGE 28
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
Date in Register          Delivery Date:    Processing     Delivery Date:   Delivery Date:
before Payment Sent       user-entered      Date: user-    user-entered     user-entered
                                            entered
Date in Register after    Delivery Date:    Processing     Processing       Processing Date:
Payment Sent              user-entered,     Date: Server   Date: Server     Server <DTDUE>
                          independent of    <DTDUE>        <DTPMTPRC>
                          server response




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                            PAGE 29
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
9. INTUIT PRIVATE EXTENSIONS TO OFX SPECIFICATION: PROFILE CHANGES

For each option under Good Funds, there will be private tags added to the Bill Payment Message
Set Profile <BILLPAYMSGSET> and the <EXTDPAYEE> aggregate.

OFX SECTION 12.11.2 – ADDED TAGS IN <BILLPAYMSGSET>

The <INTU.DATEMODEL > tag specifies the processing model chosen.

<INTU.DFLTDAYSWITH> indicates the default number of days prior to delivery date that funds
are withdrawn from user’s account (the lead-time). For new payees, this is the default value until
it is overridden by a <INTU.DAYSWITH> value in the <EXTDPAYEE> aggregate.

Procdate1

The <INTU.DATEMODEL> value should be PROCDATE1. This will enable the correct user
interface, with the processing date field enabled and delivery date field disabled, as well as the
appropriate dialog messages within the product to alert the user of the specific processing
change.

The <INTU.DFLTDAYSWITH> value will not be applicable, since delivery date will not be
provided by the FI. Therefore, this tag should be omitted for this model.

Procdate2

The <INTU.DATEMODEL> value should be PROCDATE2. This will enable the correct user
interface, with both the processing date field and delivery date field enabled, as well as the
appropriate dialog messages within the product to alert the user of the specific processing
change.

The <INTU.DFLTDAYSWITH> value, 0-N, will be specified by the processor.

Procdate3

The <INTU.DATEMODEL> value should be PROCDATE3. This will enable the correct user
interface, with both the processing date field and delivery date field enabled, as well as the
appropriate dialog messages within the product to alert the user of the specific processing
change.

The <INTU.DFLTDAYSWITH> value, 0-N, will be specified by the processor.




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                      PAGE 30
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
BILL PAY MESSAGE SET PROFILE <BILLPAYMSGSET>

For the complete bill pay message set profile, see OFX Specification 1.0.2, section 12.11.2 (
signifies new Intuit private tags.)


 Tag                                       Description
 <BILLPAYMSGSET>
        <BILLPAYMSGSETV1>
               …                           MSGSETCORE and other BILLPAYMSGSET tags
  <INTU.DATEMODEL>                        This tag is added to support Good Funds
                                           implementation in Quicken and QuickBooks OFX. This
                                           tag specifies the processing model chosen.

                                           The allowable values are:
                                            DELDATE (Delivery Date model)
                                            PROCDATE1(Processing date sent in DTDUE)
                                            PROCDATE2 (Delivery date sent in DTDUE)
                                            PROCDATE3 (Processing date sent in DTDUE)
    <INTU.DFLTDAYSWITH>                   This tag is added to support Good Funds
                                           implementation in Quicken and QuickBooks OFX. For
                                           new payees, this is defined as the number of days
                                           before delivery date that funds are withdrawn. Quicken
                                           and QuickBooks OFX will use this default unless payee
                                           specific days with is specified in <INTU.DAYSWITH>
                                           in extended payee aggregate.
                                            If Delivery Date, this tag will be omitted.
                                            If Procdate1, this tag will be omitted.
                                            If Procdate2 or Procdate3, this value will be 0-N
                                               where N is specified by the processor.
        </BILLPAYMSGSETV1>
 </BILLPAYMSGSET>




OFX SECTION 12.5.2.6 – ADDED TAGS TO <EXTDPAYEE>

The Extended Payee aggregate communicates a payee identifier to the client. It also contains the
processing day parameters for a payee. It can be sent to the client for any payee whose
processing day parameters are different from the processor’s default values, even for payees with
no IDs.

<INTU.DAYSWITH>tag is added to <EXTDPAYEE> aggregate to support Good Funds
implementation. <INTU.DAYSWITH> is defined as the number of days prior to delivery date that
funds are withdrawn (the lead-time).


PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                   PAGE 31
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1
If present, the <INTU.DAYSWITH> value overrides the <INTU.DFLTDAYSWITH> value.

Procdate1

The <INTU.DAYSWITH> value does not apply. If this tag is present, it will be ignored.




Procdate2 and Procdate3

The <INTU.DAYSWITH> value, from 0-N, is specified by the processor.
Complete Extended Payee <EXTDPAYEE>
 Tag                             Description
 <EXTDPAYEE>                     Extended-payee aggregate
               …                 PAYEEID and other EXTDPAYEE tags
  <INTU.DAYSWITH>               This tag is added to support Good Funds
                                 implementation in Quicken and QuickBooks OFX. It is
                                 defined as the number of days prior to delivery date
                                 that funds are withdrawn, -
                                  If Delivery Date, this value does not apply and will
                                      be ignored if present.
                                  If Procdate1, this value does not apply and will be
                                      ignored if present.
                                  If Procdate2 or Procdate3, this value must be
                                      specified for any payee whose
                                      <INTU.DAYSWITH> differs from the
                                      <INTU.DFLTDAYSWITH>.
 </EXTDPAYEE>
In summary, the <INTU.DAYSWITH> and <DAYSTOPAY> values vary with each Good Funds
option:
 Model                 <INTU.DAYSWITH>             <DAYSTOPAY> (Leadtime)
 Delivery date         Does not apply:             0-N where N is specified by the
                       Withdrawal date = delivery  processor
                       date
 Good Funds –          Does not apply              Does not apply
 Procdate1
 Good Funds –          0-N where N is specified by Does not apply
 Procdate2 or          the processor
 Procdate3




PAYMENT PROCESSESING OPTIONS: GOOD FUNDS                                                PAGE 32
LAST UPDATED: 7/7/2010 PN: PPO_GF_1.1

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:26
posted:7/8/2010
language:English
pages:32
Description: Quickbooks Extensions document sample