Understanding Errors 

Overview 

While syncing your sales orders, customers, products, or Accounting Rules on your RevRec site via third-party systems and bulk import, RevRec processes the data through multiple layers of control and validation checks to identify any errors or discrepancies. This document walks you through the different types of errors or warnings that RevRec looks for and reports during the validation process and how you can resolve them.

RevRec processes data in three stages, and applies validation rules for each stage to identify issues.

Depending on the severity of the data error, RevRec throws errors or warnings for different use cases.

• Errors: In case of errors, RevRec will not process the data unless the respective errors are resolved. For example, when a data sync error occurs, RevRec will not process the data unless you update the data in your source system.

• Warnings: For less severe issues, RevRec will still apply default rules and continue to process. For example, when a user-provided customer doesn't exist in your RevRec site, RevRec displays a warning and auto-creates the customer.

Data Sync Error 

When you have integrated your RevRec site with different source systems for data input (for example, your sales orders are synced from Salesforce and your invoices are synced from Xero), RevRec compares the data that gets synced from these different systems and alerts you when they don't reconcile. The system identifies any issues encountered during the auto-sync between RevRec and source systems by comparing the source data already saved in RevRec with what is getting synced via the download.

Example 

Let's consider for example that you use Salesforce CRM system and Xero as your invoicing system. You first run a sync job with Salesforce to sync all your sale orders and then run a sync job with Xero to sync invoices for the customers. During the data sync, RevRec finds that there are some invoices in Xero and the corresponding customer records do not exist in Salesforce. These invoices with the missing customers are logged as Data Sync Errors by RevRec, however the data population is not terminated.

Resolving Data Sync Errors 

Data sync errors can be resolved by updating the data in your source systems.

For the above example, if you enable the setting to Use Customer Name Mapping while integrating your Chargebee site with Xero or any billing system, RevRec checks and maps your invoices with customer names that are synced from the CRM system. Invoices or credit notes created for a customer whose name doesn't match with any customer records are tracked as Pending Data.

Once you add or update the customer details in your CRM system and sync the data again, RevRec validates the data and no errors will be logged against the new job.

Data Input Validation Error 

When you upload data in RevRec through file upload or when you run a sync job for any integrated source system, RevRec applies certain data rules to validate the data that is being uploaded. If the data is found to be inconsistent with the data requirements for processing, RevRec logs them as a Data Input Validation error.

Example 

For example, a missing customer-id against the contract or a missing invoice date. The system cannot process the contract information until the data is provided.

Resolving Data Input Validation Errors 

Data input validation errors can be resolved by updating the erroneous data in its source as follows:

• If the data was uploaded via bulk upload and you have identified the reason for an error, you can update the corresponding record row in the excel sheet and upload the specific sheet or the entire file again.
• If the data was synced from a source system, you can resolve the errors by fixing relevant data in the source system. In the case of multiple source systems, you may have to update the record in the source systems.

Once you have resolved the issues and uploaded/synced the data again, RevRec will validate and process the data.

Data Processing Error 

Data that is uploaded or synced into RevRec gets processed for revenue recognition based on the revenue rules, expense rules, and other configurations that you set up. When RevRec fails to produce the output due to incorrect configuration or missing rules, the system identifies them as Data Processing Validation errors.

Example 

For example, data processing validation errors are thrown when

• Sales orders are added for products with undefined Accounting Rules.
• Sales orders have missing or incorrect data - such as the quantity field defined with a negative unit - that were not captured during input validation but are captured during data processing.

Resolving Data Processing Errors in RevRec 

Resolution for data processing errors can be different for each processing error. For example, you can resolve a processing error related to missing rules by creating the accounting rules for the corresponding product. For sales orders with missing or incorect data, you can update the corresponding record with correct data from the RevRec UI. In both cases, remember to reprocess the sales order record so that the revenue recognition impact from the data change gets updated.

RevRec automatically removes the processing error from the job error report once it is resolved and no error will be found in the system.

Where to Look for Errors? 

Follow the steps mentioned below to view the data sync, data input validation, or data processing validation errors on your RevRec site:

1. Login to your RevRec site, and switch to the right environment.
2. Click Reports > Control and Validation.

The Control reports and Job Errors reports can be used to verify data in your RevRec system, identify errors, and fix them.

Control Reports 

You can use the following Control reports to look for a summary of data discrepancy in your RevRec site:

• The Invoice Control report compares the invoices that are downloaded from the source systems and the invoices that are processed by RevRec, and calls out any differences in the invoice amounts. This helps you identify any discrepancies due to data sync or data input validation errors that you can verify and fix using the Data Errors report.
• The Journal Entry Control report compares the journal entry revenue and the unearned revenue, and validates that no journal entry is missed due to General Ledger account mapping issues for recognized revenue for the period. This report helps you identify any data processing validation errors that you can verify and fix using the Data Errors report.

Job Errors Report 

The Job Errors report provides the details for each data issue, so you can conduct research to provide the fixes. Additionally, it is a log that keeps track of all the data errors and warnings for each job processed in your RevRec site - for example, once an error is reported, the report will have it in the record for the original job always, even after the error is fixed through a new job process.

Note: The Job Errors page can also be accessed from the Sync page by clicking on the link appearing in the job summary.

In the Search section, you can use the following search filters to find relevant job errors:

• Job ID: Enter the Job ID directly to filter errors related to a specific job.
• Type: Select Input or Output type from the Type drop-down to filter and view errors of the respective types. RevRec categorizes the Data Sync and Data Input Validation errors as Input errors and the Data Processing Validation errors as Output errors.
• Severity: Using the severity drop-down, you can filter for errors or warnings.
• Error on or After/before: You can also narrow down the results by applying the date filter.

In the Search Result section, errors and warnings are grouped by the source and an error count is reported for each error record. You can click the count to see the individual records that are impacted by the issue.