[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[[["\u003cp\u003eViewing costs by project hierarchy allows for analysis by folder or organization, helping to group costs by cost centers, for example.\u003c/p\u003e\n"],["\u003cp\u003eTo analyze costs by organization or folder, the report's "Group by" option should be set to "Project hierarchy," and the "Folders & Organizations" filter can be used to select specific areas of interest.\u003c/p\u003e\n"],["\u003cp\u003eProject hierarchy represents the ancestry of a project within the resource hierarchy (Organization > Folder > Project), including the project's current and historical ancestry.\u003c/p\u003e\n"],["\u003cp\u003eChanges to a project's ancestry, such as name changes or moving to a different folder or organization, can result in the same project appearing in multiple rows in the report table when grouped by project hierarchy.\u003c/p\u003e\n"],["\u003cp\u003eTo effectively visualize all projects with the same project hierarchy or visualize if a project has multiple ancestries, sort the table by the "Project hierarchy" or "Project ID" columns, respectively.\u003c/p\u003e\n"]]],[],null,["# Billing reports: Analyzing your costs by project hierarchy\n\n\u003cbr /\u003e\n\nViewing your costs by project hierarchy helps you analyze\ncosts by folder or organization. For example, if you use folders in an\norganization to represent cost centers, you can effectively configure your\nreport to group all costs by those cost centers.\n\nTo analyze your costs by project hierarchy, including costs by Organizations\nor costs by Folders, set the report's\n[**Group by** option to **Project hierarchy**](/billing/docs/how-to/reports#group-by-project-hierarchy).\nYou can also use the report's\n[**Folders \\& Organizations filter**](/billing/docs/how-to/reports#filter-by-folders-orgs)\nto select specific folders/organizations to focus the data returned in the\nreport.\n\nAbout project and resource hierarchy\n------------------------------------\n\n[Projects](/billing/docs/concepts#projects)\nform the basis for creating, enabling, and using all Google Cloud\nservices.\n[Folders](/billing/docs/concepts#folders)\nare used to group projects under the\n[organization node](/billing/docs/concepts#organization)\nin a\n[resource hierarchy](/billing/docs/concepts#gcp_resource_hierarchy_overview).\nA folder can contain projects, other folders, or a combination of both.\nEach resource has exactly one parent.\n\nMetaphorically speaking, the Google Cloud resource hierarchy resembles the\nfile system found in traditional operating systems as a way of organizing and\nmanaging entities hierarchically. From a cost management perspective, you might\nuse folders in an organization to represent cost centers (such as *Devops* or\n*Finance*). You can view your costs by project hierarchy to analyze your costs\nby folder.\n\n*Project hierarchy* is the ancestry of a project, the resource hierarchy\nmapping of the project (Organization \\\u003e Folder \\\u003e Project). Projects can stand\nalone (that is, not be associated with any folders or organizations) or be\nthe child of an *Organization* or *Folder* . Project hierarchy tracks the\n*current* and *historical* project ancestry. For example, changing a\nproject's name, or moving a project to a different folder or organization,\naffects the\n[*historical* project ancestry](#project-ancestry-changes).\n\nTo gain a deeper understanding about resource hierarchy and Cloud Billing,\nrefer to [Cloud Billing concepts, Resource hierarchy](/billing/docs/concepts#gcp_resource_hierarchy_overview).\n\nConfigure your report to show project hierarchy\n-----------------------------------------------\n\nTo view your costs by project hierarchy (organization \\\u003e folder \\\u003e project),\ntake the following steps:\n\n1. In the Google Cloud console, [open the Reports page](https://console.cloud.google.com/billing/reports) for the Cloud Billing account you want to analyze.\n2. In the report Filters, set a [**Time range**](/billing/docs/how-to/reports#time-range) to use a ***starting date*** *on or after* **January 1, 2022**.\n3. In the\n [**Group by**](/billing/docs/how-to/reports#group-by)\n selector, choose\n [**Project hierarchy**](/billing/docs/how-to/reports#group-by-project-hierarchy).\n\n The report returns a row for each unique combination\n of *Organization \\\u003e Folder \\\u003e Project* , and the table includes columns for\n *Project* , *Project ID* , *Project number* , and *Project hierarchy*.\n\n The values listed in the *Project hierarchy* column show\n *Organization name \\\u003e Folder name*.\n\n### Analyze the report when grouped by Project hierarchy\n\n- You can\n [**sort the table data**](/billing/docs/how-to/reports#data_order)\n on different columns to view the project hierarchy costs in different\n ways:\n\n - To visualize *all of the projects* that have the *same project hierarchy* , sort the table by the **Project hierarchy** column.\n - To visualize if you have the *same project* associated with *more than one* ancestry, sort the table by the **Project ID** column.\n- You can narrow the report's project hierarchy results using the\n [**Folders \\& Organizations**](/billing/docs/how-to/reports#filter-by-folders-orgs)\n filter.\n\n- While you are viewing the report grouped by *Project hierarchy* , if you\n change the report's time range to include a *starting date prior to\n January 1, 2022* , the\n [*Group by*](/billing/docs/how-to/reports#group-by)\n selection is automatically updated to group by *Project*.\n\n- If you select some folders or organizations in the\n [*filter*](/billing/docs/how-to/reports#filter-by-folders-orgs),\n and then update the *time range* to include a *starting date prior\n to January 1, 2022*, the folders/organizations selections are removed.\n\nUnderstand and analyze changes in project ancestry\n--------------------------------------------------\n\nFor the time range you are analyzing, it is possible for the same Project\nto be listed in more than one row in the report table. This can occur if\nsomething related to the project's ancestry has changed. Changes that affect\na project's ancestry include the following:\n\n- Changing the project's name\n- Moving the project to a different organization and/or folder\n- Changing a parent folder's name\n- Moving a parent folder into another folder and/or organization\n\nTo **visualize if you have projects associated with more than one ancestry** ,\n[**sort the table data**](/billing/docs/how-to/reports#data_order)\nby the **Project ID** column.\n\n### Examples of changes in project hierarchy\n\nThe following examples show different scenarios where something related to the\nproject's ancestry was changed, and how that change impacts the results in the\nreport, depending on how you **Group** the results.\n\nAll of these examples assume that the changes affecting the project ancestry\noccurred after January 1, 2022.\n\n### Example 1: Project name change\n\nYou can edit a project's display name, but the project ID and the project number\nare immutable and remain constant.\n\n[Group by *Project*](/billing/docs/how-to/reports#group-by-project)\n\n[Group by *Project hierarchy*](/billing/docs/how-to/reports#group-by-project-hierarchy)\n\nNotes about *project name changes* when grouping by *project hierarchy*:\n\n- For the report's time range, if the project has not incurred any usage *after* the name is changed, then you will only see one row for the project, listed as *Old Project Name*.\n- For the report's time range, if the selected time range *starts after* the date the project's name was changed, then you will only see one row for the project, listed as *Current Project Name*.\n- If you use the [Project filter](/billing/docs/how-to/reports#filter-by-projects) to select a project, the project's name displayed in the list of options is always the *Current Project Name* . The *project ID* is not editable and remains the same after a project's name is edited.\n\n### Example 2: Project moved to a different parent folder\n\nIn this example, *My test project* is moved from *folder1* to *folder2* .\nAfter the move, *My test project* is now a child of *folder2*. Folders are\nalways the child of a parent organization.\n\n[Group by *Project*](/billing/docs/how-to/reports#group-by-project)\n\n[Group by *Project hierarchy*](/billing/docs/how-to/reports#group-by-project-hierarchy)\n\n### Example 3: Parent folder moved *into* a different folder\n\nIn this example, *folder1* is moved into *test folder* . After the move,\n*folder1* is now a child (or subfolder) in the parent *test folder*.\nFolders are always the child of a parent organization.\n\n[Group by *Project*](/billing/docs/how-to/reports#group-by-project)\n\n[Group by *Project hierarchy*](/billing/docs/how-to/reports#group-by-project-hierarchy)\n\n### Example 4: Name change of a parent folder\n\nYou can edit a folder's display name, but the folder ID is immutable and\nremains constant.\n\n[Group by *Project*](/billing/docs/how-to/reports#group-by-project)\n\n[Group by *Project hierarchy*](/billing/docs/how-to/reports#group-by-project-hierarchy)\n\nNotes about *folder name changes* when grouping by *project hierarchy*:\n\n- For the report's time range, if the folder's projects have not incurred any usage *after* the folder's name is changed, then you will only see one row for the folder, listed as the Org \\\u003e *old folder name*.\n- For the report's time range, if the selected time range *starts after* the date the folder's name was changed, then you will only see one row for the folder, listed as the Org \\\u003e *current folder name*.\n- If you use the [Folders \\& Organizations filter](/billing/docs/how-to/reports#filter-by-folders-orgs) to select a folder, the folder's name displayed in the list of options is always the *Current Folder Name* . The *folder ID* (displayed below the folder name) is not editable and remains the same after a folder's name is edited.\n\n### Example 5: Project moved to a different organization\n\nIn this example, *My test project* is moved from *Org1.net* to *Org2.com* , and\nthe project is not in any folder. After the move, *My test project* is now a\nchild of *Org2.com*.\n\n[Group by *Project*](/billing/docs/how-to/reports#group-by-project)\n\n[Group by *Project hierarchy*](/billing/docs/how-to/reports#group-by-project-hierarchy)\n\n### Example 6: Project moved to a different billing account\n\nCloud Billing accounts exist outside of the project's\n[resource hierarchy](/billing/docs/concepts#gcp_resource_hierarchy_overview).\nIf you\n[move a project to a different billing account](/billing/docs/how-to/modify-project#change_the_billing_account_for_a_project),\nthe project hierarchy remains attached to the project.\n\n[Grouped by *Project hierarchy*](/billing/docs/how-to/reports#group-by-project-hierarchy)\n\nViewing report for **OLD billing account**\n\nViewing report for **NEW billing account**\n\nRelated topic\n-------------\n\n- [View your billing reports and cost trends](/billing/docs/how-to/reports)"]]
