# Who can license utility billing dispute records | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-utility-billing-disputes-records
Last updated: 2026-10-19

For utility billing dispute records, start with the finance director or controller, because property accounting runs utility recovery and knows where reads, allocation rules, tickets and credits live. Then reach the CEO, who can authorize a licensing discussion; at an owner-operator that is usually the owner. If the company manages buildings for third-party owners, each owner's consent may be needed for that owner's books, and if an outside vendor bills tenants, its contract may govern the records it holds.

This decision tree is part of the [utility billing disputes guide](/guides/workflow-utility-billing-disputes). It is written for property accounting advisors who know an owner-operator or property manager with years of utility recovery history. It is general information, not legal advice.

## The finance director is the guide, not the decision

In most property companies, utility billing sits with property accounting. The finance director or controller sets allocation rules, reviews disputed charges and approves credits above a threshold. That makes them the person who can answer every metadata question: how many disputes a year, whether old rule versions survive, which buildings are submetered and which are billed by formula.

What the finance director usually cannot do is commit the company to a licensing discussion about its records. That decision belongs to the CEO. And in property, there is a second layer: who the records belong to depends on who owns the buildings.

## Four forks to the right person

**Fork 1: whose buildings are they?**

- *The company's own portfolio.* The records are the company's. The signer is its CEO, often the owner at an owner-operator. Continue to fork 3.
- *Buildings managed for third-party owners.* The company may be a custodian. Many management agreements say each owner owns its property's books and records, with the manager keeping them on the owner's behalf. Note which buildings are managed and under how many agreements. Continue to fork 2.
- *Both.* Treat each portfolio separately; the owned buildings can move ahead while managed ones wait for fork 2.

**Fork 2: what do the management agreements say?**

- *The manager may use operational records for its own business.* The CEO decides, after counsel confirms the clause.
- *The owner owns the books, or the agreement is silent.* Each owner's consent may be needed for its buildings. [Who owns property management records](/questions/who-owns-property-management-records) explains the custody question in more detail.

**Fork 3: who bills the tenants?**

- *The company, using its own platform.* Continue to fork 4.
- *A third-party billing company.* Its contract may say what records it holds, for how long, and what the company can retrieve. Counsel checks it before those records are counted in. The regulatory filings can help here: in Texas, for example, it is the property owner who registers a property where tenants are billed for submetered or allocated water and sewer service, under billing practice rules set by the Public Utility Commission. That tells you whose obligation the billing is, even when a vendor runs it.

**Fork 4: who is the person you know?**

- *Finance director, controller or property accountant.* A sponsor. Ask them to bring in the CEO.
- *Platform administrator or billing analyst.* Admin access to the utility billing platform is not authority over the records in it. They can describe the system; they cannot open a licensing discussion.
- *CEO, or the owner-CEO.* The signer. Introduce them, with the finance director as sponsor.

## Three portfolio shapes, worked through

| Company shape | Who signs | Who else is involved | What stays open |
|---|---|---|---|
| Owner-operator of mixed-use buildings, own billing platform | CEO, often the owner | Finance director as sponsor | Rights review result, de-identification of tenant details |
| Third-party property manager with 40 owner clients | Manager's CEO | Each owner whose books are in scope; counsel on management agreements | Which owners consent, so which buildings are in scope |
| Multifamily owner using an outside billing vendor | CEO, often the owner | Counsel on the vendor contract | Which dispute tickets the vendor holds and returns |

The table is **Illustrative**. Real structures vary, and some owners hold each building in its own entity, which can add signers.

## What the records themselves reveal about ownership

Allocation formulas are the owner's rules. EPA describes a Ratio Utility Billing System as the owner splitting master-meter charges among units by a formula usually based on square footage, occupancy or other factors. The meter map, rule versions and approved corrections therefore record decisions made by or for the owner. That is why the building-ownership fork comes before anything else, and why [data rights](/proof/why-data-rights-matter) are reviewed before value is discussed.

Tenant and resident details are a separate question. Under the EU General Data Protection Regulation, personal data is any information relating to an identified or identifiable natural person, and comparable laws apply elsewhere. Resident names, unit numbers on statements and the text of complaints can fall within it. Rights review decides what is excluded or masked; the partner never handles any of it.

## Questions that close the tree in one call

1. Does the company own all the buildings it bills, manage some for others, or both?
2. Roughly how many management agreements, and does anyone know what they say about books and records?
3. Is tenant utility billing done in house or by a vendor, and since when?
4. Who is the CEO, and is the CEO also the owner?
5. Would the CEO take a short call about licensing operational records?

## Qualification and what stays unknown

An introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. 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 90% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application.

Unknown until SourceX reviews it: which buildings and years are in scope, what management agreements and vendor contracts allow, how tenant details are masked, buyer interest and any offer. The [system map](/guides/utility-billing-disputes-records-across-systems) shows whether the records join, and the [referral brief template](/resources/utility-billing-disputes-referral-brief-template) has a field for the signer this tree identifies. Property companies that fit are described on the [property management licensing page](/industries/refer-property-management-company-data-licensing); a sponsor-backed utility contractor is a different case, covered in [utility contractor private equity](/industries/utility-contractor-private-equity), and the utility side is on the [energy and utilities page](/industries/energy-and-utilities).

## Next step

> **Refer a company. Earn up to $100,000.** Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once the tree ends at a CEO who can speak for the buildings in scope, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you make the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://www.puc.texas.gov/industry/water/watersystems/submeter/
- https://www.epa.gov/system/files/documents/2023-08/ws-homes-TRM-10-MeteringTechSheet.pdf
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
