Skip to content

Construction Management integration

CMiC COI compliance integration

Put Pikorua Security's verdict on CMiC's own compliance codes, so a non-compliant subcontractor's vouchers go to Compliance Hold automatically. Pikorua Security reads vendors, subcontracts and requests for payment through CMiC's REST APIs, verifies each certificate and endorsement, and updates the date-sensitive insurance compliance codes that CMiC already enforces at the vendor, contract and invoice level.

CMiC logo

CMiC, Job 24-0117, Westlake Tower

Voucher AP-0093417

Compliance Hold

Compliance Hold: COI deficient

GL code expired 10/01/2026 and the completed operations code is not satisfied. Voucher moved to Deferred Vouchers.

Vendor
Keystone Mechanical LLC
Subcontract
24-0117-SC-031
Voucher amount
$212,880.00
Payment status
Compliance Hold (C)
Code GL expiry
10/01/2026
Code AI-CO
Not satisfied

Written by Pikorua Security Oct 16, 2026, 06:00 AM ET

Setup time
3 to 4 hours
Connection
CMiC REST API + OAuth 2.0 + webhooks
Fields synced
7 fields, 5 trigger events
Included on
Enterprise

Sync fields

What Pikorua Security reads from and writes to CMiC.

Filter by direction. Pikorua Security writes compliance fields only; amounts, approvals and banking details stay with your team.
Fields Pikorua Security syncs with CMiC
FieldDirectionWhat happens
Vendors (AP vendor master)CMiC to Pikorua SecurityVendor code, legal name and status. Pikorua Security matches on vendor code first, so renamed or merged vendors keep their history.
SubcontractsCMiC to Pikorua SecurityContract number, job, value and assigned compliance codes tell Pikorua Security which requirement template applies.
Requests for payment and vouchersCMiC to Pikorua SecurityOpen RFPs and vouchers are read so the hold report shows the dollars at stake for each deficiency.
Insurance compliance codes: expiry datesPikorua Security to CMiCGeneral liability, umbrella, auto and workers compensation codes receive the verified policy expiration. CMiC's date-sensitive logic does the rest.
Insurance compliance codes: satisfied statusPikorua Security to CMiCA code is marked satisfied only when the endorsement and the limit pass your exhibit, not when a certificate arrives.
Voucher payment statusCMiC to Pikorua SecurityPikorua Security reads Compliance Hold (C) and Normal (N) to confirm the hold took effect and to report how long releases take.
Vendor and subcontract eventsCMiC to Pikorua SecurityCMiC webhooks on new vendors and subcontracts start a compliance request right away.

Trigger events

When the certificate changes, CMiC changes with it.

Each trigger is a rule you can switch on, off or to notify-only per project, property or vendor tier.
How payment and access gates work
  1. Hold

    Insurance policy expires

    Then: The verified expiry on the code passes, and CMiC's compliance check moves new and unpaid vouchers on that subcontract to Compliance Hold (C) and the Deferred Vouchers tab.

  2. Hold

    Additional insured or primary and non-contributory wording missing

    Then: Pikorua Security marks the insurance code not satisfied even though the dates are current, so the subcontract fails compliance until the endorsement is verified.

  3. Hold

    Limits below the subcontract requirement

    Then: Code marked not satisfied with the shortfall in the code comment, and the project accountant is notified.

  4. Warn

    Policy expiring in 30 days

    Then: Verified expiry dates confirmed and the broker receives the day-30 request. No hold yet.

  5. Release

    Renewal verified

    Then: New expiry dates and satisfied status written to the codes. AP releases held vouchers to Normal (N) or Express (E) in the next payment cycle.

Setup

Live in 3 to 4 hours.

5 steps, done by your CMiC administrator and a Pikorua Security Admin together. Nothing to install on your servers.

CMiC logoCMiC REST API + OAuth 2.0 + webhooks
  1. 1

    Register the API client

    Your CMiC administrator registers Pikorua Security as an OAuth 2.0 client-credentials application in the identity provider CMiC uses, for example Microsoft Entra ID.

  2. 2

    Grant API security roles

    Assign a CMiC API Security role limited to reading vendors, subcontracts and vouchers and updating insurance compliance codes. Nothing else.

  3. 3

    Map compliance codes

    Match your existing insurance codes, such as GL, UMB, AUTO and WC, to Pikorua Security coverage lines. Pikorua Security creates no codes unless you ask.

  4. 4

    Match vendors and subcontracts

    Pikorua Security imports the vendor master and active subcontracts, proposes matches and lists vendors with no certificate on file.

  5. 5

    Confirm hold behavior

    With your AP lead, confirm which codes put vouchers on Compliance Hold, review the preview, and switch on write-back.

CMiC already knows how to hold a voucher

CMiC, the Toronto-based construction ERP, treats insurance, bonding and lien waivers as compliance codes that can be enforced at the vendor, contract or invoice level. Codes are date sensitive, subcontract codes default onto requests for payment and vouchers, and a voucher that fails compliance takes the payment status Compliance Hold (C) and moves to the Deferred Vouchers tab. That is a real payment gate. It is only as good as the dates and statuses typed into the codes.

Pikorua Security fills those codes from a verified packet. The expiry comes from the policy, not from a certificate that may list a stale term, and a code is marked satisfied only when the endorsement wording passes your exhibit: CG 20 10 and CG 20 37 for ongoing and completed operations, CG 20 01 for primary and non-contributory, CG 24 04 for waiver of subrogation.

Built for multi-company CMiC databases

Large CMiC customers often run several companies in one database, each with its own vendors, jobs and code sets. Pikorua Security maps requirement templates per company and per job type, so a public school job with a state-mandated owner indemnity and a private warehouse are checked against different rules even when the same mechanical subcontractor works on both.

Every write is made by the Pikorua Security API user and recorded in Pikorua Security's audit log with the rule that fired, which keeps internal audit satisfied and leaves your CMiC change history readable.

FAQ

CMiC connector questions.

Pikorua Security is compliance software. It verifies certificates and endorsements against your contract requirements; it does not sell insurance or give legal advice.

Does Pikorua Security release vouchers from Compliance Hold?
No. Pikorua Security updates the compliance codes. Releasing a held voucher to Normal (N) or Express (E) stays with your AP team, so a payment never goes out without a person in CMiC choosing to release it.
We authenticate CMiC through Microsoft Entra ID. Does that work?
Yes. CMiC's REST APIs use OAuth 2.0 client credentials issued by a third-party identity provider. Pikorua Security is registered as a client in your provider, and the secret or certificate expiry date is shown on Pikorua Security's Integrations screen so it never lapses unnoticed.
Which Pikorua Security plan includes CMiC?
CMiC and the other ERP connectors are part of Enterprise, which starts at $1,400 per month and includes a dedicated risk engineer who helps map your compliance codes.
Will it touch lien waiver or bonding codes?
No. Pikorua Security verifies insurance and only writes to the insurance codes you map. Lien waiver and bonding codes stay under your current process.

14-day free production trial

Connect CMiC during your 14-day trial.

Upload your current certificates, authorize CMiC, and see which vendors would be on hold today before you switch a single rule on.