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.

Support for Retention-Specific Payment Due Dates Under Ontario Construction Act

Aijaz SK-OracleJul 22 2025 — edited Jul 22 2025

Description:

We’re exploring an enhancement to the Track Draw Deadlines feature to better support retention-only draw compliance under the Ontario Construction Act and similar regulatory requirements across Canada.

What’s the challenge?

Under the Ontario Construction Act, retention payments (often 10%) are governed by different timelines than standard progress draws. Currently, the Track Draw Deadlines feature does not differentiate between these types of payments, which can create compliance risks or confusion for contractors and subcontractors.

What are we proposing?

We are considering adding the ability to:

  • Specify a secondary Payment Due Date (PDD) rule that would apply only to retention draws.
  • Introduce a new project-level setting to enable retention-specific PDD logic.
  • Allow base date + offset configuration for retention PDD, separate from standard draws.
  • Support contract-level overrides for retention deadlines, using the same permissions as current PDD overrides.
  • Ensure the new retention deadlines reflect in all UI pages, documents, and reports.

What we need from you

  • Would this capability help your team stay compliant with retention payment timelines?
  • How are you currently tracking different payment deadlines for retention draws (if at all)?
  • Would the ability to override this logic at the contract level be useful?

We’d love to hear your feedback and use cases to guide how we prioritize and build this feature.

Comments
Post Details
Added on Jul 22 2025
Submitted
0 people have voted for this idea
0 comments
62 views