You CAN have multiple payment profiles, although it is recommended to have a SINGLE payment profile at the Org leve

  • multiple payment profiles - not recommended by google (it messes with their sustained use discounts that are important for larger footprints).
  • 2. Best way to handle multiple profiles is invoiced billing

What does a GCP Org Structure look like in the real world?

  1. In an ideal world the Org structure on GCP would map to their off cloud org structure.
  2. In the real world, it is often driven by the actual networking build out - e.g. Shared services or Security/Governance is typically the FIRST child folder under the Org Level. A sample structure is shown below:
org folder structure GCP
org folder structure GCP

Can you segregate billing based on a given folder structure?

In theory, yes. You can set up multiple payment profiles within the GCP console. The downside (why Google doesn't recommend it) is that it messes with their sustained use discounts.

Summary

In practice, you would want to use INVOICED (after consumption) billing to attain this level of segregation. You would still retain a SINGLE payment profile at the Org level.

Also, in practice, the folder structure for an organization rarely maps to their off cloud real world organization structure.

In my experience, network design (and environment segregation) are the drivers behind folder  structures.