The rate table is only useful if you classify the payment first
The WiseFi guide makes a simple point that many finance teams still miss in practice: there is no turnover threshold for withholding tax. If the payment is of a qualifying type, the deduction question starts immediately. That means the real work happens before someone looks up a percentage.
The guide's flow is:
- identify the payment type;
- identify the payee; and
- only then apply the rate.
That order matters because many internal errors come from jumping straight to the rate column.
The common 5% resident bucket is broader than many teams assume
The schedule groups a number of commercial payments into a familiar 5% resident pattern. On the pages cited above, the guide places these categories in that band for resident payees:
- general contracts for supply and services;
- consultancy and professional fees;
- technical and management fees;
- agency and commission fees; and
- construction contracts.
For many businesses, that means a large share of vendor spend will not require a bespoke rate analysis every time. It still requires proper classification, but the starting pattern is more consistent than people often think.
Rent is the point where over-simplified rules start to fail
The same schedule shows why a blanket "everything is 5%" approach breaks quickly. Rent categories sit differently from the ordinary service and contract buckets. The guide highlights land and building rent, as well as equipment or plant and machinery rent, as categories that need separate attention.
The practical implication is obvious: procurement teams should not reuse a professional-fee deduction rule for lease or equipment arrangements. If the vendor onboarding workflow does not distinguish these payment types, someone will eventually deduct the wrong amount.
Non-resident status changes the risk profile fast
The guide's resident versus non-resident note is short but important. It says the higher 10% default rate applies to non-residents across the schedule, subject to treaty relief. It also explains why status is not only a passport question:
- an individual can be resident through presence and factual ties; and
- a foreign company can still be treated as Nigerian if management and control are exercised in Nigeria.
So the right workflow is not "foreign bank account equals non-resident." The right workflow is to document the payee status before the first payment cycle.
A better rate-review workflow
If you want the schedule to work operationally, the review should be built into payment approval:
- require the business team to tag the payment type before finance review;
- capture resident versus non-resident status as a vendor-master field;
- escalate lease, royalty, dividend, and cross-border payments instead of forcing them through the default service rule; and
- keep the PDF open where a payment type is ambiguous rather than relying on memory.
Bottom line
The WiseFi guide is useful because it turns the WHT question back into a classification exercise. Once your team knows the payment type and the payee status, the rate schedule becomes much easier to use. Without those two decisions, the percentage you apply is mostly guesswork.