A verified certificate tells you a vendor was insured on the day it was reviewed. It does not decide whether that vendor can win a bid, sign a contract, or get paid. NetVendor and myCOI (now illumend) both manage vendor insurance compliance; the difference is what each platform does with it.

myCOI specializes in certificates of insurance. Its Lumie AI reads certificates and endorsements, validates coverage, and alerts teams when policies expire. It does not offer vendor sourcing, bidding, or contract management.

NetVendor enforces vendor eligibility across the full vendor lifecycle. Non-compliant vendors are blocked at bid award and payment at the PO and invoice stage in every connected property management system.

That is the operational difference between NetVendor and myCOI. One validates the insurance document. The other governs the vendor.

‍

‍

NetVendor vs myCOI: How They Compare

myCOI is a COI tracking platform. It improves how insurance documentation is collected, validated, and monitored. It is not designed to govern whether vendors can proceed through sourcing, bidding, or contracting based on their compliance status.

NetVendor is built on Compliance-Led Vendor Management. It includes COI collection and compliance validation, then connects them to a control layer that determines vendor eligibility from onboarding through payment.

For property management portfolios where vendors operate across multiple properties and ownership structures, that distinction determines whether one standard governs every vendor decision or only the insurance record.

NetVendor vs myCOI: Key Differences at a Glance

This comparison shows what each platform covers at each stage of the vendor lifecycle, based on public information as of October 2026.

‍

‍

Bottom line: Choose myCOI if certificate and endorsement review is the job. Choose NetVendor if you need to govern vendors across sourcing, bidding, contracts, and payment in every connected system.

‍

‍

What NetVendor and myCOI Actually Do

NetVendor and myCOI both support vendor compliance, but they solve different problems. myCOI tracks and monitors insurance documentation, while NetVendor connects compliance to key stages of the vendor lifecycle and enforces vendor eligibility from bid award through payment.

NetVendor’s governance covers insurance verification, OFAC screening, W-9 collection, background checks, and license verification, all connected to sourcing, bidding, and contracts. That scope difference, not document-reading accuracy, is the real decision.

What NetVendor Is Designed to Do

NetVendor delivers Compliance-Led Vendor Management. It connects compliance requirements to sourcing, onboarding, bidding, and contracts, and enforces them across a property management portfolio.

Core capabilities include:

• Vendor onboarding and credentialing
• Certificate of Insurance collection and validation, including verification of policy endorsements, not just certificates
• Direct outreach to vendors and their insurance agents to obtain, verify, and correct compliance documentation
• Live, bilingual vendor support in English and Spanish
• AI-powered COI intake through the Intelligent Processing Center, verified by licensed compliance experts, for faster vendor approvals
• Enforcement of vendor eligibility at bid award and payment at the PO and invoice stage
• Vendor sourcing and competitive bidding from a network of 100K+ already-credentialed vendors
• Portfolio-wide compliance reporting
• Contract management with a central repository, approval routing, in-app eSignature, and renewal alerts
• Concurrent integration with Yardi, RealPage, AppFolio, Entrata, MRI, ResMan, and Rent Manager
• Vendor governance beyond insurance, including OFAC screening, W-9 collection, background checks, and license verification

This structure makes vendor compliance a control layer across the vendor lifecycle rather than a standalone tracking function.

‍

‍

How myCOI (now illumend) Approaches Vendor Compliance

myCOI rebranded to illumend in 2026. illumend is an AI-native rebuild of the same 16-year compliance business, powered by its Lumie AI engine. Lumie reads certificates and endorsements, surfaces hidden exclusions, flags gray areas, and returns an immediate compliance assessment, often within minutes. That document intelligence is genuinely strong. The distinction is scope: myCOI is not designed to govern the vendor across the full lifecycle, particularly in complex real estate portfolios where sourcing, bidding, and ownership-level rules also shape vendor eligibility.

Core capabilities typically include:

• COI collection and document intake
• Insurance verification and compliance validation
• Default six-email expiration sequence starting 14 days before a policy expires
• Compliance dashboards and status visibility
• AI (Lumie) that reads endorsements, detects hidden exclusions, and returns an immediate compliance score
• AI-drafted remediation guidance and contract-to-requirement extraction

illumend has also added live integrations with Yardi Voyager 7S, Procore, and CMiC. In Yardi Voyager 7S, compliance status can gate vendor payment. It does not integrate with RealPage, Entrata, or MRI.

‍

‍

Where COI Tracking Stops Short for Property Management Portfolios

COI tracking platforms like myCOI solve a well-defined and important problem, which is why many organizations continue to rely on them. Insurance tracking significantly improves visibility and reduces manual administrative work.

COI tracking governs the certificate, not the vendor. It does not source vendors, run bids, or manage contracts, so eligibility decisions happen in other systems. Renewal handling differs too. myCOI’s default expiration sequence begins 14 days before a policy expires. NetVendor sends automated expiry notifications, and when coverage is missing or lapsing, NetVendor compliance specialists contact the vendor’s insurance agent directly, so vendors don’t chase their own COIs.

Vendor Compliance vs Vendor Management: Why the Distinction Matters

Vendor credentialing and vendor management are often treated as interchangeable, but they solve different problems, which is why compliance alone isn’t enough to manage vendor risk.

Vendor credentialing answers a documentation question. Are the required insurance policies and licenses in place? Vendor management answers an operational question. Should this vendor be eligible to win a bid or get paid?

That distinction becomes critical at scale. A vendor can be fully credentialed on paper and still enter workflows too early, operate inconsistently across properties, or bypass controls tied to sourcing and bidding.

Vendor credentialing verifies documentation. Vendor management controls whether a vendor can be awarded a bid or get paid.

‍

‍

What Changes When Vendor Lifecycle Control Is Centralized

Vendor lifecycle control is the mechanism behind Compliance-Led Vendor Management: vendor requirements are verified at onboarding, monitored continuously, and enforced at every governed action, including bid award and payment. It ensures compliance is not just verified at a point in time, but holds for as long as a vendor works in the portfolio. NetVendor applies vendor lifecycle control through its Bidding and Contracts lifecycle: contracts are created from a bid award start with a compliant vendor, with bid history and contract approvals, signatures, and changes all documented and exportable.

When vendor lifecycle control is centralized, compliance shifts from a passive checkpoint to an active control system.

Instead of verifying documentation after vendors are already in motion, organizations establish clear rules that determine whether vendors can proceed at all. That shift changes how risk enters the portfolio.

With lifecycle control in place, organizations gain:

• Non-compliant vendors stopped at every governed action, not discovered after the fact
• Reduced exposure from expired or incomplete insurance
• Portfolio-wide visibility into vendor status
• Standardized vendor processes across assets

Those controls hold across complex portfolios because compliance models are configured by owner, property, and vendor type, set once at HQ and enforced automatically, with no front-line involvement. The result is not just better compliance tracking. It is a fundamentally different operating model where compliance governs vendor participation.

Portfolio-Level Impact: What Happens at Scale

At a single property, a compliance issue can feel isolated. At portfolio scale, those same issues begin to compound.

Vendors often operate across multiple properties, sometimes under different ownership structures or compliance requirements. Without centralized control, inconsistencies begin to appear. The same vendor may be approved in one location and non-compliant in another. Duplicate records emerge. Standards drift.

NSA Storage (now part of Public Storage) faced exactly this compounding dynamic during rapid expansion. COIs, W-9s, and renewals for its 2,000+ vendors were tracked through spreadsheets and scattered documentation, even with a dedicated compliance role, and an audit surfaced gaps. After bringing its vendors into one system with NetVendor, NSA Storage keeps 1,100+ properties audit ready. As Jennifer, NSA Storage’s Accounts Payable Manager, put it, “The stress we used to feel around compliance is completely gone.”

Over time, risk is no longer tied to a single vendor or property. It becomes aggregated exposure across the entire portfolio.

This is where lifecycle control becomes less of an operational improvement and more of an executive requirement.

Operational Consequences of Limited Lifecycle Control

When lifecycle control is limited, teams are forced into reactive workflows.

Compliance issues are discovered after the fact rather than prevented up front. Staff spend time following up with vendors and insurance agents instead of enforcing consistent standards. Data becomes fragmented, and visibility depends on manually reconciling multiple systems.

These challenges often show up as:

• Delayed detection of compliance issues
• Manual coordination across vendors and agents
• Inconsistent enforcement across properties
• Disconnected vendor records across systems

Berger Communities, managing 60 communities across Pennsylvania, Delaware, and Maryland, described their pre-NetVendor process plainly. Kristina Super, Director of Strategic Services, said the accounting team “had to manually track compliance using a binder” and that “it was insane that in 2018, we didn’t have an automated system.” After implementing lifecycle control, Berger achieved a 99% risk reduction, 100% site-level enforcement with vendors blocked from payment if non-compliant, and streamlined onboarding for new properties.

Horizon Realty Advisors, a multifamily and student housing operator managing 600+ vendors, had left compliance tracking to a manual process in its AP department. With compliance enforced through NetVendor, Horizon saves 30 hours a week and $30K+ in annual labor.

What begins as operational friction eventually turns into portfolio-level risk exposure.

‍

‍

Frequently Asked Questions About NetVendor vs myCOI

What is the main difference between NetVendor and myCOI?

myCOI specializes in certificates of insurance, with strong AI review of certificates and endorsements. NetVendor governs the vendor across the full lifecycle, blocking non-compliant vendors at every governed action from bid award to payment, and adds sourcing, bidding, contracts, OFAC screening, W-9 collection, and background checks.

Is illumend the same as myCOI?

Yes. myCOI rebranded to illumend in 2026, the same 16-year certificate-of-insurance compliance business rebuilt around an AI engine called Lumie. Legacy myCOI domains still resolve, and illumend.ai is the canonical site. illumend has added integrations with Yardi Voyager 7S, Procore, and CMiC, while its focus remains certificate and endorsement compliance.

Is NetVendor or myCOI better for property management companies?

It depends on the operational need. myCOI is a strong fit for teams focused on improving COI tracking workflows and compliance visibility. NetVendor is the better fit for property management companies that need to control vendor eligibility across multiple properties, PMS platforms, or ownership structures where compliance gaps compound at scale.

Does myCOI manage the full vendor lifecycle?

No. myCOI focuses on COI collection, AI insurance verification, and ongoing compliance monitoring, with no vendor sourcing, bidding, or contract management. NetVendor covers sourcing, onboarding, credentialing, bidding, and contracts, adds OFAC screening, W-9 collection, and background checks, and enforces compliance from bid award through payment.

What PMS integrations does NetVendor support compared to myCOI?

NetVendor integrates concurrently with Yardi, RealPage, AppFolio, Entrata, MRI, ResMan, and Rent Manager, and stops non-compliant vendors at the PO and invoice stage in each. myCOI (illumend) integrates with Yardi Voyager 7S, where compliance status can gate payment, plus Procore and CMiC. It does not integrate with RealPage, Entrata, or MRI.

What happens when compliance gaps are monitored but not enforced?

Coverage gaps surface only after they matter. Across a portfolio, one non-compliant vendor working at 10 or 20 properties creates aggregated liability, including denied claims and uninsured incidents. Enforcement at bid award and payment closes that gap before a vendor be awarded a bid or get paid.

What is Compliance-Led Vendor Management?

Compliance-Led Vendor Management is an operational model where compliance is the condition for vendor participation, not a tracking function that runs alongside it. Non-compliant vendors are blocked at bid award and payment at the PO and invoice stage. NetVendor enforces this model across sourcing, bidding, contracts, and payment.

Choosing Between Monitoring Compliance and Controlling Vendor Risk

NetVendor vs myCOI is not just a feature comparison. It is a decision about how vendor risk is managed.

The myCOI platform focuses on insurance tracking, document automation, and compliance monitoring. It provides visibility into whether documentation is current.

NetVendor delivers Compliance-Led Vendor Management. It verifies vendor requirements at onboarding, monitors them continuously, and enforces them at bid award and payment across every connected PMS.

For organizations primarily focused on improving workflows for COI collection, organization, and validation, myCOI can be a strong fit. For organizations looking to control vendor eligibility across complex portfolios and multiple systems, NetVendor addresses a broader operational need.

At portfolio scale, the decision comes down to a single question: Are you monitoring compliance status or governing the vendor across the full lifecycle?

If you're evaluating vendor compliance software across multi-PMS or multi-ownership portfolios, schedule a demo to see how NetVendor enforces vendor eligibility across every connected system and how it fits your portfolio's compliance requirements.