Audits
PolicyCenter Cloud API includes endpoints that allow you to work with audits. Audits typically take place on policies where the premium is based on estimated amounts that must later be replaced with actual amounts. An example of this would be a Workers’ Comp policy where the premium can change based on the salaries of the covered workers. PolicyCenter Cloud API supports two types of audits in the base configuration: final audit and premium report. Final audit covers an entire policy term, while premium report covers specified time periods within a policy term.
Whether or not audits are available is dependent on LOB settings. In the base configuration, Workers’ Comp and General Liability LOBs are set as auditable.
For complete details on audits, see Application Guide.
Audit policy definitions
Depending on your LOB configuration, audits might be scheduled automatically when you quote and bind your policy. For example, you might create a Workers’ Comp policy that will have premium reports and a final audit scheduled for the term of the policy. These audits are created based on an audit schedule pattern that defines audit properties such as frequency of the premium reports (monthly, quarterly), and when audits begin and end. (See Product definitions for audit schedule patterns for information on retrieving audit schedule patterns.)
Audit policy vs audit job endpoints
Audits are accessible in Cloud API through the Policy and Job APIs. Audits are created with the Policy API. Any actions that take place on the audit between the time it’s created and the time a job is started are also done through the Policy API.
After an audit is started, there are a few actions that take place on the audit job, such as quoting and completing, and therefore are done through the Job API. However, most actions, including most updates to the audit, continue to be done through the Policy API. See the following sections for how and when to use the various endpoints in the Policy and Job APIs: