Multi-channel network operations
ZMCN is the operating platform for a multi-channel network — channel lifecycle, content rights and settlement over one system of record. The partner share, the deduction and the payment can each be reproduced from the line they came from.
255 channels · 25.2K assets · 602.0K live claims
What the platform is reading
through 2026-09-26Read from the network’s own YouTube reporting, which runs a day or two behind; revenue is audited to T-15. What a period pays is not shown here — this page needs no sign-in, and that figure is negotiated against.
under the content owner
matched by Content ID
over 15 reported days
same window
where our content was claimed
Every figure on this site is read from the platform’s own dataset. Trailing windows count evaluated, still-tracked channels only: a channel whose partner granted no authorisation token is not measured at all, and tracking freezes on the day a channel is delinked.
The operator's problem
None of them are reporting problems. They are all the same problem: the number cannot be reproduced by the person being asked to accept it.
ZMCN ingests YouTube CMS, the Studio API, OTT distributors and DSP direct reporting into one period. A file whose identifiers do not map to a channel or an entity cannot merge until they are resolved — a job that needs review is held rather than half-applied, and the period cannot close over it. still held for exactly that reason.
The channel rate supersedes the partner rate, the incentive is added when the partner’s month clears the threshold, and the management fee is deducted last. ZMCN stores that working alongside the line, so finance, the partner and the auditor quote the same number.
Close the period, raise one invoice per partner, Finance reviews, the CEO signs, the run writes a bank file, and the UTRs that come back are matched against the invoices. Of imported payments are matched against what was owed, and anything that does not match is named — and they are shown as unmatched rather than absorbed.
The answer
Operations, partners, creators, finance and analysis each get a portal built for what they actually do — over the same data, with the same rules, settled by the same engine.
Network operations — ops managers and executives, and the super admins above them
The network's content partners — their admins and their finance contacts
Creators and channel managers working inside a partner
Finance managers and executives who own the network's books
Analysts and anyone who has to explain a number to somebody else
The settlement desk: royalty operations, finance, and the CEO who signs
Settlement
A percentage on its own is an assertion. ZMCN keeps every component of the resolution on the line, so the number can be re-derived years later without asking anyone what the rule was at the time.
A worked example. It follows one channel's revenue from what YouTube reported to what the partner is owed. No partner has been onboarded and no period has been closed on this platform yet, so these are illustrative figures showing the shape of the output — not live data. The channel, view and claim counts elsewhere on this site are real.
Revenue share · Lifestyle Lane
August 2026The share resolves to 72.00%, but Divo TV carries an unrecouped advance. The month recoups $6,656.59 against the balance and the payout is held at zero — held in full, never reduced to a part payment.
Pre-publish fingerprint gate
thresholds are configurableThe upload is terminated at the gate, an infringement alert is logged and the partner is notified.
Routed to the operations queue with a segment diff, matched asset and owning partner attached.
The band the requirements left open. We resolve it to review — a wrong auto-approve costs a CMS strike.
Published, and added to the network hash catalogue so the next upload is checked against it.
Matching is on video and audio segments. Never on the thumbnail, never on the title.
Rights
Every upload is fingerprinted against the whole network before it can reach YouTube. The verdict comes with the matched asset, the owning partner and the segments that matched, so a block can be argued with.
From period to payment
Six steps, each of which refuses to proceed until the one before it is clean.
Four sources per period. Rows whose identifiers cannot be mapped block the merge instead of quietly becoming someone else’s revenue.
Channel over partner, incentive on threshold, management fee deducted. The working is stored with the line.
Studio API against CMS on every line. A negative beyond $10 is flagged and has to be explained before the period can close.
One invoice per partner per period, carrying the share, the incentive, the fee, advance recoupment, TDS and GST.
Two approvals, in that order, neither skippable. An invoice can be held with a reason at either stage.
The run produces a bank file; returning UTRs are matched against invoices and classified as matched, partial, duplicate, over-payment or unmatched.
Reconciliation
how a returning payment is classifiedA UTR coming back from the bank is matched against the invoice it should settle and classified as matched, partial, duplicate, over-payment or unmatched. Each of the four that are not “matched” needs a different action, so they are never collapsed into one failed bucket.
No payment run has been made on this platform yet, so there is nothing to count here. When there is, this is where it will be counted.
Governance
Role-based access across the portals, tenant isolation on every query, PII masked by default with each reveal logged, and an append-only record of every mutation.
Eight roles, ten permission scopes, and two of them — retrospective moves and audit trajectory overrides — reserved to a super admin alone.
Every portal reads the network's own reporting — 255 channels, 25.2K assets and 602.0K live claims you can open one by one.
