Billing milestone statuses

SECURITY  Security level with Admin permission to configure Contracts & Un-Posting. Refer to Admin security settings.

NAVIGATION   > Admin > Features & Settings > Contracts & Un-Posting > Billing Milestone Statuses

Billing milestones apply to fixed price contracts, where billing is not based on labor. Instead, a billing event is triggered when a predefined milestone is reached. Billing milestone statuses, together with the milestone due date, control if and when the milestone becomes available for billing and invoicing.

Autotask is implemented with three predefined billing milestone statuses:

  • In Progress  This is the default milestone status applied when the milestone is created. Milestones with this status are not available for billing, even after the due date has been reached.
  • Ready to Bill  When the milestone status is set to Ready to Bill and the due date has been reached, the billing milestone will appear in Contracts > Approve and Post > Milestones for posting and invoicing. Ready to Bill is a system status that cannot be deactivated.
  • Billed  This is a system status that is automatically applied to the milestone when it is posted.

You can add additional custom statuses if needed for internal tracking. To open the page, use the path(s) in the Security and navigation section above.

Option Description

Edit, Edit [Entity Name]

Puts the selected row into Edit mode or opens the Edit <Option> dialog. The fields that can be edited are usually the ones you populate when you create a new list item. Make your changes and click Save, or Cancel.

NOTE  On some pages, you may not be able to edit System options.

Activate/Inactivate, Activate/Inactivate [Entity Name]

New options are active by default.

  • When an option is inactivated, it is no longer available for use, but existing associations with other entities remain in place and in effect.
  • You will be unable to inactivate an option that is referenced elsewhere.

NOTE  Sometimes, the association that prevents inactivation is not obvious. For example, to inactivate a ticket status associated with Incoming Email Processing, you must select a different one first.

Delete, Delete [Entity Name]

The ability to delete an option is severely restricted. List options cannot be deleted if:

  • The option is a system option
  • The option is the default option where a default is required
  • The option is associated with (has been used for) an entity

IMPORTANT  To preserve data integrity, Autotask prevents deletion of entities that have dependent entities or are referenced elsewhere! If you are unable to delete an entity, you should inactivate it to make it unavailable for use.