Withholding Tax on Cross-Border Payments: The TRA File the Bank Will Ask For

This page is the cross-border withholding operating file: which outward payments from a Tanzanian resident commonly meet a TRA withholding row, what the bank will reconcile, and why a treaty slogan is not a return. It is not the 2026 rate table, not a transfer-pricing treatise, and not a BOT circular.

• Rate map (confirm live): 2026 tax rates
• Treaty claims: double tax treaties
• Related-party substance: transfer pricing
• The SWIFT pack: repatriating profits

As at 10 September 2026. Confirm tra.go.tz and the Finance Act of the year. This page publishes no withholding percentage, no due date, and no invented section number. Zatra’s professional fee is only on /pricing/.

Name the payment before you name a rate

Withholding is a classification problem first. Dividend, interest, royalty, natural-resource payment, insurance premium, and a service fee with a Tanzanian source are different rows. Calling a dividend a ‘management fee’ to skip corporate authorities, or calling a management fee a dividend to skip substance, is how you buy two TRA files and a bank suspicion. Pick the legal category that matches the contract and the facts.

Resident-to-resident withholding exists too: that is a sibling orientation, not this page. This page is money leaving, or a non-resident’s Tanzanian-source income being paid by a Tanzanian person. If you are not sure which, stop and take advice. Guessing the row is how a later assessment is built.

Who is the withholder

The Tanzanian payer is usually the person TRA will ask. A Tanzanian company paying a Dubai consultant, a Nairobi parent, or a South African licensor should assume it has a withholding file until the live Act says otherwise. ‘The invoice was in dollars’ does not move the file. ‘We paid from a foreign account of the same group’ can make the file worse, not better.

Branches, permanent establishments and Zanzibar companies add a Union overlay. A BPRA company can still meet Union income-tax withholding. Confirm which desk takes the return. The Union-versus-non-union page is the split. This page is the payment.

What the pack usually contains

Orientation, not a frozen TRA form. Confirm the live return, the payment code, and whether a nil explanation is a filing or a silence. Silence is how penalties (whatever the live figure is; not published here) get discussed later.

Treaties reduce a row. They do not skip the file

Where a double-tax agreement applies, a reduced rate can exist. TRA will still want the residence paper and the beneficial-owner story the live practice asks for. Wikipedia is not that paper. A holding company in a treaty state with no substance is how the claim dies. See the treaty page. Do not model a reduced rate in a term sheet until the claim file exists.

Limitation-on-benefits and beneficial-owner language are live treaty text. This page will not paraphrase a protocol from memory. Read the treaty that is actually in force for that partner state. Confirm TRA’s list of instruments in force, not a blog list.

The bank is in this file

Commercial banks applying BOT documentary standards often ask for TRA evidence on outward payments that look like income. A withholding receipt, a payment slip, or a reasoned confirmation that none applies, whatever the live bank list wants, sits next to the invoice. See BOT foreign-exchange rules. A TISEZA certificate is not a withholding exemption.

Related-party fees attract more questions, not fewer. Have the contract, the board paper, the transfer-pricing file, and the WHT file in the same sitting. Splitting them across three consultants who do not read each other is how the SWIFT sits.

Management fees, in operator language

Groups love a monthly management fee. TRA loves asking who sat in which chair. If the fee is the only way cash leaves because the company has no distributable profits, expect the fee to be recharacterised in an audit conversation. Substance: named people, named work, named hours or deliverables, an invoice a stranger could understand. A one-line ‘HQ support’ is not substance.

Local withholding on resident professional fees is a different row. Do not paste a non-resident service-fee story onto a Dar advocate’s invoice, or the reverse.

GN 487A is not a WHT rule

Reserved business classes can still generate lawful payments if the company is allowed to exist. They do not create a secret TRA exemption. Screen the activity on the restricted list before you build a fee structure that assumes the company can trade.

Sequence

1. Classify the payment against the live Income Tax Act families, not against the email subject line.
2. Check a treaty claim only if the beneficial owner is actually resident in that state.
3. File or pay on the live TRA process before you promise a value date.
4. Match names across BRELA/BPRA, TIN, invoice, return and SWIFT.
5. Keep the evidence with the next audit pack and the next dividend.

Where this file stalls

• Promising a Friday remittance on a Thursday invoice with no WHT thought
• Treaty rates copied from a slide deck
• Management fees with no named work
• Paying from a director’s personal account to ‘save time’
• Mixing Zatra’s fee into a TRA charge: pricing only

Worked path: Dubai consultant vs Nairobi parent dividend

A Dar manufacturer paying a Dubai individual for a two-week factory diagnostic is a service-fee story: contract, deliverable, where the work was done, and the live non-resident row. If the person did the work physically in Tanzania, the source story is usually easier for TRA to like and harder for a ‘foreign services’ slogan. Confirm the live source rule. Do not invent it.

A Dar manufacturer paying a Nairobi parent a dividend is not that story. It needs accounts, resolutions, and the dividend row, plus any treaty file. Pushing the same cash through as ‘regional support’ is how you explain two instruments in one audit. Use the repatriation page for the corporate act. Use this page for the TRA slice of that act.

Currency of this file

Finance Acts rewrite withholding rows. TRA portals rewrite payment codes. This page is operator orientation as at 10 September 2026. If a sentence here disagrees with tra.go.tz or the assessment letter, those win.

Documents the withholder should already have

Contract or board resolution that names the payment type; invoice that matches that type; TIN of the payer; identity of the beneficial owner if a treaty is claimed; the live TRA payment evidence; and the SWIFT instruction that uses the same names. If any name drifts, stop. A Dubai free-zone invoice that names a different legal person from the treaty residence certificate is two files pretending to be one.

Keep last year’s withholding pack with this year’s. Repeating a dividend is cheaper when the last receipt still exists. Losing the receipt is how you argue with a bank officer who was not there in 2025.

What this page will never publish

A WHT percentage. A due date. A treaty rate. A ‘safe’ management-fee markup. A penalty in shillings. Those rows move. The 2026 tax-rate map is the rate file and must itself be reconfirmed. This page is the classification file.

Failure modes the officer already knows

Net-of-tax clauses that assume the Tanzanian company will gross-up without anyone modelling the cash. Paying a director’s personal account because the parent’s account is ‘in compliance review’. Labelling a dividend as freight. Using a tourist as a consultant so the invoice looks like travel. Those are how assessments are built. This page is orientation, not a how-to for concealment.

As-at 10 September 2026: diary discipline

When the contract is signed, diary the withholding question the same week, not the week of the SWIFT. Confirm tra.go.tz the morning you pay. If the portal and this page disagree, the portal wins.