Start with your business’s actual tax position, then configure the software. A VAT percentage on a receipt does not establish whether the business should charge it, whether the product has been classified correctly or whether an invoice has passed through the required electronic fiscal process. These are separate questions, and a retailer needs an answer to each.
Our recommended starting point is Bizman for the operational discussion: how sales, returns, invoice references and supporting records will be captured and retrieved. Bring your accountant into that discussion before changing tax settings. This article does not claim that Bizman is an NRS-approved service provider, a certified fiscal solution or already connected to the Merchant Buyer Solution for your business.
Commercial disclosure and review status: BriskRetail offers Bizman. This is an affiliated operational guide, researched on 23 October 2026, awaiting qualified Nigerian tax review before publication. It is not a determination of an individual retailer’s obligations. The examples are synthetic; unresolved rollout and business-classification questions are identified below rather than presented as settled advice.
COVER BRIEF — Original illustration, 1600 × 900. A sales receipt, structured invoice record and accountant’s checklist, clearly distinct. Alt text: “Retail sales records checked against VAT treatment and electronic invoice validation.” No government seal, certification badge or invented approved-provider logo; artwork pending.
1. Use the current framework and the correct transaction period
The Federal Ministry of Finance’s transition announcement of 18 June 2026 identifies 1 January 2026 as the Nigeria Tax Act’s commencement date and distinguishes earlier periods from the new framework. An old article about FIRS may describe a real historical process while giving an incomplete answer for a transaction today.
The current NRS tax-law library lists the Nigeria Tax Act and Nigeria Tax Administration Act, 2025. For a settings change, record the legal entity, transaction date, applicable instrument and adviser’s decision. Do not overwrite historical invoices simply to make their branding or tax description resemble the latest screen.
Keep the difference between a trading name and a legal entity visible. Two branches may belong to one business; two businesses sharing an owner may need separate records. Ask the adviser which entity issues each invoice and which identifier belongs on it. The NRS MBS portal announced in July 2026 that Tax ID replaces TIN as the legal identifier for e-invoicing. Check the required identifier and onboarding records rather than copying a legacy field without review.
Create a short decision record for each configuration: who approved it, when it takes effect, which products or transactions it affects and how it will be tested. Keep the previous version available for explaining older documents. Software support should implement the agreed decision; a technician should not become the business’s tax adviser by default.
2. Determine business status and product treatment separately
Section 148 of the Nigeria Tax Act, 2025 specifies a 7.5% VAT rate subject to the Act’s relevant exceptions. Sections 186 and 187 distinguish exempt supplies from supplies chargeable at zero percent. A till therefore needs meaningful tax categories, not one unchecked rate applied to everything.
The Nigeria Tax Administration Act contains small-business treatment in section 22. The retrieved gazetted text defines a small business using annual gross turnover of no more than ₦100 million and fixed assets of no more than ₦250 million, excluding professional-service businesses. It also provides for opting out by written notice and for a business ceasing to qualify. These conditions require an adviser’s application; turnover alone is not a complete decision.
This matters because online summaries may carry different thresholds, earlier rules or assumptions about company income tax. Do not use an old ₦25 million or an unsupported ₦50 million shorthand to change the till. Confirm the operative text, any relevant amendment and your circumstances with a qualified adviser.
For products, prepare descriptions precise enough to classify: what the item is, its packaging or service component and any mixed bundle. “Food,” “medical” or “school item” is not a sufficient internal explanation by itself. Record an approved category with its reason and effective date. If an item remains uncertain, put it on the review list before configuring a confident-looking rate.
3. Follow a dated applicability decision tree
Use this working decision tree with your accountant. It separates VAT treatment from e-invoicing deployment; neither answer should be inferred solely from the other.
| Decision point | Evidence to assemble | Next action |
|---|---|---|
| Who makes the supply? | Legal entity, branches, Tax ID and transaction type | Confirm the invoice issuer |
| What VAT treatment applies? | Business status, product classification, elections and applicable period | Approve tax codes and document basis |
| Which EFS/MBS category applies? | Current NRS notice, turnover evidence and any direct notice | Obtain a written category and effective-date decision |
| Is the connection enabled? | Portal enablement, provider scope or self-integration evidence | Rehearse the approved transaction route |
| Are exceptions resolved? | Returns, credit notes, rejected invoices and downtime procedure | Approve operation or leave the issue open |
Section 23 of the Tax Administration Act addresses the Electronic Fiscal System and leaves deployment and transition arrangements to the Service. A universal claim that every Nigerian shop has the same immediate onboarding deadline would ignore that implementation question.
Unresolved at this research date: the official MBS portal advertises a phased timeline, but its complete underlying notice was not retrievable in this review. A developer-community announcement labels July dates as enforcement, while published accounts of the February notice distinguish go-live from later enforcement. Do not choose a convenient date from those conflicting summaries.
Ask NRS or your adviser for the current signed notice, the applicable turnover band, any category-boundary clarification and the distinction between onboarding, pilot, go-live and enforcement. Save the answer with the business’s compliance file. This guide deliberately leaves the business-specific deadline unassigned; that is a review task, not an exemption or permission to delay.
4. Distinguish a receipt, a PDF and a fiscal e-invoice
A receipt can show that money was collected. An invoice describes an amount owed for a supply. A PDF is a document format. None of those descriptions alone proves that structured invoice data was validated or reported through the prescribed process.
The NRS key definitions distinguish structured electronic invoices from scanned or copied paper documents. They also distinguish system integrators from access point providers. Ask who prepares the data, who transmits it and who is responsible when validation fails.
The final NITDA National Regulatory Guideline for Electronic Invoicing, 2025, made on 26 August 2025, addresses technical roles and invoice verification. Its IRN verification procedure is a useful reminder that a decorative QR code is not independent evidence of successful fiscalisation.
Keep the local sale number, invoice number and returned fiscal reference in linked fields. Staff should be able to find the same transaction from any of them. When a customer asks for a corrected document, preserve the relationship to the original rather than silently replacing a file and losing the explanation.
DIAGRAM BRIEF — Original diagram, 1440 × 960. Local sale → structured submission → accepted or rejected response → customer document and audit record. Alt text: “An electronic invoice needs a traceable validation result, not just a PDF or QR image.” Conceptual process only; no claim that every transaction follows an identical legal timing rule.
5. Test inclusive prices, discounts and mixed baskets
The following is an arithmetic exercise for a supply already confirmed as chargeable at 7.5%. It does not decide whether a particular product or business should charge VAT. Assume a net amount of ₦20,000 after the approved discount. VAT is ₦20,000 × 7.5% = ₦1,500, making the tax-inclusive total ₦21,500.
If ₦21,500 is already the inclusive amount, extract the net amount as ₦21,500 ÷ 1.075 = ₦20,000. Adding another 7.5% would charge the tax twice. For this example, an equivalent extraction is inclusive amount × 7.5 ÷ 107.5.
| Synthetic basket line | Net amount | Approved example treatment | Tax | Total |
|---|---|---|---|---|
| Item A after discount | ₦20,000 | 7.5% | ₦1,500 | ₦21,500 |
| Item B | ₦5,000 | Assumed zero-rated for this exercise | ₦0 | ₦5,000 |
| Basket | ₦25,000 | Separate line classifications | ₦1,500 | ₦26,500 |
Item B is deliberately generic: the table does not classify an actual commodity. Test an exempt line separately too; a zero tax amount does not make the underlying categories interchangeable. Let the adviser approve how basket discounts are allocated across lines and how the applicable base is calculated.
Also test a partial return, a price correction and a credit sale. A payment received today may settle an earlier invoice, while a sale today may remain unpaid. Bank deposits are therefore not a substitute for the tax-period sales record. Read the payment reconciliation guide alongside this exercise.
Agree the rounding method and compare line totals with invoice totals using realistic small prices and quantities. A persistent one-naira difference should have an explained rounding policy, not an unexplained balancing entry. Keep higher calculation precision where appropriate and display currency amounts consistently.
6. Keep records that explain the numbers
The practical goal is to reconstruct a transaction without depending on a cashier’s memory. Save the commercial event, approved tax treatment, payment evidence and any correction as related records. Access should be controlled, and the owner should know how to retrieve usable copies.
| Record group | Minimum operational detail to agree | Useful check |
|---|---|---|
| Sale and invoice | Unique references, date, entity, line quantities and prices | Can one sale be traced end to end? |
| Tax calculation | Tax category, base, rate, amount and rule version | Can the accountant reproduce it? |
| Fiscal exchange | Submission reference, status, response and correction link | Is accepted different from queued? |
| Payment and return | Method, settlement reference, original sale and refund | Are money and tax corrections reconciled? |
| Supporting evidence | Supplier documents, approvals, exports and access history | Can an authorised reviewer retrieve it? |
Section 31 of the Tax Administration Act imposes record-keeping obligations. Have your adviser specify the applicable retention period, commencement point and any audit or dispute hold. Do not make one blanket deletion rule for invoices, customer marketing records and system logs merely because the software offers a single setting.
Retaining a backup is not enough if nobody can search or open it. Rehearse retrieving a prior-period invoice, its related credit note and the supporting calculation. Include staff turnover and supplier exit in the plan: access should not depend on a former employee’s personal email account.
For input-tax treatment, let the accountant assess eligibility and supporting evidence. Do not assume every purchase tax amount is recoverable, or that an approved invoice alone settles every condition. The operational system should provide the evidence rather than promise automatic tax savings.
7. Plan for rejection, downtime and corrections
A system needs explicit states such as prepared, submitted, accepted, rejected and awaiting investigation. “Saved” is too vague for a manager deciding whether the process completed. Specify who checks the exception queue and who contacts the provider or authority when it does not clear.
Rehearse an invalid identifier, a missing required field and a timeout after submission. A timeout can mean that the response was lost even though processing occurred. The supplier should show how it checks the original reference before retrying, so one commercial sale does not become duplicate fiscal records.
Ask the adviser and provider to document the permitted procedure during an outage, including customer documentation and subsequent reporting. Do not assume offline POS capability creates a legal grace period. Separate the technical ability to continue trading from the approved fiscal procedure.
For returns, preserve the original sale and use the applicable correction mechanism. Test a partial return after settlement and one after a reporting period has closed. Confirm who can approve it and what must reach the accountant. Deleting an original invoice to make a daily report look tidy destroys the relationship the business needs to explain.
8. Make the Bizman scope concrete before buying
Ask BriskRetail to demonstrate the proposed Bizman POS invoice and return workflow using the synthetic basket above. Then ask for the actual integration scope, if any: named provider, supported transaction types, current approval evidence, responsibilities, costs and acceptance tests. A product logo or a sales statement should not replace that documentation.
Bizman remains our recommended starting point for coordinating the retail workflow. If fiscal connectivity is required and cannot be demonstrated for the proposed configuration, use a separately verified route or reconsider the implementation before go-live. An existing accounting system paired with an approved provider may be a better fit than replacing the whole retail system solely for invoice transmission.
The NRS portal provides a provider directory and self-integration information. Verify the relevant legal entity and role there when evaluating proposals, and confirm current status directly. This article does not rank providers or endorse an unverified listing. Software, integration, support and adviser fees are quote required.
Write acceptance criteria into the project: calculations match approved examples, corrections preserve links, rejected items remain visible, exports are usable and access rights are appropriate. Ask who pays for future schema changes and who supports a failed submission outside normal office hours.
WORKFLOW BRIEF — Original review board, 1440 × 810. Business classification, tax codes, fiscal route, exceptions and sign-off, each with an owner. Alt text: “A retailer assigns tax and e-invoicing decisions before configuring the POS.” No claim that review has already occurred; image pending.
9. Leave the review with decisions, evidence and a refresh date
Before changing the live till, assemble one folder containing the entity details, approved treatment by product group, operative notices, supplier scope, sample calculations and test results. List each unresolved question with the responsible person and due date. Do not mark an unanswered legal question as a successful software test.
Set a refresh trigger for a change in business size, product mix, entity structure, tax instrument or MBS specification. The point is to keep the configuration tied to an explicit decision, rather than relying forever on the person who originally set it up.
Use the Bizman product page and request a consultation with your accountant’s requirements attached after removing sensitive data. Keep this manuscript in qualified review until its applicability questions are resolved. Good retail records make advice and compliance work possible; a receipt printer cannot do that work on its own.