# Shared finance system referral ownership | SourceX

Canonical: https://refer.sourcex.si/guides/when-two-clients-share-the-same-outsourced-finance-system
Last updated: 2026-11-05

Treat the two clients as two separate decisions. Each client's own CEO decides whether that company talks to SourceX, and nothing you or the provider can see in one client's books, user lists or reports may be used to identify, describe or introduce the other. If the two belong to one corporate group, they share a single reward cap; if they are unrelated, they are separate companies with nothing linking their introductions. Check your professional rules client by client. This page gives no legal or professional-conduct advice.

It is written for fractional CFOs, outsourced controllers and accounting practice leaders whose firm runs, or works inside, one finance platform for several clients.

## Four ways two clients end up on one finance system

| Arrangement | Whose records sit in it | Who decides for each company | Reward cap |
|---|---|---|---|
| Sister companies on one consolidated instance | Each company's own ledger, plus the group's consolidation entries | Each company's own CEO | One cap for the whole group |
| Unrelated clients on your firm's practice platform | Each client's own books, administered by your firm | Each client's CEO, separately | Separate companies, separate caps |
| A client and one of its suppliers or customers on the same provider | Each its own books; each may appear in the other's ledger as a counterparty | Each CEO, separately | Separate companies |
| Two clients of an outside provider you do not run | Each client's own books, held by the provider as a service | Each CEO; the provider decides for neither | Separate, unless the two are one group |

Hosting is not ownership. SourceX's guide on outsourced IT puts it this way: "If an outside IT provider runs your systems, you still own your records in most cases. The provider may need to help with exports, and their contract may set terms for that work." That guide is about IT providers; it is a sensible starting point for an outsourced finance system too, and SourceX's rights review settles each real case. A provider's own procedures and internal records are a separate question for the provider's CEO. Its clients' books are never the provider's to offer, and SourceX's screening page lists material that belongs to a company's clients among the cases that are usually not a fit.

## What one client's books can show you about the other

A shared system leaks context in ordinary ways, none of them improper in itself:

- **Counterparty lines.** The other client, or a company that is not your client at all, appears as a vendor or customer in this client's ledger.
- **Intercompany entries.** Group companies post to each other, which reveals structure.
- **Administrator views.** Client lists, user counts, storage and years of history per client.
- **Cross-client reports.** Benchmarks or peer comparisons your firm builds from several clients' numbers.
- **Shared staff.** The same bookkeeper closes both sets of books and remembers both.

Your access to each set of books exists for that client's engagement. It is never a basis for picking out another company, describing it or introducing it, whether that company is your client or not. Professional codes treat this as confidentiality. The IESBA's international code, in the restructured text it approved in 2018, requires accountants to respect the confidentiality of information acquired through professional and business relationships and bars using it for their own advantage or a third party's, a duty that continues when the accountant takes on a new client (our paraphrase). The AICPA's Code places its Confidential Client Information Rule at section 1.700.001, treats client information that is not public as confidential, and notes that federal, state or local laws may be stricter (our paraphrase). Which of these, if any, binds you is a question for your own board, society or counsel.

SourceX draws the same line from its side. Its screening page counts an introduction kept from the decision maker among the poor fits, and its referral overview tells partners they do not need to export, upload or describe confidential records.

## The client boundary screening map

Two tiers. The pair questions are asked once for the two clients together; the client questions are asked twice, once per client, and the answers are never merged.

| Tier | Screen | What you record | Where the answer may come from | Stop sign |
|---|---|---|---|---|
| Pair | 1. Corporate relationship | Same group, unrelated, or trading partners | Public filings; each CEO | A group link inferred from entries you saw in the books |
| Pair | 2. Origin of the idea, for each client | What first made you think of this company | That company's CEO raising it; your own engagement with that company; public facts | The other client's books, a cross-client report or an administrator view: stop for that client |
| Client | 3. Your role toward this client | Every service you or your firm perform for it, and since when | Engagement letters | A role you have not checked with your board, society or counsel |
| Client | 4. Where you are licensed, and where this client is | States or countries on both sides | Your licenses; public facts | Assuming one client's answer covers the other |
| Client | 5. Whose records they are | The client's own work, its clients' material or the provider's | The CEO, in words | Logins, exports or samples |
| Client | 6. Earlier contact with SourceX | An application, account, correspondence or none | The CEO | Guessing |
| Client | 7. The CEO's yes | A dated answer from this company's CEO | That CEO alone | The other client's CEO, a director or the provider |
| Client | 8. Route | Paid, unpaid or hold | A dated answer from your board, society or counsel | No answer yet |

**Reading the map.** A stop at screen 2 removes that client from your list. It returns only if its CEO raises the subject with you unprompted, and even then nothing about the other client enters the conversation. Screens 3 to 8 can end differently for the two clients, and usually do.

## One group or two companies: what the cap and credit follow

**One group.** SourceX's screening page is explicit: "for the reward cap that whole group, parent and subsidiaries alike, is a single company." Each company's own CEO still decides for that company. Illustrative: two subsidiaries of one 600-person group, paid $400,000 and $250,000 between them, would share a single cap of no cap, not two. Whether one sister company's earlier contact with SourceX, or another partner's introduction of a sister company, changes credit for the next is not written into the terms; SourceX works it out in its duplicate review.

**Two unrelated companies.** Each introduction stands alone, and section 2 of the terms credits one partner per company. Illustrative: client A, paid $400,000, would carry a reward of $70,000 at the default the greater of $50,000 plus 5% and 15%; client B, paid $250,000, would carry $62,500. Neither figure affects the other, and neither is a forecast.

In both cases, section 4 says the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation," so each client receives the same amount whether or not a partner was involved.

## Role and jurisdiction checks, one client at a time

Restrictions on referral pay come in two kinds, and a shared platform makes both easy to blur.

**Role-specific.** Your firm may run client A's monthly close as its outsourced controller, act as client B's fractional CFO and perform a review engagement for a third client in A's group. Same firm, three roles, possibly three different answers about whether any payment is allowed.

**Jurisdiction-specific.** Client A may be in Texas and client B in Ontario, while you hold one license. The rule-maker, and the rule, can differ by client even when the platform is the same. If your firm audits or reviews either client, begin with the [audit separation map](/guides/how-to-keep-a-data-introduction-separate-from-an-audit-engagement).

Questions to put to your board, society or counsel, with the facts from screens 3 and 4 attached:

- Does serving both clients on one platform create a conflict I must disclose to either of them?
- May I raise SourceX with one client while I hold the other's information on the same system?
- If my firm hosts the platform, does a firm policy limit outside pay connected with any hosted client?
- Does a service my firm performs for a related company change the answer for this one?

Section 5 of the terms adds only that payment must also be lawful; SourceX does not rule on your professional obligations. The [ten-line review for accountants](/guides/before-an-accountant-accepts-a-referral-reward-check-the-applicable-rules) sets out the full check for one client, and the [jurisdiction issue register](/guides/when-local-professional-rules-affect-referral-compensation) covers networks where several people could be paid.

## Three client pairs on one platform (Illustrative)

Illustrative. Invented firms and companies; no case describes what any rule says.

**A. Sister companies.** Your firm closes the books for two operating companies of a 300-person group on one consolidated instance. The CEO of the first asks about SourceX and wants an introduction. Screen 1 records one group, so one cap. You raise nothing with the second company; if the first CEO wants the group involved, that conversation runs between the two CEOs. Your counsel's dated answer permits payment with written disclosure, and the first company applies itself after you have registered and signed the SourceX Channel Partner Agreement.

**B. Unrelated clients, one benchmark report.** While building a cross-client benchmark, you notice that a 220-person client has fourteen years of history on the platform. Screen 2 stops: that company stays off your list. Five months later its CEO, having read about AI data licensing, asks you about it unprompted. You answer from SourceX's published pages, never mention the platform view or any other client, and check your role as its fractional CFO with your society. The society's answer is still pending, so you take the unpaid path: you tell the CEO SourceX exists and the company applies on its own. Had you wanted to submit the introduction yourself and take nothing, the published terms say nothing about a partner declining a reward, so SourceX decides that case; the [unpaid introduction template](/guides/the-unpaid-introduction-path-for-a-finance-professional) starts with asking it in writing.

**C. A counterparty in the ledger.** Client A's payables show a 400-person logistics firm, not your client, as its largest supplier. It never enters your notes as a prospect. Nothing that appears in A's ledger leaves A.

## What this map cannot settle

- **It is not advice.** Only the rule-maker, or your counsel reading the rule for your facts, can say what applies.
- **Rules move.** Boards, societies and laws change; date every answer.
- **Provider contracts.** Export help, fees and notice periods sit in each client's contract with its provider, and they are that client's business.
- **Group structure.** Ownership is not always visible; when in doubt, ask each CEO rather than infer from the books.
- **Fit and credit.** SourceX decides both. Its published checks still apply to every client separately: 50 or more full-time employees at peak, the company's own records, the rights to license them, and location. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

**Method note.** The map, the four arrangements and the cases were assembled on 2026-10-27 from SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its screening page, its outsourced-IT guide and the AICPA and IESBA codes as excerpted. They organize questions and interpret no rule. For a vendor hosting many tenants, the [tenant-owner boundary map](/guides/when-an-it-vendor-hosts-data-for-many-clients) is the closer fit; for a group with entities on both sides of the published tests, see the [partition map](/guides/how-to-handle-a-mixed-eligible-and-ineligible-corporate-group); for a client whose operations run through outside vendors, the [vendor-and-owner question map](/guides/a-referral-summary-for-a-business-with-outsourced-operations).

## 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 client's row clears both tiers and its CEO wants the conversation, [register as a partner](/register), compare that one company with [who qualifies](/who-qualifies) and read the [program terms](/terms) before you submit anything in its name; other finance-advisor guides are in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/guides/scenarios/licensing-data-when-you-use-an-outsourced-it-provider
- https://refer.sourcex.si/how-it-works
- https://pub.aicpa.org/codeofconduct/ethicsresources/et-cod.pdf
- https://www.ethicsboard.org/_flysystem/azure-private/meetings/files/IEBSA-Restructured-Code-Approved-Text-Clean-final_1.pdf
