An account-level budget proposal.
All fields prefixed with 'proposed' may not necessarily be applied directly. For example, proposed spending limits may be adjusted before their application. This is true if the 'proposed' field has an 'approved' counterpart, for example, spending limits.
Note that the proposal type (proposalType) changes which fields are required and which must remain empty.
JSON representation |
---|
{ "resourceName": string, "proposalType": enum ( |
Fields | |
---|---|
resourceName |
Immutable. The resource name of the proposal. AccountBudgetProposal resource names have the form:
|
proposalType |
Immutable. The type of this proposal, for example, END to end the budget associated with this proposal. |
status |
Output only. The status of this proposal. When a new proposal is created, the status defaults to PENDING. |
id |
Output only. The ID of the proposal. |
billingSetup |
Immutable. The resource name of the billing setup associated with this proposal. |
accountBudget |
Immutable. The resource name of the account-level budget associated with this proposal. |
proposedName |
Immutable. The name to assign to the account-level budget. |
approvedStartDateTime |
Output only. The approved start date time in yyyy-mm-dd hh:mm:ss format. |
proposedPurchaseOrderNumber |
Immutable. A purchase order number is a value that enables the user to help them reference this budget in their monthly invoices. |
proposedNotes |
Immutable. Notes associated with this budget. |
creationDateTime |
Output only. The date time when this account-level budget proposal was created, which is not the same as its approval date time, if applicable. |
approvalDateTime |
Output only. The date time when this account-level budget was approved, if applicable. |
Union field proposed_start_time . The proposed start date time of the account-level budget, which cannot be in the past. proposed_start_time can be only one of the following: |
|
proposedStartDateTime |
Immutable. The proposed start date time in yyyy-mm-dd hh:mm:ss format. |
proposedStartTimeType |
Immutable. The proposed start date time as a well-defined type, for example, NOW. |
Union field proposed_end_time . The proposed end date time of the account-level budget, which cannot be in the past. proposed_end_time can be only one of the following: |
|
proposedEndDateTime |
Immutable. The proposed end date time in yyyy-mm-dd hh:mm:ss format. |
proposedEndTimeType |
Immutable. The proposed end date time as a well-defined type, for example, FOREVER. |
Union field approved_end_time . The approved end date time of the account-level budget. approved_end_time can be only one of the following: |
|
approvedEndDateTime |
Output only. The approved end date time in yyyy-mm-dd hh:mm:ss format. |
approvedEndTimeType |
Output only. The approved end date time as a well-defined type, for example, FOREVER. |
Union field proposed_spending_limit . The proposed spending limit. proposed_spending_limit can be only one of the following: |
|
proposedSpendingLimitMicros |
Immutable. The proposed spending limit in micros. One million is equivalent to one unit. |
proposedSpendingLimitType |
Immutable. The proposed spending limit as a well-defined type, for example, INFINITE. |
Union field approved_spending_limit . The approved spending limit. approved_spending_limit can be only one of the following: |
|
approvedSpendingLimitMicros |
Output only. The approved spending limit in micros. One million is equivalent to one unit. |
approvedSpendingLimitType |
Output only. The approved spending limit as a well-defined type, for example, INFINITE. |
AccountBudgetProposalStatus
The possible statuses of an AccountBudgetProposal.
Enums | |
---|---|
UNSPECIFIED |
Not specified. |
UNKNOWN |
Used for return value only. Represents value unknown in this version. |
PENDING |
The proposal is pending approval. |
APPROVED_HELD |
The proposal has been approved but the corresponding billing setup has not. This can occur for proposals that set up the first budget when signing up for billing or when performing a change of bill-to operation. |
APPROVED |
The proposal has been approved. |
CANCELLED |
The proposal has been cancelled by the user. |
REJECTED |
The proposal has been rejected by the user, for example, by rejecting an acceptance email. |