You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- `outputFile`: This can be set to a string to use a single file for all transactions or an object with years as keys and paths as values to set a different file for different years.
71
+
-`outputFile`: This can be set to a string to use a single file for all transactions or an object with years as keys and paths as values to set a different file for different years.
71
72
-`subCategories`: This can be set to an object with `income` and `expense` as keys. Each of those keys must be set to an array of strings indicating the sub-categories to use for each. When importing transactions, the tool will prompt you to select one.
72
73
-`expenseTypeMapping`: The keys in the object are expense categories and the values are an expense type of "need" or "want" to automatically map expense categories to types.
73
74
-`expenseAllowance`: This can be set to an object with keys indicating a specific year. Each year should be set to an object with expense sub-categories as keys. Each sub-category should be set to an object with the keys `allowance`, indicating how much is allowed per month, and `carryover`, indicating any rollover from the previous year (or `0` if none).
74
75
-`moveFilesAfterImport`: This can be set to an object with keys indicating an account name and values indicating an absolute path to a local directory. If a destination path is set for a specific account, the CSV file will be moved there after successful import.
75
76
-`defaultImportDir`: This can be set to a directory where the import command will look for CSV files. If this is not present then the command will require a directory path in the `input` flag.
76
77
-`autoCategorization`: This can be set to a specifically-shaped object that will be used to auto-categorize transactions.
77
-
- `descriptions` is an array of one or more strings that are used to match the incoming transaction description in an "or" strategy.
78
-
- `amount` is an object that should have at least one of the following keys:
79
-
- `gt` (greater than)
80
-
- `gte` (greater than or equals)
81
-
- `lt` (less than)
82
-
- `lte` (less than or equals)
83
-
- `categorization` is the object that is merged with the transaction data if the conditions are met.
78
+
-`descriptions` is an array of one or more strings that are used to match the incoming transaction description in an "or" strategy.
79
+
-`amount` is an object that should have at least one of the following keys:
80
+
-`gt` (greater than)
81
+
-`gte` (greater than or equals)
82
+
-`lt` (less than)
83
+
-`lte` (less than or equals)
84
+
-`categorization` is the object that is merged with the transaction data if the conditions are met.
Copy file name to clipboardExpand all lines: docs/usage.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,20 @@
2
2
3
3
### Importing Transactions
4
4
5
-
The first thing you will need for this to do anything for you are some transactions in the database. Transactions are imported from CSV files and translated from their original format to the CSV database. The translators currently available are the [translators](src/translators) folder. See the [Contributing](#Contributing) section for how to add or request new translators.
5
+
The first thing you will need for this to do anything for you are some transactions in the database. Transactions are imported from CSV files and translated from their original format to the CSV database. The translators currently available are the [translators](../src/translators) folder. See the [Contributing](#Contributing) section for how to add or request new translators.
6
6
7
7
Assuming we have a CSV from one of the supported banks, we can run the importer, indicating a specific file or a directory containing one or more CSV files.
By default, the script will only import transactions for the current year. To import from a year in the past (or, I guess, the future), add a `year` argument to the command.
If the command checks out, you will be prompted to confirm the import file. This will help you determine if the configuration file is working. Next, it will prompt you for the first CSV it finds from your import path. Answering `n` will move on to the next CSV found, if there is one.
0 commit comments