Transaction File Import

Background

To import transactions from a file in CSV format, use the Cashflow Tab's Edit | Import from File menu.

EstateExec will automatically analyze the file, then present you with a list of candidate transactions from the file, which you can accept as is, modify individually, or simply discard.

This feature is particularly helpful if you've already created a spreadsheet of transactions for some reason. However, if your list is in an unsupported format (e.g., Word, PDF), is somewhat unstructured (e.g., the value is embedded in the text rather than having its own column), or is not perfectly regular (e.g., some rows have extra cells), then it may be more work to try to "automatically" import the file than to simply enter the transactions by hand. If you are unsure, we recommend trying the automated import to see if it gives you what you want with minimal effort, and if things start to get confusing or require significant formatting work, then switch gears and either the information another way.

Note that if you don't already have a file of transactions, it rarely makes sense to create one just to import it: better to instead download the transactions directly from the bank, or enter them manually.

Required File Format (CSV)

EstateExec can import from files in CSV (Comma Separated Value) format. A CSV file consists of multiple lines (one per transaction), with each transaction field separated from the next by a comma. Ideally, the file has a header row that helps explain the meaning of the properties. Here's what a sample file might look like:

Date,Amount,Check #,Name
6/12/2025,-$300.00,101,Utility Bill
6/12/2025,-$500.00,,ACH automated State Farm withdrawal
6/14/2025,$80.21,,Interest
6/17/2025,-$3000.00,,Samuel Smith
6/17/2025,$5000.00,,Savings Account

The above example looks pretty simple, and is similar to what you might have if you generated your file downloading it from your bank's online interface. EstateExec supports additional fields as well (e.g., Category, Note, etc.), which you can see during Step 4 (Assign Column Meanings) of the Import Process below.

Some things to note:

• It's helpful to have a header row (see first line), but it's not necessary
• There are no required columns, and EstateExec will do it's best to figure things out
• Check amounts (i.e., debits) should be negative, deposit amounts should be positive
• If you don't have a value for an asset's field, just skip it (but remember you still need the comma)
• If you want to include a comma in an asset, you can just put quotes around that field

If your file is in a format for a spreadsheet program (e.g., Excel), you can export the contents into a CSV file via the spreadsheet program's Save As function, selecting file type CSV. Note that when you do this, your file must only contain data in the format described above. A header row is helpful, but you must delete any title rows, extraneous notes on the side, extra tabs, and so forth. Your goal is to export a file that contains only a header row (optional), and one row per transaction.

No Template File: We do not provide a template file because if you don't already have the transactions in a spreadsheet, we recommend that you import them directly from the bank or enter them manually.

Import Process

To add transactions from a file:

1. Choose Asset: On the Cashflow Tab, select the asset for which you wish to import transactions, using the asset selector at the top left of the table
2. Start: Click the Edit | Import from File menu
3. Select File: Click Select File from the dialog that appears, and the select the file from the Open File dialog that appears
4. Assign Column Meanings: A Describe File dialog will appear, containing the contents of your file (similar to that shown at the top of this page). In the first row of the table, select the meaning for each column (e.g., Check #). If your file has a header row, EstateExec will have attempted to make some default selections for you, which you can override as necessary.
5. Correct Problems: Once a meaning is defined for a column, cells that appear problematic will be highlighted in pink. For example, if you say that a column contains Amount, but a cell contains something other than a number, it will be shown in pink. You can click (or double-click) on a cell to edit it so you can correct any problems, or you can ignore it (and EstateExec will do its best, often simply ignoring that value).
6. Import the Transactions: When everything is configured the way you want, press the Import button at the bottom of the dialog to analyze the transactions.
7. Manage the Imports: EstateExec will present you with a list of candidate transactions from its analysis of the data, which you can accept, modify on an individual basis, or discard (see below).
8. Close: When you are done dealing with the candidate transactions, press the close button at the bottom of the dialog (any unhandled candidates will simply be discarded). Whatever you did will be reflected in your current estate, which you can Save as normal, or Cancel.

Managing Imported Candidate Transactions

The Import Transactions dialog shows candidate transactions from your file that you have not yet accepted (or deleted). EstateExec classifies these candidates as listed in the first column of the Import table:

• Exists - The transaction has already been imported
• Exists? - EstateExec thinks the transaction may have been already been imported
• Matched - EstateExec has found an existing EstateExec transaction that it thinks corresponds to the import
• Matched? - EstateExec has found an existing EstateExec transaction that it thinks probably corresponds to the import
• Choose? - EstateExec can't decide between several potential matches, and wants you to choose one of the suggested matches (or none)
• New - EstateExec hasn't found a corresponding EstateExec transaction (this is the normal case)

For each such candidate transaction, you can:

• Accept EstateExec's recommendation (e.g., import it as a new transaction, merge it with one you previously created manually)
• Edit the candidate to modify the suggested category, add a note, etc., and then save it as a new transaction in EstateExec
• Match the candidate via the Merge dialog, picking an existing transaction (suggested or otherwise) to merge
• Delete the candidate to basically ignore it

Order: It's best to handle the candidates in the order listed (with Matched candidates at the top, and New ones at the bottom). As you confirm or select transactions to merge with candidates, they become unavailable for other candidates in the table. Consequently, you may see some candidates that had a possible match convert to New as you work your way through the table, since you decided that the candidate transaction was a match for something else.

New Transactions: EstateExec attempts to analyze unmatched candidates to help you integrate them, trying to intelligently identify which ones are estate expenses, distributions to heirs, debt payments, and so on. You can always override EstateExec's suggestions by Editing the download, setting it to what you want, and saving it. You cannot change the amount of a candidate transaction, but you can simply Delete it if you feel it is wrong.

As you handle each candidate, it will be removed from the table, Once you have handled all candidates, you are done.

Shortcuts

Select multiple rows using the checkmarks along the left of the table, then click Accept to accept everything selected in one swoop.

Single-click a row to edit the candidate as a new transaction (which may not be what you want if it is matched!).

Double-click a row for a default action that depends on the classification of the row:

• Exists and Exists? - Remove the candidate from the table (presumably it has already been imported)
• Matched - Accept the candidate by merging the two and removing the candidate from the table
• Matched? - Bring up the Merge dialog so you can see the suggested match(es) and decide what to do
• Choose? - Bring up the Merge dialog so you can see the suggested matches and decide what to do
• New - Bring up the Edit Transaction dialog so you can make desired changes and save the candidate as a new EstateExec transaction