@fuzzle/opencode-accountant 0.0.10-next.1 → 0.0.11-next.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/agent/accountant.md +6 -12
- package/package.json +1 -1
package/agent/accountant.md
CHANGED
|
@@ -29,13 +29,9 @@ permission:
|
|
|
29
29
|
- `ledger/currencies/` - Currency exchange rate files
|
|
30
30
|
- `ledger/YYYY.journal` - Annual hledger journal files
|
|
31
31
|
- `ledger/rules` - hledger rules files
|
|
32
|
-
- `statements/` - Bank and broker account statements
|
|
33
|
-
- `statements/import` - Upload folder for new statements to process
|
|
34
|
-
- `statements/{provider}/YYYY` - Processed statements organized by source and year
|
|
35
|
-
- `doc/agent/todo/` - Agent's task work directory
|
|
36
|
-
- `doc/agent/done/` - Tasks completed by the agent
|
|
37
32
|
- `config/conventions/` - Accounting conventions
|
|
38
|
-
- `config/
|
|
33
|
+
- `config/import/providers.yaml` - import rules configuration file
|
|
34
|
+
- `config/prices.yaml` - currency pairs configuration file
|
|
39
35
|
|
|
40
36
|
## Conventions & Workflow
|
|
41
37
|
|
|
@@ -58,13 +54,11 @@ When working with accounting tasks:
|
|
|
58
54
|
|
|
59
55
|
## Statement Import Workflow
|
|
60
56
|
|
|
61
|
-
Use the `import-statements` tool to import bank statements. The workflow:
|
|
57
|
+
Use the `import-statements` tool to import bank statements. Do not edit the ledger manually! The workflow:
|
|
62
58
|
|
|
63
|
-
1. **Prepare**: Drop CSV files into `
|
|
64
|
-
2. **Classify**: Run `classify-statements` tool to move files to
|
|
59
|
+
1. **Prepare**: Drop CSV files into the incoming import folder configured in `config/import/providers.yaml`
|
|
60
|
+
2. **Classify**: Run `classify-statements` tool to move files to the configured import pending folder
|
|
65
61
|
3. **Validate (check mode)**: Run `import-statements(checkOnly: true)` to validate transactions
|
|
66
|
-
- Tool runs `hledger print` dry run to check for unknown postings
|
|
67
|
-
- Unknown postings appear as `income:unknown` or `expenses:unknown`
|
|
68
62
|
4. **Handle unknowns**: If unknown postings found:
|
|
69
63
|
- Tool returns full CSV row data for each unknown posting
|
|
70
64
|
- Analyze the CSV row data to understand the transaction
|
|
@@ -75,7 +69,7 @@ Use the `import-statements` tool to import bank statements. The workflow:
|
|
|
75
69
|
|
|
76
70
|
### Rules Files
|
|
77
71
|
|
|
78
|
-
-
|
|
72
|
+
- The location of the rules files is configured in `config/import/providers.yaml`
|
|
79
73
|
- Match CSV to rules file via the `source` directive in each `.rules` file
|
|
80
74
|
- Use field names from the `fields` directive for matching
|
|
81
75
|
- Unknown account pattern: `income:unknown` (positive amounts) / `expenses:unknown` (negative amounts)
|
package/package.json
CHANGED