Importing credit card transactions [in-depth guide]
FTDIS's | 1. OFX/QFX/QBO import | 2. CSV import | Resources
This guide will assist you in the event that you are not able to auto-download credit card transactions via the OFX connector/Plaid for the workflow designed in the Credit card connector screen.
FTDID's
A few notes about the FTDID that is part of each individual credit card transaction.
1. Each transaction is recognized with a unique ID called FTDID. Workamajig will only allow one unique transaction per FTDID per GL Account. This is to help prevent duplicate transactions from being added.
2. Sometimes the banks change the FTDID, if the charge is still in the process of being finalized on their end. Which could end up adding a duplicate transaction in Workamajig as a result, if the FTDID changes.
3. Importing the same OFX file again, or one with overlapping date range will not import duplicates.
4. If switching TO or From the Plaid connection, keep in mind that Plaid has their own set of FTDID,s (alphanumeric vs numeric). Which means you could see duplicates appear. But you can check Mark As Cleared on the duplicates to hide them in the Connector screen. Plaid only imports the last 3 months of data, so after that, you can delete those duplicates and they wont re-appear from an active Plaid connection.
Method 1 - .OFX download/import
Most banks/credit cards allow you to download an electronic statement/report of the transactions within a specified date range.
Be sure you have the Credit Card Number entered in the GL Account Setup. As this is how the OFX import ensures the transactions get added to the correct account.
When you go to export the statement of transactions, there may be an option to choose a file type. If they do offer multiple file types, then look for a file type called OFX, QFX, QBO or similar. As these are industry-standard financial files.
You can take these files and import them right into the Credit card connector screen so you can process them as if the system was able to download them automatically.
If this works, then you will want to set up a reminder to do this as a daily or weekly manual process.
Method 2 - .CSV download/import
If your bank does not offer any type of formatted OFX file, yet you can download a report of the transactional data, similar to it looking like an excel file. Where each row of data is a single credit card transaction. Then you can take this file and add a header row to resemble the importable fields allowed in Workamajig's connector screen.
- For a detailed list of the importable fields available, please refer to the Import matrix: credit card transactions (credit card connector) [guide].
NOTE: You can manually import this type of file in two places. 1. The Connector screen so you can have users review & process their own transactions which then turns them into charges, or 2. Import them directly as approved & posted credit card charges, skipping the Connector screens workflow.
With the file now ready for importing, ensure it's properly saved as a CSV formatted file (if on a Mac, save it as CSV MS-DOS).
Then import the CSV file in the Connector screen & process them using the Connector screens workflow.