Contract stage details report
Explore the detailed guide on Contract Stage Report in Recurly's Revenue Recognition user guide.
Overview
Required plan
This feature or setting is available to all customers on any Recurly subscription plan.
Definition
The Contract Stage Report displays sales order transactions that are currently stuck in the order stage. By default, the report includes the Processed Flag and Error Message columns. This guide details the steps to access, customize, and download the report to help diagnose and resolve transaction processing issues.
Guide
Accessing and configuring the report
To access and configure the Contract Stage Report:
- Navigate to the Report:
- Go to Reports and select Contract Stage Details Report from the menu.
- Access the Mapper:
- Locate and open the report's Mapper tool.
- Add Required Columns:
- Within the Mapper, select and add the specific columns (attributes) you wish to include. By default, the report includes the Processed Flag and Error Message columns.
- Run the Report:
- Click the Run button to generate the report.
- Optionally, click the Download button to save the report locally.
Report columns
- Processed Flag: Indicates whether a transaction has been successfully processed. A flag of "E" means the transaction has encountered an error, while "N" means it has not been processed.
- Error Message: Provides detailed information about any errors encountered during processing.
Contract stage errors
The following table outlines the possible error messages and their potential causes within the Contract Stage Report:
| Error Message | Possible Reason |
|---|---|
| Credit Account is Blank | The line stuck has no credit account assigned. Please check the configurations to add in the credit account. |
| Updated SO Amount is in different sign than previous Billed Amount | The line stuck is an SO update line that has the SO amount in a different sign than the original SO. Positive SO amount cannot be updated with a negative SO amount. |
| Error Processing So update | In case of CMR, when the SO update flows in if the SO update is less than the billed amount, we can get this error. |
| Updated SO Amount is less than Billed Amount | This error indicates that the billed amount is greater than the SO amount. Hence, until we update the SO amount or allow overage, we cannot process this line. |
| Bundle child updates are not allowed | Revenue Recognition does not allow bundle child line updates. |
| Error Loading SO Line | There could be many reasons for this error. |
| Debit Account is Blank | The line stuck has no debit account assigned. Please check the configurations to add in the debit account. |
| Pob Rule setup is missing in book | The line has no POB rules configured. Please check the POB rules section and configure the POB rules to process this line. |
| Pob setup missing for some lines in this contract in book | One or more of the lines in the contract are missing POB Rule configuration. Please check and update the POB rules for the concerned lines to process this line. |
FAQ
Q: What does “Debit Account is Blank” or “Credit Account is Blank” mean? A: A transaction line is missing its assigned debit or credit account. Review your configuration and assign the correct accounts to the affected lines.
Q: Why am I seeing “Updated SO Amount is in a different sign than previous Billed Amount”? A: The updated Sales Order (SO) amount uses a different sign (positive/negative) than the original billed amount. Ensure the updated SO amount uses the same sign as the original.
Q: What causes “Error Processing SO update”? A: This can occur (e.g., with a Credit Memo Request) when the updated SO amount is less than the amount already billed. Verify the SO update amount; it must not be less than the billed amount.
Q: What does “Updated SO Amount is less than Billed Amount” mean? A: The total billed amount exceeds the SO amount. Increase the SO amount to match or exceed the billed amount, or enable overage per your system policy.
Q: Why am I getting “Bundle child updates are not allowed”? A: Direct updates to bundle child lines aren’t permitted. Make updates on the parent bundle line instead.
Q: How do I fix “POB Rule setup is missing in the book” or “POB setup missing for some lines in this contract in book”? A: One or more lines do not have a Performance Obligation (POB) rule configured. Configure the appropriate POB rules for all missing lines. Note: if any line lacks a POB, the entire contract may remain stuck in Stage.
Q: What should I do for “Error Loading SO Line”? A: The associated SO line hasn’t successfully processed from the contract stage. Resolve the SO in Contract Stage first, then proceed with downstream documents.
Q: What does “Invalid Cost, SO not present in system” mean? A: The SO number in the cost file is incorrect or doesn’t exist. Verify the SO number and re-upload the file.
Q: Why am I seeing “Bundle child updates are not allowed” in the Cost Stage? A: The no-update rule for bundle child lines applies to costs as well. Update costs on the parent bundle line.
Q: How do I fix “Invalid Cost Type, Cost Type setup is missing”? A: The specified Cost Type hasn’t been configured. Add/configure the Cost Type correctly, then re-process.
Q: What does “Allocated Commission lines cannot be updated” mean? A: Lines with allocated commission are locked from updates. Use a new transaction or a reversal rather than editing the original line.
Updated 11 days ago