2026 Global Mobility & Tax Suite

1) What most teams need before using a calculator

In tax work, people often ask for a number when they actually need a decision they can defend. A number without context may look useful at first, but it rarely survives serious review. Leadership wants to know what assumptions were used. Advisers want to know whether facts were complete. Audit teams want to see where each input came from. If those questions are unanswered, even a correct formula can lead to a weak outcome.

The most common breakdown is not arithmetic. It is sequencing. Teams collect documents too late, merge fields that should stay separate, or treat one screen result as final when it is only a first pass. For example, a company might estimate Nigeria exposure from revenue alone and skip sector analysis, or a mobility team might discuss UK eligibility before confirming a full ten-year residency record. In both cases, the risk comes from process gaps rather than difficult math.

A useful tax tool should therefore do three things clearly. It should apply a stable rule set. It should expose the branch logic in plain language. It should make the next action obvious. When a case appears straightforward, the next action is documentation and archiving. When a case is unclear, the next action is escalation with evidence. This guide follows that same pattern so you can move from question to action without guesswork.

• Be clear about the decision you need today.
• Collect the right inputs before running any scenario.
• Treat outputs as explainable checkpoints, not final legal conclusions.
• Document assumptions while facts are still fresh.

2) Nigeria corporate screening in practical terms

Nigeria corporate screening is often discussed in headline form, but day-to-day compliance is more specific. In this suite, the first branch checks whether annual turnover is at or below NGN 100 million and whether the business is outside Professional Services. If both conditions are true, the result shows eligibility for the zero-percent CIT screening branch. If turnover is above NGN 100 million, the tool moves to development levy estimation using assessable profit.

That distinction matters because many teams combine turnover and assessable profit in one spreadsheet narrative. They are related, but they do different jobs in this model. Turnover determines branch direction. Assessable profit determines levy size once the high-turnover branch is active. Keeping those fields separate makes the output easier to explain and less likely to be challenged later.

Classification quality is just as important as numeric accuracy. If commercial activity changes during the year, a classification that once made sense may no longer fit. Advisory-heavy contracts, bundled services, and mixed revenue streams deserve extra care. The practical answer is to rerun screening when business facts change, not only at year-end. That turns compliance into an ongoing control, rather than a last-minute scramble before filing.

• Use turnover to select the correct branch.
• Use assessable profit to quantify levy exposure where needed.
• Record why you selected a sector classification.
• Recheck whenever revenue mix or delivery model changes.

3) UK FIG screening and timeline discipline

For UK FIG cases, reliability starts with timeline discipline. The tool asks for an exact UK arrival date and a year-by-year residency history covering the prior ten years. In this implementation, all ten years must be non-resident for the relief branch to activate. That strictness is deliberate. It prevents accidental overstatement and keeps screening consistent across users.

The second benefit of timeline discipline is communication. A clear date-based result can be shared with payroll, mobility, and advisory teams without rewriting the same explanation in different formats. This is especially useful for compensation events that depend on timing, such as vesting schedules, bonuses, and cross-border income recognition. A vague statement like "likely eligible" is hard to operationalize; a dated result is much easier to plan around.

The tool also calculates a concrete four-year end date once eligibility is triggered, using arrival date plus four years minus one day. That gives teams a calendar anchor for planning the period after relief ends. It does not replace professional advice for complex cases, but it does reduce confusion early in the process. When the timeline is clear, advisory time can focus on genuine edge cases instead of basic chronology disputes.

• Start with a verified arrival date, not an estimate.
• Complete the full ten-year history before discussing outcomes.
• Use the calculated end date in payroll and planning calendars.
• Escalate split-year or treaty-heavy situations early.

4) Using Nigeria and UK outputs together

Many users are dealing with both corporate and personal exposure at the same time. A founder may be reviewing Nigeria corporate obligations while planning a UK move. A finance team may need to brief board members on both business-level and individual-level implications in one meeting. Running the two tools separately is useful, but the real value comes from combining the outputs into a single decision pack.

A practical cross-border workflow is straightforward. First, run the Nigeria screen with validated turnover, sector, and assessable profit assumptions. Second, run the UK timeline screen with verified arrival and residency data. Third, compare the two outputs against planned cash events, payroll cycles, and advisory deadlines. This side-by-side view helps teams decide where professional review is most urgent and where current data is already strong.

This approach also improves communication quality. Instead of presenting isolated numbers, you can show decision branches, key dates, known uncertainties, and next steps in one place. That structure reduces friction in leadership discussions and makes it easier for advisers to provide targeted input quickly. In practice, that usually saves time and lowers rework across finance, legal, and mobility teams.

• Run both tools with data from the same reporting window.
• List assumptions and unresolved issues next to each output.
• Prioritize adviser review where financial impact and uncertainty are highest.
• Archive both PDF reports in a shared compliance folder.

5) Sources, language, and evidence quality

Good tax guidance depends on careful sourcing. Primary institutions should be the starting point whenever possible, because they define policy language and implementation expectations. Secondary publications can still be useful for context, but they should support, not replace, primary verification in high-stakes decisions.

Precise wording also matters. Terms like turnover, assessable profit, residency history, and treaty credit are not interchangeable. When teams use loose synonyms, misunderstandings spread quickly across reports and meetings. The tools on this site keep variables explicit to reduce that risk, and this guide follows the same principle in plain language.

Evidence quality is the final piece. If a result cannot be traced back to records, it is difficult to defend under review. A strong working file includes source documents, notes on assumptions, the date of assessment, and the generated output. That package supports better decisions now and clearer explanations later if facts are revisited.

• Start from primary authority materials when available.
• Use consistent variable names across teams and reports.
• Store evidence with the result, not in separate ad hoc folders.
• Capture the date and context of each assessment.

6) What we have learned from day-to-day use

The clearest feedback from users is that confidence matters as much as speed. People want to know whether a result can be explained to leadership and defended in front of advisers. That is why we put so much weight on transparency: inputs are visible, branch logic is explicit, and exports are easy to archive and share.

Another pattern is time pressure. Teams usually arrive here because a deadline is close, a relocation decision is pending, or a reporting pack is being finalized. In those moments, abstract commentary is not helpful. What helps is a clear path: gather the right data, run the screen, identify uncertainty, and escalate where necessary. This guide is written to support exactly that flow.

A final pattern is overconfidence in early outputs. Even when a result looks favorable, it still needs context and documentation. The most resilient teams treat a tool output as a briefing artifact, not a substitute for professional judgment. That mindset keeps decisions grounded and reduces the chance of avoidable surprises.

7) A practical workflow you can repeat every quarter

Begin with a focused question. Are you checking a threshold, an eligibility timeline, a levy estimate, or filing readiness. Name the question clearly before you run anything. Then collect only the inputs needed for that question, and validate where each number or status comes from. This keeps the process clean and prevents speculation from entering the model.

Run the relevant tool and save the output immediately. Add a short note describing assumptions, open issues, and confidence level. Pair the output with supporting records while details are fresh. If any branch depends on uncertain facts, mark the case for escalation. Clear escalation criteria are especially important for mixed-sector business models, incomplete residency records, and high-value events near policy boundaries.

Close the loop with version and follow-up discipline. Record assessment date, store the output in a shared location, and schedule a rerun when major business facts change. Repeat this cycle each quarter. Consistency is what turns a useful calculator into a reliable decision process.

• Define the question first.
• Validate inputs before running scenarios.
• Save outputs with assumptions and evidence.
• Escalate edge cases without delay.
• Repeat on a fixed review cadence.