Concert Touring and Show Settlement Software: Why the Money Is Decided at 1am in a Promoter's Office and Nobody Can Reconstruct It Later

Why touring software usually stops exactly where the money starts

It is 1:05am in a promoter's office behind a 2,400 capacity room. The tour manager is looking at a settlement sheet handwritten on a printed template. It shows a gross, a set of deductions for facility fee, ticketing fee, credit card commission and a levy nobody explained, then production costs, then the split. The deal was a guarantee against 85 percent of net box office receipts after costs, which means the entire negotiation now hinges on what counts as a cost, and the promoter's list of costs includes a catering line that looks higher than what was actually on the table at 4pm.

The tour manager signs, takes a photo of the sheet on their phone, and moves on because the bus leaves in forty minutes. Three weeks later the business manager tries to build a tour profit and loss from 31 photographs of 31 different settlement templates in 9 currencies. This is not a fringe case. This is how a large part of the live music business accounts for its revenue.

The buyer for a fix is a tour manager, a head of touring at a management company, or a promoter's operations lead, and what they need is not an itinerary app. They need the money to follow the same object the show does.

Problem 1: the deal is a formula and the software treats it as a number

Live deals are structurally varied in a way most systems refuse to model. A flat guarantee. A guarantee versus a percentage of net, whichever is greater. A guarantee plus a bonus above a defined breakeven. A pure door deal. A co promote where costs and profit split between parties. A festival buyout with a rider allowance. Each of those has a different definition of gross, a different set of allowable deductions and a different breakeven point.

Master Tour is genuinely excellent at what it does, which is advancing, itineraries, day sheets and getting a touring party to the right place with the right information. It is not a settlement engine and does not claim to be. Prism.fm sits on the venue and promoter booking side and handles pipeline and holds well. Muzeek covers booking, contracting and payments for a certain scale of act. Artist Growth reaches further into touring financials than most. What none of them do reliably is hold your specific deal formula per show and compute the settlement from it against real box office and cost inputs.

What a custom build does: the deal becomes an expression attached to the show. Gross definition, deduction list with caps, breakeven, split percentages above and below breakeven, and any bonus tiers. Enter the box office counts and the costs, and the number comes out with every step shown. That single capability changes the 1am conversation, because the tour manager is no longer checking arithmetic under time pressure, they are checking inputs against a contract the system already knows.

Problem 2: the advance and the settlement are the same show and live in different worlds

The advance sets everything: capacity and holds by price tier, ticket fees, production costs agreed in principle, catering and hospitality, local crew counts, curfew, and the deal itself. The settlement then tests all of it. In practice the advance sits in emails and a shared document, and the settlement sits on a printed template in a different building, and the only person who joins them is the tour manager, from memory, at 1am.

What a custom build does: one show record carries the deal, the agreed cost assumptions from the advance, the ticket scaling by tier, and then the actual counts and actual costs at settlement. Variance is computed automatically. When a promoter's catering line is 40 percent above the advanced figure, the tour manager sees the flag before signing rather than working it out afterwards. Over a routing, the same data tells you which promoters consistently advance one number and settle another, which is commercially useful information no management company currently has in a usable form.

Problem 3: the tour profit and loss is built in nine currencies from a shoebox

Costs on a tour are production, trucking, buses, flights, freight, visas and work permits, crew salaries, per diems, hotels, insurance, commissions and tour support. Revenue is show income, merchandise, sometimes VIP packages and sometimes a sponsorship contribution. Both sides arrive in local currency, at different times, from different people, and much of it arrives as receipts photographed by crew members.

What a custom build does: a single tour ledger where every cost is coded to a show or to the routing overhead, captured in its original currency with the rate applied at a defined date rather than whenever accounts got round to it. Per diems generate from the itinerary rather than being calculated by hand. Crew members submit receipts against their own show and their own category from a phone, offline, because the bus does not have signal. The tour profit and loss then exists during the tour rather than six weeks after it ends, which is the point at which it could still change a decision.

On withholding tax, be careful with anyone promising automation. Foreign entertainer withholding differs by territory and by treaty position, and the correct answer for your artist is a question for a specialist adviser. What software should do is capture the withholding actually deducted at each settlement with the paperwork attached, so your adviser can reclaim what is reclaimable. The reclaim is often material and it is regularly missed because the documentation lives in a photograph.

Problem 4: the touring party is a moving workforce nobody scheduled properly

Crew, band, local hires, drivers and freight all have their own movements, their own contracts and their own compliance requirements. A visa or work permit that does not cover a specific date is a cancelled show. A driver hours limit that is exceeded is a legal problem and a safety one. A crew member's day rate and their per diem run on different clocks.

What a custom build does: the personnel record carries contract terms, rate, permit coverage with dates and territories, and travel. The routing checks itself against those, so a border crossing on a date where one member's permit has lapsed shows up during routing rather than at immigration. This is not exotic engineering, it is a set of date range checks, and the reason nobody has it is that the itinerary system and the contract records have never lived in the same place.

What this costs and how long it takes

A first touring cycle, meaning the show record with deal expressions, advance capture, settlement computation with variance flags, and a tour cost ledger with mobile receipt capture, runs $65,000 to $160,000 and ships in 12 to 18 weeks. A full platform adding multi currency consolidation, crew and personnel records with permit checking, per diem generation, merchandise and VIP revenue, promoter performance analytics, and accounting system integration runs $200,000 to $450,000 phased over 6 to 12 months.

What pushes cost up in touring specifically: the number of distinct deal structures you actually use, since each one is a formula that needs testing against real historical settlements. Multi currency, because doing it properly means rate policy, revaluation and a clean audit trail rather than a conversion at export. Accounting integration, as management companies, promoters and production companies all run different ledgers and the mapping is bespoke. Offline capability, which is not optional, because arenas, trucks and border crossings are all places with no usable connectivity and all places where data gets captured. And ticketing data, which in some markets you can get as a feed and in others arrives as a promoter's printout, so design for both.

Build versus buy, and when buying is the right call

Buy if you are running straight guarantee shows in one currency and your main problem is logistics rather than money. Master Tour is a strong product for exactly that and you should use it. If you are a promoter whose pain is holds, offers and confirmations rather than settlement, Prism.fm addresses that specific workflow. Muzeek is a reasonable fit for acts at a scale where booking and payment collection are the bottleneck.

Build when the settlement itself is where value leaks. Concretely: when you run versus deals and co promotes, when settlements happen against promoter cost lists you cannot verify in the room, when the tour profit and loss takes weeks to assemble after the routing ends, or when you tour internationally and withholding documentation goes missing. Our position is that touring companies overinvest in itinerary tooling and underinvest in the settlement record, because the itinerary problem is visible daily and the settlement problem is only visible in aggregate, once a year, when it is too late to do anything about it.

How to choose a developer for touring and settlement software

Ask them to express a guarantee versus 85 percent of net after costs with a bonus tier, in front of you. If they reach for a fixed set of fields rather than a configurable deal expression, they will build you a calculator for one deal type and you use six.

Ask what happens when a tour manager opens the app in a promoter's office with no signal. It must work fully offline, hold the settlement locally, and sync later with a device timestamp. Anything else means the sheet gets photographed again and you have changed nothing.

Ask how they handle currency. The right answer involves capturing the original currency and amount, applying a rate under a stated policy, and keeping both, not converting at the point of entry and losing the source figure.

Ask who owns the code, the infrastructure and the settlement data, and settle it in writing before kickoff. Your show by show settlement history is the evidence base for every future deal you negotiate with those promoters, and it is worth more each year it accumulates. At Digital Heroes the client owns the repository and the data from the first commit.