A company has offices in multiple countries.

AWS Budgets is the correct service because it is built to track AWS costs and usage and to take action when thresholds are reached. In this scenario, the company explicitly doesnotwant automatic resource restriction, so the right pattern is to use budget thresholds and define an action path that supportsmanual review. AWS documentation explains that AWS Budgets can monitor costs and trigger budget actions, and it also supports forecast-based alerts, which help identify likely overruns as early as possible. Daily reports alone are slower and less proactive, while automatic restrictions violate the requirement. Service control policies are not the mechanism used to define spending thresholds themselves. A Budgets-based workflow is therefore the cleanest and most appropriate solution. (AWS Documentation)

============