Distributor Integration: How Your Money Really Connects in 6 Steps
Distributor Integration: How Your Money Really Connects starts with understanding what the term actually means in practice. When you upload a release to DistroKid, TuneCore, or CD Baby, you create a technical relationship between your catalog and dozens of DSPs. But that relationship is one-way: your distributor sends files and metadata downstream, collects payments from Spotify and Apple Music, then pays you. What most artists never build is the reverse connection, the system that pulls sales data back, matches it against other revenue sources, and shows you the complete picture of where your money comes from. That reverse connection is distributor integration, and without it you are managing your catalog blind.
What distributor integration actually connects
Distributor integration is three separate data flows working together. First, sales reports flow from DSPs to your distributor. Spotify generates a report of streams for your ISRC codes, sends it to your distributor, and your distributor aggregates it with reports from Apple Music, YouTube Music, and everyone else. Second, payment processing integration moves money from your distributor's account to yours, usually monthly or quarterly depending on threshold minimums. Third, metadata matching links ISRC codes in those reports to the works registered with your PRO, your mechanical rights administrator, and SoundExchange.
These three flows exist separately from CMO reporting. When PRS for Music or ASCAP pays you performance royalties, that money comes from blanket licenses with radio stations and venues, not from your distributor. When MLC pays mechanical royalties for US streams, that is a separate payment processing integration chain. Your distributor handles only the direct licensing relationship between you and DSPs (what the industry calls wholesale distribution of digital goods).
The integration challenge is that each system uses different identifiers. DSPs report by ISRC and UPC. CMOs track works by ISWC and IPI numbers. SoundExchange uses a combination of ISRC and your IPN. Without automated order processing to map these codes, you reconcile everything manually or you miss money entirely.
Why your distributor does not show you everything
Distributors aggregate DSP payments because that is their business model: they negotiate direct deals with Spotify, Apple Music, and others, then split the revenue with you. But they do not reconcile performance royalties from your PRO, mechanical royalties from MLC or MCPS, neighboring rights from PPL or SoundExchange, or sync licensing income. Those revenue streams flow through different supply chain integration paths that your distributor never touches.
This creates structural blind spots. Your DistroKid dashboard shows streaming income but not the performance royalties generated when that same stream played on a webcast radio station. CD Baby reports digital sales but not the mechanical royalties MLC collected from the same transaction. The gap is not a technical limitation. It is a business model boundary. Distributors are not rights administrators, and most have no financial incentive to show you income they do not process.
The result is that most independent artists see 40-60% of their actual revenue in their distributor dashboard and assume that is everything. The rest sits in CMO accounts, often unmatched because the metadata your distributor sent to Spotify does not align with what you registered at your PRO. Distributor integration closes that gap by pulling data from both sides and reconciling it in one place.
Step 1: Verify your distributor supports API access
DistroKid, CD Baby, TuneCore, and AWAL all offer API integration, but what each API provides varies significantly. DistroKid's API returns sales data by ISRC and territory but does not include payout dates or payment processing integration details. CD Baby provides more granular DSP payment reconciliation data but rate-limits requests to 100 calls per hour. TuneCore's API requires OAuth authentication and returns data in DDEX format, which most order management systems cannot parse without custom middleware.
AWAL and Stem offer the most complete APIs because they position themselves as data platforms, not just distributors. Both return real-time inventory tracking of streams, downloads, and revenue by work, territory, and DSP. But both also require you to meet minimum release or revenue thresholds before granting API access.
If your distributor does not offer an API (UnitedMasters and Symphonic fall into this category), you are limited to manual CSV exports. That means no automated order processing, no real-time cash flow management, and significantly higher operational costs from manual reconciliation work.
Step 2: Map your ISRC and UPC codes across systems
ISRC matching is the foundation of distributor integration because it is the only identifier that appears in both your distributor's sales reports and your CMO's royalty statements. But ISRC codes only work if they are consistent. If you registered a work at ASCAP with one ISRC, uploaded it to DistroKid with a different ISRC because you re-mastered the track, and then registered a third ISRC with MLC when you joined, you have created three orphan works that will never reconcile.
Audit your catalog by exporting your distributor's ISRC list and comparing it against your PRO, MRO, and SoundExchange registrations. Look for missing codes, duplicates where the same recording has multiple ISRCs, and mismatches where the ISRC exists but the metadata (track title, writer splits, duration) differs enough that automated matching fails.
The most common mismatch is writer splits. Your distributor does not care who wrote the song; they only care who owns the master. But your PRO needs accurate IPI numbers and percentage splits to pay performance royalties. If your distributor's metadata says "Writer: Unknown" and your PRO registration lists three co-writers, the PRO's system flags it as a conflict and holds payment until you file a manual claim.
Step 3: Connect your payment processing integration
Linking distributor payouts to your accounting means mapping payment dates to reporting periods. Most distributors pay 1-2 months after the reporting period closes. DistroKid pays for January streams in late February or early March. TuneCore pays quarterly, so Q1 streams arrive in May. If your cash flow management system expects monthly income, you need to accrue revenue in the month it was earned, not the month it was paid.
Distributor settlement works differently than DSP payment reconciliation. When Spotify pays your distributor, Spotify is settling a wholesale distribution invoice for all streams across all artists that distributor represents. Your distributor then allocates that payment across individual artists based on internal accounting. The payment you receive is not a direct pass-through from Spotify. It is your share of a bulk settlement.
This matters for tax reporting. In the US, your distributor issues a 1099 for the total amount they paid you, but that 1099 does not break down income by territory or DSP. If you need to file foreign tax reclaim forms or allocate income by source for a grant application, you must reconcile your distributor's payment processing integration data against the underlying sales reports.
Distributor integration: how your money really connects
Once integration is live, you see the complete cash flow management picture. Real-time inventory tracking shows which works earn from streaming, which earn from performance royalties, and which earn from both. You can identify supply chain integration gaps: tracks that stream heavily on Spotify but generate no PRO income because you never registered the composition, or works that earn performance royalties in Germany but show zero streams because GEMA's data does not flow back to your distributor.
Distributor partner integration reveals operational costs reduction opportunities. If you are paying both a distributor and a publishing administrator to manage the same catalog, integration shows you exactly where the overlap is and whether you are double-paying for services. If you are using multiple distributors for different territories, integration highlights where metadata drift has created duplicate ISRCs or conflicting ownership claims.
The financial benefit is not just visibility. It is speed. Without integration, you reconcile distributor statements manually, usually quarterly, and you discover problems months after they occur. With integration, discrepancies surface within days. A missing ISRC registration, a metadata mismatch, a payment processing integration failure: all become visible before they compound into larger losses. CISAC publishes annual reports on global royalty collection that highlight how much money remains unclaimed due to poor metadata matching.
Step 4: Set up automated order processing for new releases
Order management systems pull new release data from your distributor's API the moment you upload a track. The system reads the ISRC, UPC, track metadata, and release date, then triggers downstream registrations automatically. It files the ISRC with your PRO using CWR format, registers the sound recording with SoundExchange using your IPN, and submits mechanical licensing information to MLC or HFA depending on territory.
This eliminates the manual data entry that causes most royalty payment distribution failures. When you register a work manually, you introduce typos, formatting inconsistencies, and timing delays. Automated order processing uses the same metadata your distributor sent to DSPs, ensuring that what Spotify sees matches what ASCAP sees.
The configuration step is mapping your distributor's metadata fields to each CMO's registration requirements. Your distributor stores "artist name" as a single field; ASCAP needs "first name" and "last name" separately. Your distributor lists all writers in one comma-separated field; BMI requires individual IPI numbers and percentage splits. An iPaaS integration solution handles these transformations, but you must define the mapping rules once during setup.
Step 5: Build your reconciliation workflow
Reconciliation is the ongoing process of matching distributor reports against CMO statements and DSP payment reconciliation data. Every month, you compare what your distributor says you earned from Spotify against what Spotify's own reporting shows, then compare both against the performance royalties your PRO paid for those same streams.
Discrepancies fall into three categories. First, timing differences: your distributor reports January streams in February, but your PRO reports them in March. Second, scope differences: your distributor reports only direct licensing income, but your PRO includes radio play and live performance income that your distributor never sees. Third, errors: missing ISRCs, incorrect territory assignments, or payment processing integration failures where money was earned but not paid.
Wholesale distribution deals add complexity. If you licensed a track directly to a film production company, that income does not flow through your distributor. If you have a neighboring rights deal with PPL in the UK, that income is separate from your distributor's UK streaming revenue. Your reconciliation workflow must account for these parallel revenue streams or you will flag false discrepancies.
Step 6: Monitor for integration failures
API timeouts are the most common failure mode. Your distributor's API goes down for maintenance, your integration system retries the connection, and if the outage lasts longer than your retry window, you miss a day of data. Most iPaaS integration solutions log these failures, but you must monitor the logs or you will not know data is missing until reconciliation fails weeks later.
Metadata drift occurs when you update catalog information in one system but not others. You correct a misspelled track title in your distributor's dashboard, but the old spelling remains in your PRO registration. Now the ISRC codes match but the metadata does not, and automated matching fails. The fix is to propagate metadata changes across all systems simultaneously, which requires either manual coordination or an ERP integration layer that enforces consistency.
Distributor settlement delays cascade into cash flow management problems. If your distributor misses a payment cycle because of a banking error, your accounting system shows a revenue shortfall that does not reflect actual earnings. You must distinguish between "money not earned" and "money earned but not yet paid," which requires tracking expected payment dates and flagging delays as exceptions.
The technical complexity is manageable. The hard part is maintaining metadata hygiene across systems that were never designed to talk to each other. Most integration problems trace back to inconsistent ISRC codes, missing IPI numbers, or writer splits that do not add up to 100%. Fix the data quality issues and the technical integration becomes straightforward.
Conclusion
Functional distributor integration delivers operational costs reduction by eliminating manual reconciliation work and cash flow management improvements by surfacing revenue discrepancies in days instead of months. For larger catalogs, ERP integration is the next layer, connecting distributor data to accounting systems, contract management, and royalty payment distribution workflows. But most integration problems stem from metadata hygiene rather than technical complexity. Clean up your ISRC codes, verify your IPI numbers, and ensure your writer splits match across systems. The technical connection is the easy part.
AUTHOR

Carlos Palop
CEO & Co-founder, UniteSync
Carlos Palop is a seasoned music publishing expert, adept in rights management and royalty distribution, ensuring artists' works are protected and profitably managed. Their strategic expertise and commitment to fair practices have made them a trusted figure in the industry.



