Financial Settings
Settings > System Settings > Application Settings > Financial Settings
Financial Restrictions
The options available under Financial Restrictions depend on whether you are using budgets or spend plans.
Allocations
With budgets, allocations are optional. Allocations offer a high level of restriction and control over your funds.
When allocations mode is on:
- Funding sources and allocations are required.
- Funding sources must be placed at the top of the organization.
- All budgets must be associated with at least one funding source.
When allocations mode is off:
- Associating a budget with a funding source is optional.
- Funding sources can be used by all projects in the organization or limited to only be used by specific OUs.
- Funding sources are optional. You can attribute funds to budgets instead of drawing funds from funding sources.
For more information, see Allocations Mode.
Enforce Budgets
When budgets are enforced, all projects must have a budget. When they are not enforced, projects can still have budgets, but they are optional.
Enforce Funding Sources
When enforce funding sources is on, all budgets must be associated to a funding source.
Enforcing funding sources can be useful if you don't want to use allocations, but still want to use funding sources or attribute spend to a specific “bucket of money.”
Spend Plan Restrictions (Legacy)
Default Spend Settings
Default Spend Data Type
Set a default spend type. The selected data type will be shown anywhere spend is shown in the application. If a billing source doesn't support the selected data type, Billed will be shown instead.
Billed
The billed (invoiced) amount is shown for each funding source. Commitment charges are shown at the funding source level.
This view is useful if you want to see spend represented the same way that you see it on your financial invoice.
This is the only spend data type that was available in Kion before the 3.8.0 release.
NOTE: This is the only spend type available when using Detailed Billing Report as the report type for AWS spend on a billing source.
Amortized - Attributed (AWS Only)
With amortized billing, upfront costs for the resources you purchased are distributed across the term of the plan (the commitment period). In most cases, this is on a recurring monthly basis. This attributed view provides vertical financial data through your organization chart by attributing spend to accounts linked to the billing source based on their effective resource consumption.
This view is useful if:
- You do not want to see a cost spike on the first of the month.
- You have set up budgets at the project level.
NOTE: This spend type is not available using Detailed Billing Reports. This spend type will reflect Billed spend on Billing Sources using the Detailed Billing Report as the report type for AWS spend.
Amortized - Not Attributed (AWS Only)
With amortized billing, upfront costs for the resources you purchased are distributed across the term of the plan (the commitment period). In most cases, this is on a recurring monthly basis. This unattributed view provides horizontal financial data across your organization chart, showing spend at the parent, billing account where the resources were purchased, not on the linked accounts.
This view is useful if:
- You do not want to see a cost spike on the first of the month.
- You have not set up project level budgets, or you track spend at the top-level OU or funding source level instead.
NOTE: This spend type is not available using Detailed Billing Reports. This spend type will reflect Billed spend on Billing Sources using the Detailed Billing Report as the report type for AWS spend.
List
The on-demand list prices for resources are shown. This does not reflect any discounts or price variances.
This view is useful if:
- You have your own customers using Kion.
- You want to reduce end-user visibility into the discounts your organization receives.
NOTE: This spend type is not available using Detailed Billing Reports. This spend type will reflect Billed spend on Billing Sources using the Detailed Billing Report as the report type for AWS spend.
Switching between spend data types may trigger financial enforcements as the data is adjusted. If this is the case, you will be alerted before the setting configuration is saved.
Credits, Refunds, and Discounts
Select whether you would like to show credits, refunds, and discounts as deducted by default.
-
Deduct Credits (Billed and List only). Credits are adjustments that are applied to your account to cover eligible service costs. This can include promotional, purchased, and other granted credits.
Prior to version 3.8.0, credits were only deducted from funding source spend. Now, historical spend will show with either credits deducted or not deducted for all items throughout the app based on your selection here.
-
Deduct Refunds and Discounts. Refunds can occur when a billing report is updated after finalizing your bill for the previous month. Discounts include reductions to your rate that are applied during a given billing period. Some discount examples are reservation discounts, committed use discounts, and savings plan discounts.
When using Amortized spend data types, only discounts are reflected. Refunds and credits are not.
Reprocess Historical Spend Data
When switching between spend data types, your historical spend will need to be reprocessed to show the new data type. You will also be asked to reprocess your data when first upgrading to version 3.8.0+. If you do not reprocess your historical data, it will continue showing the previous data type. This can lead to mixed reporting, so we recommend reprocessing at your earliest convenience when switching spend data types.
In order to reprocess historical data, you must have historical financial reports in the storage location your billing source is configured to pull from and that data must be in the correct format. If data for a selected month is missing or unreadable, that month will be skipped and we will move on to the next. To identify which financial reports Kion has access to, see Troubleshooting Processing Financial Data.
During reprocessing, some financial features may not be available. If this is the case, a banner will be displayed in Kion for users with financial permissions. Additionally, some financial data may shift. For users with financial permissions, an in-app notification will be sent when data reprocessing is finished.
Reprocessing historical spend data impacts reported spend shown throughout Kion. This may trigger financial enforcements as the data is adjusted. If this is the case, you will be alerted before the process begins.
Default Spending Time frames
Set the default aggregate spend and project spend time frames to show throughout the application. These settings apply to the organization chart, OU cards, OU details, project cards, and project details. If this setting is also configured in a user's My User Settings, their configuration takes precedence.
Forecasting and Estimates
Forecasting generates an estimate of your future spending based on your current spending. It uses a linear projection that is based on this month's spending and trend data from previous months.
When enabled, estimates can be seen on project and OU spend overviews, spend reports, and spend graphs.
Financial System Settings
Migrating from Spend Plans to Budgets
When users switch back to spend plans all budgets and thresholds will be lost. All enforcements created that are associated w/ budgets and thresholds will be lost.
Daily Financial Reporting
With version 3.12, Kion introduced daily granularity in spend reports. This is a setting that can be toggled on or off in financial settings. Upon upgrade, this setting will be turned on by default for all spend going forward.
If daily ingestion is currently “Off”, you can enable it by doing the following:
- Go to Settings in Kion
- Navigate to “System Settings” > “Financial Settings” > “Financial System Settings”
- Toggle Daily Spend Data “On"
- From this point, daily data will be ingested going forward by default. However, if you want daily data for prior months, it will require a reprocessing for the months desired
- If historical daily granularity is desired, navigate to “Reprocessing Historical Data” and kickoff the process for the historical months the desired to convert to daily
- Reprocessing Historical Data is also located within Financial Settings
If you do not reprocess historical months, only future days will be ingested and applicable to see spend when using daily granularity in spend reports. Prior months will not show daily spend, and spend reports will default to months when using those time frames.
Additionally, if you ingested daily granularity for a time period and then toggled the setting to “Off”, the previous daily data will remain in Kion, but the go forward ingestion will be monthly only. In this scenario, for you remove the historical daily spend, a reprocessing for that time frame would be required.
Tagged Spend Cache Generation
We have made performance improvements to our tag processing. When enabled, the system will generate a tagged spend cache which allows spend reports involving a single tag key to generate more quickly. This setting is on by default and should make tag spend reports more performant.
However, for Billing Sources with large financial reports, generating this cache may cause delays in financial processing. This setting should only be toggled off if you are experiencing problems with financial data loading. When disabled, the system will not generate the tagged spend cache and instead will run the report against the raw spend data.