# Audit status in data referrals: a claims checklist | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-discuss-audit-status-without-overstating-certifications
Last updated: 2026-11-04

Say only what the issuing document says, or what SourceX's own trust center says, and give the date. On 27 October 2026 that page listed a SOC 2 Type II report and ISO/IEC 27001 and 27701 certifications as in progress, with none issued. So "certified", "compliant" and "audited" are all overstatements about SourceX today. Use each instrument's own noun: a service auditor issues a report, and an outside certification body issues a certificate. When a founder asks, link the page, state the date and let SourceX answer anything beyond it.

Audit wording drifts in one direction. "In progress" becomes "underway", then "nearly there", then "certified", usually without anyone intending to mislead. A VC operating partner who introduces companies sits in the middle of that drift, so the checklist below is built to stop it at the partner.

## What "are they certified?" is usually asking

A founder who asks this before agreeing to an introduction usually wants one of four things:

- **Independent assurance.** Has anyone outside SourceX examined its controls?
- **A procurement gate.** The company's own vendor policy may require an issued report before a vendor holds confidential data.
- **Your judgment.** Is the partner vouching for SourceX?
- **Their own homework.** Will the company's own audit report, or lack of one, decide whether it qualifies?

Each has a short, true answer, and none of them is "yes, they're certified."

## A report, a certificate and work in progress are different things

The two instruments founders ask about are not the same kind of document, and the words that fit one do not fit the other.

AICPA describes SOC 2 as reporting on an examination of controls at a service organization relevant to security, availability, processing integrity, confidentiality or privacy. The deliverable is a report from a service auditor; in AICPA's illustrative Type 2 report, it contains management's assertion, the description of the system, the auditor's report and the tests of controls with their results (a paraphrase of AICPA's materials). That is why SourceX's trust center speaks of a report "not yet issued" rather than a certificate.

ISO says it does not certify anyone and does not issue certificates; certification is done by external certification bodies, so no company is certified "by ISO" (a paraphrase of ISO's certification page). An ISO/IEC 27001 claim therefore needs a named certificate from an outside body, with a scope and a date.

| Word or phrase | What it asserts | True of SourceX on 27 Oct 2026? |
|---|---|---|
| "In progress" | Work has begun and nothing has been issued | Yes, for all three items on its trust center |
| "Report issued" | A service auditor has delivered a report on a described system | No: the report is listed as not yet issued |
| "Certified" | An external certification body has issued a certificate | No: both certifications are listed as not yet issued |
| "ISO certified" | Wrong on its face, since ISO certifies no one | No |
| "Compliant" | Nothing specific: no instrument, scope or date | Do not use it |
| "Controls in place today" | The specific controls SourceX lists as current | Yes, quoted from its list with the date |
| "Independent security assessments" | An item SourceX lists under planned | Planned only |

## The verified security-claim checklist

Run any sentence about security status through eight checks before it leaves you, in writing or aloud.

1. **Whose claim is it?** SourceX's status is SourceX's to state. A company's status is the company's. An Acquisition Partner's is not public, so it is nobody's to repeat.
2. **Is there a document behind it?** An issued report, an issued certificate, or the owner's own published status page.
3. **Does the noun fit the instrument?** A report for SOC 2, a certificate for the ISO/IEC standards.
4. **Is it issued, in progress or planned?** Say which, using the owner's word.
5. **Is the scope stated?** Which entity and which system. A report or certificate speaks for what it covers and nothing wider.
6. **Is it dated?** Status changes; an undated status sentence goes stale the day it is sent.
7. **Quoted or paraphrased?** Prefer a link and a short quotation to your own summary.
8. **Would it survive forwarding?** If the sentence turns false once its date or link is stripped off, rewrite it until it does not.

Applied to twelve sentences partners actually reach for, the checks give three verdicts.

| Sentence | Verdict | Which check it fails or passes |
|---|---|---|
| "SourceX is SOC 2 certified." | Never | 3 and 4: wrong noun, wrong status |
| "SourceX is ISO certified." | Never | 3 and 4: ISO certifies no one, and nothing is issued |
| "SourceX is fully compliant." | Never | 2 and 5: no instrument, no scope |
| "They'll have it all by next quarter." | Never | 2: a forecast nobody has published |
| "I've looked at their security and it's solid." | Never | 1: you tested nothing |
| "Your own audit report will help you qualify." | Never | 1: not one of SourceX's screening checks |
| "Their trust center lists an audit report and two certifications as in progress, none issued, as of 27 October 2026." | Say it, linked | Passes all eight |
| "Nothing is delivered until the company has signed the Master agreement and the deal's Confirmation and SourceX gives the go-ahead." | Say it, linked | A control SourceX lists as in place today |
| "Companies only see their own records on SourceX's platform." | Say it, linked | Another control on SourceX's current list |
| "Their questionnaire answers and a DPA where applicable are shared privately after review." | Say it, linked | SourceX's own description of its procurement materials |
| "Independent security assessments are on SourceX's planned list." | Say it, dated | Status stated in SourceX's word |
| "Ask their security contact; I'll send you the link." | Say it | Routes the question to the owner |

## What is known, what depends on review and what nobody has checked

**Known, from SourceX's own pages.** The status of the audit report and the two certifications; the controls SourceX lists as in place today, among them organization-level access, private storage with expiring links, agreement before delivery and a full audit trail; and, from section 7 of the program terms, that partners never receive applicant documents.

**Conditional on review.** Security questionnaire responses, a business continuity overview, the incident escalation process, contract templates and a DPA where applicable are shared privately after review. Sensitive reports go only to signed-in accounts after a SourceX administrator approves the request.

**Not checked by anyone in this conversation.** The partner has not tested a single control, and the company's own controls are not under discussion until it applies. No date for issuing the report or the certifications has been published, so none can be repeated.

## A procurement question from a founder's security lead (Illustrative)

Illustrative: the firm, its people and its vendor policy are invented, and nothing here predicts a result.

A 300-person freight audit and payment firm is in a fund's portfolio. Its security lead writes to the fund's operating partner: "Our vendor policy requires an issued audit report before a vendor holds confidential data. Is SourceX audited?"

The partner's answer, in full:

> On 27 October 2026 SourceX's trust center listed its SOC 2 Type II report and its two ISO/IEC certifications as in progress, with none issued; here is the link, and please check it again before you rely on it. Nothing of yours would be delivered before an agreement is signed, so your policy would apply at that point and you decide then. Their security contact can answer anything else directly. If your policy means waiting, tell me and I'll note why and stop.

The security lead replies that the firm will wait until a report is issued. The partner records "declined until an audit report is issued, per vendor policy", with the date, and does not chase. That is a legitimate decline, and the bounded answer is what made it possible to accept it cleanly.

A founder's own audit status is a different question. SourceX's screening looks at size at peak, years of records, rights and a CEO who wants the conversation, not at certifications; [whether a company needs an audit report to license data](/questions/do-we-need-soc-2-to-license-data) answers that side in full.

## Where overstatement creeps back in

- **Forwarding chains.** Each retelling drops a qualifier. Send the link and the date, never a paraphrase that can be paraphrased again.
- **Status moves.** SourceX's trust center lists planned items beside current ones. A correct sentence today can be wrong next quarter, so re-check before reuse.
- **Investor materials and referral notes.** A fund's internal memo about SourceX as a business and a note to a founder about a referral are different documents with different readers. Keep status claims out of both unless they are quoted, linked and dated.
- **Reassurance about outcomes.** The same discipline applies to money: [discussing a partnership without promising a payout](/guides/how-to-discuss-a-potential-partnership-without-promising-a-payout) covers the reward side.
- **Contract terms are not audits.** [How data is secured in licensing](/proof/what-is-data-security-in-licensing) describes contractual protections. A protection in a contract is not an issued report, and neither stands in for the other.

**Methods note.** The checklist and the twelve sentences were built on 27 October 2026 from SourceX's trust center, section 7 of the program terms, SourceX's screening guidance and home page, AICPA's SOC 2 materials and ISO's certification page. They do not measure how often partners overstate status or how founders respond to a bounded answer; no such figures have been published. To test the checklist, record every security-status sentence you send for a quarter and score each against the eight checks.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When a founder has SourceX's dated status in hand and still wants the conversation, [register as a partner](/register), run the company through [who qualifies](/who-qualifies) and read [the terms](/terms) before submitting the introduction. Platform teams can find the portfolio side in the [overview for venture platform teams](/for/venture-platform-teams), and more objection guides sit in the [guide library](/guides).

Repeating SourceX's audit status accurately is part of referral work; weighing SourceX as an investment is a separate exercise, and materials for it can be requested through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://sourcex.si/trust
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/
- https://www.aicpa-cima.com/cpe-learning/publication/soc-2-reporting-on-an-examination-of-controls-at-a-service-organization-relevant-to-security-availability-processing-integrity-confidentiality-or-privacy
- https://www.aicpa-cima.com/resources/download/illustrative-service-auditors-soc-2-r-type-2-report
- https://www.iso.org/certification.html
- https://sourcex.si/investors
