Error messages in Zuora Revenue
Zuora Revenue displays error codes with messages to help you find the root cause and fix the errors. The following content provides you with a detailed explanation and corrective action for each error message.
RPRO-00002 - The transaction line is not processed due to invalid CV Eligible Flag value
This error occurs when the flag value does not meet the requirements. Valid values for CV Eligible Flag are Y, N or blank.
Recommended solution |
---|
|
RPRO-00003 - The transaction line is not processed due to missing Customer Name
This error occurs when the Customer Name is not specified in the transaction. Customer Name is a required field.
Recommended solution |
---|
|
RPRO-00006 - The transaction line is not processed due to missing Line Item Number
This error occurs when the Line Item Number is not specified in the transaction. Line Item Number is a required field.
Recommended solution |
---|
|
RPRO-00007 - The transaction line is not processed due to missing Invoice Qty
This error occurs when the Invoice Qty is not specified in the transaction. Invoice Qty is a required field for the following Line Types: INV, CM, CM-C, CM-R and CM-RO.
Recommended solution |
---|
|
RPRO-00008 - The transaction line is not processed due to invalid LT Contract Liability segment
This error occurs when the LT Contract Liability segment field contains invalid accounting segments based on the account setup. See Setups > Application > Account Setup and click the Account Type tab to view the Accounting Segments format.
Scenario |
Recommended solution |
Missing Segments |
|
---|---|
Invalid Segment |
RPRO-00009 - The transaction line is not processed due to invalid currency code or invalid rounding on Ext List Price/Ext Sell Price
This error occurs when one of the following conditions is met:
-
The Transaction Currency and/or Functional Currency do not match with any currency codes under the currency set up under Application > Currency.
-
The Ext List price and/or Ext Sell Price have the decimal points exceeding the rounding set up under Application > Currency.
For the currency issues:
Scenario |
Recommended solution |
---|---|
Misspelled currency code |
|
New currency code |
Note: See Configure currency format for the setup. |
For the rounding issues:
Scenario |
Recommended Solution |
---|---|
Incorrect decimal points sent from the source system |
|
Incorrect rounding set up in the system |
Note: See Configure currency format for the setup. |
RPRO-00011- The transaction line is not processed due to invalid Functional Ex Rate
If the Transaction Currency and the Functional Currency are the same, the Functional Ex Rate must be 1. This error occurs when the Functional Ex Rate does not equal to 1.
Scenario |
Recommended solution |
---|---|
Incorrect Functional Ex Rate from the source system |
|
Either Transaction Currency or Functional Currency is not correct |
|
RPRO-00012- The transaction line is not processed due to invalid Global Ex Rate
This error occurs when the Global Ex Rate does not equal to 1. Note that, if the Functional Currency and the Reporting Currency are the same, the Global Ex Rate must be 1. The Reporting Currency is set up under Setups > Application > Profile and search profile REPORTING_CURRENCY.
Scenario |
Recommended solution |
---|---|
Incorrect Global Ex Rate from the source system |
|
Incorrect Functional Currency from the source system |
|
RPRO-00014 - The credit memo is not processed due to missing start date
This error occurs when the Start Date is missing on the credit memo for this specific credit rule. When you enable this validation rule, the Start date is required if the credit memo has a Fixed Duration Credit Rule. See Credit Memo Transactions for additional information on credit rules.
Scenario |
Recommended solution |
---|---|
Incorrect Credit Rule |
|
Missing Start Date on the credit memo |
|
RPRO-00015- The transaction line is not processed due to invalid start date
This error occurs when the Start Date is earlier than the year 1947. Note that, the start date of the transaction line cannot be earlier than the year 1947.
Recommended solution |
---|
|
RPRO-00016- The transaction line is not processed due to invalid end date
The end date of the transaction line cannot be earlier than the year 1947. This error occurs when the End Date is earlier than the year 1947.
Recommended solution |
---|
|
RPRO-00018- The transaction line is not processed due to missing start date
This error occurs when the Start Date is missing on the transaction. When DURATION is specified on the transaction, the system calculates the End Date based on the Start Date plus Duration.
Data Requirements |
---|
|
Recommended solution |
---|
For the impacted transaction,
|
RPRO-00020 - The transaction line is not processed due to invalid Deferred Segments
This error occurs when the Deferred Segments field contains invalid accounting segments based on the account setup. See Setups > Application > Account Setup and click the Account Type tab to view the Accounting Segments format.
Scenario | Recommended Solution |
---|---|
Missing Segments |
|
Invalid Segment delimiters ( e.g.comma, colon or vertical bar) |
RPRO-00021 - The transaction line is not processed due to missing deferred segments
Deferred Segments are required for all transaction types, except CST transactions. This error occurs when the Deferred Segments field is blank.
Recommended solution |
---|
|
RPRO-00022 - The transaction line is not processed due to invalid Revenue Segments
This error occurs when the Revenue Segments field contains invalid accounting segments based on the account setup. See Setups > Application > Account Setup and click the tab Account Type to view the Accounting Segments format.
Scenario |
Recommended solution |
---|---|
Missing segments |
|
Invalid segment delimiters (e.g. comma, colon or vertical bar) |
RPRO-00023 - The transaction line is not processed due to missing revenue segments
This error occurs when the Revenue Segments field is blank. Revenue Segments are required for all transaction types, except CST transactions.
Recommended solution |
---|
|
RPRO-00030 -The RORD line is not processed due to missing Orig SO Line ID
This error occurs when the Orig SO Line ID is blank. Orig SO Line ID is required for RORD transactions..
Recommended solution |
---|
|
RPRO-00035 - The transaction line is not processed due to missing invoice number
This error occurs when the Invoice Number is blank. Invoice Number is required for all billing transactions, including transaction types: INV, CM, CM-C, CM-R and CM-RO.
Recommended solution |
---|
|
RPRO-00036 - The transaction line is not processed due to missing Invoice Line ID
This error occurs when the Invoice Line ID is blank. Invoice Line ID is required for all billing transactions, including transaction types: INV, CM, CM-C, CM-R and CM-RO.
Recommended solution |
---|
|
RPRO-00039 - The transaction line is not processed due to invalid Cost Def Segments
This error occurs when the Cost Def Segments field contains invalid accounting segments based on the account setup. See Setups > Application > Account Setup and click the Account Type tab to view the Accounting Segments format.
Scenario |
Recommended solution |
---|---|
Missing segments |
|
Invalid segment delimiters (e.g. comma, colon or vertical bar) |
RPRO-00040 -The transaction line is not processed due to missing Cost Def Segments
This error occurs when the Cost Def Segments are blank. Cost Def Segments are required for CST lines.
Recommended solution |
---|
|
RPRO-00041 - The transaction line is not processed due to invalid Cost Rev Segments
This error occurs when the Cost Rev Segments field contains invalid accounting segments based on the account setup. See Setups > Application > Account Setup and click the Account Type tab to view the Accounting Segments format.
Scenario |
Recommended solution |
---|---|
Missing segments |
|
Invalid segment delimiters (e.g. comma, colon or vertical bar) |
RPRO-00042 - The transaction line is not processed due to missing Cost Rev Segments
This error occurs when the Cost Rev Segments are blank. Cost Rev Segments are required for CST lines.
Recommended solution |
---|
|
RPRO-00043 - The transaction line is not processed due to invalid cost Functional Ex Rate
This error occurs when the Cost Func Ex Rate does not equal to 1. If the Cost Currency and the Functional Currency are the same, the Cost Func Ex Rate must be 1.
Scenario |
Recommended solution |
---|---|
Incorrect Cost Func Ex Rate from the source system |
|
Incorrect Cost Currency from the source system |
|
RPRO-00044 - The transaction line is not processed due to invalid Cost Global Ex Rate
This error occurs when the Cost Global Ex Rate does not equal to 1. If the Functional Currency and the Reporting Currency are the same currency, the Cost Global Ex Rate must be 1.
Reporting Currency is set up under profile REPORTING_CURRENCY. Navigate to Setups > Application > Profile to view the setup.
Scenario |
Recommended solution |
---|---|
Incorrect Cost Global Ex Rate from the source system |
|
Incorrect Functional Currency from the source system |
|
RPRO-00045 - The transaction line is not processed due to invalid currency code or invalid rounding on Cost Amount
This error occurs when one of the following conditions is met:
-
The Cost Currency does not match with any currency codes under the currency set up under Application > Currency.
-
The Cost Amount has the decimal points exceeding the rounding set up under Application > Currency.
For the currency issues:
Scenario |
Recommended solution |
---|---|
Misspelled currency code |
|
New currency code |
Note: See Configure currency format for the setup |
For the rounding issues:
Scenario |
Recommended solution |
---|---|
Incorrect decimal points sent from the source system |
|
Incorrect rounding set up in the system |
Note: See Configure currency format for the setup |
RPRO-00046- The transaction line is not processed due to invalid credit rule
This error occurs when the Credit Rule value does not meet the requirements. Valid values for Credit Rule are P, L, F or blank.
Credit Rules |
Glossary |
---|---|
P |
Prorate |
L |
Last in first out |
F |
Fixed Duration |
If the Credit Rule is not specified on the credit memo transaction, the system considers the first in first out rule. See Credit Memo Transactions for additional information on credit rules.
Recommended solution |
---|
|
RPRO-00047 - The credit memo line is not processed due to invalid credit rule on standalone CM
This error occurs when the Credit Rule field is not blank. The Credit Rule field must be blank for Standalone CM transactions.
Standalone CM is defined as a CM transaction without an Orig Inv Line ID.
Recommended solution |
---|
|
RPRO-00049 - The transaction line is not processed due to invalid Unbill Flag value
This error occurs when the flag value does not meet the requirements. Valid values for Unbill Flag (also known as Right To Bill Flag) are Y, N or blank.
See SO accounting entries for additional information on Unbill Flag (or Right to Bill Flag).
Recommended solution |
---|
|
RPRO-00050 - The transaction line is not processed due to invalid term
This error occurs when the Term is 0 or negative. The Term must be greater than 0 or blank.
Recommended solution |
---|
|
RPRO-00051- The transaction line is not processed due to missing Customer Number
This error occurs when the Customer Number is not specified in the transaction. Customer Number is a required field when the validation rule is enabled.
Recommended solution |
---|
|
If Customer Number is not a required field for your business scenario, disable the stage validation rule as needed.
RPRO-00052 -The transaction line is not processed due to invalid FV Eligible Flag value
This error occurs when the FV Eligible Flag value does not meet the requirements. Valid values for FV Eligible Flag (also known as SSP Eligible Flag) are Y, N or blank.
Recommended solution |
---|
|
RPRO-00053 - The transaction line is not processed due to invalid SOB ID
This error is applicable to Oracle users only. This error occurs when the SOB ID is not specified. SOB ID is a required field for all transactions.
Recommended solution |
---|
|
RPRO-00058 - The RORD line is not processed due to invalid Ext Sell Price
Ext Sell Price (ESP) for RORD transactions must be in negative value or $0. This error occurs when the ESP is greater than $0.
Recommended solution |
---|
|
RPRO-00059 - The transaction line is not processed due to missing Ext Sell Price
Ext Sell Price (ESP) is required for all transactions, except for CST transactions. This error occurs when the ESP is blank.
Recommended solution |
---|
|
RPRO-00061 - The transaction line is not processed due to invalid Rev Offset Segments
This error occurs when the Rev Offset Segments field contains invalid accounting segments based on the account setup. See Setups > Application > Account Setup and click the tab Account Type to view the Accounting Segments format.
Scenario |
Recommended solution |
---|---|
Missing segments |
|
Invalid segment delimiters (e.g. comma, colon or vertical bar) |
RPRO-00062 - The transaction line is not processed due to invalid Def Offset Segments
This error occurs when the Def Offset Segments field contains invalid accounting segments based on the account setup. See Setups > Application > Account Setup and click the tab Account Type to view the Accounting Segments format.
Scenario |
Recommended solution |
---|---|
Missing segments |
|
Invalid segment delimiters (e.g. comma, colon or vertical bar) |
RPRO-00063 - The credit memo is not processed due to missing end date
When this validation rule is enabled, End date is required when the credit memo has a Fixed Duration Credit Rule. This error occurs when the End Date is missing on the credit memo for this specific credit rule.
See Credit Memo Transactions for additional information on credit rules.
Scenario |
Recommended solution |
---|---|
Incorrect Credit Rule |
|
Missing End Date on the credit memo |
|
When the credit rule is set as F (Fixed Duration), Start Date and End Date are expected on the transaction to amortize the credit amount in the specified duration. If both dates are not specified on the transaction, the system will amortize the credit amount based on the percentage of the billed amount. If Start Date and End Date are not needed with Credit rule “F” for your business scenario, disable the stage validation rules (RPRO-00014 for Start Date and RPRO-00063 for End Date) as needed.
RPRO-00066 - The transaction line is not processed due to invalid contract modification date
This error occurs when the Contract Modification Date is before the SO Date. The Contract Modification Date must be later than the SO Date.
Recommended solution |
---|
|
RPRO-00067 The transaction line is not processed due to invalid exchange rate
This error occurs when the exchange rate fields listed below have negative values.
-
Functional Ex Rate
-
Global Ex Rate
-
Cost Func Ex Rate
-
Cost Global Fx Rate
Note that exchange rates must have positive values.
Recommended solution |
---|
|
RPRO-00068 - The transaction line is not processed due to invalid duration
This error occurs when the Duration is 0 or negative. Duration must be greater than 0 or blank.
Recommended solution |
---|
|
RPRO-00069 - The transaction line is not processed due to invalid FV date
When the FV Date (also known as SSP Date) is specified on the transactions, the system validates if the FV Date is later than the first day of the current open period. If the FV Date is blank, the system will skip the validation. This error occurs when the FV Date is earlier than the current open period.
Recommended solution |
---|
|
Note: FV Date is needed when Derive SSP/RSSP Date is set to Line Level SSP Date under Contract Modification Revision Timeline. Navigate to Policies > Contract Modification and view under Revision Timeline for the setup. Also, see Timeline for contract modification for additional information.
RPRO-00072 - The transaction line is not processed due to missing Order Quantity
This error occurs when Ordered Qty is 0 or blank on SO and RORD transactions. Ordered Qty must be greater than 0 on SO and RORD transactions.
Recommended solution |
---|
|
RPRO-00075 - The transaction line is not processed as the specified start/end date do not match the specified duration
This error occurs when the system calculated duration does not match the specified duration on the transaction. When the transaction specifies Start Date, End Date and Duration, the system calculates the duration based on the start and end date, and validates against the specified duration.
Validation Rule Status |
Data Requirements |
---|---|
Enable |
|
Disable |
|
Recommended solution |
---|
For the impacted transaction,
|
RPRO-76 - The transaction is not processed due to missing F Ex Rate and/or G Ex rate
Functional Ex Rate and Global Ex Rate are required for the following conditions. The transactions will not be processed if the requirements are not met. Update the rates in the source system and re-send the transactions to ZR.
Required Fields |
Conditions |
---|---|
Functional Ex Rate |
When Transaction Currency and Functional Currency are different For example, transaction currency is CAD and functional currency is USD |
Global Ex Rate |
When Functional Currency and Reporting Currency are different. For example, functional currency is USD and the reporting currency is EUR |
RPRO-77 - The SO update line is not processed due to exchange rate mismatch between the SO update line and the SO line in the system
This error occurs when the Functional Ex Rate of the SO update line does not match the Functional Ex Rate of the SO line in the system. If the SO line in the system has not yet released revenue, an SO update line with a different rate will be processed. This error only applies to the lines with released revenue.
Scenario |
Recommended solution |
---|---|
The new exchange rate on the SO update line is not valid |
|
The new exchange rate on the SO update line is valid |
Note: The functional balance of the previously recognized revenue will be reversed via the manual deferral. Upon collection of the SO update line and manual revenue release, the functional revenue balance will be scheduled based on the new rate and cumulative catch up of the functional revenue balance is expected in the current period. |
RPRO-79 - The SO update line is not processed due to CV Eligible Flag mismatch between the SO update line and the SO line in the system
When the revenue contract (RC) is under prospective allocation treatment, the CV Eligible Flag on the SO update line and the SO line in the system must be the same.
Scenario |
Recommended solution |
---|---|
The CV Eligible Flag on an SO update line is not valid |
|
The CV Eligible Flag was incorrect in the system. The SO update line is to correct the flag |
Switching allocation to retrospective will have an impact on allocation revenue. The allocation will be retrospectively recalculated based on the current transaction price in the RC and the allocation revenue will be recognized as cumulative catch-up in the current period. Once the RC is switched to retrospective, the previous prospective allocation calculation will be wiped out and cannot be retrieved. |
RPRO-00082 - The RORD line is not processed due to currency mismatch between the RORD and the SO in the system
This error occurs when the RORD currency is not the same as the associated SO currency.
Recommended solution |
---|
|
RPRO-00353 - The RORD line is not processed as the RORD start date and/or end date conflicts with the associated SO line
This error occurs when:
-
RORD Start Date is before the SO Start Date, or
-
RORD End Date is after the SO End Date
The RORD start and end date must be within the associated SO start and end date range.
Recommended solution |
---|
|
RPRO-00356 - The RORD line is not processed due to manual actions on the SO line
When this validation is enabled and the attribute RORD Completion Review Flag (SKIP_RORD_VALIDATION) is set to N or blank on the RORD transactions, the system blocks the RORD transactions for further processing. This validation serves as a manual checkpoint for the users to review and validate the revenue contracts or RORD before the data collection.
To process the RORD transactions, update the RORD Completion Review Flag as Y and re-collect the transactions into ZR.
If the review is not required prior to the data collection for your business scenario, disable the stage validation rule as needed.
RPRO-00357 - The RORD line is not processed as the Ext Sell Price on the RORD is greater than the Net Sell Price on the associated SO line
To consume the RORD line, its Ext Sell Price (ESP) must be equal or less than the Net Sell Price (NSP) of the SO line in the system.
Scenario |
Recommended solution |
---|---|
ESP on RORD line is not correct |
|
NSP in the system is incorrect due to previously consumed CM, CM-R or RORD |
Suppose the previous consumed transactions are incorrect, resulting in an incorrect Net Sell Price in the system. In that case, it is recommended that the ESP on the current RORD transactions be updated to adjust the revenue contract to the desired Net Sell Price. Allocation was calculated based on the previous consumed transactions in the prior periods. Adjusting the current RORD transactions may correct the booking values of the contract but will not rectify the allocation. |
RPRO-00600 - The transaction line is not processed as the SO Line ID on the transaction does not match with any SO in the system.
Scenario |
Expectation |
Recommended solution |
---|---|---|
The SO lIne has an Extended Selling Price (ESP) of $1000, and the invoice line is -$200. |
If the SO has a positive ESP, the invoice line must be a positive value. |
|
The SO Line has an ESP of -$1000, and the invoice line is $200. |
The invoice line must be a negative value if the SO has a negative ESP. |
RPRO-00601/RPRO-78 - The INV line is not processed due to the incorrect signage. The signage of the INV and the signage of the associated SO must be the same.
Scenario |
Expectation |
Recommended solution |
---|---|---|
The SO lIne has an Extended Selling Price (ESP) of $1000, and the invoice line is -$200. |
If the SO has a positive ESP, the invoice line must be a positive value. |
|
The SO Line has an ESP of -$1000, and the invoice line is $200. |
The invoice line must be a negative value if the SO has a negative ESP. |
RPRO-00602 - Encountered Internal error - Please contact the support team for further assistance.
The transaction encounters an internal error. Please contact Zuora Global Support for further assistance.
RPRO-00603 - The upload file is not processed due to special characters “=”, “+”, “@”
This error occurs when the profile ENABLE_CSV_DATA_SANITIZATION is set to Block.
Remove the special characters from the upload file and reprocess it. Alternatively, you can review and update the profile set up as follows to process the upload file again.
- Navigate to Setups > Application > Profiles and search for the profile ENABLE_CSV_DATA_SANITIZATION.
- Hover the mouse above the ENABLE_CSV_DATA_SANITIZATION line.
- Click the edit icon
- Select the applicable value from the System Level Value drop-down field.
Field values |
Expected Behavior |
---|---|
Block |
The system will display an error if the special characters are not removed |
Raw |
The system will accept the special characters and process the file |
Sanitize |
The system will remove the special characters and process the file |
RPRO-00604 - Total SSP for the RC is $0
The sum of the Extended SSP in the revenue contract is $0. Analyze the error further to confirm if the Extended SSP of $0 is accurate.
A common scenario may drive a $0 Ext SSP in the revenue contract.
Scenario
Based on the SSP setup, $0 extended SSPs are derived in each line for a total of $0 SSP.
SO Line ID |
Items |
Extended List Price |
Extended Sell Price |
Extended SSP |
---|---|---|---|---|
SO1.1 |
HW |
1000 |
600 |
0 |
SO2.1 |
SW1 |
500 |
200 |
0 |
SO3.1 |
SW2 |
500 |
200 |
0 |
Total |
700 |
400 |
0 |
RPRO-00605 - Second level allocation is not performed as the second level allocation identifier does not exist in the transaction
Second-Level Allocation error occurs when the ENABLE_LVL2_ALLOCATION profile is configured to Yes due to the transaction's absence of a second-level allocation identifier. for further information.
Scenario |
Recommended solution |
---|---|
The second-level identifier field is mapped incorrectly in the profile. |
Complete the following steps to review if the second-level identifier is configured correctly:
|
The second-level identifier field is mapped correctly, but the identifier field is missing from the transaction. |
|
The transaction is sent incorrectly with the CV Eligible LVL2 Flag as Y. Second-level allocation is not expected in this scenario. |
|
RPRO-00606 - Second level allocation is not performed as the sum of second level allocation % is not equal to 100%
Second-Level Allocation is turned on but the total percentage of the second-level allocation within the same second-level allocation group does not equal to 100%.
Scenario |
Recommended solution |
---|---|
The percentage of the allocation is sent incorrectly |
|
A second-level allocation eligible line is not processed due to an error in inbound data. |
|
RPRO-00607 - SSP allocation is not performed as unable to derive SSP.
This error occurs when ZR cannot derive the SSP from a transaction. See SSP setup for additional information.
Scenario |
Description |
Recommended solution |
---|---|---|
The SSP template is not active for the current period |
Each template has a start date and end date. Confirm the dates on templates related to the impacted transactions and ensure they are still active for the current period. |
When the template is reactivated, this update may impact other transactions.
ZR considers a period or an extra space an exception, resulting in an SSP error. |
The values to define the SSP grouping are not valid or do not exist |
For each attribute used for SSP determination, you must define the expected values for ZR to look up the SSP |
ZR considers a period or an extra space an exception, resulting in an SSP error. |
RPRO-00608 - The transaction is not processed due to other errors in the bundle. Review and fix the errors on the bundle line(s) for further processing
This error occurs when any lines within the bundle encounter another error. Review and fix the error on the bundle line and re-collect the lines in ZR.
The following example shows bundle lines using the Bundle Parent Line ID. The parent and child transaction lines have the same ID values.
Item |
Bundle Parent Line ID |
---|---|
Parent sku |
SO123-1 |
Child sku 1 |
SO123-1 |
Child sku 2 |
SO123-1 |
RPRO-00609 - Discount charge line is not processed due to missing parent charge line in the system
Scenario |
Description |
Recommended solution |
---|---|---|
Incorrect configuration in Zuora Billing for a parent charge. |
The Exclude item booking from revenue field in Zuora Billing is configured as Yes for a parent charge resulting in the parent charge not being synced to ZR. |
|
The parent and discount charges should be excluded from ZR. |
The Exclude item booking from the revenue field in Zuora Billing is incorrectly configured to No for a discount charge and synced to ZR. |
|
The parent charge line has not been processed due to other errors. |
Use Parent Charge Num and Parent Charge Segment to identify the parent charge line in the inbound. Both parent and discount charges have the same values in both fields. |
|
The parent charge line from the source system is missing. |
Technical errors have caused the parent charge line not to sync to ZR. |
|
RPRO-00610 - The SO cancellation line is not processed due to outstanding billed quantity on the line
The SO cancellation line with a cancel flag configured as Y is not processed because the billed quantity on the SO line in the system is not fully canceled. To consume the SO cancellation line, the net billed quantity on the line must be zero.
Scenario |
Description |
Recommended solution |
---|---|---|
The SO cancellation line is not valid |
Incorrect cancellation sent from the source system |
|
The SO cancellation line is valid, but the billed quantity is not fully canceled |
See example below |
|
Scenario 2 Example:
The original SO has a quantity of 10, and two billed invoices with a total quantity of 7. When the SO cancellation is processed, the total billed quantity is 7, as no credit memo is processed to reduce the billed quantity.
Type |
SO Line ID |
INV Num |
INV Line ID |
Orig INV Line ID |
Quantity |
---|---|---|---|---|---|
SO |
SO123-1 |
10 |
|||
INV |
SO123-1 |
INV1 |
INV1.1 |
5 |
|
INV |
SO123-1 |
INV2 |
INV2.1 |
2 |
Solution:
Create a credit memo (Tran Type is CM-C) to reduce the billed quantity.
Type |
SO Line ID |
INV Num |
INV Line ID |
Orig INV Line ID |
Quantity |
---|---|---|---|---|---|
CM-C |
SO123-1 |
CM1 |
CM1.1 |
INV1.1 |
5 |
CM-C |
SO123-1 |
CM2 |
CM2.1 |
INV2.1 |
2 |
RPRO-00611 - The SO update line is not processed because the Ext Sell Price (ESP) of the SO update line is less than the total invoiced (INV and CM-C) amount in the system
To consume the SO update line, its ESP must be equal to or greater than the total invoiced amount (INV and CM-C) in the system.
Scenarios |
Descriptions |
Recommended solution |
---|---|---|
SO update line is not valid |
Incorrect update sent from the source system |
|
The new ESP on the SO update line is valid but the invoiced amount (INV and CM-C) is greater than the new value. |
A credit memo must be created to reduce the billed amount |
|
Example A:
The original SO has an ESP of $1000, and two invoices totaling $700 have been billed.
An SO update line with an ESP of $500 is sent to ZR, and this error appears. The ESP is less than the total billed amount of $700.
In this situation, ZR only accepts a SO update with an ESP of $700 or above.
Type |
SO Line ID |
INV Num |
INV Line ID |
Orig INV Line ID |
Amount |
---|---|---|---|---|---|
SO |
SO123-1 |
$1000 |
|||
INV |
SO123-1 |
INV1 |
INV1.1 |
$500 |
|
INV |
SO123-1 |
INV2 |
INV2.2 |
$200 |
Solution: If the intent is to update the SO with an ESP of $500, generate a credit memo(Tran type CM-C) to cancel the invoice, which reduces the invoiced amount to $500 ($500+$200-$200). The SO update with an ESP of $500 will then be processed.
Type |
SO Line ID |
INV Num |
INV Line ID |
Orig INV Line ID |
Amount |
---|---|---|---|---|---|
CM-C |
SO123-1 |
CM1 |
CM1.1 |
INV2.2 |
-$200 |
Example B:
The original SO has an ESP of $1000. Two invoices totaling $700 and a CM-C of—$200 have been billed, for a total invoiced amount of $500.
An SO update line with ESP of $300 is sent to ZR and this error appears. The SO update line has $300 ESP, which is less than the total billed amount of $500.
In this situation, ZR only accepts an SO update with an ESP of $500 or above.
Type |
SO Line ID |
INV Num |
INV Line ID |
Orig INV Line ID |
Amount |
---|---|---|---|---|---|
SO |
SO123-1 |
$1000 |
|||
INV |
SO123-1 |
INV1 |
INV1.1 |
$500 |
|
INV |
SO123-1 |
INV2 |
INV2.2 |
$200 |
|
CM-C |
SO123-1 |
CM1 |
CM1.1 |
INV2.2 |
-$200 |
Solution: If the intent is to update the SO with an ESP of $300, generate a credit memo (Tran type CM-C) to cancel the invoice, which reduces the invoiced amount to $0 ($500+$200-$200-$500). ZR will then process the SO update with an ESP of $300.
Type |
SO Line ID |
INV Num |
INV Line ID |
Orig INV Line ID |
Amount |
---|---|---|---|---|---|
CM-C |
SO123-1 |
CM2 |
CM2.1 |
INV1.1 |
-$500 |
RPRO-00612 - The SO update line is not processed because the Ext Sell Price (ESP) of the SO update line is less than the total credit memo (CM and CM-R) amount in the system
This error occurs when the new ESP exceeds the total SO-based CM/CM-R amount on the line. A credit memo referencing the SO by using SO Line ID (Orig INV Line ID is blank) is considered an SO-based credit memo.
Example A:
Month 1 — The original SO has an ESP of $1000 and an invoice of $500 has been issued.
Type |
SO Line ID |
Ext Sell Price |
Net Sell Price |
Type |
SO Line ID |
INV Num |
INV Line ID |
Invoice Amount |
|
---|---|---|---|---|---|---|---|---|---|
SO |
SO123-1 |
$1000 |
$1000 |
INV |
SO123-1 |
INV1 |
INV1.1 |
$500 |
Month 2 — A SO-based CM of $-700 is generated.
The credit memo ($700) is more than the invoice ($500), assuming the $200 invoice will be processed in the future.
Type |
SO Line ID |
Ext Sell Price |
Net Sell Price |
Type |
SO Line ID |
INV Num |
INV Line ID |
Invoice Amount |
|
---|---|---|---|---|---|---|---|---|---|
SO |
SO123-1 |
$1000 |
$300 |
CM |
SO123-1 |
CM1 |
CM1.1 |
-$700 |
If the new ESP is $600 on the SO update, the line will not be processed. In this scenario, ZR will accept only an SO update with an ESP of $700 or above.
Solution: If the intent is to update the SO with an ESP of $600, complete the following steps:
- Reverse the CM1 in the source system.
The CM and CM-R reversal transaction types also have the Tran type as CM and CM-R, respectively, with a cancel flag configured as Y.
- Reverse the $200 Invoice pending processing.
- Process the SO update with the ESP of $600.
As a result, the current ESP on the booking is $600. The net invoiced amount is $500. $100 is pending for billing.
The above example and the suggested solutions also apply to SO-based CM-R scenarios.
RPRO-00613 - The SO update line is not processed because the Ext Sell Price (ESP) of the SO update line is less than the revenue recognized in the system
The error is only applicable for transactions relevant to consumption POBs.
Scenarios |
Description |
Recommended solution |
---|---|---|
The new ESP on the SO update line is valid but the revenue recognized is greater than the new ESP value. |
Consumption revenue is overstated. |
Manually deferring revenue on a consumption POB line is not allowed. |
SO update line is NOT valid. |
Incorrect update sent from the source system. |
|
RPRO-00614 - The SO update line is not processed due to the start date mismatch between the SO update line and the SO line in the system
This error occurs when the start date of the SO update line does not match the start date of the SO line in the system.
If the SO line in the system has not yet released revenue, an SO update line with a new start date will be processed. This error only applies to the lines with revenue released.
Scenario |
Description |
Recommended solution |
---|---|---|
The new start date on the SO update line is valid |
The revenue recognition started with an incorrect date from the previous SO line |
|
The new start date on the SO update line is not valid |
Incorrect update sent from the source system |
|
RPRO-00615 - The SO update line is not processed due to the RTB flag mismatch between the SO update line and the SO line in the system
The Right to Bill (RTB) flag on the SO update line and the SO line in the system must be the same. If the SO line in the system does not have any released revenue, the SO update line with a new RTB value will be processed. The error applies to the lines with released revenue.
See SO accounting entries with RTB flag for more information.
Scenarios |
Description |
Recommended solution |
---|---|---|
RTB flag was sent incorrectly in the past. The SO update line is to change the RTB flag. |
RTB flag defines unbill AR vs. CA/CL classification. Due to the incorrect RTB flag sent in the past, the current accounting on Unbill AR vs CA/CL classification in the RC is not correct. |
An SO update to change the RTB flag is not recommended, as the accounting results on the Unbill AR vs. CA/CL classification may not be as you expect. |
RTB flag on an SO update line is not valid. |
Incorrect update sent from the source system. |
|
RPRO-00616 - The SO update line is not processed due to different signage of the Ext Sell price between the SO update line and the SO line in the system
The Extended Sell price (ESP) signage on an SO update line and the SO line in the system must be the same.
Scenarios |
Description |
Recommended solution |
---|---|---|
The new ESP signage on the SO update line is not valid. |
Incorrect update sent from the source system. |
|
The new ESP signage on the SO update line is valid. |
It is rare to send a SO update with different signage on ESP. For example, change the value of the ESP from +$1,000 to -$1,000. |
|
RPRO-00617 - The SO update line is not processed as a system-generated SO line does not allow certain fields to be updated.
A system-generated SO line has the SO Line ID beginning with REVPRO and is created when an invoice or a credit memo does not reference any SO. This error occurs when the SO Line ID is blank.
Currently, the system does not support SO update for certain fields on a system-generated SO line. The unsupported fields are as follows:
- Ext Sell Price
- Ext List Price
- Unit Sell Price
- Unit List Price
- Ordered Qty
- Revenue Start Date
- Revenue End Date
- Duration
- Term
- Deferred Segments
- Revenue Segments
- Intercompany Account
- Contract Asset Account
- Contract Impairment Account
- Adjustment Liability Account
- Adjustment Revenue Account
- Contra Adjustment Revenue Account
- Payables Account
- LT Adjustment Liability
- LT Def Cogs Acct
- LT Contract Asset
- Unbilled AR Account
If an update is needed for the above fields, follow the below steps:
- Delete the errored SO update line from the inbound data.
- Reverse the invoice or credit memo in the source system and collect them in ZR to offset the existing transaction.
- Resend the invoice or credit memo with the correct values on the attributes or flags to ZR for processing.
RPRO-00619 - The INV line is not processed as the associated SO line in the system is canceled
This error occurs when the associated SO line is already canceled.
Scenarios |
Recommended solution |
---|---|
The invoice line is not needed |
No subsequent billings are expected on the line as the SO line is canceled. |
The invoice line is needed but has an incorrect reference ID to the canceled SO |
|
The invoice line is needed, but the SO line was incorrectly canceled in ZR previously |
Once an SO is canceled, ZR does not support reversing the SO cancellation. |
RPRO-00620 - The RORD line is not processed as the associated SO line in the system is canceled
Scenarios |
Recommended solution |
---|---|
The RORD line is not needed or duplicate. |
No additional RORD is expected on the line after the cancellation of SO. |
The RORD line is needed but has an incorrect reference ID to the canceled SO. |
|
RPRO-00621/RPRO-00657 - The credit memo line is not processed as the credit memo amount is greater than the amount of the associated INV
This is a data issue in the upstream system when the credit memo amount exceeds the referenced invoice amount. Review and confirm the credit memo amount against the associated invoices. Correct the credit memo in the source system and re-send it to ZR.
For Zuora’s OTR customers, this error occurs when the applicable invoice was previously fully or partially offset by other ad-hoc credit memos. Please contact Zuora Global Support for further assistance.
It is recommended that an ad-hoc credit memo from ZB be treated as a standalone credit memo in ZR. This is to prevent data corruption. By setting the original invoice line ID as null on the ad-hoc credit memo before ZR collection will ensure proper data and accounting results.
RPRO-00622 - The INV line is not processed as this INV transaction will overstate the SO sell price
The ALLOW_OVERSTATED_INVOICE profile is configured for handling your company’s policy on the allowance or disallowance of overbilling on a stated booking. Once the profile is updated, ZR applies the rule setting to all future transactions.
This error occurs when the ALLOW_OVERSTATED_INVOICE profile is configured to No. Based on the profile configuration, the system will not collect any invoice transactions if the total billed amount exceeds the original booking amount (net selling price).
Scenarios |
Recommended solution |
---|---|
The invoice line is not needed |
|
ALLOW_OVERSTATED_INVOICE profile configuration is not correct |
|
RPRO-00623 - The INV line is not processed as this INV transaction will overstate the SO quantity
The ALLOW_OVERSTATED_INVOICE profile is configured for handling your company’s policy on the allowance or disallowance of overbilling on a stated booking. Once the profile is updated, ZR applies the rule setting to all future transactions.
This error occurs when the ALLOW_OVERSTATED_INVOICE profile is configured to No. Based on the profile configuration, the system will not collect any invoice transactions if the total billed quantity exceeds the original quantity on the SO.
Scenarios |
Recommended solution |
---|---|
The invoice is not needed |
|
ALLOW_OVERSTATED_INVOICE profile configuration is not correct |
|
RPRO-00624/RPRO-00654 - The credit memo line is not processed as the referenced INV does not exist in the system
This error occurs when the original Invoice Line ID on the credit memo does not exist in the system.
Scenarios |
Recommended solution |
---|---|
The credit memo line is needed, but the reference ID is not correct |
|
The referenced invoice is in inbound due to other errors |
|
The referenced invoice is not sent or synced into ZR |
|
RPRO-00625 - The CST line is not processed as the cost type does not match with the cost type for the specific POB template of the SO line
Scenarios |
Description |
Recommended solution |
---|---|---|
The cost type value is not properly configured in ZR. |
Correct cost type value is sent from the source system but the value is not set up correctly in ZR. |
|
The cost type value on the CST line is not valid. |
Incorrect cost type value sent from the source system. |
|
RPRO-00626 - Encountered Internal error - Please contact the support team for further assistance
This error occurs when a transaction encounters internal errors. Please contact Zuora Global Support for further assistance.
RPRO-00627/RPRO-00013 - The transaction line is not processed as the revenue end date is before the revenue start date
The revenue start date must be before or equal to the revenue end date.
Type |
Recommended solution |
---|---|
OTR customer |
|
Standalone Zuora Revenue customer |
|
RPRO-00628 - The transaction is not processed as both Def Offset and Rev Offset segments have values
Under offset accounting setup and requirements, only one type of offset segment (Def Offset or Rev Offset) is allowed. See Offset accounting for additional information.
Complete the following steps to resolve the error:
-
Identify why both the segment values are sent to ZR for an impacted line.
-
Reverse the transaction in the source system.
-
Re-send the transaction with the proper segment values from the source system to ZR.
RPRO-00629/RPRO-00001 - The transaction line is not processed as the "Tran Type" value is not valid
Scenario |
Description |
Recommended Solution |
---|---|---|
The value of the transaction type is not valid. |
The following are the supported transaction types:
|
|
RPRO-00630 - The SO line is not processed due to missing SO line id
Scenario |
Description |
Recommended solution |
---|---|---|
Missing SO Line ID |
All SO lines must have an SO Line ID value. |
For Non-OTR:
For OTR: Please contact Zuora Global Support for further assistance. |
RPRO-00631 - The CST line is not processed due to missing Cost amount
Scenario |
Description |
Recommended solution |
---|---|---|
The Cost amount is missing |
Cost amount is required for all CST lines. |
|
RPRO-00632 - The CST line is not processed due to missing Cost Type Name
Scenario |
Description |
Recommended solution |
---|---|---|
Cost Type Name is missing |
CST line requires to have Cost Type Name |
|
RPRO-00633/RPRO-00634/RPRO-00048 - The CST line is not processed due to invalid Cost type name
All CST lines require a valid Cost Type Name. Cost Type ID should be blank.
Scenario |
Description |
Recommended solution |
---|---|---|
The Cost Type Name value is invalid |
Cost Type Name should match with the names already set up in ZR for all CST lines Note: ZR considers a period or an extra space as an exception |
|
RPRO-00635 - The transaction is not processed due to missing INV line ID
Scenarios |
Description |
Recommended solution |
---|---|---|
The INV Line ID is missing |
INV Line ID is required for the below Tran Types:
|
For Non-OTR:
For OTR: Please contact Zuora Global Support for further assistance. |
RPRO-00636 - The INV line is not processed as Orig SO line ID should be blank
Scenario |
Description |
Recommended solution |
---|---|---|
The Orig SO Line ID contains a reference. |
The INV Tran Type lines do not require any Orig SO Line ID’s reference. |
For Non-OTR:
For OTR:: Please contact Zuora Global Support for further assistance. |
RPRO-00637 - The credit transaction line is not processed as both Orig INV line ID and Orig SO line ID have references. Only one reference is allowed on a credit transaction
Scenario |
Description |
Recommended solution |
---|---|---|
Both Orig INV Line ID and Orig SO Line ID have references. |
Only one reference (Orig INV Line ID or Orig SO Line ID) is needed for credit transactions. |
For Non-OTR:
For OTR: Please contact Zuora Global Support for further assistance. |
RPRO-00638 - The CMC line is not processed due to missing references. Either Orig INV line ID and Orig SO line ID should have a reference
Scenario |
Description |
Recommended solution |
---|---|---|
The line is either missing an Orig INV Line ID or an Orig SO Line ID |
A reference to the originating transaction (Orig INV Line ID or Orig SO Line ID) is required for credit transactions. |
For Non-OTR:
Note: For Non-OTR, referencing a CM-C to a SO (using the Orig SO Line ID) may result in incorrect accounting from future transactions. Zuora recommends you reference a CM-C to an invoice (using Orig INV Line ID). For OTR: contact Zuora Global Support for further assistance |
RPRO-00639 - The SO line is not processed due to invalid impairment type values
Scenario |
Description |
Recommended solution |
Impairment type value is invalid |
To process a contract impairment accounting, the system requires an Impairment type. The value on the Impairment type field must be blank or should contain one of the following:
|
|
See Contract Impairment for further details.
RPRO-00641 - The CST line is not processed as the cost management module is not enabled
Scenario |
Description |
Recommended solution |
---|---|---|
The cost management module is not enabled |
The CST lines are used for cost accounting. The cost management module must be enabled to process CST lines. Note: Cost management is an add-on module. |
|
RPRO-00642 - The SO line with cost amount is not processed as the cost management module is not enabled
Scenario |
Description |
Recommended solution |
---|---|---|
The cost management module is not enabled |
Cost Amount is used for cost accounting. The cost management module must be enabled to process the SO lines with cost amounts. Cost management is an add-on module |
|
RPRO-00643 - Revenue on the child POB is not released as the revenue on the parent POB is not released
The revenue on a parent's POB must first be released before a Child POB can be released. Under the POB template setup, the child POB is set up with a POB dependency and links to a parent POB. Navigate to Policies > Performance Obligations to locate the applicable POB template and access the POB dependency to review the setup.
Scenario |
Recommended solution |
Revenue on parent POB is not released |
|
The POB dependency setup is not correct |
|
RPRO-00644 - Revenue is not released as both revenue start date and revenue end date are outside of the ZR accounting calendar
Navigate to Setups > Applications > Accounting Calendar to review the calendar. To release the revenue, the periods associated with the start date and end date must be set up correctly in ZR to release the revenue.
Scenario |
Recommended solution |
The revenue start and end dates are not correct |
|
The revenue start and end dates are accurate, but the periods are not available in the ZR accounting calendar |
|
RPRO-00645 - Encountered Internal error - Please contact the support team for further assistance
The transaction encounters internal errors. Contact the Zuora Global Support for further assistance.
RPRO-00646 - The SO for the deleted amendment is not processed as the same deleted amendment was previously processed in ZR
This error applies to OTR only and is applicable if the CONSUME_DELETED_TRANSACTION profile is configured to Yes.
Scenario |
Description |
Recommended solution |
---|---|---|
Duplicate deleted amendment SO |
The deleted amendment SO line was previously processed in ZR |
Delete the duplicated line from the inbound table. |
RPRO-00647 - The SO with previous charge version is not processed and the same charge version was previously processed in ZR
This error applies to OTR only.
Scenario |
Description |
Recommended solution |
---|---|---|
A duplicate SO line with the previous charge version was sent to ZR |
The SO line with the previous charge version was already processed in ZR |
Delete the duplicate line from the inbound table. |
RPRO-00648 - The transaction is not processed as it is associated with the charge version not existed in ZR
This error normally occurs when the associated SO lines have a future SO book date. ZR does not collect any transactions beyond the current open period.
Scenario 1 - Invoiced in the current period but it is associated with a version not collected into ZR.
This scenario is applicable when the Past End-of-Term profile is turned on in ZB. See billing rules to understand the implications of billing transactions.
Example:
On Jan 1, 2024, a subscription is booked and is partially billed.
Tran Type |
SO Line ID |
Version |
Book Date |
Invoice Date |
Amount |
Revenue Start Date |
Revenue End Date |
---|---|---|---|---|---|---|---|
SO |
SO1.1 |
1 |
1/1/24 |
1000 |
1/1/24 |
12/31/24 |
|
INV |
SO1.1 |
1 |
1/1/24 |
500 |
1/1/24 |
6/30/24 |
On July 1, 2024, a new charge to the subscription was added, and version 2 was created with August 2024 as the booking date. In the open period of July 2024, the system will not consume these SO transactions as the booking date is in the future.
Tran Type |
SO Line ID |
Version |
Book Date |
Invoice Date |
Amount |
Revenue Start Date |
Revenue End Date |
---|---|---|---|---|---|---|---|
SO |
SO1.1 |
2 |
8/1/24 * |
1000 |
1/1/24 |
12/31/24 |
|
SO |
SO2.1 |
2 |
8/1/24 * |
800 |
8/1/24 |
12/31/24 |
Note - These transactions are not collected in ZR in the month of July 2024.
In the same period in July 2024, a bill run generates an invoice on the first charge. As the Past End-of-Term profile is turned on for the invoice, the invoice on the first charge can bill more than the initial booking values for the period beyond the initial term end date of the charge.
Tran Type |
SO Line ID |
Version |
Book Date |
Invoice Date |
Amount |
Revenue Start Date |
Revenue End Date |
---|---|---|---|---|---|---|---|
INV |
SO1.1 |
2 |
7/15/24 |
550 |
1/1/24 |
1/31/25 |
During the current period of July 2024, the system will error out the INV even if the invoice date is in the current period. The INV is referenced to SO1.1 (Version 2), where the Book Date is in August 2024, which is not collected in ZR in July 2024
Scenario 2—The proration credit memo is for the current period, but the amendment date is in the future.
On January 1, 2024, a subscription is booked and fully billed.
Tran Type |
SO Line ID |
Version |
Book Date |
Invoice Date |
Amount |
---|---|---|---|---|---|
SO |
SO1.1 |
1 |
1/1/24 |
1000 |
|
INV |
SO1.1 |
1 |
1/1/24 |
On February 1, 2024, amend the subscription to reduce the price to $600 with the book date of March 1 2024. However, a proration credit memo is generated for $400 on February 1 2024
Tran Type |
SO Line ID |
Version |
Book Date |
Invoice Date |
Amount |
---|---|---|---|---|---|
SO |
SO1.1 |
2 |
3/1/24 * |
600 |
|
CM-C |
SO1.1 |
2 |
2/1/24 |
-400 |
Note - This transaction is not collected in ZR in the month of February 2024.
During the current period of February 2024, the system will not process the SO with the future book date. Although the credit memo has the date in February 2024, the system will error out the credit memo as it is tied to Version 2 amendment.
For both scenarios above, it is not recommended that amendments be made with a future date as the system would not consume such bookings. For the impacted line,
-
Recommended Solution 1—Do not take action in the current period on future SO bookings and the associated invoice or credit memo. Postpone the collection until the respective SO period is open.
Postponing the collection on both SO and invoice/credit memo will result in discrepancies in different areas.
-
Reconciliation of discrepancies in the booking and billing between ZB and ZR.
-
Reconciling variances between revenue contract roll forward report and general ledger.
-
Billed and unbilled revenue classification discrepancies may lead to different CA/CL netting or unbilled AR results.
-
Revenue recognition discrepancies depend on the POB types. For example, upon billing POB.
-
Recommended Solution 2 - If waiting for the future date to mature is not an option, contact the Zuora Global Support for further assistance to resolve the SO book date issue.
For other scenarios not listed above, contact the Zuora Global Support for further assistance.
RPRO-00650 - The ramp allocation is not performed due to inconsistent average pricing methods under the same ramp group
Term and Volume are two average pricing methods for ramp allocation. Under the same Ramp group defined by you using the RAMP_DEAL_REF, only one method is allowed for the ramp calculation.
Scenario | Recommended Solution |
---|---|
Inconsistent methods under the same ramp group |
|
If the transaction has no value under the AVG_PRCING_MTHD, ZR will consider the method based on the setup under the AVERAGE_PRICING_METHOD profile. If the transaction uses the Term or Volume method from the source system, the transaction values will supersede the defaulted method.
See Ramp allocation for more information about the ramp configuration and calculations.
RPRO-00651- Ramp allocation under the same ramp deal does not result in straight-line revenue. A hold is applied to the RC
This error occurs when the per-day-per-unit rate is not the same across all the ramp lines. Revenue is not recognized on a straight-line basis under the same ramp group. A hold is applied to the RC for you to review further.
Scenarios |
Recommended solution |
Rounding issues |
Note: The RAMP_HOLD_THRESHOLD profile is to set the threshold for rounding differences. This error will not appear if the per-day-per-unit difference is within the defined threshold. |
Other scenarios |
|
See Ramp allocation for more information about unit rate calculation.
RPRO-00655 - The credit memo cancellation transaction is not processed as the referenced orig INV line ID does not exist in ZR
This error occurs when the orig INV Line ID on the credit memo cancelation does not exist in the system.
Scenario |
Recommended Solution |
Incorrect reference in original invoice Line ID |
|
The referenced credit memo is in inbound due to other errors |
|
The referenced INV is not sent or integrated into ZR |
For non-Zuora’s order to revenue datasets,
|
RPRO-00659 - The CM-C transaction is not processed as the referenced SO line does not have any billing.
This error occurs when the CM-C is referenced to a SO line which does not have any billing transactions in the system. This is applicable to OTR only.
Scenario |
Recommended solution |
---|---|
The INV is not synced or integrated into ZR |
|
The INV(s) is in inbound due to other errors |
|
RPRO-00660 - The credit memo transaction is not processed as the credit memo amount is more than the available invoice amount
The credit memo amount is more than the aggregate amount of all the previously processed invoices/credit memos on the transaction.
Scenario |
Description |
Recommended Solution |
Missing invoice(s) from the source system |
Associated invoice(s) generated from the source system but not yet processed into ZR. |
|
Unprocessed invoice(s) due to other errors |
Associated invoice(s) are errored out in inbound |
|
ncorrect credit memo amount |
Incorrect credit memo generated from the source system |
|
Incorrect credit memo(s) processed in the past due to incorrect referencing |
Previously processed credit memo has incorrect reference to the transaction. As a result, the transaction is incorrectly offset by the credit memo and the net billing amount in the system is lower than expected. |
|
RPRO-00661 - The credit memo line is not processed as the credit memo amount is more than the net sell price on the SO
The credit memo amount cannot be higher than the net sell price on the transaction.
Scenario |
Description |
Recommended Solution |
Incorrect Credit Memo amount |
Incorrect credit memo generated from the source system |
|
SO was incorrectly reduced in the past |
SO update, RORD or credit memos were sent in the past to reduce the booking value. As such, the net sell price is lower than expected in ZR |
Please contact Zuora Global Support for further assistance. |
RPRO-00662 - CM-C with SO reference is not supported
For non-Zuora’s order to revenue dataset, CM-C with SO reference is not supported. CM-C is for invoice cancellation and therefore CM-C must reference an invoice.
Scenario |
Description |
Recommended Solution |
Correct CM-C type with SO reference |
CM-C type with SO reference is not allowed and not supported in ZR for non-Zuora's order to revenue dataset. |
|
For Zuora’s order to revenue dataset, it is rare to encounter this error. Please contact Zuora Global Support for further assistance.
RPRO-00663 - The CM-C cancelation line is not processed as it is not supported
CM-C cancellation is not supported in Zuora Revenue.
CM-C is for invoice cancellation. If the CM-C is deemed incorrect or needs to be reversed in ZR, re-generate the invoice from the booking in the source system to offset the CM-C.
RPRO-00664 - The transaction line is not processed due to invalid book ID
Scenario |
Recommended solution |
---|---|
The value of the Book ID is blank or invalid |
|
RPRO-00665 - Missing accounting segments. Please update the segments and re-process the TA batch
The TA update batch is not processed because at least one of the JE records contains invalid accounting segments. All predefined segments must be populated properly during the TA process.
Possible Scenario |
Recommended solution |
---|---|
SO Transactions with missing accounting segments |
|
IINV Transactions with missing accounting segments |
|
See Configure accounting structure for more details on the account segments set up.
RPRO-00666 - The credit transaction is not processed as the sum of all credits in the batch are greater than the net billing amount on the line
Credits more than the billings on a transaction are not allowed and therefore the system validates if all invoice-based CMs and CMRs (credit memos referenced to an invoice using Orig INV Line ID) in a single collection batch are greater than the net billed amount on the transaction.
Scenario |
Description |
Recommended solution |
---|---|---|
Invoice(s) not in ZR inbound |
Invoice(s) created in the source system but not yet integrated to ZR inbound |
|
Credits more than the billing |
Total credits are greater than total billing in the source system |
|
RPRO-00668 - The event is not processed due to invalid release percentage
The release percentage (REL_PCT) cannot be less than 0% or more than 100% for percent based events template.
Scenario |
Recommended solution |
---|---|
Invalid release percentage in the event upload |
|
RPRO-00669 - TA is not processed as the selected book in the batch is not enabled
This error occurs when the selected book is not enabled for Transfer Accounting (TA) or when a one-time set up is required to enable a revenue book.
Scenario |
Recommended solution |
---|---|
Incorrect book entered in a TA batch |
|
The selected book is not enabled for posting |
|
RPRO-00670 - Warning: Transfer validations failed and RC holds are applied
This error occurs when the TA update process is successful, except for the revenue contract that did not pass the transfer validations. A transfer hold is applied to the impacted RCs, and they are excluded from the TA process. Access the Transfer Accounting Error Report to review the list of impacted revenue contracts and the respective validation errors.
RPRO-00671 - TA update batch is not processed due to TA custom code/data issues
This error occurs when the TA update batch encounters unexpected errors. Please contact Zuora Global Support for further assistance.
RPRO-00672 - TA transfer batch is not processed due to TA custom code/data issues
This error occurs when the TA update batch encounters unexpected errors. Please contact Zuora Global Support for further assistance.
RPRO-00673 - Encountered internal error - Please contact support team for further assistance
This error occurs when the applicable program encounters internal errors. Please contact Zuora Global Support for further assistance.
RPRO-00674 - Missing accounting segments. A transfer hold is applied on the RC and it is excluded from further TA processing
This error occurs if one of the Journal Entry (JE) records in the batch contains invalid accounting segments. All predefined segments must be populated properly during the transfer accounting process.
If more than one segment is missing in the accounting string, the JE records display an error. A transfer hold is applied on the impacted revenue contracts and are excluded from the TA update process until the error is resolved. Valid records will be processed in the TA update batch for further processing.
Possible Scenario |
Recommended solution |
---|---|
SO Transactions with missing accounting segments |
|
INV Transactions with missing accounting segments |
|
See Configure accounting structure for more details on the account segments set up.
RPRO-00675 - Carve reclass entries are not net to $0. A transfer hold is applied on the RC and it is excluded from further TA processing
At least one revenue contract with carve reclass entries does not net to $0. A transfer hold is applied to the impacted revenue contracts, and they are excluded from the TA update process until the error is resolved. Please contact Zuora Global Support for further assistance.
Other revenue contracts without errors will be available for transfer accounting.
To review the carve reclass entries, perform the following steps:
- Navigate to Run Reports in the Report section or Journal Entries in Workbench.
- Access and download the current period Accounting Report in the Report section or Journal Details using
.
- Identify the current period transactions with the below filters
- Initial reporting flag = Y
- Schedule type flag = Adjustments
RPRO-00676 - Bundle reclass entries are not net to $0. A transfer hold is applied on the RC and it is excluded from further TA processing
This error occurs if at least one revenue contract with a bundle reclass entry does not net to $0. A transfer hold is applied to the impacted RCs, and they are excluded from the TA update process until the error is resolved. Please contact Zuora Global Support for further assistance.
Other revenue contracts without errors will be available for transfer accounting.
To review the bundle reclass entries, perform the following steps:
- Navigate to Run Reports in the Report section or Journal Entries in Workbench.
- Access and download the current period Accounting Report in the Report section or Journal Details using
.
- Identify the current period transactions with the below filters
- Initial reporting flag = Y
- Schedule type flag = Revenue
RPRO-00677 - Encountered internal error - Please contact support team for further assistance
This error occurs when the journal entry process encounters internal errors. Please contact Zuora Global Support for further assistance.
RPRO-00678 - Encountered internal error - Please contact support team for further assistance
This error occurs when the journal entry process encounters internal errors. Please contact Zuora Global Support for further assistance
RPRO-00679 - Encountered internal error - Please contact support team for further assistance
This error occurs when the journal entry process encounters internal errors. Please contact Zuora Global Support for further assistance.
RPRO-00681 - Encountered internal API error - Please contact support team for further assistance
This error occurs when the applicable program encounters internal errors. Please contact Zuora Global Support for further assistance.
RPRO-00683 - The CM-RO transaction is not processed as the referenced RORD is not in the system
This error occurs when the referenced RORD transaction (referenced by Orig SO Line ID on the CM-RO) is not in the system.
Scenario |
Recommended solution |
---|---|
The RORD is not synced or integrated into ZR |
|
The RORD is in inbound due to other errors |
|
RPRO-00684 - The transaction is not processed due to missing grouping attributes.
This error occurs when the grouping attribute(s) on the transaction is blank. Grouping attributes are defined under the “Group by” field in the RC Grouping template. See Create RC grouping template for additional information.
Scenario |
Recommended solution |
---|---|
Values on the grouping attribute(s) not populated in the source system |
|
RPRO-00685 - Impairment type other than R & R Within SSP is not processed due to inconsistency in impairment types for this RC
Once the revenue contract (RC) is processed with the impairment type of R & R Within SSP, other impairment types are blocked from further processing and require you to take certain actions. This error occurs when:
-
The RC is previously consumed with the impairment type of R & R Within SSP and the un-consumed RORDs are not R & R Within SSP.
-
In the same collection batch, there are multiple RORD lines for the RC with R & R Within SSP and other impairment types.
Scenario |
Recommended solution |
---|---|
Un-consumed RORD should have impairment type of R & R Within SSP to align with the existing types in the RC |
|
The new impairment type (non-R & R Within SSP) supersedes the existing type (R & R Within SSP) in the RC |
|
Mixed impairment types in the same batch |
If multiple types are required in the same batch for the same period, follow the RORD collection sequence in the KC. |
See Contract Impairment for additional information.
RPRO-00686 - Impairment type with R AND R WITHIN SSP is not processed due to inconsistency in impairment types for this RC
This is applicable to OTR customers only.
This error occurs when the un-consumed RORDs have the R & R Within SSP impairment type. Once the revenue contract (RC) is processed with impairment types other than R & R Within SSP, the RORDs with impairment type of R & R Within SSP are blocked from further processing and require the users to take certain actions.
Scenario |
Recommended solution |
---|---|
Un-consumed RORD should not have an impairment type of R & R Within SSP |
|
The impairment type R & R Within SSP takes the precedence in the RC |
Revenue in the RC must be posted in order to consume the RORD lines with R & R Within SSP when the previous RORDs were not the same type
|
See Contract Impairment for additional information.
RPRO-00687 - Intercompany accounting schedules are not net to $0. A transfer hold is applied on the RC and it is excluded from further TA processing
This error occurs if at least one revenue contract with intercompany accounting entries does not net to $0. A transfer hold is applied to the impacted revenue contracts which are excluded from the TA update process until the error is resolved. Please contact Zuora Global Support for further assistance.
Other revenue contracts without errors will be available for transfer accounting.
To review the intercompany entry details, complete the following steps:
- Navigate to Run Reports in the Report section or Journal Entries in Workbench.
- Access and download the current period Accounting Report in the Report section or Journal Details using
- Identify the current period transactions with Account Type = Intercompany
RPRO-00688 - Carve reclass entries are not net to $0. Please contact the support team to resolve the error and re-process the TA batch
The TA update batch is not processed because at least one revenue contract with carve reclass entries does not net to $0. Please contact Zuora Global Support for further assistance. Revenue contracts with or without errors will not be available for transfer accounting. Re-submit the TA update batch after the error is resolved.
To review the carve reclass entries, perform the following steps:
- Navigate to Run Reports in the Report section or Journal Entries in Workbench.
- Access and download the current period Accounting Report in the Report section or Journal Details using
- Identify the current period transactions with the below filters
- Initial reporting flag = Y
- Schedule type flag = Adjustments
RPRO-00689 - Bundle reclass entries are not net to $0. Please contact the support team to resolve the error and re-process the TA batch
The TA update batch is not processed because at least one revenue contract with bundle reclass entries does not net to $0. Please contact Zuora Global Support for further assistance. Revenue contracts with or without errors will not be available for transfer accounting. Re-submit the TA update batch after the error is resolved.
To review the bundle reclass entries, perform the following steps:
- Navigate to Run Reports in the Report section or Journal Entries in Workbench.
- Access and download the current period Accounting Report in the Report section or Journal Details using
- Identify the current period transactions with the below filters
- Initial reporting flag = Y
- Schedule type flag = Revenue
RPRO-00690 - Intercompany accounting schedules are not net to $0. Please contact the support team to resolve the error and re-process the TA batch
The TA update batch is not processed because at least one revenue contract with intercompany accounting schedules does not net to $0. Please contact Zuora Global Support for further assistance. Revenue contracts with or without errors will not be available for transfer accounting. Re-submit the TA update batch after the error is resolved.
To review the intercompany entry details, complete the following steps:
- Navigate to Run Reports in the Report section or Journal Entries in Workbench.
- Access and download the current period Accounting Report in the Report section or Journal Details using
- Identify the current period transactions with Account Type = Intercompany
RPRO-00691 - Error: Transfer validations failed
This error occurs when the TA update batch is not processed because at least one revenue contract in the batch did not pass the transfer validations. Access the Transfer Accounting Error Report to review the list of impacted revenue contracts and the respective validation errors.
RPRO-00693 - RC is locked - Unable to save or process the changes as another user is editing the RC
This error occurs when ZR cannot save or process the changes because another user is editing the same RC. Re-save your changes after the other user completes their changes.
RPRO-00694 - New Password is blank. Please re-enter the new password
This error occurs when ZR cannot process the password setup as the New Password field is blank. Please enter a new password to proceed.
RPRO-00695 - Confirm New Password is blank. Please re-enter the confirm password
This error occurs when ZR cannot process the password setup as the Confirm New Password field is blank. Please re-enter the password to proceed.
RPRO-00696 - New password cannot be the same as your previous passwords
The new password is the same as your previous passwords based on the configurations under the profile “LAST_N_PWD_CANNOT_BE_USED”. Please re-enter a new password to proceed.
See Configure Password Policy for more information on password configurations.
RPRO-00697 - New Password and Confirm New Password do not match
The New Password and Confirm New Password do not match. Please re-enter the passwords to proceed.
RPRO-00698 - New password does not meet the length requirements
The new password does not meet the length requirements based on the lookup configurations under “MIN_PASSWORD_LENGTH” and “MAX_PASSWORD_LENGTH”. Please re-enter a new password to proceed.
Navigate to Setup>Applications>Lookup to locate the above lookup. See Configure Password Policy for more information on password configurations.
RPRO-00699 - New password must contain both lower case and upper case
This error occurs when ZR cannot process the password set up as the new password must contain both lowercase and uppercase letters. Please re-enter a new password to proceed.
RPRO-00700 - New password must contain both letter and number combination
This error occurs when ZR cannot process the password set up, as the new password must contain both letters and numbers. Please re-enter a new password to proceed.
RPRO-00701 - Encountered internal error when resetting password - Please contact support team for further assistance
This error occurs while resetting the password. Please contact Zuora Global Support for further assistance.
RPRO-00702 - Invalid SO Num and/or SO Line ID
This error occurs during Significant Financing Component payment upload.
Scenario | Description | Recommended Solution |
---|---|---|
Missing SO Num and/or SO Line ID | Either SO Num or SO Line ID is null, for ZR to associate the payment record to the SO or SO Line, a valid reference must exist. |
|
SO Num or SO Line ID references not exist in the system | The SO Num and/or SO Line ID on the payment upload do not exist in the system. |
RPRO-00703 - Payment amount cannot be blank
This error occurs during Significant Financing Component payment upload.
Scenario | Description | Recommended Solution |
---|---|---|
Missing payment amount` | Payment amount is required in payment upload |
|
RPRO-00704 - Payment date cannot be blank
This error occurs during Significant Financing Component payment upload.
Scenario | Description | Recommended Solution |
---|---|---|
Missing payment date | Payment date is required in payment upload |
|
RPRO-00705 - Payment amount must be equal to the sell price of SO or SO Line ID
This error occurs during Significant Financing Component payment upload.
Scenario | Description | Recommended Solution |
---|---|---|
Incorrect payment amount |
Payment amount must be equal to the sell price in the system. If the payment schedule is on
|
|
RPRO-00706 - Payment upload is not processed as the principal amount is not populated
This error occurs during Significant Financing Component payment upload when the principal amount is
- Not derived properly, and/or
- Calculated at $0.
Scenario | Description | Recommended Solution |
---|---|---|
All SFC eligible lines with $0 SSP |
If SSP is configured to calculate the financing principal amount and all SFC eligible lines in the RC have $0 SSP, the principal amount is then calculated at $0, and the system is not further processing the interest calculation. |
Review and confirm the SSP in the RC
|
For other scenarios, such as the system encountering issues in deriving the principal amount, please contact Zuora Global Support for further assistance. |
See Significant Financing Component for additional information.
RPRO-00707 - Max. 240 characters are allowed
All field values, except the following fields, are limited to 240 characters. Update the field values and re-upload the file for further processing.
- COMMENTS
- DEF_SEGMENTS
- REV_SEGMENTS
- COST_DEF_SEGMENTS
- COST_REV_SEGMENT'
- QUOTE_NUM
RPRO-00708 - Max. 3000 characters are allowed in the "COMMENTS" field
The COMMENTS field is limited to 3,000 characters. Update the field values and re-upload the file for further processing.
RPRO-00709 - Non-English characters are not allowed
This error is applicable when the profile “UPLOAD_NON_ENGLISH_CHARS” is set to “N”.
Based on the configurations, non-English characters are not allowed in the upload. The acceptable characters are as follows,
!"#$%&''()*+,-./0123456789:;<=>'' ''?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~'
Scenario | Recommended Solution |
---|---|
Invalid field values with non-English characters |
|
Valid field values with non-English characters |
|
RPRO-00710 - Encountered internal errors
This error occurs when the system validates the non-English characters during the upload process. Please contact Zuora Global Support for further assistance.
RPRO-00711 - Missing values
This error occurs during Event upload processing and when multiple account segments are defined in the event upload template.The system will only process the event upload file when,
- All defined event account segment fields are blank, or
- All defined event account segment fields have account values
If the upload records are provided without any event account segment values, the events will be processed using the existing account segments on the SO line. If you expect the upload records to be processed against account segments different from the SO lines, you must provide all defined event account segments in the upload.
Please update the errored record(s) and re-upload the file for processing.
RPRO-00712 - Invalid number
According to the upload template setup in the system, the Input Value Type is set as Number. Only numerical values are allowed. Please update the errored record(s) and re-upload the file for processing.
The Input Value Type setup is under the Field Mapping tab within the file upload template. Navigate to the File Upload section and identify the type of the upload templates to view the setup accordingly.
RPRO-00713 - Invalid date
According to the upload template setup in the system, the Input Value Type is set as Date (DD-MON-YYYY or any specific format) in the Date Format field. Only date values are allowed. Please update the errored record(s) with the correct format and re-upload the file for processing.
Within the file upload template, the Date Format setup is under the Template Definition tab and the Input Value Type setup is under the Field Mapping tab. Navigate to the File Upload section and identify the type of the upload templates to view the setup accordingly.
RPRO-00714 - Multi-Org access restrictions
This error occurs when users do not have the access rights to the specific organization. Please work with your system administrator to obtain organization access or have the designated users with access rights to re-process the file upload.
RPRO-00715 - Duplicate INV_LINE_ID
The same INV_Line_ID is found in more than one record in the upload file. INV_Line_ID is a unique ID for an invoice line and duplicate ID is not allowed. Please update the errored record(s) and re-upload the file for processing.
RPRO-00716 - Invalid values in RSSP Min Type
Below are the three accepted values under “RSSP Min Type”. Please update the errored record(s) and re-upload the file for processing.
- CUSTOM
- LIST PRICE
- SELL PRICE
See Residual SSP derivation for more information.
RPRO-00717 - RSSP Min (%) must be BLANK
When RSSP Min Type is “CUSTOM”, RSSP Min (%) must be blank. Please update the errored record(s) and re-upload the file for processing.
See Residual SSP derivation for more information.
RPRO-00718 - RSSP Min (Amount) must have values
When RSSP Min Type is “CUSTOM”, RSSP Min (Amount) must have values. Please update the errored record(s) and re-upload the file for processing.
See Residual SSP derivation for more information.
RPRO-00719 - RSSP Min (Amount) must be BLANK
When RSSP Min Type is “LIST PRICE”, RSSP Min (Amount) must be blank. Please update the errored record(s) and re-upload the file for processing.
See Residual SSP derivation for more information.
RPRO-00720 - RSSP Min (%) must have values
When RSSP Min Type is “LIST PRICE”, RSSP Min (%) must have values. Please update the errored record(s) and re-upload the file for processing.
See Residual SSP derivation for more information.
RPRO-00721 - Both RSSP Min (Amount) and RSSP Min (%) must be BLANK
When RSSP Min Type is “SELL PRICE”, both RSSP Min (Amount) and RSSP Min (%) must be blank. Please update the errored record(s) and re-upload the file for processing.
See Residual SSP derivation for more information.
RPRO-00722 - Invalid values in RSSP FV Type
Below are the five acceptable values under “RSSP FV Type”. Please update the errored record(s) and re-upload the file for processing.
- CUSTOM
- LIST PRICE
- SELL PRICE
- HIGHER OF SP OR RSSP MIN AMOUNT
- RSSP MIN BASIS
See Residual SSP derivation for more information.
RPRO-00723 - RSSP FV (%) must be BLANK
When RSSP FV Type is “CUSTOM”, RSSP FV (%) must be blank. Please update the errored record(s) and re-upload the file for processing.
See Residual SSP derivation for more information.
RPRO-00724 - RSSP FV (Amount) must be have values
When RSSP FV Type is “CUSTOM”, RSSP FV (Amount) must have values. Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00725 - RSSP FV (Amount) must be BLANK
When RSSP FV Type is “LIST PRICE”, RSSP FV (Amount) must be blank. Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00726 - RSSP FV (%) must be have values
When RSSP FV Type is “LIST PRICE”, RSSP FV (%) must have values. Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00727 - Both RSSP FV (Amount) and RSSP FV (%) must be BLANK
If RSSP FV type is one of the following | Expected Values |
---|---|
|
No values under both RSSP FV (Amount) & RSSP FV (%) |
Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00728 - Invalid values in Alternate SSP Type
Below are the three accepted values under “Alternate SSP Type”. Please update the errored record(s) and re-upload the file for processing.
- CUSTOM
- LIST PRICE
- SELL PRICE
See Residual SSP derivation for more information.
RPRO-00729 - Alternate SSP (%) must be BLANK
When Alternate SSP Type is “CUSTOM”, Alternate SSP (%) must be blank. Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00730 - Alternate SSP (Amount) must have values
When Alternate SSP Type is “CUSTOM”, Alternate SSP (Amount) must have values. Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00731 - Alternate SSP (Amount) must be BLANK
When Alternate SSP Type is “LIST PRICE”, Alternate SSP (Amount) must be blank. Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00732 - Alternate SSP (%) must be have values
When Alternate SSP Type is “LIST PRICE”, Alternate SSP (%) must have values. Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00733 - Alternate SSP (Amount) and Alternate SSP (%) must be BLANK
When Alternate SSP Type is “SELL PRICE”, both Alternate SSP (Amount) and Alternate SSP (%) must be blank. Please update the errored record(s) and re-upload the file for processing. See Residual SSP derivation for more information.
RPRO-00734 - SSP Min Type/RSSP FV Type/Alternate SSP Type cannot be blank
RSSP Min Type/RSSP FV Type/Alternate SSP Type fields are Mandatory. Below are the acceptable values under each type. Please update the errored record(s) and re-upload the file for processing.
RSSP Min Type | RSSP FV Type | Alternate SSP Type |
---|---|---|
|
|
|
See Residual SSP derivation for more information.
RPRO-00735 - Start Date, End Date, Dr Activity Type and Cr Activity Type cannot be blank
For Waterfall type MJE, the below fields are mandatory and cannot be blank. Please update the errored record(s) and re-upload the MJE for processing.
Mandatory fields in Waterfall MJE upload:
- Start date
- End date
- Dr Activity type
- Cr Activity type
RPRO-00736/RPRO-00761 - Invalid currency code
The uploaded currency does not match with any currency code under the currency setup under Applications > Currency.
Scenario | Recommended Solution |
---|---|
Misspelled currency code |
|
New currency code |
|
RPRO-00737 - Number of decimals exceeds the setup limit
The uploaded amount has the decimal points exceeding the rounding setup under Applications > Currency.
Scenario | Recommended Solution |
---|---|
Incorrect decimal points in the file |
|
Incorrect rounding set up in the system |
|
RPRO-00738 - Invalid POB Template Name
The uploaded POB template name does not match with any POB templates in the system. Refer to Policies > Performance Obligations > POB Templates to view all the POB templates. Please update the errored record(s) and re-upload the file for processing.
See Create POB template for more information on POB template.
RPRO-00739 - Invalid Transaction Field Name
This error occurs under the POB assignment by item/sku process.The uploaded “Transaction Field Name” does not match with any attribute names in the system. The attribute name is used to derive the POB name in a revenue contract. Please update the errored record(s) and re-upload the file for processing.
See Define POB assignment rules for more information.
RPRO-00740 - Encountered internal error while locking the RC
This error occurs when locking the RC for edit by multiple users. When encountering this error, re-query this RC (Navigate to Workbench > Search > input the RC ID or other identifiers), confirm if the edit is made successfully. If the edit has not been properly saved previously, re-perform the same edit and save it.
If the error persists, please contact Zuora Global Support for further assistance.
RPRO-00741 - Encountered internal error - Please contact the support team for further assistance
Unable to complete event processing due to internal errors. Please contact Zuora Global Support for further assistance.
RPRO-00742 - Invalid syntax in SQL - Please review and fix the SQL statement
Invalid syntax found in the query. Please update and re-run the query. See Send database query from the user interface for more information.
RPRO-00743 - Encountered internal SQL error - Please contact support team for further assistance
Unable to generate the data due to internal SQL error. Please contact Zuora Global Support for further assistance.
RPRO-00744 - One Org is allowed in the upload
This error occurs when the upload file contains more than one Org. Only one Org is allowed per upload. Review and update the upload file to include a single value under the Org ID field and re-submit the file again.
RPRO-00745 - Encountered Internal Error
The upload process encounters internal errors. Please contact Zuora Global Support for further assistance.
RPRO-00748 - The event is not processed as 0% is not accepted on non-cumulative percent based event
The release percentage (REL_PCT) cannot be 0% for non-cumulative percent based events template.
Scenario |
Description |
Recommended solution |
---|---|---|
Release percentage should be more than 0% |
Incorrect percentage sent from the source system |
|
Release percentage should be 0% |
0% release presents no events are needed for revenue recognition. |
|
RPRO-00749 - The event is not processed as $0 is not accepted on non-cumulative amount based event
The release amount (REL_AMT) cannot be $0 for non-cumulative amount based events template.
Scenario |
Description |
Recommended solution |
---|---|---|
Release amount should be more than $0 |
Incorrect amount sent from the source system |
|
Release amount should be $0 |
$0 release presents no events are needed for revenue recognition. |
|
RPRO-00750 - The event is not processed as amount based event is not supported for recurring charges
This error is not applicable to standalone customers. Please contact Zuora Global Support for further assistance if this error exists.
For Zuora’s OTR customers, only percent-based and quantity-based events are supported for recurring charges. Amount-based events are not supported.
Scenario |
Recommended solution |
---|---|
The Recurring charge is incorrectly assigned to a POB template with amount-based event |
To correct the POB assignment (this will correct the future recurring charges coming to ZR),
For existing charges with an incorrect POB in ZR,
|
POB template incorrectly set up with the amount- based event |
To correct the POB template (this will correct the future recurring charges coming to ZR
For existing charges with an incorrect POB in ZR,
|
RPRO-00751 - Encountered Internal error - Please contact the support team for further assistance
This error occurs during the event collection. Please contact Zuora Global Support for further assistance.
RPRO-00752 - The event is not processed due to missing release percentage
The release percentage (REL_PCT) cannot be blank for percent based events template.
Scenario |
Description |
Recommended solution |
---|---|---|
Release percentage is blank |
Missing percentage from the source system |
|
RPRO-00753 - The event is not processed due to missing release amount
The release amount (REL_AMT) cannot be blank for amount based events template.
Scenario |
Description |
Recommended solution |
---|---|---|
Release amount is blank |
Missing amount from the source system |
|
RPRO-00754 - The event is not processed due to missing release quantity
The release quantity (REL_QTY) cannot be blank for quantity based events template.
Scenario |
Description |
Recommended solution |
---|---|---|
Release quantity is blank |
Missing quantity from the source system |
|
RPRO-00755 - The event is not processed due to incorrect signage on release amount
The signage of the release amount (REL_AMT) must be the same as the signage of the Ext Sell Price for amount- based events.
Scenario |
Description |
Recommended solution |
---|---|---|
Incorrect signage of release amount |
Incorrect amount sent from the source system |
|
RPRO-00756 - The transaction is not processed as the CM-RO is already cancelled
This error applies to OTR only and occurs when another transaction is generated to cancel the CM-RO again.
This is rare to encounter this error. Please contact Zuora Global Support for further assistance.
RPRO-00757 - The transaction is not processed as the referenced CM-RO does not exist in the system
This error applies to OTR only and occurs when the referenced CM-RO (referenced by Orig INV Line ID) does not exist in the system.
Scenario |
Description |
Recommended solution |
---|---|---|
Referenced CM-RO not in ZR inbound |
Billing transactions created in the source system but not yet integrated to ZR inbound |
|
Referenced CM-RO is stuck in inbound due to other errors |
The referenced CM-RO cannot be processed as it encounters other errors |
|
RPRO-00758 - Encountered Internal error - Please contact the support team for further assistance
This internal error occurs during the manual journal entry validations. Please contact Zuora Global Support for further assistance.
RPRO-00759 - Invalid SOB ID
This error occurs when the SOB ID value does not match with the setup in the system.
Recommended solution |
---|
|
RPRO-00760 - Encountered Internal error - Please contact the support team for further assistance
This internal error occurs during the manual journal entry validations. Please contact Zuora Global Support for further assistance.
RPRO-00762 - Invalid Activity Type
This error occurs when the activity type value does not match with any values set up under the lookup table. Navigate to Setups > Application > Lookups and search for the MANUAL_JOURNAL for the lookup table.
Scenario |
Recommended solution |
---|---|
Incorrect activity type on the journal entry |
|
A new activity type value is needed |
|
RPRO-00763 - Invalid Reason Code
This error occurs when the reason code does not match with any codes set up under the lookup table. Navigate to Setups > Application > Lookups and search for the MANUAL_JOURNAL for the lookup table.
Scenario |
Recommended solution |
---|---|
Incorrect reason code on the journal entry |
|
A new reason code is needed |
|
RPRO-00764 - Invalid Ex Rate Type
This error occurs when the Ex Rate Type value does not match with any values set up under the lookup table. Navigate to Setups > Application > Lookups and search for the MANUAL_JOURNAL for the lookup table.
Scenario |
Recommended solution |
---|---|
Incorrect exchange rate type on the journal entry |
|
A new exchange rate type is needed |
|
RPRO-00765 - Missing Ex Rate Date
This error occurs when the Ex Rate Date is not specified on the journal entry line.
Recommended solution |
---|
|
RPRO-00766 - Missing Ex Rate
This error occurs when the Ex Rate is not specified on the journal entry line. Ex Rate is a mandatory field in the journal entry.
Recommended solution |
---|
|
RPRO-00767 - Missing G Ex Rate
This error occurs when the G Ex Rate (Reporting Exchange Rate) is not specified on the journal entry line. G Ex Rate is a mandatory field when the Ex Rate Type is defined as “Users”.
Recommended solution |
---|
|
RPRO-00714 - The transaction line is not processed as the period is currently undergoing the close process
This error occurs when the period is undergoing the close process. If the period status is under PENDING CLOSE, the system does not process any transactions.
Scenario | Recommended Solution |
---|---|
The transactions should be collected in the current period |
|
The transactions should be collected in the next period |
|
RPRO-00769 - Payment upload is not processed as the Ext List price is not available in the RC for principal calculation
This error is applicable when the Ext List Price (ELP) is selected to calculate the Financing Principal Amount. Refer to Policies> Financing for the system configurations. See Significant Financing Component for additional information.
This error occurs during Significant Financing Component (SFC) payment upload when the ELP is not available on the SFC eligible line(s).
Scenario |
Recommended Solution |
---|---|
ELP is blank from the source system |
ELP is a required data when the SFC is configured to calculate based on ELP.
|
For other scenarios, such as the system encountering issues in deriving the principal amount, please contact Zuora Global Support for further assistance. |
RPRO-00770 - Payment upload is not processed as the Ext Sell price is not available in the RC for principal calculation
This is applicable when the Ext Sell Price (ESP) is selected to calculate the Financing Principal Amount. Refer to Policies> Financing for the system configurations. See Significant Financing Component for additional information.
This error occurs during Significant Financing Component (SFC) payment upload when ESP is not available on the SFC eligible line(s) due to internal errors. Please contact Zuora Global Support for further assistance.
RPRO-00771 - Payment upload is not processed as the SSP is not available in the RC for principal calculation
This error is applicable when the Standalone Sell Price (SSP) is selected to calculate the Financing Principal Amount. Refer to Policies> Financing for the system configurations. See Significant Financing Component for additional information.
This error occurs during Significant Financing Component (SFC) payment upload when the SSP is not available on the SFC eligible line(s).
Scenario |
Description |
Recommended Solution |
---|---|---|
SSP Error in the RC |
If the RC encounters SSP error, the system is unable to calculate the principal amount. You may locate the SSP error by the following methods:
|
|
RC is not eligible for allocation |
If the entire RC is not eligible for allocation, SSP will not be populated. The system is unable to calculate the principal amount |
As the SFC is configured to calculate based on SSP, and if the SSP is not available due to another user’s configurations, it is recommended that the company’s policy on how SFC should be calculated in these scenarios be reviewed and necessary changes made to on the configurations. |
For other scenarios, such as the system encountering issues in deriving the principal amount, please contact Zuora Global Support for further assistance. |
RPRO-10000 - The transaction is not processed as the same SO Line ID is already processed in a different org
This error is applicable for multi-org customers.
The specific SO Line ID is already processed under a different org in the system. The same SO Line ID cannot be processed other than the original org.
Scenario |
Recommended solution |
---|---|
The errored transaction has a correct SO Line ID but an incorrect org |
|
The errored transaction has an incorrect SO Line ID |
|
The previous processed transaction has an incorrect org |
|