Royalty Flush

A royalty-processing platform where ARG replaced spreadsheet-heavy workflows with a backend engine for CWR ingestion, royalty calculation, and reporting.

ARG automated a royalty-processing workflow that previously depended on Excel sheets and macros. We built a backend royalty engine for CWR file processing, royalty organization, obligation calculation, and reporting, giving the team a controlled, repeatable alternative to manual spreadsheet operations.

Category: Music Rights
Client: North Music Group
Featured engagement: 1 Year
Technology: .NET Core, Entity Framework, Octopus Deploy, Docker, React, Hangfire, PostgreSQL, MediatR

Services

Royalty Engine
CWR Processing
Reporting
Backend

What had to be solved

Royalty Flush needed to replace a manual royalty workflow built around Excel sheets and macros. The process could handle some internal needs, but it was difficult to scale, audit, and operate reliably as royalty data grew.

The platform needed to ingest multiple CWR files, normalize royalty information, calculate obligations, and generate reports without relying on fragile spreadsheet logic.

The challenge was to turn a manual finance operation into backend software that could be repeated, reviewed, and trusted.

How we made it work

Built a backend royalty engine to replace Excel-based processing
Implemented CWR file ingestion for multiple royalty input files
Structured royalty data so obligations could be calculated and reviewed consistently
Added reporting flows to make royalty outputs easier to inspect and share
Reduced dependence on manual macros by moving repeatable logic into backend services
Supported QA around calculation flows, file handling, and reporting output

Results

Royalty Flush moved royalty operations away from fragile spreadsheets and into a repeatable backend workflow, making CWR processing, royalty calculation, and reporting easier to operate and review.

1 Royalty engine built
30+ CWR file types supported by the engine
1000+ Music catalogs managed on the platform