The most common routing mistake is treating WHT as a single-portal obligation
The WiseFi guide's state-level chapter is worth reading because it forces a distinction many teams blur in practice: withholding tax administration is not always routed to the same authority. The correct path depends on the payee category.
That means the payment team should not ask only, "are we required to deduct?" It should also ask, "which regime governs this payee?"
The guide's table is simple and useful
The table in the cited chapter draws a clean line:
- Nigerian companies and deemed residents sit under the companies-income-tax framework and are administered federally through the NRS;
- individual residents such as sole traders and freelancers fall under PITA and are generally administered through the relevant state internal revenue service; and
- partnerships follow the PITA-style state path tied to the relevant state-of-residence logic.
The practical message is that payee type is not back-office trivia. It determines the remittance route.
Why this matters operationally
A lot of businesses have a single finance mailbox, a single payment run, and a single tax team. That creates pressure to force every deduction through one default process. The guide implies that this is exactly how routing mistakes happen.
If the vendor master does not distinguish:
- company versus individual;
- resident versus non-resident; and
- the relevant registration details and TIN path,
then the deduction may be made correctly in principle but administered in the wrong place.
Vendor onboarding should solve most of this upfront
The compliance checklist later in the guide reinforces the same idea. It says the onboarding pack should capture TIN details and residency declarations. That is the right design choice because the routing decision should happen before the invoice approval stage.
A sensible onboarding form should therefore make the business confirm:
- the legal status of the payee;
- whether the payee is an individual, company, or partnership;
- the governing tax authority for the transaction; and
- the portal or filing path that should be used if WHT arises.
Mixed vendor populations need different controls
This issue gets more important where the same business pays:
- incorporated suppliers;
- consultants operating as individuals;
- partners in informal or family-business structures; and
- cross-border service providers.
Those facts create different deduction and routing questions, even when the business sees them all as "vendors."
Bottom line
The state-level chapter of the WiseFi guide is really a data-governance chapter in disguise. If the business classifies the payee correctly at onboarding, the NRS-versus-SIRS question becomes manageable. If it leaves that decision to month-end remittance, the error rate goes up quickly.