How to Create Automated Royalty Statements With Twin.so

Royalty teams lose hours collecting files before they even start reviewing the numbers. Automated royalty statements reduce that manual work by moving repetitive browser tasks into a controlled workflow.

Twin.so is useful as the browser-automation layer. It can help royalty administrators access approved portals, retrieve statements, organize files, and route exceptions for review. It doesn’t replace contract logic or accounting controls. It handles the repetitive work around those systems.

The right setup starts with a clear process, not a single automation task.

THE ROYALTY STATEMENT PROBLEM IS A WORKFLOW PROBLEM

Royalty data rarely arrives in one consistent format. A label may receive CSV files from a distributor, PDF statements from a rights organization, and portal reports from a digital service provider. A publisher may need to collect information from several sub-publishers with different reporting periods and file structures.

The manual process usually looks like this:

1. Sign in to several portals.
2. Search for the latest reporting period.
3. Download available files.
4. Rename and move each file.
5. Open the files and check for missing data.
6. Enter totals into a royalty system or spreadsheet.
7. Ask someone else to review the results.

Each task appears small. Together, they create delays and increase the chance of missing a statement, downloading the wrong period, or overwriting a previous file.

A record-label royalty software discussion shows why teams often look for a system that can import distributor data, calculate payments, and produce artist reports in one workflow. The need is operational. People want fewer manual handoffs and a clear record of what happened.

Twin.so fits before the accounting stage. It can automate browser activity, while your royalty platform or spreadsheet handles calculations, contract rules, splits, reserves, and payments.

WHAT AUTOMATED ROYALTY STATEMENTS SHOULD HANDLE

A useful workflow has five stages:

• Collection: Retrieve statements from approved distributor, DSP, PRO, publisher, or label portals.
• Organization: Store each file with the source, reporting period, download date, and account name.
• Preparation: Convert inconsistent file names and formats into a predictable intake process.
• Validation: Check whether a file is missing, duplicated, incomplete, or outside the expected reporting period.
• Review: Send clean files forward and route exceptions to a person.

This separation matters. Browser automation can collect a file. It shouldn’t decide whether a contractual royalty calculation is correct unless you have separately tested and approved that logic.

Dedicated platforms such as Tone’s royalty accounting system combine functions such as royalty management, contract splits, and payouts. A Twin.so workflow can support that type of system by preparing source documents before they enter the accounting process.

Your final workflow should make every statement easy to identify. Capture these fields where available:

• Source or provider
• Reporting period
• Payment date
• Territory
• Currency
• Artist, writer, or beneficiary
• Release and track
• ISRC, catalog, or other identifiers
• Usage volume
• Rate
• Deductions
• Reserves
• Net royalty

You don’t need to force every portal into the same file format on day one. Start by creating consistent metadata around each download. That metadata gives your team a reliable way to find and review files later.

BUILD AUTOMATED ROYALTY STATEMENTS WITH TWIN.SO

Build the workflow around one source first. Prove that it works. Then add other portals.

1. Map the current collection process

List every source that sends royalty information to your team. Record the portal address, account owner, reporting frequency, expected file type, and destination folder.

Separate sources by access method:

• Portals that require a normal username and password
• Portals that require multifactor authentication
• Portals that provide a direct download
• Portals that require filters before exporting a report
• Sources that send files by email instead of through a browser

This inventory tells you which tasks Twin.so can automate and which tasks still need a human checkpoint. Don’t build one large workflow before you understand these differences.

2. Create a controlled browser task

Configure Twin.so to open the approved portal, sign in through the permitted account, select the reporting period, and locate the correct statement.

Use a dedicated account where the provider allows it. Store credentials through the approved security controls for your workspace. Don’t place passwords inside task descriptions, file names, or shared notes.

If a portal requests multifactor authentication, stop the workflow for a human approval step unless your organization has an approved method for handling that request. A workflow that bypasses access controls creates a security problem, not an efficiency gain.

3. Download and name the statement

Use a consistent file naming structure. A practical pattern is:

Provider_ReportingPeriod_Account_FileType

For example, a file might include the provider name, the quarter, the label account, and whether it is a sales or usage report.

Twin.so should save the file to the correct workspace or hand it to the next approved system. If the destination can’t be confirmed, stop the task. Never allow an uncertain run to overwrite an existing statement.

4. Record run metadata

Every successful download needs supporting information. Record the source, account, reporting period, file name, download time, and workflow status.

This information can sit in a tracking sheet, database, or royalty operations system. The exact destination depends on your current setup. The important point is consistency.

A file without source information becomes difficult to verify six months later. A file with source information can be traced, reviewed, and compared against the original portal.

5. Route the result for review

Don’t send every downloaded file straight to payment. Send it to an intake queue first.

The reviewer should confirm that the file covers the right period, belongs to the right account, and contains the expected columns. Once the file passes review, move it into the calculation workflow.

This is how you create automated royalty statements without removing accountability from the process.

RECONCILE DATA BEFORE YOU APPROVE PAYMENTS

Collection and reconciliation are different jobs.

Twin.so can help retrieve a statement. It can’t determine whether a payment rate matches a contract unless that rule exists in a separate, tested calculation system.

Your reconciliation process should compare the new statement against:

• The previous reporting period
• Expected usage or sales activity
• Contractual splits
• Recoupable costs and advances
• Territory and currency rules
• Known payment dates
• Prior artist or beneficiary totals

Look for practical exceptions. A statement may contain the right file name but the wrong period. A portal may publish a revised report without changing the original download name. A currency column may be missing because the provider changed its export format.

A monthly royalty automation discussion reflects a common expectation: teams want recurring statements without manually rebuilding the same process every month. Recurring collection only helps when the review rules are also recurring.

Set simple checks before you add complex logic. For example, flag a missing reporting period, a duplicate file hash, an empty data file, or a total that differs sharply from the prior period. The reviewer can then decide whether the difference is valid.

SAFEGUARDS, EXCEPTIONS, AND THE AUDIT TRAIL

Royalty data affects payments and rights-holder trust. Treat the automation like an operational system.

Start with access controls. Limit each browser task to the portals and actions it needs. Use separate accounts for separate entities where possible. Review who can edit, run, pause, and approve each workflow.

Build explicit exception paths for common failures:

• The login page changed.
• Multifactor authentication is required.
• No statement is available.
• The file has a new name or format.
• The reporting period is missing.
• A duplicate file already exists.
• The downloaded file is empty.
• The total falls outside the review threshold.

When an exception occurs, the workflow should stop and produce a useful message. That message should identify the provider, account, reporting period, failed step, and time of failure. “Task failed” isn’t enough for a royalty administrator to act.

Maintain an audit trail for every run. Store the workflow name, run ID, user or service account, source portal, timestamps, downloaded file, status, and reviewer decision. Keep the original source file unchanged. Create a separate normalized copy if you need to modify headers, formats, or values.

An automated download without a source record is only a file. An automated download with a source record is evidence.

Set approval thresholds based on your risk. A low-risk file rename may run without review. A new provider, changed format, or unusual payment total should require a person to approve the next step.

Never allow an automation to silently replace an existing statement. Save revised files as new versions and record why the change occurred.

ROLL OUT THE WORKFLOW IN A SMALL PILOT

Choose one provider and one reporting period for the first test. Use two recent statements if you have them. Run Twin.so beside the manual process and compare the results.

Check four things:

1. Did the workflow reach the correct portal and account?
2. Did it select the correct reporting period?
3. Did it download the complete file?
4. Can another team member trace the run without asking the person who built it?

Fix naming, timing, access, and exception rules before adding more sources. Then move the workflow into a scheduled process with a human review queue.

Keep a manual fallback. Portals change. Accounts expire. Providers revise their export pages. Your team needs a documented way to complete collection when the browser task stops.

CONCLUSION

Automated royalty statements work best when browser collection, accounting logic, and human approval have clear boundaries. Twin.so can handle repetitive portal work, while your royalty system manages contracts, calculations, reconciliation, and payments.

Start with one source. Capture complete run metadata. Stop on exceptions. Preserve the original files. That operating model gives music publishers, labels, managers, and independent creators faster collection without losing control of the numbers.