An app for analyzing and reporting on your financial data in YNAB written in C# and built on Azure.
This app generates different kinds of financial reports that are useful in budgeting and planning. The reports are delivered as Excel spreadsheets, web pages, or are pushed directly to users via SMS.
This simple report sends an SMS with the activity for a specific category for the current month.
This report shows the performance of your accounts over the past year. It takes a list of account groups as input and for each group, shows a timeseries line chart of the total value of each group. The output is a self-contained HTML file with inline SVG charts.
The typical use case for this is to group your investment accounts in various ways and then visualize their performance over time.
This report lists each budget category along with any goal information and its monthly cost. The purpose is to figure out for each category what the typical monthly cost is over the long term, not at a specific point in time (which is what YNAB's website is really good at). This can then be used for long-term cash flow planning.
If a category has repeating target then the monthly cost is calculated directly from that. For example, if the target is $120 annually then the monthly cost is calculated as $10 (even if this year you've already funded the full amount).
If a category does not have a repeating target then we still want to capture it in the report so we calculate the monthly cost based on the remaining time and money needed to reach the target. For example, if the target is $600 by June 1st and the report is generated in January, and half has already been funded at that point, then the monthly cost is (($600 - $300) / 6) = $50. This differs from how the repeating targets are calculated (which ignore how much as been funded) but its more accurate for these sorts of one-off goals.
It generates the report and saves it as an Excel file to your Desktop. Here's what it looks like:
| CategoryGroup | Category | GoalCadence | GoalDay | GoalTarget | MonthlyCost | GoalPctComplete |
|---|---|---|---|---|---|---|
| Fixed Monthly | Mortgage | Monthly | 3rd | $400.00 | $400.00 | 100% |
| Fixed Yearly | Car Registration | Yearly | Feb-28 | $500.00 | $41.67 | 100% |
| Goals | Vacation | None | Jun-15 | $1000.00 | $150.00 | 30% |
| ... |
This report lists all transactions for a specific category and month. The transactions are grouped by the memo field. This is particularly useful if you have one category for your discretionary spending, but still want to be able to sub-categorize your spending.
Clone the repo and open up the folder (I use VS Code for Mac with the C# Dev Kit, Azure, and Function App extensions).
1. Edit the configuration files
Edit the Deployments/infra.bicepparam file to add your YNAB personal access token, Twilio credentials, and your YNAB budget info. If you want to run the CLI via VS Code, then edit the .vscode/launch.json to adjust the parameters for your YNAB budget info.
2. Deploy the infrastructure
cd Deployments
./deploy-infra.sh mynabster infra.bicepparam
./deploy-code.sh mynabsterThe function app can also be run locally and supports debugging with breakpoints.
3. Run the CLI
Run the app via VS Code or directly via the command line.
The reports are generated by an Azure Function that is called by the console app for on-demand reports and by a logic app for scheduled reports. All secrets are stored in a key vault. The function app and logic app use system-assigned managed identities to authenticate with the key vault. The CLI uses the default credential to authenticate with the key vault to obtain the necessary secrets to run the function app. Similarly, when running the function app locally, it also uses the default credential to access the key vault. Both the function app and logic app use a consumption plan so the app costs about $10/mo.