Logomelino

Publisher Archetypes

General

melino Publishing is built to serve a wide range of publishing business models. Below are eight common archetypes and how the module maps to each one's priorities and pain points.

Archetype 1 — The Traditional Full-Service Publisher

Who they are: A mid-sized independent publisher signing songwriters and composers, handling all registrations, collecting from societies worldwide, and paying out royalties via statements. Typically 5,000–20,000 works. May control both original and sub-published repertoire.

Core workflow in melino:

  • Manage Works with full participant splits and territory-based IP chains
  • Export CWR files for society registration
  • Define Publishing Contracts per writer with recoupment terms and advance tracking
  • Process incoming Imports from societies and sub-publishers
  • Generate and send Statements to writers

Key features:

NeedFeature
Share & territory managementWorks → Participants tab + IP Publishing Info Chain
Society registrationWorks → Tools → CWR Export
Recoupment accountingContract → Advances tab + Opening Balance
Automated statementsStatements + Explates
Sub-publishing deal trackingContracts with territory-specific Terms

Watch out for split conflicts when multiple co-writers are involved — verify all Work participant shares sum to 100% before generating Statements.

Archetype 2 — The Production Music / Library Publisher

Who they are: A high-volume catalog business licensing music for TV, film, advertising, and digital media. Catalogs can exceed 10,000 works. The same composition often exists in many versions (full, sting, loop, stems). Revenue is driven by sync licensing and broadcaster performance.

Core workflow in melino:

  • Bulk import large work catalogs via Excel
  • Use Alternate Titles to manage version names within a single Work record
  • Run mass CWR generation for large registration batches
  • Use Work Type / Version Type fields to distinguish originals from arrangements and edits
  • Process cue-sheet-based income via Imports with high row volumes

Key features:

NeedFeature
High-volume work ingestionWorks → Import from Excel (up to 10 MB per batch)
Version and edit managementWorks → Alternate Titles + Version Type
Mass registrationWorks → Tools → CWR Export with batch filtering
Metadata consistencyImplates with strict required-column validation
Advanced searchWorks list with filtering by type, status, participant

Watch out for duplicate Works when the same composition is submitted by multiple sources under slightly different titles. Always include ISWC in bulk imports as the deduplication key.

Archetype 3 — The Publisher-Label Hybrid

Who they are: A music company running both a record label and a publishing division — often for the same roster. Controls both master rights and publishing rights. Royalties flow from neighboring rights AND performance/mechanical sources, and each asset requires tracking under both "hats".

Core workflow in melino:

  • Use a unified Participant database (shared composers and artists across publishing and label workflows)
  • Separate master-rights income from publishing income using Distribution Channels and Publishing Sources within Contract terms
  • Generate combined statements covering both royalty streams for the same artist
  • Manage cross-collateralised advances via Contract opening balances

Key features:

NeedFeature
Shared participant databaseParticipants module (cross-referenced across modules)
Rights-type separationContract Terms → Distribution Channel + Configuration
Combined artist statementsStatements broken down by source
Cross-collateralisationContract → Opening Balance + Advances tab

Watch out for data duplication — the same person may exist as both a Participant (for publishing shares) and a Publishing Partner (for financial settlement). Establish a naming convention early and cross-reference both records.

Archetype 4 — The Pure Administrator

Who they are: A service-based publisher administering catalogs on behalf of independent writers or smaller publishers — without owning any copyright shares. Charges a fee or commission. Transparency and operational efficiency are the business model.

Core workflow in melino:

  • Manage separate catalogs per client using Catalogues (one Catalogue per administered client)
  • Use Administration contract type for all Contracts (no ownership, service only)
  • Generate client-level statements showing collected income minus administration fee
  • Use Editions to maintain clear separation between clients if they have distinct imprints

Key features:

NeedFeature
Multi-client catalog separationCatalogues (one per client) + Editions
Admin deal contract typeContracts → Type = Administration
Commission automationContract Terms → Rate (admin commission) + Reduction
Client-level reportingStatements filtered by Partner/Catalogue
Bulk client onboardingWorks bulk import + Implate per client

Watch out for mixing administered works (where the client owns shares) with controlled works (where the administrator also holds a share). The contract type and participant shares must clearly reflect which applies for each Work.

Archetype 5 — The Publisher Group / Parent with Sub-Publishers or Editions

Who they are: A larger entity owning or controlling several sub-publishers or imprints, common in the European/GEMA space. Each sub-entity may have its own society registrations and deal structures, but reporting flows upward to the parent.

Core workflow in melino:

  • Use Editions with a parent-child hierarchy to model the group structure
  • Assign each Work to its correct Edition (imprint) with an IP Name Number
  • Run consolidated statements at the group level by filtering across all editions/companies
  • Model internal splits between parent and sub-publisher as Contracts between related companies

Key features:

NeedFeature
Parent-child publisher hierarchyEditions → Parent Edition field
Edition-level work taggingWorks → Edition assignment
Entity-based reportingStatements filtered by Company + Edition
Internal sub-publishing splitsContract Terms with territory and rate per entity
Separate society affiliationsCompany → Publishing → Society Credentials (per entity)

Watch out for rights conflicts between Editions — when a Work is registered under one Edition but income is collected under another. The IP Publishing Info Chain on the Work should explicitly define which entity controls which territory.

Archetype 6 — The Self-Publishing Artist or Writer-Publisher

Who they are: A songwriter or composer who has set up their own publishing company to retain 100% of their rights. Smaller catalog (under 2,000 works), often still growing. New to the business side, needs simple tools with professional output.

Core workflow in melino:

  • Create Works with themselves as the sole Participant (100% share)
  • Export CWR files to register with their PRO
  • Set up a simple Contract for any co-writer or co-publisher arrangements
  • Receive society statements and process as Imports
  • Generate basic Statements for co-writers

Key features:

NeedFeature
Simple catalog managementWorks with single-participant setup
Society registrationWorks → Tools → CWR Export
Co-writer split trackingWorks → Participants tab
Basic royalty statementsStatements → PDF export
Low overhead contract managementOne Contract per co-writer or admin deal

This archetype is often new to the financial side of publishing. Ensure the Term Category is set correctly on their Partner record so Statements are generated on the right cadence (typically annual). Overly frequent statements for small amounts create unnecessary overhead.

Archetype 7 — The International Sub-Publisher

Who they are: A regional publisher representing foreign catalogs within a specific territory (e.g. a German publisher administering Nordic or US repertoire locally). Does not own rights globally — operates on a territory-limited mandate from the original publisher. Registers locally, collects locally, and remits royalties back to the original publisher minus their fee.

Core workflow in melino:

  • Onboard foreign catalogs via bulk Works import
  • Set territory-scoped ownership in the IP Publishing Info Chain per Work
  • Use sub-publishing contract type with territory and time limits in Contract Terms
  • Generate remittance statements to the foreign principal showing collected income minus retention
  • Scope CWR registrations to controlled territories only

Key features:

NeedFeature
Territory-scoped ownershipWorks → IP Publishing Info Chain (territory + date range)
Sub-publishing contract termsContract → Terms tab (territory + rate + Valid From / Until)
Inbound catalog bulk importWorks import from Excel
Remittance statement generationStatements → export to original publisher as Partner
Controlled share administrationContract → Works tab with territory-limited share

Watch out for contract expirations and rights reversions. When a sub-publishing mandate expires, the territory-limited Contract must be set to inactive and the IP chain must be updated to reflect the reversion. Failing to do this will cause ongoing income to be incorrectly attributed.

Archetype 8 — The Legacy Estate Manager (The Catalog Caretaker)

Who they are: A catalog-focused publisher or estate manager maintaining and monetizing an established repertoire — often the works of legendary writers or composers with decades of accumulated rights data. Not actively signing new talent. Accuracy, historical data, and data cleanup are the primary concerns.

Core workflow in melino:

  • Perform a full historical data migration (see Client Onboarding)
  • Use bulk Works import to ingest the existing catalog, mapping to ISWCs and society numbers
  • Reconcile income from many sources using multiple Implates (one per source format)
  • Lock all historical statements once imported — no recalculation
  • Use Statement Tools for period-end audit and financial reconciliation

Key features:

NeedFeature
Bulk data import and cleanupWorks import from Excel + ISWC deduplication
Historical ownership trackingWorks → IP Publishing Info Chain with date ranges
Multiple income source ingestionImports + one Implate per source format
Audit and reconciliationStatement Tools
Locked historical statementsStatements → Lock
Duplicate detectionISWC + GEMA work number as deduplication keys

Watch out for incomplete or inconsistent metadata in the source data — legacy catalogs often have works with missing ISWCs, conflicting titles, or unresolved ownership chains. Plan for a data-cleaning phase before migration, and flag works with missing ISWCs as a post-migration task rather than blocking the import.

Archetype Quick-Reference

ArchetypeCatalog SizeComplexityKey melino Features
Traditional Full-Service PublisherMedium (5k–20k)MediumCWR, Contracts, Statements, Recoupments
Production Music / Library PublisherLarge (10k+)High metadataBulk import, Version management, Mass CWR
Publisher-Label HybridMediumHigh cross-rightsChannel separation, Shared participants
Pure AdministratorMany smallHigh client countMulti-catalogue, Admin contracts, Commission
Publisher Group / EditionsLarge, multi-entityVery high hierarchyEditions hierarchy, Entity reporting
Self-Publishing ArtistSmall (under 2k)LowSimple works, CWR, Basic statements
International Sub-PublisherMedium (inbound)Very high territoryIP chain, Territory contracts, Remittance
Legacy Estate ManagerLarge (historical)High data qualityBulk import, Historical migration, Audit

On this page