Qlero
← Back to blog
Royalties·November 19, 2026·8 min read

Exactuals Alternatives: Payments vs Royalty Accounting

By Qlero Team

Qlero wordmark on a dark blue background.

Compare Payment Hub, SR1’s move to RyteBox and Qlero’s documented workflows. Separate royalty calculations, payment execution and the handoff between them.

Comparing Exactuals alternatives starts with two separate questions: can the system calculate what each payee is owed, and can the payment process deliver the approved amount to the intended recipient? A statement balance and a completed bank transfer are not the same result.

There is also an important product-history correction. SR1 should not be treated as a current Exactuals module: RyteBox announced its acquisition of SR1 from Exactuals in a post dated 12 February 2024, updated 3 February 2025. A comparison built around an assumed current Exactuals bundle of Payment Hub, SR1 and RAI would therefore be misleading.

This guide separates payment processing, royalty calculation and metadata work. It uses public vendor documentation checked on 19 November 2026, not hands-on comparative testing.

What Payment Hub by Exactuals is presented as today

City National Bank's current Payment Hub page presents a high-volume payment service, including music royalty and entertainment residual payments. It describes payor/payee visibility, identity verification and compliance controls. The page identifies Exactuals as an RBC company and a wholly owned subsidiary of City National Bank.

City National's royalty-payment overview describes registering payee information, aggregating payment data and distributing payments through the bank. These are the supplier's descriptions, not evidence that every transfer is instant, every tax obligation is covered or the service is more secure than an alternative.

The public help center makes the scope more concrete:

  • Payment-method setup says available options depend on the payor and that required bank fields vary by country.
  • Payment and statement viewing describes statuses, payment details and attached documents, where present. Access to a statement does not identify which calculation engine produced it.
  • Tax-document collection describes payor-requested W8/W9 uploads, with role restrictions, and says not every payor enables the feature. This does not establish universal tax calculation or filing.

Ask for the methods, currencies, territories, fees and controls included in your proposed service. Do not substitute a historical country count or a broad marketing description for that scope.

Where SR1 fits now

RyteBox's current SR1 support page confirms the acquisition and provides its support route. It describes continued SR1 use in the short term and a longer-term move to RyteBox. That is a stated transition plan, not proof that every customer has migrated or that your migration date is fixed.

Nor is it fair to assume SR1 has only superficial calculation features. Its public documentation includes master-deal royalty bases and a 50/50 net-profit-share template, including expense-recoupment configuration. Those guides establish specific documented workflows, not support for every agreement.

If you are evaluating an existing SR1 installation, address its terms, support and future path with the current supplier. Evaluate any Payment Hub connection separately; shared history does not prove a current included integration.

Payments depth versus accounting depth

For this comparison, accounting depth means the ability to represent the relevant agreement, match sales data, calculate royalties and explain the resulting balances. Useful tests include participation shares, calculation bases, deductions, escalation thresholds, advances and the treatment of corrections.

Payments depth means the supported process after an amount is approved: payee setup, permitted payment routes, approvals, required documentation, execution and handling of failures or returns.

These are evaluation categories, not a ranking of suppliers. A payments-focused product is not automatically weak at calculations, and an accounting-focused product is not automatically weak at payments. Bank ownership alone does not establish comparative security or calculation accuracy.

Ask a qualified adviser to resolve ambiguous contract or tax treatment. Do not make a software demonstration stand in for that decision.

A practical scenario: 200 artists across 15 countries

Consider a hypothetical distributor with 200 artists, a mixture of flat-rate and escalating agreements, and intended recipients in 15 countries. These numbers describe a test scenario, not a customer, benchmark or supported-territory claim.

The calculation test should reproduce agreed expected results from a small, representative set of sales and contracts. Include an escalation threshold and an unrecouped advance. Keep royalty earnings, the closing balance and the proposed payout distinct.

The payment test should then follow an approved amount into the proposed payment route. Verify recipient identifiers, currency, required details, approvals, any fees or withholding treatment, and the returned payment reference and status. Include a rejected instruction and establish who resolves it without creating a duplicate payment.

A file or API handoff is a possible architecture to evaluate, not a confirmed Qlero–Exactuals integration. Obtain the receiving system's specification and test a sample. A CSV export alone does not prove compatibility, settlement or reconciliation; neither does a successful calculation demonstrate compliance in 15 countries.

Four questions to ask a payments or accounting supplier

  1. Which agreement cases can you demonstrate? Use your actual recoupment, escalation and cross-collateralization requirements where relevant. Ask how the product represents each one, rather than assuming a category label answers the question.
  2. What happens when a figure is disputed? Request the source data, terms, calculation explanation and correction process. Distinguish retained statements from a complete history of user changes.
  3. Which product, team and contract cover each part? Separate the calculation service, payment service and any future migration. Identify what is available now, what needs implementation and what remains a plan.
  4. How is the handoff supported? Agree the format, identifiers, status return, exception owner and costs. Ask whether the proposed connection is supported, custom work or untested.

These are recommended acceptance checks. We have not tested either supplier against them.

What to look for when calculation accuracy is the priority

CapabilityWhat to verify in your evaluation
Structured deal-term modelingDemonstrate the precise basis, shares, deductions, escalation behavior and recoupment provisions your agreements require.
Reconciliation against sales dataTrace a representative input through matching and exceptions before treating its output as final.
Calculation history and explanationInspect the inputs, configuration, results and correction records actually available; do not assume a complete audit log.
Payment handoffValidate the destination format or API, recipient references, approvals, failure handling and reconciliation.

Use the recoupment calculator for an illustrative discussion, not as verification that a proposed product implements your agreement or moves money.

RAI: distinguish historical metadata claims from current scope

Exactuals' 29 January 2021 announcement described RAI as a software development kit and open API intended to improve intellectual-property metadata. That is historical product context, not confirmation of its current availability, ownership-data accuracy or inclusion in a new Payment Hub contract.

If RAI appears in an old comparison or proposal, ask the supplier to confirm its present scope and support. Metadata cleanup, royalty calculation and payment execution remain different tasks. A corrected identifier does not by itself establish ownership, contractual shares or entitlement to payment.

Where Qlero fits

Qlero's contract-term documentation describes Sales, Cost, Deduction and Escalation terms. Creating and linking terms requires Agreements write access; editing a shared term affects every contract using it.

Its calculation guide separates the royalty base, participation share and adjusted rate. Participation overrides, deductions, escalations and PPD pricing require Pro or Enterprise. The documented result for a sales row is not the final statement balance or a bank payment.

For recoupment records, the advance and adjustment guide says manual Advance and Other transactions affect balances at their entered amounts, without applying a royalty rate. They do not send money. A correction after a period closes enters the next period; it does not rewrite the closed statement.

Payment routes need equal care:

  • Manual payments: the payment-run guide requires the Payments add-on and appropriate Payments & Transactions permissions. CSV/Excel downloads support review. Bank transfers are arranged outside Qlero before execution records payments as Paid; that action does not itself transfer money.
  • Tipalti: the payee setup guide documents opening Tipalti's form from Qlero for labels using it. Details entered there are held by Tipalti, and Ready concerns setup, not receipt of funds. This is distinct from ordinary Qlero Billing Information, which can contain bank details for self-billing.

The Qlero–Tipalti integration overview asks buyers to confirm availability, onboarding and pricing. Its stated current setup is one company per instance; multiple entities need a separate setup and cost discussion. Do not infer unrestricted availability or a Qlero–Exactuals connection from this different integration.

Frequently asked questions

Do I need both royalty accounting and payment software?

You need both functions covered, but not necessarily two separate applications. Define the responsibilities first, then evaluate whether one service or a tested combination meets them.

Is SR1 still an Exactuals royalty-calculation product?

RyteBox announced that it acquired SR1 from Exactuals and currently provides its support route. Treat historical descriptions of the Exactuals suite accordingly. Confirm your particular product, contract and transition arrangements with the current suppliers.

Can accounting software hand off to a bank-backed payment platform?

It is an architecture to test, not automatic compatibility. Check the supported interface, identifiers, approval flow, errors and status reconciliation. This article does not establish a native Qlero–Payment Hub integration.

Does bank ownership make a platform inherently more secure?

Ownership is not a comparative security test. Request current security evidence and assess the controls, access model and responsibilities relevant to your setup. Do not infer superiority from the corporate relationship alone.

How do I assess calculation depth?

Ask the supplier to reproduce your independently checked agreement examples, including difficult cases. Inspect the configuration and explanation of results. Detailed documentation is useful evidence, but neither a confident demo nor a documentation gap settles every requirement.

What is RAI's role in this comparison?

The historical announcement describes metadata tooling, not a royalty calculation or bank transfer. Verify current availability and scope before treating it as part of a proposed solution.

Choose the gap you actually need to close

Start with the result you cannot reliably achieve today: a defensible calculation, an explainable balance or a controlled payment process. Then compare defined product scopes and demonstrated workflows, including the handoff between them.

For Qlero's payment administration, see the Payments overview. To evaluate your contracts and intended payment route together, book a focused demo. Bring representative files and agreement examples, and ask which requirements are documented, demonstrated or still subject to setup.

See it on your own catalog

A focused walkthrough of your deals, sales ingestion, and period close.