# CFM Processes

Finops Center provides your companies Core Cloud Financial Processes.&#x20;

In FinOps Center 26.4.0, several CFM processes have been enhanced with new workflows. Weekly Spend Card Governance now enforces accountability at the product owner and portfolio manager level through weekly accept/dispute/reject cycles based on business weeks (Sunday to Saturday). Budget Management includes a full lifecycle with approval locks, reschedule requests, and status tracking. The cost allocation model follows the hierarchy: Budget > Account Allocation (%) > Workload > Resources, with open resources sharing cost by allocation percentage and claimed resources assigned 100% to a workload. Savings Management introduces a cost recommendations workflow where Financial Admins approve and Cloud Engineers implement optimizations. Vendor Management enables negotiated AWS discount tracking (EDP/PPA rates) through a vendor discounts pricebook.

* Financial Budget Onboarding/Modifying&#x20;
* Business User Onboarding&#x20;
* Financial Budget Mapping to User
* Financial Budget to Cloud Allocation&#x20;
  * AWS Account to Budget
  * Resource to Workload to Budget
  * Release Resource
  * Rollup Allocation/Visibility
* Estimate to Budget
* Budget Scheduling
  * Create Schedule
  * Approve/Reject Schedule
  * Request Reschedule
  * Approve Reschedule
  * Rollup Budgets
* Period Spending Cost Governance
* Cost Optimization Approvals
* AWS Credit Allocation
* Close Month
  * AR File
  * FP\&A


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.finopscenter.com/cfm-processes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
