Skip to main content

Using Siteline Without a Direct ERP Integration

Simplify your billing, stay in sync, and keep projects moving—no integration needed.

Jason Snow avatar
Written by Jason Snow
Updated over 6 months ago

Siteline makes it easy to get the full value of our platform with no integration required. Whether you enter data manually, use our import templates, or pull from GC portals, every option supports faster billing, fewer errors, and better visibility. You can mix and match methods to fit your workflow. This guide outlines all supported approaches and best practices.


Available Import & Setup Options


Option 1: Manual Project Setup

Best for: Teams that want a fast, flexible setup with minimal lift

  • Projects can be created directly within Siteline in under 10 minutes

  • Forms and vendors can be copied from past projects

  • Scales to any volume; some customers manage 1,000+ projects manually while still getting the full value of Siteline

💡 Best Practice: Use this method when project details are still evolving or when speed is the priority.


Option 2: Excel Template Imports

Best for: Larger project volumes, bulk onboarding, or teams that prefer spreadsheets

Siteline supports detailed Excel import templates for:

Import Type

Key Fields (Required *)

Projects

Project Name*, GC Project Number*, Project address*, General contractor*, GC Address, Start Date, Cost Type, Job #, Internal Project Number, # of pay apps previously submitted, Contract number, Contract date, day of month pay apps are due, QuickBooks job name, Quickbooks Customer Name, Tax group

SOVs

Line #, Description of work, Scheduled Value*, Cost Code, Scheduled value, Phase Code, Category

Vendors

Company Name*, Company address, Contact Name, Email*, Phone, Vendor ID, Compliance Type

AP Invoices

Project #, Vendor Name, Upper tier vendor name, Invoice Date, Invoice #, Invoice Amount*, Retainage held, Notes, Cost or description, Amount paid, Payment #, Last payment date

Job Costs

Project Number*, Project Name*, Cost to date*, Cost at completion*, Additional Committed Costs

Note: SOV imports can only be done during initial setup. Once billing begins, updates must be made manually or by creating a new SOV version.

💡 Best Practice: Excel imports are highly customizable and work well for initial implementation or ongoing maintenance, especially for customers managing large project volumes.


Option 3: Import from GC Portals

Best for: Staying aligned with GC data across the project lifecycle

  • Pull data from general contractor portals like Procore, Textura, and GCPay

  • Import includes SOVs, change orders, and other project metadata

  • Ensures Siteline mirrors what your GC expects to see

💡 Pro Tip: Use this method to keep change orders and values in sync, even when your ERP doesn’t.


Option 4: Siteline API (GraphQL)

Best for: Read-only reporting or building internal dashboards

  • Siteline’s API enables read-only access to key data across projects, billing, and vendors

  • Great for teams who want to pull Siteline data into reporting tools or internal systems

Note: The API cannot be used to write data into Siteline.

🔐 To Request Access: Contact your CSM or email [email protected].


Which Option Is Right for You?

Use Case

Recommended Option

Want a fast, flexible setup

Manual Project Setup

Need to onboard 10+ jobs at once

Excel Template Imports

Need to stay aligned with GC expectations

GC Portal Import

Want to report on Siteline data

Siteline API (Read-only)

Did this answer your question?