Common Errors with Billing Schedules
When you are working with billing schedule records, the following failure notices can occur in your SOAP responses.
A record with the same unique signatures already exists
The system generates this error when you try to create a new billing schedule with an external Id that is already in use. Either change the external Id of the record you are adding, or make a change to the existing record.
Invalid projecttask reference key x
This error can occur when you are trying to create a fixed bid milestone billing schedule. In some cases, you might create a sublist that references existing milestone tasks. If you use milestone tasks that do not match the project identified through the project body field, the system generates this error.
Invalid billingschedule reference key x for jobbillingtype y
You might see this error when attempting to attach a billing schedule to a project record. This error relates to the project record’s Billing Type field. This field must be set to the correct type for the schedule you are trying to attach. If Billing Type is set to a different type, or if it has not been set, the system returns this error.
Recurring monthly events cannot be scheduled after the 28th
You may see this error when both of the following are true:
-
You are trying to add a charge-based billing schedule with the frequency body field set to _monthly.
-
The seriesStartDate body field is set to the 28th, the 29th, the 30th, or the 31st of any month, or the field is left empty but the SOAP request is sent on one of those dates.
You must choose a recurrence count greater than 0
This message refers to a problem with the numberRemaining field (numberRemaining is labeled Recurrence Count in the user interface). The message indicates that you failed to set a value for the field. The field is required when frequency is set to any value other than _never.