How can this be accomplished?
Implement AWS Organizations and create a service control policy that defines the billing relationship with the new master account.
Configure AWS Organizations Consolidated Billing and provide the finance team with IAM access to the billing console.
Send Cost and Usage Reports files to a central Amazon S3 bucket, and load the data into Amazon Redshift. Use Amazon QuickSight to provide visualizations to the finance team.
Link the Reserved Instances to the master payer account and use Amazon Redshift Spectrum to query Detailed Billing Report data across all accounts.
Explanations:
AWS Organizations can centralize billing and manage Reserved Instance (RI) benefits, but a service control policy (SCP) is used for managing permissions and not billing relationships. SCPs cannot manage the centralized billing or Reserved Instance sharing.
AWS Organizations with Consolidated Billing allows centralizing billing across multiple accounts and sharing Reserved Instance benefits. IAM roles can be configured for the finance team to access billing data in the master account.
Sending Cost and Usage Reports to an S3 bucket and using Amazon Redshift for analysis doesn’t centralize billing or RI benefits. It only provides a method for analyzing cost data, which is not the same as managing billing and RI benefits across accounts.
While linking Reserved Instances to the master payer account is correct, using Amazon Redshift Spectrum to query Detailed Billing Report data is unnecessary for centralizing billing and Reserved Instance benefits, which can be achieved via AWS Organizations and Consolidated Billing.
I gauge that the answer is:
Configure AWS Organizations Consolidated Billing and provide the finance team with IAM access to the billing console.