Download PDF
Download page Changing the Status of Billing Schedules.
Changing the Status of Billing Schedules
Once you invoice a billing schedule its status changes from Pending Billing to Pending Invoiced or Invoiced. The status change depends upon whether the invoice is created with a Draft or Approved status.
The following table lists all the combinations of the actions and the status change that Conga Billing supports.
Action | Status Change | |
---|---|---|
From | To | |
Auto Approved = True | Pending Billing | Invoiced |
Auto Approved = False | Pending Billing | Pending Invoiced |
Approve Invoice | Pending Invoiced | Invoiced |
Cancel Invoice | Pending Invoiced | Pending Billing |
Move to draft | Invoiced | Pending Invoiced |
Cancel button | Invoiced | Pending Billing |
(From Billing Plan) | Pending Milestone | Pending Billing |
The following table lists all the combinations of the actions (ABO operations such as Change or Termination) and the status change that Conga Billing does NOT support.
Action | Status Change | |
---|---|---|
From | To | |
Amendment | Pending Billing | Superseded |
Termination | Pending Billing | Canceled |
Amendment | Pending Invoiced | Superseded |
Termination | Pending Invoiced | Canceled |
Termination on mid-date of Invoice | Invoiced | Invoiced Canceled |
Termination | Invoiced | Canceled |
- For a wallet asset line item (WALI), when you run the API to update or change the status of a billing schedule from Invoiced to Pending Billing, then the API validates the billing schedule fee amount with respect to the wallet balance. If the validation passes, it executes the request otherwise displays a validation message if there is no sufficient available balance in the wallet.
- If multiple billing schedule IDs belonging to the same WALI are passed then the validation is done by taking the sum of the fee amounts of all those billing schedules belonging to a single WALI.
- If you pass multiple billing schedule IDs, the order of processing happens in the order of the IDs sent to the API.
The following table lists the parameters of the API and the returned results.
Parameters | Result | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CODE
| If you pass the list of wrappers as a parameter, the API changes the status of the billing schedules to the next higher or to the previous status. Example: Suppose you have defined a recurring asset line with the following information: Selling Frequency: Yearly Billing Frequency: Monthly List Price: USD 1,200.00 Remaining Billable Amount (RBA): USD 1,200.00 12 billing schedules are generated with a Fee Amount of USD 100.00 and the status as Pending Billing. When you execute the API the status of the billing schedules and the RBA changes as:
| |||||||||||||||
CODE
| If you pass a set of IDs as a parameter, the API performs bulk processing and changes the status of the billing schedules to the next higher or to the previous status. Example: Suppose you have defined a recurring asset line with the following information: Selling Frequency: Yearly Billing Frequency: Monthly List Price: USD 1,200.00 Remaining Billable Amount (RBA): USD 1,200.00 12 billing schedules are generated with a Fee Amount of USD 100.00 and the status as Pending Billing. When you execute the API, you get the following response:
|