Considerations

Review these considerations after using REST API to release revenue on performance obligations:

• If any of the required attributes for processing are missing or invalid, a validation error is displayed with required corrective action.
• The API rejects the additional subline if the referenced source document line isn’t in processed status.
• The unique identifiers for both the source document line and the additional satisfaction event must be valid in order to successfully process and release the hold.
• Required values for satisfied quantity, satisfied percent, or amount applied depend on the event type and satisfaction measurement model.

Business benefits include:

• Enables scalable, API driven integration for organizations managing high volumes of additional satisfaction events.
• Reduces manual effort and eliminates dependency on FBDI based import processes.
• Improves accuracy and consistency by enforcing required validations during event creation.
• Accelerates the release of revenue recognition holds when customer acceptance, proof of delivery, payment or service provisioning events are completed.
• Enhances auditability and operational efficiency through direct system to system processing.