Siteline simplifies how subcontractors prepare, track, collect on, and submit pay apps, even when the general contractor requires Textura. This guide explains how Siteline and Textura work together, what data flows between systems, how to set everything up, and how your monthly billing workflow changes.
How Siteline Works With Textura
Siteline becomes the single place where you prepare your monthly billing. When you’re ready, Siteline syncs your pay app values, lower-tier lien waivers, and compliance documents directly into Textura. You then log into Textura to wrap up the submission steps (signature, notarization, and any GC-specific final requirements).
What Siteline does:
Imports project and SOV from Textura when linking a project
Lets you prepare billing in Siteline
Syncs invoice values to Textura
Syncs compliance documents and lower-tier lien waivers
Displays rejection reasons when a GC rejects your pay app in Textura
What Textura does:
Requires the official submission
Handles signatures, notarization, and GC workflows
Houses the final approved pay app records
How Siteline + Textura Work Alongside Your ERP
Siteline, Textura, and your ERP work smoothly together—even though Textura does not integrate directly with ERPs. Each system has a specific role:
Your ERP is your internal financial system of record.
Siteline is where your team prepares accurate, GC-ready pay apps.
Textura is the GC’s billing portal where billing must ultimately match and be submitted.
Here’s how they fit together:
1. Textura holds the master contract and billing data for the project.
When a GC portal is involved, Textura becomes the source of truth for anything the GC requires, including:
Original contract value
Approved change orders
Current SOV structure
Prior billed amounts
Retainage rules
Your pay application must align to Textura’s structure and values, because that’s what the GC is enforcing.
2. Siteline is where your team builds the pay app.
Siteline sits between your internal processes and Textura, helping your team:
Prepare accurate billing
Track progress, quantities, and compliance
Mirror Textura’s SOV or use a more detailed internal SOV (Siteline > Textura mapping)
Siteline keeps the billing aligned to what Textura expects, while still supporting your internal level of detail.
3. Your ERP remains the internal accounting system of record.
The ERP is still used for:
Job cost tracking
AP/AR
Financial reporting
Revenue recognition
Once a pay app is submitted through Textura, the ERP can be updated with the final billed values.
Put together:
Textura = billing authority for the project
Siteline = billing engine + workflow control
ERP = internal financial record
Siteline keeps all three aligned so that what you bill internally, what the GC sees, and what your accounting team books all stay in sync.
Flexible SOV Structures (Detailed in Siteline; Simple in Textura or ERP)
Siteline supports the exact SOV values that Textura requires—but your internal team can still work from a more detailed, operational view in Siteline if that’s how you run jobs.
The key points:
The totals and contract values stay identical across Siteline and Textura.
Only the visual structure can differ—Siteline can show more detail internally, while Textura stays high-level.
This is common and fully supported.
Examples of Supported Visual Structures
In Siteline (Internal Operational Detail):
40–60 detailed production line items
Breakouts by cost code, crew, area, or phase
Used for tracking progress, quantities, materials, etc.
In Textura (GC-Facing Simplicity):
8–12 high-level divisions
GC’s contract SOV, which Siteline must match in total
Required structure enforced by the portal
In the ERP (Accounting-Level Summary):
One line per cost code or cost category
Simplified because ERPs typically don’t track production detail
What Siteline Handles Automatically
Rolls detailed internal line items into the high-level Textura structure
Keeps all totals identical to the GC’s SOV
Ensures billing values always match what the GC expects
Syncs the correct calculated amounts to Textura
Why Subs Use This Approach
Subs choose this structure when they want:
More internal visibility and job-level detail
Better production tracking
A workflow that aligns field, PMs, and accounting
Cleaner, simpler GC-facing billing
Siteline lets teams run jobs with the level of detail they need without breaking alignment with Textura.
Ideal Workflow Summary: Siteline + Textura
Here is the recommended best-practice workflow for subcontractors working in both systems:
Import the project and SOV into Siteline from Textura.
Siteline becomes the source of truth for building the pay app.Prepare your entire pay app inside Siteline.
Enter billing amounts, track change orders, generate forms, and attach documents.Sync billing, compliance, and waivers to Textura when ready.
Siteline sends structured data directly to Textura.Log into Textura to finalize submission.
Complete signatures, notarization, and GC-specific submission steps.If the GC rejects the pay app, Siteline updates automatically.
Fix the issue in Siteline > resync > finalize in Textura.
Repeat monthly with the same workflow.
Siteline handles preparation; Textura handles submission.
This workflow keeps your team working quickly in Siteline while satisfying GC portal requirements.
Monthly Workflow: Siteline > Textura
Step 1: Import the Project From Textura
Create a new project in Siteline.
Choose to import from Textura.
Then search for the project name, number, or GC.
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 to Textura
While in a pay app, click the Invoice tab and click Sync invoice to Textura. Full instructions are available here.
Siteline will send:
Billing values
Retention
Lien waivers
Compliance documents
If Textura returns an error, Siteline shows the message and how to resolve it.
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:
Pro tip: Siteline allows you to filter out to view Textura rejections only.
View more information about rejections here.
Setting Up Textura for Siteline
Before syncing pay apps to Textura, you must set up a dedicated Siteline Admin User inside Textura. The Siteline Admin User must have:
Project Manager role
Compliance Manager role
Email set to the Siteline-provided @vip.siteline.com address
This user must be added to every project you want to sync with Siteline. Learn more about setup here.
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
Learn more about rejections here.
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.
Best Practices for Syncing Siteline > Textura > Your ERP
This is the workflow that both sales and implementation teams can confidently recommend.
Best Practice #1: Sync to Textura First
Always push your finalized billing from Siteline >Textura before making updates in your ERP. Why?
Textura may enforce rounding rules or retention requirements.
GC edits or rejections should be addressed before invoicing in your ERP.
You want to avoid producing ERP invoices with values the GC hasn’t seen.
Best Practice #2: After Textura submission, enter/update the invoice in your ERP
Once you’ve completed your submission in Textura and you know the GC has accepted your billing values, update your ERP with:
Billed values
Retention
Change orders
Any adjustments (if the GC edited your pay app before approval)
Best Practice #3: Use Siteline as the operational source of truth
Siteline should be the system your PMs and billing team rely on for month-to-month billings because it contains:
The exact SOV you’re billing
Change orders
Compliance requirements
Lien waivers
All pay app documents
Any Textura rejection messages
Invoice history by pay period
Your ERP remains your financial record; Siteline is your project billing engine.
Best Practice #4: Avoid double-data entry by aligning timing
The cleanest sequence is:
Prepare full pay app in Siteline
Sync to Textura
Resolve any rejections
Submit in Textura
Update ERP based on approved billings
This ensures:
ERP always reflects accepted values
Pay apps are never out of sync
Textura and ERP stay aligned without rework
Teams follow one clean billing cycle
FAQ
Does Siteline notarize my documents?
No. Notarization must be done in Textura.
Do GC comments sync into Siteline?
No. Comments must be reviewed and responded to directly in Textura.
Can Siteline submit my pay app automatically?
No. Textura always requires manual submission.
Can GC billing updates sync back into Siteline?
No. Only rejection events flow back. All other adjustments must be handled manually.
Does Siteline support syncing lower-tier lien waivers?
Yes. Siteline can send lower-tier waivers directly to Textura.