⚠️ See Known Issues & Limitations before using this tool.
You can import CSVs on the Tiller Console to add transaction data directly into a Tiller-managed account. This could be an automated account where we’ve pulled data from your bank automatically but you just want to add more history, or it could be an account you want to track 100% manually. You can also use this workflow to add transactions if a bank connection is down. See more about how to handle duplicates when the connection comes back up.
How to import a CSV
Log in to the Tiller Console at https://my.tiller.com
Click on the Import CSV button under the Manage Accounts header
Click the “Upload” button then navigate on your computer and find the CSV file
Map the account(s) from the CSV file to your Tiller-managed account(s)
Map the columns from the CSV file to Tiller required columns
Click “Finish” to import the data
Confirm or add the Import Tag column to your spreadsheet (optional but recommended) - steps are here
Launch Tiller Money Feeds and fill your imported data
If the import is for a manually tracked account, be sure to update the balance.
Once the data is imported into the database it’s available to fill as if it came from an automated aggregation source (i.e. Yodlee or Plaid) so you will need to launch Tiller Money Feeds and click the Fill button.
How it works
The CSV Importer can detect whether your CSV file has one or more accounts’ worth of data in it. You can opt to ignore an account’s data that’s in the CSV file and not import it. It can also detect some column headers and automatically map them to the Tiller columns. It will detect a few permutations of how amount data may be organized in the CSV file and automatically map that to the Tiller Amount data. See more about the supported amount formats and what to do if yours doesn’t match.
When you finish the Import configuration (mapping accounts and columns) the data is imported into Tiller’s database for the selected accounts. Since there is no de-duplication workflow currently this means that you may end up with duplicate transactions for an account in Tiller’s database if there is an overlap of Transactions.
Review the recommended workflows below to make sure you don't end up with duplicates or learn how to clean them up if you do.
Recommended workflows
Making sure you don’t end up with duplicates
Before uploading a CSV double check the Transactions already in your spreadsheet for the account(s). Make sure you’ve filled in the latest data of the account(s) if applicable. Review the date ranges of the Transactions for each account. When exporting the CSV from your bank account be sure to set the date range to exclude transactions already available in Tiller. If you’re using the CSV Importer to fill in transactions while a bank connection is down, you’re most likely going to end up with duplicates. See our recommended steps below.
How to clean up duplicates
If you’re using the CSV Importer and find that you’ve ended up with duplicate transactions here are the steps we recommend to clean up those duplicates. These steps work off the assumption that duplicates were introduced when an automated connection was resumed and recommend that you keep the transactions from CSV Importer in your spreadsheet because they most likely are the ones you've categorized, but remove those import logs from the database since they're already in your spreadsheet.
The Import Tag column is required for this workflow.
Open your spreadsheet
Fill the latest data for the account(s)
Use the built in filter features to filter the Transactions sheet to review one account at a time where duplicates exist
Locate where the duplicates start by scrolling down to review past transactions by taking note of the date and the transaction details (description/amount)
Review the Import Tag column and make note of the tag associated with the duplicates, write this down or copy/paste it somewhere. If you don't have the Import Tag, you'll need to review the date ranges of the Transactions
Filter the dataset by the Source column to show only the transactions from the automated source (Yodlee or Plaid) that also do not have an Import Tag. If you don’t have the Source column you could use the Category column if the imported versions are categorized. You can add the Source column and it will fill going forward, but will not retroactively update for existing transactions in the sheet.
Delete the duplicate transactions that are visible after applying the filter. These are only deleting the transactions in the spreadsheet, they are not deleting the transactions in the database. Coming soon: ability to remove CSV Imports from the database to clean up duplicates in the database.
Supported Amount Formats
The CSV Importer expects the amount data to use one of the following formats:
A column with the header “Amount” where the amounts are positive and negative using $0.00 format.
A column with the header "Amount" where the amounts are absolute values (no positive or negative) and a second column with the header “Type” that contains only the values “credit” or “debit” to denote whether the transaction should be positive or negative.
Two columns to represent amounts with absolute values with the headers being either “Inflow” and “Outflow” or “Credit” and “Debit
Import Tag column
The Import Tag column is a helpful column for identifying transactions that were filled into your spreadsheet from a CSV Import. It can be useful for identifying and removing duplicate transactions.
How to add the Import Tag column
The Import Tag column is a default column only in the Foundation Template since the CSV Import feature was released so it may not be in your Transactions sheet. Follow the steps below to add it.
Insert a column to the far right of the last available column in the Transactions sheet.
Name the column "Import Tag" (no quotes) in the header (row 1)
The Import Tag data will fill only if the data was imported via a CSV file and will not fill retroactively it will only populate for new data filled after the time it was added.
The Import Tag is shown when your CSV Import completes.
Known issues & limitations
We do not deduplicate data at this time. Be sure your import does not overlap with Transactions you already have for the account.
Using this tool to import transactions during an outage or disconnection may cause duplicate transactions.
No ability to delete an import from the database yet (i.e. if you accidentally import the data into the wrong account).
This workflow does not update the balance for the account. If you're uploading transactions for a manually tracked account, be sure to update the balance after importing transactions.