Project teams get clear status in Procore
Check compliance status where you manage work, and gate job site access without switching tools.
Integrations
Integrations that keep compliance in your workflow
PINS keeps compliance decisions in one place, while project and finance teams stay in the systems they already use.
Project teams see Approved or Not Approved inside Procore. Finance teams can control payment in Vista. Risk teams keep waiver history and policy checks in PINS.
Compliance where decisions happen
Keep teams in their workflow, without losing control
PINS keeps compliance decisions and history in one place, while project and finance teams stay in the tools they already use.
Finance can control payment in Vista
PINS writes compliance status back into Vista so payment controls happen in the accounting workflow, not in email threads.
Risk keeps the source of truth
Waiver history, exceptions, and policy checks stay tied to each third party so decisions stay consistent as volume grows.
Procore integration
COI compliance status inside Procore, tied to the commitment
PINS is available in a Procore side panel so project teams can see compliance status without leaving Procore. Commitments flow from Procore into PINS automatically. When a COI is reviewed and approved, status flows back in real time.
Vista integration
Compliance status written back to Vista for payment control
PINS tracks vendor and subcontractor compliance, then writes status back to Vista so AP and subcontract payment controls happen inside your accounting workflow. Supports AP Vendor and SL Subcontract levels, with flag-type and date-type compliance codes.
API integration
Sync COI compliance data into the systems you already run
The PINS API is used to sync compliance status and related COI data between PINS and your internal systems. Most teams use it for reporting, operational workflows, and downstream enforcement, while PINS remains the system of record for insurance decisions and history.
Access is provided with API credentials. PINS supports integration design, provisioning sandbox environments, and troubleshooting during implementation.
Common API use cases
- Sync vendor and third party compliance status into internal systems
- Feed dashboards and reporting (Power BI and other BI tools)
- Trigger operational workflows based on Approved or Not Approved status
- Keep waiver and exception history attached to each third party for reference
- Export structured compliance data for audits, renewals, and downstream workflows
Systems teams connect to PINS
- Power BI (reporting and dashboards)
- Workday
- Tyler (Munis and New World)
- COINS
- PropWorks
- Other internal data warehouses and finance or procurement tools
Credentials
Provided when API access is enabled
Primary use
Data sync between PINS and other systems
Implementation support
PINS assists with integration design and troubleshooting, including sandbox environments
Update frequency
Depends on integration design (real time or scheduled sync)
Stop Reviewing.
Start Approving.
