RevRule by Payload, problem guide

The deal changed on August 15. The spreadsheet found out in September.

Renegotiations take effect on a date, not at the next convenient quarter-end. When the new split reaches the royalty sheet one period late, someone is underpaid for every day in the gap, and the correction is a manual restatement nobody wants to sign.

Try the free sandbox RevRule overview and pricing

The failure modes

Three ways a mid-period change goes wrong

Applied late

The new split is keyed in from the next period. Revenue between the effective date and the update is computed at the old rate. The renegotiated party is underpaid, and the difference is rarely volunteered.

Applied to the whole period

The new split overwrites the old one for the full quarter, including weeks before the amendment existed. Now the other side is short, and a previously correct statement has to be withdrawn.

Applied with no record

The number in the sheet changes and the old value is gone. Months later, nobody can show which rate produced a given line, so a routine artist question becomes a forensic exercise.

Worked example

One renegotiation, 17 days, $414.11

Synthetic demonstration, fictional figures

In a published synthetic fixture run on the RevRule engine (a fictional 12-artist label, 40 tracks, 5,000 statement lines, $219,518.20 in synthetic quarterly gross), one artist's share on four tracks was renegotiated from 50 percent to 60 percent, effective 2026-08-15, inside the quarter. The engine held both versions of the rule with their effective dates: events before August 15 computed at 50 percent, events on or after at 60 percent, and the ledger records which rule version produced each line. A parallel spreadsheet model that applied the new split one monthly period late, from September 1, misdirected $414.11 to the label instead of the artist, in the 17 days from August 15 to August 31 alone, on just those four tracks. Synthetic data; not a customer result.

Notice what the error is made of. It is not carelessness and it is not a large percentage. It is a ten-point change, a seventeen-day gap, and four tracks. Catalogs run hundreds of tracks, and renegotiations, option pickups, and rate escalators happen every year. Each one opens the same gap between the date the deal changed and the date the spreadsheet changed.

How RevRule handles it

Splits are versioned rules with effective dates

In RevRule, a split is not a cell that gets overwritten. It is a rule in a Revenue Graph, and an amendment adds a new version with its own effective date. Every revenue event is computed under the version in force on the event's date, and the hash-chained ledger records the rule version behind every line, queryable by event, participant, or entry type and returnable in full as JSON. A renegotiation next year cannot rewrite a quarter that already settled, and the question "which rate applied on August 20" has a one-line answer.

Simulate before you commit a change: simulation is a dry run with zero side effects, so the effect of a new split can be previewed against real events before it governs a live run. RevRule does not hold funds, execute payments, or collect royalties; it computes what is owed under your rules for money already collected.

Get a free API key RevRule for music labels Buy for $99 or start a managed plan

Pricing: $99 one-time perpetual license (uncapped operations, unlimited Revenue Graphs, 1 API key), or managed plans at $29, $79, and $199 per month with higher operation, graph, and key allowances. Evaluation accounts are limited to 1,000 operations per month and 3 Revenue Graphs. Seven-day refunds. Support by email, best effort.

Questions

Split changes, answered plainly

When a royalty split is renegotiated mid-period, which rate applies to earlier revenue?

The rate in force on the date of each revenue event. Events before the effective date compute under the old split; events on or after it compute under the new one. Applying the new split to the whole period overpays the renegotiated party, and applying it late underpays them. Both are breaches of the amended deal, just in different directions.

How big can the error be if a new split is applied one period late?

In our published synthetic fixture (a fictional 12-artist label, one artist's share moving from 50 percent to 60 percent effective mid-August), applying the new split one month late misdirected $414.11 in just the 17 days between the effective date and month end, on four tracks. The figure scales with the size of the change and the revenue in the gap.

How do you keep split changes straight across a catalog?

Store the split as a versioned rule with an effective date instead of overwriting the old number. Then every event is computed under the rule in force on its own date, the ledger records which rule version produced each line, and a later renegotiation never rewrites history that was already settled.