Multi-Currency Tour Invoice Consolidation & Foreign Tax Credit

A touring artist's back office consolidates a year of multi-country tour invoices and foreign withholding certificates by extracting each document into one Excel or CSV table. At minimum, the table carries show date, country, gross fee in original currency, currency code, withholding rate, withholding amount, certificate identifier, FX rate, and the home-currency triplet (gross, withholding, net). That single table is then both the home-currency P&L and the per-country foreign tax credit support schedule attached to Form 1116 in the U.S., Form T2209 in Canada, the Foreign Income Tax Offset claim in Australia, or SA106 in the U.K.

The work is mostly schema discipline — populating the columns deliberately as documents arrive, not patching them row-by-row in March. Get the columns right and the four target FTC support schedules become sorts and pivots on the same table. Two adjacent live-music workflows look close enough on the search results to confuse, and this article is not either of them: the tour accountant's same-night work — show settlement, road float, deal-memo reconciliation against box office — is in-tour show settlement and tour accounting invoice processing, and film, TV, and streaming guild residuals administration is entertainment residuals processing for film and TV guild statements. Multi-country touring artist bookkeeping for a year-end FTC schedule is the third workflow, and the row-level extraction map for it is what nobody publishes.

The IRS, HMRC's Foreign Entertainers Unit, the CRA, and the ATO publish the rules for what to file. Tour-management resources cover the in-tour stage and stop at "give the receipts to your accountant." Generic multi-currency accounting vendors talk to multinational CFOs running consolidated subsidiary accounts, which is not the same problem. The piece nobody publishes is the schema and the prompt design that turn a stack of agency invoices, venue invoices, rider receipts, and nine kinds of withholding certificate into the same table the bookkeeper attaches to a tax return. That is what follows.

The document stack the back office actually receives

The post-tour pile splits cleanly into two layers — the invoices issued from the artist's side, and the certificates foreign tax authorities issue back. Keeping them separate matters; once they are interleaved the reconciliation step gets harder, not easier, because the whole point of section 5 is to join one against the other.

Invoices the artist or agency issues

Agency-issued performance fee invoices to promoters and festivals carry the artist's gross contracted fee for the show. Where the artist is represented by an agency, the invoice typically reads as issued by the agency on behalf of the performer, with the promoter or festival as the addressee — that "for the attention of" line is the promoter, not the artist, and it is a recurring source of vendor-identification errors handled in section 7. This is the document withholding will attach to.

Venue buyout invoices appear when the deal is structured as a flat venue fee rather than a guarantee plus splits. Whether withholding attaches depends on whether the buyout is treated as performance income to the artist's contractual entity or as a payment to a separate venue entity; the schema's category-flag column is what carries that distinction into the FTC step.

Rider and travel reimbursement invoices are artist-side cost recoveries — the freight on the backline, the per-diems, hotel pass-throughs, ground transport. These are not performance income, withholding generally does not attach to them, and they belong on the spreadsheet flagged in their own category so they do not silently land in the foreign-income total on a Form 1116 or a T2209 schedule. Per-diem and ground-transport receipts end up in the same year-end stack when the back office is also building the management P&L from these documents; the schema can carry them as their own category rather than forcing a second workflow.

Certificates foreign tax authorities issue back

These are the documents the home-country tax authority will want to see when the FTC claim is reviewed. The back office's pile typically holds some subset of nine certificate types depending on which markets the tour visited:

U.S. Form 1042-S. The IRS-prescribed information return the U.S. payor (promoter, festival, or central withholding agent) issues to the foreign performer for U.S.-source performance income, listing gross income paid, U.S. tax withheld, the income code, and the withholding agent. The 1042-S is the cleanest of the nine because the form layout is uniform across payors.
U.K. FEU statement. Issued by the U.K. payor reporting under the Foreign Entertainers Unit regime within HMRC, summarising gross fee, U.K. tax withheld at the basic rate (or at the reduced rate where an FEU2 or FEU8 reduced-rate certificate has been granted pre-show), and the payment details.
Canadian Regulation 105 receipt. The T4A-NR slip the Canadian payor issues for non-resident services performed in Canada, listing gross fee, Reg 105 withholding (typically 15% federal, plus Quebec's 9% in Quebec), and the payor and recipient details.
German Steuerbescheinigung issued under §50a EStG. A one-page certificate the German promoter (Veranstalter) issues showing the gross fee, the §50a withholding rate (the headline rate is 15% plus solidarity surcharge for the basic case), and the tax remitted. The article does not reach into the German promoter side; the certificate exists because that side did its job and remitted to the Bundeszentralamt für Steuern.
Spanish IRNR certificate. The Modelo 296-supported certificate the Spanish payor issues evidencing the IRNR (Impuesto sobre la Renta de no Residentes) withholding for the artist's Spanish-source performance income.
Australian Payment Summary. The ATO-prescribed payment summary the Australian payor issues evidencing FRWT (foreign resident withholding tax) deducted from amounts paid to the foreign-resident performer for Australian shows.
Dutch Artiestenregeling statement. The Dutch payor's certificate under the artistes-and-sportspersons regime, evidencing the wage-tax-equivalent withheld on the gross fee for Dutch performances.
French Article 182 A bis attestation. The French payor's attestation of the Article 182 A bis withholding on the artist's France-source performance income, with rate and gross.

A useful concrete anchor for the U.S. row of this inventory: a non-resident artist or athlete performing independent personal services at a U.S. event will usually have 30% withheld from the gross income earned, unless a Central Withholding Agreement is in effect, per IRS guidance on the Central Withholding Agreement program for foreign artists and athletes. That 30% is the default the 1042-S will document; the CWA case where it is not 30% is the edge case in section 7.

Each certificate is a one-page summary of gross fee, rate withheld, amount withheld, and the payor — and at year end each one is the evidence the home-country tax authority needs to grant the foreign tax credit for that show. A row in the extraction table without the matching certificate identifier is, for FTC purposes, a row without proof of foreign tax paid.

The agency-issued performance fee invoice is also worth seeing from the other direction. The same invoice the back office files away as performance income from a German festival is the document the promoter or agency's inbound review of the same artist fee invoice was looking at on the way in, with a different set of concerns — payment approval, not foreign tax credit support. Useful context for understanding why some payors push back on rebill or correction requests once the show is in the rearview mirror, and useful framing when the back office is the one chasing missing certificates from a payor that has already considered the file closed.

When the back office is extracting at scale rather than transcribing — using AI extraction across a year of these documents in one pass — the operational job is to extract artist agency invoices for the tax return at the same time as it extracts the matching withholding certificates, so the joins in section 5 have something to join on.

The extraction table, column by column

Every row in the table represents one document — one agency invoice, one venue buyout, one rider invoice, or one withholding certificate. The columns are designed so that the reconciliation step can match an invoice row to its certificate row, and so that the FTC support step can group rows by country and by category without re-extraction. A few columns will look redundant on any single row; they exist for the joins, not for the row in isolation.

The columns

Show date. The date the performance happened. Anchors FX conversion when the home-country method is date-of-payment-adjacent, and assigns the row to the correct tax year. Distinct from the payment date, which can lag the show by months.

Country. The country where the show was performed — the source country for tax purposes. In some structures the promoter's country of incorporation differs from the show country (a U.K.-incorporated promoter putting on a Berlin show); the show country is what determines which jurisdiction's withholding regime applies.

Jurisdiction. The specific withholding regime in force on that row: U.S. federal, U.K. FEU, Canadian federal Reg 105, Quebec where applicable, German §50a EStG, Spanish IRNR, Australian FRWT, Dutch Artiestenregeling, French Article 182 A bis. Country and jurisdiction answer different questions and should not be merged into one column. Multi-jurisdiction countries (Canada with Quebec, the U.S. with state-level overlays) and country pairs that share a regime would each break a single-column shortcut.

Promoter / payor entity. The legal name of the entity that paid. In a third-party-payor structure, that is the entity which actually settled the wire — not the entity whose name is on the deal memo. This column is the one that joins to the certificate's "payor" or "withholding agent" field.

Performer entity. The contractual entity the invoice was issued from on behalf of the artist — sole proprietor in country A, loan-out company in country B, agency-as-agent in country C. The "for the attention of" addressee on an agency invoice is the promoter or festival, not the performer; conflating the two is a recurring error and the reason for keeping these as separate fields.

Gross fee in original currency. The contracted performance fee before any deduction. The number from the invoice, untranslated.

Currency code. ISO 4217 three-letter code — USD, EUR, GBP, AUD, CAD, CHF, JPY, and so on. A separate column from the amount because the FX work in section 4 keys off it, and because aggregating across rows requires the currency to be machine-readable.

Withholding rate. The rate stated on the certificate, expressed as a percentage. This is the rate actually withheld, not the legal default for the jurisdiction. Section 7 covers when and why the two diverge — treaty positions, pre-tour reduced-rate certificates, and CWA-negotiated rates.

Withholding amount in original currency. The absolute withholding figure from the certificate, in the same currency as the gross fee. Where the certificate has not yet arrived, this column is empty and the certificate-status column carries the reason.

Net paid in original currency. What hit the artist's or agency's bank account in the original currency — gross minus withholding minus any other deduction the certificate evidences. Holds even where withholding is zero, because the column is populated from invoice and remittance evidence rather than calculated.

FX rate. The rate used to convert original currency to home currency for this row. Stored as a number rather than computed downstream, because the FTC support schedule will be reviewed against the rate that was actually used.

FX method. Date-of-payment, annual average, monthly average, or another method permitted by the home-country regime. Section 4 walks through which method each home-country tax authority accepts. Recording the method per row matters because a single return can defensibly mix methods only where the regime allows it, and the reviewer needs to see which row used which.

Home-currency gross. The gross fee converted using the FX rate and method on the row. Feeds the home-currency P&L and the foreign-income figure on the FTC schedule.

Home-currency withholding. The withholding amount converted using the same FX rate and method as the gross. Most regimes require consistency across the row; using yesterday's rate for the gross and today's rate for the withholding produces a row that does not balance and invites a request for evidence.

Home-currency net. The net amount converted, which should equal home-currency gross minus home-currency withholding within rounding tolerance. A row where the three columns do not reconcile flags an FX-method or arithmetic error before the schedule is filed, not after.

Certificate identifier. The certificate's own reference number — 1042-S form sequence, FEU statement number, Reg 105 receipt number, Steuerbescheinigung serial, IRNR Modelo 296 reference, ATO Payment Summary number, and so on. The audit trail to the underlying document.

Certificate status. One of received, requested, or outstanding. The reconciliation step depends on this column being populated even when the certificate itself is not yet in hand, because outstanding rows are the work the back office still owes the FTC schedule.

Category flag. Artist fee, venue buyout, rider, travel reimbursement, or per-diem. Drives FTC eligibility (only performance-income rows feed foreign-income totals) and the home-currency P&L category split (rider and travel reimbursements do not appear on the income side; they appear as cost recoveries elsewhere).

Gross-up vs net-of-withholding flag. Which side of the deal absorbed the withholding. In a gross-up structure the promoter or festival agreed to pay the contracted gross figure on top of the foreign tax, and the foreign tax was effectively paid on the artist's behalf; in a net-of-withholding structure the artist directly bore the withholding. FTC eligibility differs because of the indirect-tax treatment in gross-up cases, and section 5 covers the reconciliation consequence.

One prompt, one shape, every document

The schema works because one extraction prompt produces it from every document type in the year. The back office uploads the year's stack — agency invoices, venue invoices, rider receipts, the various withholding certificates — in batches, and the same saved prompt extracts the same column layout from each, leaving fields blank where they do not apply. A rider reimbursement invoice has no withholding columns; a Form 1042-S has no rider category; a Steuerbescheinigung has no net-paid column because that figure lives on the matching invoice instead. The schema accommodates the gaps by design, because the joins in section 5 are what re-form the picture. This is the workflow where AI invoice data extraction for tour back-office documents earns its place over manual transcription, and the resulting Excel, CSV, or JSON file carries the same column shape on every row regardless of which document type produced it. Source-file references on each row let the bookkeeper trace any value back to the underlying PDF during review — a load-bearing capability for an FTC support schedule, because the home-country tax authority may query a row years later and the answer is the original certificate behind that row.

The extraction layer is not the filing layer. The product produces the structured table; the bookkeeper or CPA reviews the table, resolves the outstanding-certificate rows and the rate mismatches, and only then does the table feed a tax return or a management P&L. The same applies to FX: the user supplies the FX method and the rate (or a multiplier in the prompt that turns original currency into home currency at the chosen rate), and the extraction reads the original-currency amount from the document and applies the user's instruction. The point of the schema is consistency across thousands of documents in a touring musician multi-currency spreadsheet, not auto-filing.

FX conversion choices by home-country tax regime

The FX method recorded in the table has to be one the artist's home-country tax authority accepts as evidence of foreign-income translation, because the FTC support schedule is reviewed against that standard. The home-currency P&L and the FTC support schedule are the same table; the FX method has to satisfy both.

Each of the four largest English-language home-country regimes offers more than one defensible method. The article does not pick one for the reader. The point is that whichever method the practitioner chooses gets recorded per row alongside the rate itself, so the schedule survives review years after the show.

U.S.-resident artist filing Form 1116

The IRS yearly average exchange rate is the practical default for translating foreign-currency income for foreign tax credit purposes, and the IRS publishes the rates by currency for prior tax years. For most touring schedules — many shows, many currencies, one return — yearly average is the method that scales without per-row date research. The schema's FX-method column reads "IRS yearly average" for these rows, and the FX rate column carries the published yearly average for the relevant currency and tax year. Spot rates on date of receipt are also defensible and can be appropriate where the foreign income is concentrated in a small number of payments rather than spread across a touring year, but mixing methods within one return invites a question and the column has to record which row used which.

Canadian-resident artist filing T2209 / TP-772-V

The CRA accepts the Bank of Canada exchange rate, with a choice between the Bank of Canada daily rate on the date the income was received and the Bank of Canada annual average rate published for the relevant year. For a year of cross-border touring, the annual average is the simpler method and is usually defensible when the foreign-source income is spread across the calendar; the daily rate is more appropriate when the income is concentrated in a few high-value payments. The schema records which of the two was used per row because mixing methods inside a single T2209 / TP-772-V invites a request for the underlying evidence, and the answer the back office wants to give is "every row's FX-method column reads either Bank of Canada daily or Bank of Canada annual average, here is the rate used and the source."

Australian-resident artist claiming the FITO

The ATO publishes its own foreign-exchange-rates guidance for translating foreign income for the Foreign Income Tax Offset, and the back office records the rate and the ATO source per row to match. The general principle is the same as the other regimes — pick a method the authority accepts, record it consistently, and have the per-row evidence on hand if the offset claim is reviewed.

U.K.-resident artist filing Self Assessment with SA106

HMRC accepts spot rates or monthly average rates for converting foreign income on Self Assessment. The practitioner picks one method and applies it consistently across the return. For a touring year the monthly average is usually the method of least friction; for a tour with a small number of high-value foreign payments the spot rate on the date of receipt is often closer to the economic reality. The schema's FX-method column reads "HMRC spot" or "HMRC monthly average" per row, and the FX rate column carries the rate used.

One operational consequence

When the FX method is annual average, the show date determines the tax year, and the same year's annual average is used regardless of when in the year the show happened. When the FX method is date of payment, the FX rate column carries the rate published for the actual payment date — which is a different date than the show date when payment lags by weeks or months. Confusing the two is one of the more common errors at year end, especially for tours that close out across the calendar boundary. To convert tour invoices to home currency without that error, the FX rate column has to be populated against whichever date the row's FX method calls for — show date for annual-average rows, payment date for date-of-payment rows — with the underlying remittance evidence available in the source-file reference.

Reconciling agency invoices against the foreign withholding certificates

The reconciliation step is a join. Invoice rows carry gross and net amounts and an expected withholding country; certificate rows carry certificate identifiers, withheld amounts, and a payor. The join key is usually country plus payor plus show-date proximity, because the certificate may not name the show explicitly — a quarterly Form 1042-S can aggregate a payor's full year of payments to one performer, and the back office has to allocate the certificate's withholding across the matching invoices itself. The schema's certificate-identifier and certificate-status columns are the pivot on which non-resident performer withholding reconciliation runs.

The three reconciliation states

Matched. The invoice row has a certificate row whose gross income and withholding amount agree, within rounding tolerance, and whose rate equals the rate the invoice expected. Certificate-status reads "received". This is the clean case and feeds the FTC schedule directly.

Outstanding. The invoice row has no certificate yet. Certificate-status reads "requested" if the chase is in progress with the payor or the foreign tax authority, and "outstanding" if the row is sitting unaddressed. The home-country FTC support schedule typically cannot include the credit without the certificate as evidence; until the certificate arrives, the foreign tax that was withheld on that show is a known number but an unsupported claim. The status column lets the bookkeeper see at a glance how much foreign tax credit is parked behind missing paperwork.

Mismatched. A certificate exists, but the withholding rate or the withholding amount does not equal the legal default for the jurisdiction. This is the row that needs adjudication. Silently accepting it is what produces an FTC schedule that does not survive review.

Why a rate may legitimately not equal the legal default

There are three good reasons a withholding rate on a certificate sits below — or, occasionally, above — the headline default for the jurisdiction. Each one is the row's own story; the back office's job is to record which story applies.

A treaty-based reduced rate. The artist's home country has a tax treaty with the source country that reduces the headline artist-and-athlete withholding rate. The certificate may carry a treaty article reference; if it does, the schema records the reference and the rate together so the FTC schedule can defend the rate later. Where the treaty position has not actually been claimed pre-show — for example, where a U.S. payor withheld at 30% even though the artist's country of residence has a treaty position that would reduce the rate to a lower figure for short-stay performers — the back office's path is usually a refund claim with the IRS rather than a schema fix, and the row stays at 30% with a flag.

A CWA in effect for U.S. shows. When the IRS has approved a Central Withholding Agreement for a U.S. tour leg, the rate the payor applies on the 1042-S is the CWA-agreed estimated rate calculated against estimated net U.S. tax liability — typically well below 30% — rather than the 30% default. The CWA case is handled in section 7; it is mentioned here as one of the legitimate reasons a 1042-S may not show 30%.

A pre-tour reduced-rate application granted by the source country's authority. A U.K. FEU2 or FEU8 reduced-rate certificate granted by HMRC's Foreign Entertainers Unit before the show, a Canadian Regulation 105 waiver granted by the CRA, a Spanish IRNR reduced-rate authorisation, and so on. Each of these is a payor-facing instruction that the legal default rate should not be applied to this artist for this show. The certificate the back office receives after the show will carry the reduced rate as a result, and the schema records the reduced-rate authorisation reference alongside the rate.

When a mismatched row maps to one of these three reasons, the schema records the supporting reference (treaty article, CWA identifier, FEU2/FEU8 number, Reg 105 waiver number) and the row closes as defensible. When it does not — when the rate is wrong because the payor calculated it incorrectly, or because the certificate was prepared in error — the row is genuinely an error and the back office contacts the payor or the certificate issuer. The schema should not absorb the error silently; the FTC schedule attached to the home-country return is what the home-country authority will see, and it has to either claim the credit at the rate the certificate evidences or carry the reason the certificate's rate is not the headline default.

Gross-up versus net-of-withholding deals

The deal structure changes how the credit flows even when the rate and the amount on the certificate are correct. In a gross-up deal, the promoter or festival agreed to absorb the foreign withholding and pay the artist the contracted gross fee on top of the tax — the foreign tax was effectively paid on the artist's behalf, the artist's economic position is the contracted gross, and the FTC schedule should still claim the credit with the certificate as evidence because the foreign tax was paid in respect of the artist's foreign-source income. In a net-of-withholding deal, the artist's economic position is the contracted gross minus the foreign withholding, and the FTC claim follows directly from the certificate.

The gross-up flag column on the schema carries the distinction into the FTC step. Without the flag the two deal structures look identical on the row — same gross, same withholding, same net — and the home-currency P&L treats the gross-up case incorrectly, understating the artist's effective fee. The schema records the flag explicitly because the deal memo is where the answer lives, and the deal memo is not on the certificate.

When the U.S. side is doing the inverse exercise

When the back office is chasing an outstanding U.S. certificate, it is worth knowing what the U.S. payor's accounts payable team is actually doing on its side. They are extracting foreign withholding tax from tour invoices in exactly the inverse direction — collecting W-8BEN, withholding at 30% or the CWA rate, remitting to the IRS, and producing the Form 1042-S the back office is waiting for. The mechanics are documented from the AP perspective in U.S. AP teams handling foreign vendor withholding and Form 1042-S reporting, and the article is a useful reference when chasing a payor whose 1042-S has not yet arrived: the timing, the form's annual cycle, and the W-8BEN dependency all sit on that side of the workflow.

How the table feeds Form 1116, T2209, FITO, and SA106

The column choices in section 3 — country, jurisdiction, gross fee, withholding rate and amount, FX rate and method, the home-currency triplet, certificate identifier, category flag, gross-up flag — were chosen so the populated table can be sorted, filtered, or pivoted into any of the four target FTC support schedules without re-extraction. The table is the data layer; the four regimes below are four different presentations of the same data. A tour income foreign tax credit spreadsheet that satisfies one regime should, with the right grouping, satisfy the others.

U.S. Form 1116

Form 1116 reports foreign income and foreign tax paid by category basket — passive category, general category, and the rest — with per-country sub-totals inside each basket. The form expects the gross foreign income converted to USD using the IRS yearly average rate (or another method the filer can defend), and the foreign tax paid converted using the same rate.

From the extraction table the work is:

Filter to performance-income rows. Category-flag values of artist fee, venue buyout, and any other performance-income flag stay in; rider, travel reimbursement, and per-diem rows are excluded — they are not foreign income for FTC purposes.
Assign each row to its 1116 basket. For touring artists, performance income is typically general-category foreign-source income, but this is the practitioner's call per the row's facts.
Group by country within each basket. Sum the home-currency gross column to produce the foreign income line per country, and sum the home-currency withholding column to produce the foreign tax paid line per country.
The FX-method column should already read "IRS yearly average" for these rows from the section 4 work, and the FX-rate column should already carry the published yearly average for the relevant currency and tax year. The schedule attached to the return is the filtered, sorted detail.

Canadian Form T2209 (federal) and TP-772-V (Quebec)

The Canadian case is a two-form variant. T2209 calculates the federal foreign tax credit per country, against non-business and business income separately, and TP-772-V mirrors the calculation at the Quebec level for Quebec-resident artists. The extraction table feeds both: filter to performance-income rows, sort by country, sum the home-currency gross per country as the "foreign income" figure (allocated between non-business and business per the row's own classification), and sum the home-currency withholding per country as the "non-Canadian income tax paid" figure. The FX-method column should already read "Bank of Canada daily" or "Bank of Canada annual average" per row from the section 4 work, with the rate in the FX-rate column. The Bank of Canada rate evidence the CRA expects on review is that per-row rate column itself, attached as the support schedule. For Quebec residents the same grouping translates directly to TP-772-V.

Australian Foreign Income Tax Offset

The FITO claim is governed by the ATO's foreign income tax offset rules, with eligibility tied to the income being assessable foreign income and to the foreign tax having been paid on that income.

From the extraction table:

Filter to performance-income rows.
Group by country to produce the per-country foreign income (in AUD) and the per-country foreign income tax paid (in AUD), drawn directly from the home-currency gross and home-currency withholding columns.
The FX-method column should reflect one of the ATO's accepted approaches, and the rate column should carry the rate used. The ATO offset cap calculation is the practitioner's work, applied on top of the per-country totals the schedule supplies.

U.K. Self Assessment with SA106

SA106 carries foreign tax credit relief on Self Assessment, and the relief is capped at the U.K. tax otherwise payable on the foreign income — so the schedule attached is evidence (per-country foreign income, per-country foreign tax paid) rather than the credit calculation itself. The mechanics on the extraction table are the same as the other regimes: filter to performance-income rows, group by country, sum home-currency gross per country as the foreign-income line and home-currency withholding per country as the foreign-tax-paid line. The FX-method column should read "HMRC spot" or "HMRC monthly average" consistently across the return, with the rate per row in the FX-rate column.

What the schedule does not do

Tax-return preparation, line-level form completion, and the calculation of credit caps and limitations sit with the practitioner. The extraction table is the source of truth for the figures that go into that work; it is not the return. A row in the schedule that the practitioner decides to exclude — because the gross-up structure changes the credit treatment, because the certificate is outstanding and the credit cannot yet be claimed, because the income basket is contested — gets excluded at the schedule-to-form step rather than being deleted from the table. The table is the audit trail; the schedule is one view of it; the return is what the practitioner files based on the schedule.

Edge cases — vendor identity, third-party payors, and CWA-negotiated rates

Three cases break a naive single-row, single-entity reading of the schema. A single performer billed via multiple legal entities across countries; a promoter that pays through a third-party payor entity; and a U.S. show under a Central Withholding Agreement where the rate is the IRS-negotiated estimated rate rather than 30%. None of the three requires a second schema. Each is handled by populating existing columns deliberately.

Multi-entity performers

The same artist may invoice as a sole proprietor in one country, through a loan-out company in another, and through the agency-as-agent in a third. Treaty positions, banking arrangements, and tour-routing decisions all push toward different contractual entities for different legs. The schema's performer-entity column carries the contractual entity for that row — the entity actually invoicing — while the country column carries the show country and the payor column carries the entity that paid. Three distinct columns answer three distinct questions:

Which artist-side entity is the foreign income attributed to for the home-country return?
Where was the show held, for jurisdiction purposes?
Who paid, for matching to the certificate?

The "for the attention of" addressee on an agency-issued invoice is the promoter or festival receiving the invoice, and it should never be confused with the performer entity. The extraction prompt has to treat them as separate fields explicitly — pull the issuing entity (the artist's contractual entity) into the performer-entity column, pull the addressee (the promoter or festival) into the payor column, and accept that the agency may appear in either or neither depending on the row's structure.

For home-country return purposes, foreign income is usually attributed to the performer entity that is the artist's home-country tax filer. Where the loan-out company is the contractual entity in the source country but the artist files personally in the home country, the foreign income flows through to the personal return per the home-country regime's pass-through rules, and the schedule has to be defensible on that basis. The schema does not solve the legal-entity question; it makes the question legible by surfacing performer entity, country, and payor as separate columns rather than collapsing them.

Third-party payor structures

A festival may book the artist through an agency but settle the wire through a separate payment-services entity. A U.S. promoter operating under a CWA may settle through a CWA-designated central withholding agent rather than paying the artist directly. A multi-night residency at a venue group may be booked under one corporate name and paid through the group's treasury function in a different country.

The payor column on the row should reflect the entity that actually paid — the entity whose name will appear on the wire confirmation or the cheque — not the entity that signed the deal memo. The certificate the back office receives, when it arrives, will be issued by or against the actual payor; if the schema's payor column carries the deal-memo entity instead, the join in the reconciliation step will fail and the row will look outstanding when it is not. The deal-memo entity is useful information and can live in a separate column or a notes field, but the join key is the actual payor.

The CWA case

When a touring artist has negotiated a Central Withholding Agreement with the IRS for a U.S. tour leg, the rate applied on the Form 1042-S is the CWA-agreed estimated rate calculated against estimated net U.S. tax liability, not the 30% default. CWA rates are typically a meaningful fraction of 30% — the agreement's whole point is that withholding more closely tracks the artist's actual U.S. tax liability — and they vary tour-to-tour because the CWA is negotiated against a specific set of projected gross fees and deductions.

The schema accommodates the CWA case by recording the CWA-agreed rate in the withholding-rate column and the CWA identifier alongside the certificate identifier. The CWA case is the cleanest illustration of why the schema records the rate per row rather than computing it from a per-jurisdiction default lookup: a U.S. row with a 12% CWA rate and a U.S. row with the 30% default coexist on the same return, and the only thing that distinguishes them is what the certificate evidences and what supporting reference the back office has on file.

The CWA case also drives a year-end true-up. The CWA estimated rate is, by design, an estimate; the artist's actual U.S. tax liability — calculated on the artist's U.S. return — may be higher or lower than the CWA assumed, and the difference is settled when the return is filed. The schema's role is to carry the CWA-evidenced figures cleanly into the U.S. return and into the home-country FTC schedule, with the per-row CWA reference making the rate rationale reproducible on review.