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-00600 - The transaction line is not processed as the SO RPRO-00601 - 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.

RPRO-00601 - 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.

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.

1. Navigate to Setups > Application > Profiles and search for the profile ENABLE_CSV_DATA_SANITIZATION. 
2. Hover the mouse above the ENABLE_CSV_DATA_SANITIZATION line.
3. Click the edit icon 
4. Select the applicable value from the System Level Value drop-down field.

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.

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.

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%. 

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.

 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.

RPRO-00609 - Discount charge line is not processed due to missing parent charge line in the system

 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 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.

Solution: 

Create a credit memo (Tran Type is CM-C) to reduce the billed quantity.

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.

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.

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.

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.

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.

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.

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.

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:

1. 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.

2. Reverse the $200 Invoice pending processing.
3. 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.

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.

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. 

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.

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. 

RPRO-00620 - The RORD line is not processed as the associated SO line in the system is canceled

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.

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).

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.

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. 

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

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 - 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.

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 - The transaction line is not processed as the "Tran Type" value is not valid

RPRO-00630 - The SO line is not processed due to missing SO line id

RPRO-00631 - The CST line is not processed due to missing Cost amount

RPRO-00632 - The CST line is not processed due to missing Cost Type Name

RPRO-00633/RPRO-00634 - 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.

RPRO-00635 - The transaction is not processed due to missing INV line ID

RPRO-00636 - The INV line is not processed as Orig SO line ID should be blank

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

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

RPRO-00639 - The SO line is not processed due to invalid impairment type values

See Contract Impairment for further details.

RPRO-00641 - The CST line is not processed as the cost management module is not enabled

RPRO-00642 - The SO line with cost amount is not processed as the cost management module is not enabled

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.

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.

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.   

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.

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.

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.

 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.

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.

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

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. 

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.

See Ramp allocation for more information about unit rate calculation.

RPRO-00664 - The transaction line is not processed due to invalid book ID

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.

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-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-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.

See Configure accounting structure for more details on the account segments set up.

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.

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:

1. Navigate to Run Reports in the Report section or Journal Entries in Workbench.
2. Access and download the current period Accounting Report in the Report section or Journal Details using . 
3. Identify the current period transactions with the below filters
4. Initial reporting flag = Y
5. 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:

1. Navigate to Run Reports in the Report section or Journal Entries in Workbench.
2. Access and download the current period Accounting Report in the Report section or Journal Details using .
3. Identify the current period transactions with the below filters
4. Initial reporting flag = Y
5. Schedule type flag = Revenue

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:

1. Navigate to Run Reports in the Report section or Journal Entries in Workbench.
2. Access and download the current period Accounting Report in the Report section or Journal Details using
3. 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:

1. Navigate to Run Reports in the Report section or Journal Entries in Workbench.
2. Access and download the current period Accounting Report in the Report section or Journal Details using
3. Identify the current period transactions with the below filters
   1. Initial reporting flag = Y
   2. 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:

1. Navigate to Run Reports in the Report section or Journal Entries in Workbench.
2. Access and download the current period Accounting Report in the Report section or Journal Details using
3. Identify the current period transactions with the below filters
4. Initial reporting flag = Y
5. 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:

1. Navigate to Run Reports in the Report section or Journal Entries in Workbench.
2. Access and download the current period Accounting Report in the Report section or Journal Details using
3. Identify the current period transactions with Account Type = Intercompany

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-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.

RPRO-00703 - Payment amount cannot be blank

This error occurs during Significant Financing Component payment upload.

RPRO-00704 - Payment date cannot be blank

This error occurs during Significant Financing Component 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. 

RPRO-00706 - Payment upload is not processed as the principal amount is not populated

This error occurs during Significant Financing Component payment upload. This occurs when the principal amount is not derived while processing the interest calculation from the payment upload.

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{|}~'

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,

1. All defined event account segment fields are blank, or
2. 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

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.
 

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 - Invalid currency code

The uploaded currency does not match with any currency code under the currency setup under Applications > Currency.

RPRO-00737 - Number of decimals exceeds the setup limit

The uploaded amount has the decimal points exceeding the rounding setup under Applications > Currency.

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-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. 

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.

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.

For Zuora’s order to revenue dataset, it is rare to encounter this error. Please contact Zuora Global Support for further assistance.

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.

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-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-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.