Prepare the portal file
Generate and validate the accepted CSV structure, employee fields, TINs, phone numbers, and emolument data before upload.
Lagos / PAYE, eTax, and payroll records
Payroll does not end when salary is paid. The filing work starts there.
Lagos employers still need to prepare employee schedules, upload the portal-format file, track monthly PAYE, file annual Form H1, maintain PayerID and e-TCC records, and resolve rejected or partial submissions. We turn that repeated work into a reviewable payroll-to-eTax workflow.
LIRS eTaxPAYE schedulesForm H1HR + finance review
Pattern demonstration / tax decisions remain human
The repeated Lagos work
The portal rejects the small mistakes that payroll teams repeat.
The opportunity is not calculating a number once. It is keeping employee data, schedules, payments, and returns aligned.
Track monthly and annual work
Keep PAYE remittance, Form H1, Tax Form A, e-TCC, business-premises, and related owner dates visible.
Keep payment and filing proof
Reconcile bill references, receipts, acknowledgements, returns, certificates, and unresolved portal issues.
State and federal are not the same
Use the Lagos route for Lagos work.
State PAYE and eTax
LIRS handles state-specific processes, PayerID, eTax, Form H1, e-TCC, and related Lagos revenue workflows.
Keep federal work separate
Companies Income Tax, federal VAT, and company WHT belong to the federal tax route, not the LIRS workflow.
Keep HR and finance aligned
The employee master, payroll schedule, payment, filing, and review owner must agree before submission.
A Lagos PAYE workflow
Validate the employee file before eTax sees it.
Maintain the employee master
Keep names, TINs, phone numbers, PayerIDs, emoluments, and employment changes under controlled access.
Generate the portal schedule
Prepare the current LIRS CSV template and catch duplicate, missing, or malformed fields before upload.
Reconcile payment and filing
Join payroll, bill references, receipts, acknowledgements, returns, and e-TCC status in one evidence record.
Route corrections
Make rejected, partial, locked, or amended records visible to the HR, payroll, finance, or LIRS owner.
The real win is not a faster calculation. It is fewer payroll records failing after the team thought the work was finished.
Pricing / fixed scope
Know the starting numbers before you ask.
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One Workflow
Starting from$3,500 / ₦2.5m
2 to 3 weeksOne workflow for a small team, with training and handover.
See the one-workflow packageFirm-wide
Starting from$7,500 / ₦8m
4 to 6 weeksMultiple sources, roles, integrations, and admin handover.
See the deploymentAnnual support
Starting from$3,000 / ₦1.5m
per yearStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Why trust Pristine3D?
We build and operate production software.
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
We already run live products
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
We start with the actual workflow
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
The boundary stays visible
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Straight answers
Common questions.
Is this Nigeria-wide?
This page is specifically Lagos and LIRS. State tax workflows should be separated from federal NRS/FIRS work and from other state authorities.
Can it submit the LIRS CSV?
It can generate and pre-validate the current portal-format file. A payroll or tax owner remains responsible for final upload, payment, and filing.
Can it fix a submitted record?
The current research says amendments may require LIRS assistance or HQ. The workflow should flag the issue and prepare the correction packet, not pretend it can edit the portal.
Own your knowledge base
The model is not the product. The knowledge base is.
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
Your corpus, your index
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Models are swappable parts
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
The knowledge base is the alpha
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Related setups.
Start with the payroll file
Which LIRS submission keeps failing or taking too long?
Tell us the employee source, schedule, portal, payment evidence, and reviewer. We will map the controlled workflow.