Skip to main content

Siteline + Textura - Usage

Monthly workflow: prepare billing in Siteline and sync to Textura

Written by Bradley LaFave

Intended audience: accountant or project manager. This page walks through the recurring monthly workflow. For one-time account setup, see Setup.

Monthly workflow: Siteline β†’ Textura

Step 1: Import the project from Textura

Create a new project in Siteline.

Create a new project in Siteline

Choose to import from Textura.

Choose to import from Textura

Then search for the project name, number, or GC.

Search for the project

Siteline imports the project details and schedule of values. To learn more and see full instructions about importing, click here.

Step 2: Prepare the pay app in Siteline

Add billing amounts, attach forms, and complete your normal Siteline workflow.

Step 3: Sync the pay app to Textura

There are 2 primary ways to handle setting a pay app as synced on Siteline. If you add billing in Siteline and would like to update Textura, follow the steps below. If you've already updated billing in Textura and would simply like to mark the pay app as synced in Siteline, skip to Marking a pay app as synced without sending data.

Syncing billing values from Siteline to Textura

  1. In the Billing module, open the project and the pay app you would like to sync to Textura.

  2. Open the Invoice tab of the pay app.

  3. Click Sync invoice to Textura. This will sync the billing values you've entered for this month to the Textura draw request/pay app.

Sync invoice to Textura button

  1. Once you've clicked sync invoice, a dialog will appear until the sync is complete. Please do not navigate away from the page or close the tab during this process.

Sync in progress dialog

  1. Once the sync is complete, it will show a success dialog. You can then click Submit on Textura to complete the final submission in Textura.

  2. If the sync fails, a dialog will show up. If Textura gives us an error message explaining what went wrong, we'll show it on this dialog. Once you have corrected any issues, you can follow step 3 to continue the process. You can also click Sync again if there aren't corrections to be made.

Siteline will send:

  • Billing values

  • Retention

  • Lien waivers

  • Compliance documents

Marking a pay app as synced without sending data

This is for the case where you have to submit your billing on Textura directly (not recommended) or where a GC modifies your billing directly on Textura.

  1. In the Billing module, open the relevant project.

  2. Update the billing values of the relevant pay app on Siteline to reflect Textura.

  3. Click the menu icon on the right-hand side of the pay app you want to mark as synced.

Mark as synced menu option

  1. Select Mark as synced. The status of the pay app will update, but Siteline will not sync any information to Textura.

Step 4: Complete submission in Textura

Siteline then opens Textura in your browser. You must log in and complete:

  • Signatures

  • Notarization

  • Final submission steps

Step 5: If the GC rejects the pay app

If rejected in Textura:

  • Siteline automatically marks the pay app as Rejected

  • Displays the rejection reason

  • Resets the pay app so you can fix and resync

Example:

Rejection reason banner on a pay app

Pro tip: Siteline allows you to filter out to view Textura rejections only.

Filter billing homepage by Rejected in Textura status

View more information about rejections on the Troubleshooting page.


Syncing compliance documents to Textura

  1. In the Compliance module, open the project you'd like to sync compliance documents for.

  2. Go to the Requirements tab, then click the blue Queue to sync icon on each document that you'd like to sync. Documents you fill out or upload will be automatically queued.

  3. After adding all the documents to the queue, click the Sync to Textura button.

  4. Confirm the list of requirements to sync, then click the Sync to Textura button.


What Siteline imports from Textura

(During project setup)

When you create a project in Siteline and select "Import from Textura," Siteline pulls in:

  • Project details

  • Schedule of Values

  • Approved Change Orders

This import occurs only during initial project setup. Learn more about importing here.

What Siteline sends to Textura

A. Pay app / invoice values

Synced using the "Sync invoice to Textura" button. Values sent include:

  • Line-item billing

  • Retention

  • Line totals

  • CSV file used by Textura

If formatting issues occur (e.g., retention must be a whole number), Siteline will display the error Textura returns.

B. Compliance documents

Siteline sends:

  • The PDF document

  • Expiration date (if provided)

C. Lower-tier lien waivers

Siteline sends:

  • The PDF waiver

  • Vendor/tier mapping

What does not sync to Textura

These items must be handled directly in Textura:

  • Signatures

  • Notarization

  • Submission

  • GC comments

  • GC-modified invoice values

  • GC-modified SOV values

None of these flow automatically between systems. Learn more about syncing here.

What flows back into Siteline from Textura

Textura β†’ Siteline data flow is limited by design. Only two behaviors flow back:

1. Rejections

If the GC rejects your pay app, Siteline:

  • Marks the pay app as rejected

  • Displays the rejection message

  • Allows you to correct issues and re-sync

2. Manual "Mark as Synced"

If the GC adjusts your values and you do not want to override their changes, you can mark the pay app as synced in Siteline without re-syncing.

No other changes (e.g., GC-edited billing amounts or SOV changes) flow back automatically.

What must still be done directly in Textura

These steps cannot be done in Siteline and must be completed inside Textura:

  • Notarization

  • Submission signatures

  • GC comment review

  • Final approval steps

  • Reviewing multi-tier compliance from the GC side

  • Subcontractor-specific contract actions

  • Viewing GC-modified draw information

Siteline handles preparation. Textura manages legal submission.

Did this answer your question?