.svg)
SaaSGrid automatically audits your CRM data and flags potential issues to help improve data hygiene.
Overview
Issues arise from the Opportunity level, and have two levels: warnings and errors.
Warnings are notifications of potential inaccuracies in your data. Opportunities with warnings are still included in your ARR. On the other hand, errors indicate any Opportunities that could not be included in your ARR. This is because there is too much information that is missing for the customer, or processing the customer will lead to inaccurate calculations.
Issue Types
Contract Errors
Contract Errors are instances where SaaSGrid has not generated a contract model for a particular CRM record due to a data inconsistency. The possible contract errors are listed below:
Missing Data (Error)
Example Message: "We were not able to include this Opportunity in your data because (field_name) was blank."
There are missing fields that are critical to customer information (ex. Contract amount). Without these fields, SaaSGrid cannot model the contract. Correct this error by populating the customer information in your CRM.
Contract Dates Out of Order (Error)
Example Message: "We were not able to create a contract from the Opportunity 'Opportunity Name' because the start date of the Opportunity is after its end date. To resolve, please update your CRM and resync."
If an opportunity has a start date after the end date in your CRM, SaaSGrid will not attempt to model the contract. Correcting the start and end date in your CRM and resyncing the integration will update SaaSGrid to show the correct values.
Missing Company (Error)
Example Message: "There is no obvious Company with which to link this Deal. We must either find a single Company associated with the Deal, or one of several associated Companies must be marked as the 'primary' Company."
If no Company or Account exists to connect a deal to, SaaSGrid will not attempt to model the contract. Correcting the relationship between company and opportunity will resolve this error.
Contract Warnings
Contract Warnings are instances where SaaSGrid has generated a contract model for a particular CRM record despite detecting an error. We recommend reviewing these issues and how they are represented in your data, as SaaSGrid solves these issues automatically. The possible contract errors are listed below:
Invalid Rule (Warning)
Example Message: "The contract we created from this Deal is a month-to-month contract that contains non-recurring revenue. Your integration settings indicate that non-recurring revenue should be spread across the service period of a contract - this is not possible with a month-to-month contract. The non-recurring revenue on this contract that comes from line items will be recognized in the first month of the contract. To resolve, please update your CRM or rules configuration and resync."
SaaSGrid will flag any opportunities that are not compatible with the rules you have configured and recommend a solution based on the rules incompatibility.
Contract Gap (Warning)
Example Message: “There is a gap between the 'End Date' of the contract (previous opportunity name) and the ‘Start Date' of the renewal (renewal opportunity name). The gap is less than 1 month, so we are not showing this customer as having churned and added a Bridge Contract to fill the gap. Please confirm if this is the desired behavior for this customer."
This warning arises when there is a gap and the gap is less than one month between the end date of the previous contract and the start date for the next. In this case, SaaSGrid creates a Bridge Contract so that the customer does not show as churned then resurrected. If a Bridge Contract should be applied, there is no need for further action.
Contract Match (Warning)
Example Message: “We were not able to associate this Closed Won 'Renewal' Opportunity with another Opportunity. This is likely because the 'Start Date' of this Opportunity does not align closely enough with the 'End Date' of another Opportunity. To resolve, consider updating Opportunity dates or categorization in your CRM and resyncing.”
A Renewal Opportunity needs to be matched to an existing Opportunity, otherwise it is considered a net new contract. SaaSGrid can connect a Renewal Opportunity to another Opportunity if its start date is close to the end date of an existing contract. You can resolve a Contract Match warning by correcting your start date of the new contract to match the end date of the former contract.
Contract Overlap (Warning)
Example Message: “The 'End Date' of Opportunity (opportunity_id) overlaps with the 'Start Date' of Opportunity (opportunity_id). During this overlap, we are including MRR from both Opportunities are in your data. If this is not correct, edit the 'End Date' or 'Start Date' in your CRM and resync.”
This warning indicates when SaaSGrid finds a potential renewal contract that overlaps with an existing contract. By default, SaaSGrid will record MRR from both your original contract and its possible renewal during its overlapping months. If there should not be overlapping dates, update your contracts in your CRM account with the correct dates. If your customer has two contracts with overlapping dates, there is no need for further action.
Issue Status
All issues are either resolved or unresolved. All issues are unresolved until the check box is manually selected in the Resolve column or the issue is corrected on your CRM.
For best practice, correct any warnings and errors in your CRM account if they reveal any inaccuracies in your data. However, for warnings, if the message is not applicable, you can manually select the check box for ‘Resolved.’
