Intended audience: accountant or project manager. These are the day-to-day issues you'll handle yourself without needing engineering or IT help.
What happens when my pay app is rejected in Textura?
When you have a pay app rejected in Textura, Siteline will automatically revert the corresponding pay app.
Siteline has a status for rejected Textura pay apps. The Rejected in Textura filter on the billing homepage will show your rejected Textura pay apps:
Siteline will also show a banner with the reason for the rejection on the pay app overview:
How to fix it: read the rejection reason, correct the underlying values or documents in Siteline, and click Sync invoice to Textura again. Then return to Textura to complete signing, notarization, and submission.
Associate multiple contracts with one Siteline project
If you're working on a job that requires you to submit one invoice to your customer, but it must be filed as multiple different contracts or purchase orders in your ERP, you can link those projects together to create one SOV in Siteline.
Please note: This feature is available for customers using Sage 300, Spectrum, Vista, Acumatica, or Sage Intacct.
Look up one contract and use that to add the project to Siteline.
Once you've created the project, go to Settings, and scroll down to Integrations. Click + Link additional contract. If you have more than one ERP instance associated with Siteline, choose the integration from the dropdown. Once contracts have loaded, choose the one you'd like to add to the project.
At this time, you can re-rank the list of contracts to determine the default order of the line items. Note: Once you have saved this and made any changes to the order of the line items, any new line items will be added to the bottom of the SOV, by default.
Return to the SOV tab and click Import SOV (it may say something like Full SOV instead).
After reviewing the line items, click Import.
Once you've imported all of your line items, you can re-order them as you like. A new column will appear that lists which contract each line item is associated with.
After billing, when you're ready to sync your AR invoice to your ERP, click Sync in the top right corner while you're in a pay app. A dropdown menu will appear that will list the contracts associated with the job. Click on the contract you'd like to sync, and follow the usual steps to sync that to your ERP. Once complete, do the same for the other contracts that had billing associated with them in that pay app.
GC edits aren't appearing in Siteline
By design, only rejection events flow back from Textura to Siteline. If the GC edits your billing values, modifies the SOV, or leaves comments, none of those changes sync automatically.
What to do: review the changes directly in Textura. If you want to keep the GC's adjusted values without overriding them from Siteline, use Mark as synced in Siteline instead of re-syncing.
Notarization, signatures, or submission aren't completing
These steps cannot be done from Siteline — they must be completed directly inside Textura after you sync the pay app. Siteline opens Textura in your browser after a successful sync so you can finish the submission.
Sync error: missing role on the Siteline Admin user
If a sync fails with an error about permissions or project access, verify that your Siteline Admin user in Textura has both the Project Manager and Compliance Manager roles on the specific project. Missing either role will block the sync.
Retention value rejected as not a whole number
Textura enforces formatting rules on certain fields (for example, retention must be a whole number in some configurations). When formatting issues occur, Siteline will display the error Textura returns on the sync so you know exactly what to correct before re-syncing.
Incorrect pre-siteline billing / retention amounts
Issue
When importing a project into Siteline, pre-siteline billing and retention amounts are not correct.
Cause
Siteline needs each item in the reference invoice (invoice prior to importing the project into Siteline) to be in the Textura SOV, otherwise billing and retention values cannot be tracked over time. Because SOVs in Textura can be altered in many ways (eg: GC splits a line item into multiple new line items), sometimes the reference invoice does not match the SOV.
For instance:
Project starts with 1 big line item for $1,000,000
Subcontractor bills $10,000 on that item in the first month
GC splits the SOV into 10 line items, each with $100,000
Subcontractor imports the contract into Siteline
At this point, the reference invoice has 1 item and the SOV has 10 items, with no way to link them together. This will cause the pre-siteline billing and retention amounts to be $0.
Workaround
Siteline needs the reference invoice (invoice prior to importing the project into Siteline) to match the Textura SOV exactly (excluding change orders). Our recommendation is to bill in Textura directly, then reimport the project into Siteline after the draw is closed.
SOV import errors when Textura SOV does not match last Textura invoice
Issue
Unable to find invoice item item from draw number in the Textura SOV. The item was most likely removed or split into multiple items. Please refer to link for more information.
Cause
The last invoice in Textura must match the Textura SOV exactly (excluding change orders). Because SOVs in Textura can be altered in many ways (eg: GC splits a line item into multiple new line items), sometimes the last invoice does not match the SOV.
For instance:
Project starts with 1 big line item for $1,000,000
Subcontractor bills $10,000 on that item in the first month
GC splits the SOV into 10 line items, each with $100,000
At this point, the last invoice has 1 item and the SOV has 10 items, with no way to link them together. This will cause the SOV import to fail.
Workaround
Siteline needs the last invoice in Textura to match the Textura SOV exactly (excluding change orders). Our recommendation is to bill in Textura directly, then reimport the project into Siteline after the draw is closed.