Enterprise DNA

Instead of Klopotek

Stop renting Klopotek. Own your royalty system.

We build your version around your contracts, royalty periods and statement layout, bring your Klopotek titles, contracts and balances across and run it for you.

Klopotek's published cloud offers for association members start at US$400 a month for two full users and one read-only user, plus US$75 a month for each extra user. That is US$4,800 a year before the team grows, and anyone else gets a quote.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Read the invoice first

What the monthly fee is really paying for

Klopotek prices its cloud by the month and by the person. Most of what a publisher uses it for is records, a statement run and questions. Look at what you pay for before the next renewal.

payments

A monthly fee to start

The member offers list US$400 a month for two full users and one read-only user. That is US$4,800 a year before anyone else joins.

group_add

Every extra person

Each additional user is US$75 a month on those offers, or US$900 a year, so rights, finance and editorial each add to the bill.

request_quote

A price you have to ask for

Outside the association offers, pricing comes through a demo and a quote. You cannot see the number before the sales call.

apps

A suite of separate apps

Contracts, royalty accounting, royalty recipients, rights sales and rights accounting are each their own app to learn and license.

query_stats

Reporting through another engine

Klopotek Analytics is the reporting layer. A question your screens do not cover becomes a report someone has to build.

support_agent

Ad-hoc reports sold as a feature

Klopotek's own offer pages pitch ad-hoc reports as a reason to buy. Here every question is one: you ask it in plain words.

The royalty system you own

Start with the questions your rights and finance team ask every period

Royalty run

Statements that add up, every period

Each contract carries its rates by format and channel, and the run turns the period's sales into a statement line by line.

  • check Escalators that split copies across the rate they cross
  • check Rates on recommended retail price or net receipts
  • check A reserve against returns, held and released next period
  • check A test run to check before anything is approved

Advances

Know what is owed and what has earned out

Every instalment is tied to signing, delivery or publication, so the system knows the day it falls due.

  • check Advances due now, with the days overdue
  • check Unearned advance by contract and title
  • check Balances carried in from your last statement
  • check Payments recorded with the date the money left

Rights

Follow rights money to the author

Every licence, the income it brings and the author's share land on the next statement without retyping.

  • check Licence payments overdue from the licensee
  • check Licences ending in the next 90 days
  • check Rights still free to sell, work by work
  • check A chase note to the licensee, drafted for you

Rules and paperwork

Keep the obligations straight as you go

The rules a New Zealand or Australian publisher answers to are checked against the records, each with its source.

  • check Legal deposit: 20 working days in New Zealand, one month in Australia
  • check Withholding on overseas authors, 30% in Australia and 15% in New Zealand unless a treaty rate applies
  • check GST on registered authors only with a written agreement on file
  • check Statements, remittance advices and advance information sheets in your brand

Make it yours

Design your own Klopotek replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Klopotek. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Klopotek replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Klopotek data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Publishing Royalties for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Publishing Royalties for Claude Code

Connected to your own database

What needs my attention today?

Statement due soon

Item
S2 K-101
Why
no statement run yet; due 2026-12-23

Statement due soon

Item
S2 K-104
Why
no statement run yet; due 2026-12-23

Statement due soon

Item
S2 K-105
Why
no statement run yet; due 2026-12-23

Statement overdue

Item
S2 K-106
Why
no statement run yet; the contract says 30 days, due 2026-10-24, 20...

Statement due soon

Item
S2 K-107
Why
no statement run yet; due 2026-12-23

Advance due

Item
ADV-104 Night Ferry
Why
$3,000 on publication to Daniel Ashworth, due 2026-11-03, 10 days o...

Advance due

Item
ADV-113 Small Mercies
Why
$4,000 on delivery to Mere Paki, due 2026-10-29, 15 days overdue

Manuscript late

Item
W07 The Long Paddock
Why
due 2026-10-29, 15 days late; publishing 2027-03-13

Contract not signed

Item
W08-HB Glass Harbour
Why
publishes in 60 days and the contract is not signed

Legal deposit

Item
W03-HB Coastal Kitchen
Why
1 to the National Library of Australia by 2026-12-03

Legal deposit

Item
W02-PB Night Ferry
Why
0 of 2 copies to the National Library of New Zealand; deadline was ...

Rights income overdue

Item
RI-302 Ostwind Verlag
Why
$4,500 expected 2026-10-24, 20 days ago

Rights licence expiring

Item
R-202 The Salt Road
Why
audio licence to Larkspur Audio ends 2027-01-12, in 60 days

Reversion clause live

Item
K-107 High Country Letters
Why
out of print 24 months; the contract lets Estate of Hugh Kerr ask f...

No royalty rate

Item
K-104 W04-AU
Why
audio home sales recorded and the contract has no rate for them, so...

No royalty rate

Item
K-105 W04-AU
Why
audio home sales recorded and the contract has no rate for them, so...

Tax details

Item
A01 Mere Paki
Why
GST-registered, 15% is added to payments, and no agreement date is ...

Ask it anything

Ten questions to ask your royalty records

Each one has a working answer in the demo publisher. Your own list and contracts make the answers yours.

chat_bubble Which statements are past the deadline in the author's contract, and by how many days?
chat_bubble Which advances are now due because the manuscript was delivered or the book published, and are still unpaid?
chat_bubble How much advance is still unearned across the list, and which of those titles sold nothing in the last 90 days?
chat_bubble Which paperbacks crossed their royalty escalator this period, and how many copies sold at the higher rate?
chat_bubble Which overseas authors are we withholding the full default rate from because no treaty rate is recorded?
chat_bubble Which GST-registered authors are being paid GST with no written agreement on file?
chat_bubble Which print editions published in the last year have not gone to the national library, and when was each due?
chat_bubble Which out-of-print titles have passed the reversion period in their contract?
chat_bubble Which rights payments are overdue from licensees, and what is the author's share of each?
chat_bubble Which sales are earning nothing because the contract has no rate for that format or channel?

Switching

How to switch from Klopotek

The move involves exporting your titles, contracts and sales, then checking the imports and your own contract rules before you switch systems.

  1. 1

    Export your Klopotek records

    Start with your title list as an ONIX export from Klopotek’s Metadata Export Manager. Prepare your royalty schedule as a CSV that includes each contract’s carried balance, and your sales as a CSV. If you are unsure how to produce the schedule or sales files, export what your account allows, usually CSV or Excel, and check with Klopotek.

  2. 2

    Load the records with test runs

    Load the title export, contract schedule and sales records in that order. Each import offers a test run, so check each file before applying it. The test checks the whole file before anything changes. Use the results to confirm that the records and carried balances are being read as expected, then apply the import.

  3. 3

    Review and resolve flagged records

    Check what the import flags before relying on the new records. Look for missing or mismatched details in titles, contracts, carried balances and sales. Resolve problems in the source records or mapping, then run the test again and apply the corrected file. Your first statement should pick up from the balance on your last statement.

  4. 4

    Run both systems side by side

    Keep Klopotek running while you use the new system for a short period. Compare the records and royalty results for the same period, including contract balances and sales. Use any differences to find fields, rules or source records that need attention. Do not stop using Klopotek until you have checked the results you need for the move.

  5. 5

    Switch off Klopotek

    Once you are satisfied with the imported records and results, move your work to the new system and stop using Klopotek for current records. Statement history does not import, so keep it in Klopotek or retain it as PDFs. Make sure you can still refer to that history before ending your Klopotek access.

construction

Where the real effort goes

The main work is usually mapping your own fields and contract rules, then deciding how much history to bring. Statement history stays in Klopotek or as PDFs, rather than moving into the new system. If Enterprise DNA installs and runs it for you, they handle the migration work, including bringing your Klopotek data across.

Not ready for a call?

Get your Klopotek switch plan by email

We will send you the step-by-step plan for moving your business off Klopotek, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for /attention
  3. 3 Export your titles as ONIX and run import onix with --dry-run, then import contracts and sales
  4. 4 Run /royalty-run as a dry run and compare it with your last Klopotek statements
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your contract clauses, royalty periods and statement layout
  • check Your Klopotek titles, contracts and balances brought across and checked against your last statements
  • check An author portal or a web screen if you want one
  • check Distributor sales files that load themselves each month
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Set up, backed up and kept running for your list
  • check Connected to your accounts, distributor reports and email
  • check Each royalty run prepared for your sign-off
  • check Run through Omni by Enterprise DNA alongside the rest of your business
Talk to Sam

Questions

Instead of Klopotek, answered

Will our authors still get proper statements? expand_more

Yes. Each author gets a statement for each period, line by line: copies sold by format and channel, the rate, the royalty, the reserve held against returns, the advance still to earn out, and any withholding or GST on the payment. It goes out as a document in your brand. If you want authors and agents to log in and download their own, we build that portal into your version.

Can we bring our contracts and balances across? expand_more

Your title list comes across from the metadata export you already send to retailers, and your contracts from a royalty schedule spreadsheet with the balance each author carries. Do a test run first. The whole file is checked before anything changes, and the first statement picks up from the balance on your last one. Statement history stays in Klopotek or as PDFs.

Does it handle escalators, co-authors and sub-rights? expand_more

Yes. A rate can step up after a set number of copies, and copies are split across the two rates in the period they cross it. Co-authors each have their own contract with their share. Rights income from translation, audio or other licences flows to each author at the share in their contract.

Is the tax handling advice? expand_more

No. The system applies the withholding rate and GST you record for each author and flags what is missing, with the source for each rule. Your accountant confirms the treatment for each author; the system makes sure it is applied the same way every time.

What does it cost to run instead? expand_more

The free version has no per-user charge. You pay for your own hosting and your coding agent subscription. If we build and run it, there is one setup fee and then a retainer. Bring your Klopotek invoice and user count to the call and we will compare them honestly.

Bring your Klopotek invoice to Sam

Spend 30 minutes with Sam. Bring your Klopotek invoice, one author contract and your last royalty statement. We will work out what to keep, what to build and what it takes to run your version.

Publishing Royalties for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Klopotek?

Get your version built