Skip to Main Content

Textura Payment Management

Announcement

We want to hear your ideas on how to enhance your experience using Oracle Textura! You can help promote an idea by:

  • Being as specific as possible about your request.
  • Clearly articulating the benefits. For example, improving integration or simplify a process.
  • Voting for suggestions you think should be implemented.

An Oracle Forums account is required to post. Visit Registering for Textura Forums page for more information.

Lock In GC and Sub CO's In the Draw Context They Are Created In.

Problem Statement

  • Many invoice documents include change order and/or adjustment sections that show current and prior-period activity.
  • Today, when a customer enters change orders or adjustments in the current period and then needs to reject the previous period (often due to owner requests), the system rolls the current-period change orders/adjustments back into the previous period.
  • As a result, users must manually “undo” the current-period entries, fix the previous period per the owner’s request, and then recreate those same change orders/adjustments in the current period—creating duplicate work and risk of error.

Proposed Solution

  • Decouple the handling of change orders and adjustments from prior-period rejection events.
  • Introduce an option or default behavior that preserves change orders and adjustments in the draw/period where they were originally created, even if a prior period is rejected/re-opened.

Business Impact

  • Reduces rework: Eliminates the need to undo and recreate entries after a prior-period rejection, saving time.
  • Improves accuracy: Minimizes data entry errors and period misclassification caused by manual redo steps.
  • Increases customer satisfaction: Aligns with common owner-request workflows where prior periods are frequently adjusted without disrupting current-period progress billing.
Comments
Post Details
Added on Mar 18 2026
New
0 people have voted for this idea
0 comments
50 views