Import Matrix: Credit Card Transactions (Credit Card Connector)
Technical Documentation
This help file is for importing of CSV files. The preferred format for importing of Credit Card Transactions is OFX. The OFX format is a standardized banking format designed for sharing banking transactions uniformly. An OFX file downloaded from the financial institution and uploaded to Workamajig should import cleanly with no other user interaction required. This is also the format used by the automated connector process. Manually editing OFX files is not recommended or supported by Workamajig.
If your financial institution does not support OFX, you may import Credit Card Transactions in a CSV file which is editable in most spreadsheet applications such as Excel. In this case, an import process similar to other Workamajig import modules is used. Please read this document carefully to ensure data is imported correctly.
When importing any file into Workamajig, the three fields below must be set. The Select a file to Import will contain the .csv file you will be importing; the Browse button allows you to search for the .csv file to import. The Field Delimiter is used to tell the system how the data in the file is separated; typically this will be a Comma; however the valid values are: Comma, Asterisk and Tab. The First Row Contains Field Names checkbox tells the system the first row of data in the file contains the field names, which will be used to match to the actual Workamajig field names, if no match is found during the Upload, the field name will default to “Ignore This Field” and allow you to select from the valid Workamajig field names for the data being imported.
For more on the importing workflow and other possible solutions to finding an OFX file from your bank please review the Importing Credit Card Transactions guide.
Available Fields
Amount
Charged By
Date
Expense Account Number
FITID
GL Account Number
Memo
Payee Name
Transaction Type
Matrix
|
Field Name |
Key Field |
Required |
Valid Values |
Table Validation |
Table |
Field Validation |
Comments |
|
GL Account Number |
|
Yes |
|
Yes |
GL Accounts |
Account Number |
This is the Account of the Credit Card transactions are being imported for |
|
Date |
|
Yes |
Must be a valid date |
|
|
|
This is the transaction date |
|
Date Posted |
|
No - See Comments |
Must be a valid date |
|
|
|
If not included, will be set to the current date |
|
FITID |
|
Yes – See Comments |
Must be a unique value for this Credit Card Account |
Yes |
CC Entry |
FITID |
If not supplied, the field may be left off of the CSV file altogether and Workamajig will give each transaction a unique value for you. *See the explanation of FITID at the bottom of this page. |
|
Amount |
|
Yes |
Numeric |
|
|
|
NOTE: The amounts are reversed on import. The .csv file should have positive Debits and Fees and negative Payments and Credits. |
|
Memo |
|
|
|
|
|
|
|
|
Payee Name |
|
Yes |
|
|
|
|
|
|
Transaction Type |
|
Yes |
Debit, Credit, Payment, FI Fee |
|
|
|
|
* FITID is the Financial Institution Transaction ID and is supplied by the bank. It is required in order to differentiate multiple transactions; it is possible for all other values to be duplicated. The Credit Card Connector process rejects values that have been previously downloaded from the bank. If your banking institution does not supply this information, you may leave it off of the CSV file altogether. Workamajig will create a unique value for each transaction imported. If the FITID field is in the CSV file and the value is left blank, the import process will issue an error stating FITID is required. If the FITID value matches a value already in Workamajig, the import process will issue an error as updates are not supported.
In the event an unprocessed transaction needs to be re-imported, it may cleared from the Credit Card Connector screen by selecting that row and clicking the Mark as Processed action button. This will allow that transaction to be re-imported. Note: the original transaction will be over-written.