Skip to main content

Integration

AEC Integrations maintained

How Sage 100 Contractor and Oracle Textura Payment Management exchange data

5 types of data shared

Textura ERP Integration API

Direction:Both

Oracle Textura Payment Management reads construction contract data from Sage 100 Contractor through Oracle's Textura ERP Integration API. This adapter is the outlier of the fifteen: it is import-only. Subcontracts and subcontract change orders flow from Sage 100 Contractor into Textura, and nothing flows back — invoice, invoice-rejection, payment and document export are all unavailable, as are project and prime-contract-change-order import. A contractor on this pairing still posts approved invoices and payments into Sage 100 by hand. Oracle configures the integration as part of the subscription.

At a glance

How you get it
NativeOffered by Oracle
→

Sends to Oracle Textura Payment Management

  • Commitments & Contracts Listed by AEC Integrations
  • Cost Codes Listed by AEC Integrations
  • Change Orders Listed by AEC Integrations
←

Receives from Oracle Textura Payment Management

  • Invoices & Payments Listed by AEC Integrations
⇄

Syncs both ways

  • Documents Listed by AEC Integrations

Directory updates

Know when new tools and reviews land

AEC Integrations is live and still growing. Add your email for occasional updates as we expand the directory with new tools, integrations, and reviews.