| Statements |
| |
This
page displays your current account statement
and transactions. You can also select a previous
statement closing date from the drop-down menu
to display summary and transaction information
for that statement cycle.
Transactions can be sorted by transaction
date ( Normal View )
or by Quicken® expense categories ( Expense
View ).
To facilitate your record keeping, a plain
copy of a statement and its transactions
can be displayed for printing by clicking
on the Format to Print link.
To download transactions to your computer,
select a file format from the Download Transactions
drop down menu. See Downloading FAQs below for more details. |
| Displaying
Transaction Details |
| |
Click
on the description of any transaction to view
detailed transaction information. You can change
the Expense Category (and always revert back
to the original category), or enter a personal
memo (up to 50 characters) to be kept with
the transaction.
Tip: You could
enter the word "deductible" in the Transaction
Memo for every transaction that is tax deductible,
and then - at tax time - use the Find Transactions
feature to display your deductible transactions. |
| Disputing
a Transaction |
| |
You
can dispute a transaction by clicking on the
link to display a transaction dispute form.
Print the form using your browser's print process,
then fill in the requested information. Sign
the form and mail it to Customer Service at
the address shown. Please note that notification
of a disputed transaction must be received
within 60 days of the closing date of the statement.
Note: Your signature
on a hard copy of the form is required before
we can process this dispute. |
| Downloading
FAQs |
| |
Q: What
format should I use? |
| |
A: Select
a .QIF format for Quicken 98 or earlier, or Quicken/Money,
depending on which software application you wish
to use. QIF is a flexible format for exchanging
transaction information, complete with merchant
addresses, memos, and category information. Downloading
.QIF files will not launch your Quicken application.
Save the file (using the .QIF extension), and
then open it later using your application.
Use the .CSV (comma-separated text) or the
.DAT (tab-separated text) to download your
transactions for use with Excel or other
spreadsheet and database programs. |
| |
Q:
What fields are contained in the downloaded
file? |
| |
A: The
download file contains the following data elements:
  |
Transaction
Posted Date |
  |
Merchant
Description |
  |
Merchant
Category Code |
  |
Transaction
Date |
  |
Merchant
City |
  |
Merchant
State |
  |
Amount
of Transaction |
  |
Description
of Category |
  |
Memo
on a Transaction |
|
| |
Q:
Why Does the Transaction Data Show Up On My Screen? |
| |
A: Different
browsers react differently to file downloads.
All Windows browsers rely to some extent on the
registered file types on your system to know
what to do with incoming files. Unfortunately,
they occasionally misbehave on some configurations.
Your browser may present a dialog asking you
to save the file, or it may display the information
on your screen. If it asks you to save the file,
it may suggest the correct filename, or it may
not.
Whether the data shows up on screen or not,
the idea is to save it to disk under the
correct filename. When your browser presents
a File Save dialog, use the directory list
to navigate to the directory where you store
your statement files. Then check the suggested
filename carefully. If it does not use an
appropriate filename and extension, correct
it before clicking the Save button.
If the browser displays the information
on the screen, use the "File | Save As" menu
choice, then follow the directions above. |
| |
Q:
I Just Downloaded and There Are Duplicate Transactions
in My Register! |
| |
A: If
you download the same statement twice, or download
a statement that overlaps data you have entered
into your software, then you may create duplicate
transactions in your register.
Unfortunately, the web server cannot prevent
this from happening. If this happens to you,
either discard the changes and examine the
situation carefully before re-importing the
data, or manually discard the duplicate items. |