Keep one employee source
Maintain names, TINs, PayerIDs, RSA PINs, PFA, emoluments, dates, and payroll changes under controlled access.
Nigeria / finance + HR / recurring statutory payments
We build a statutory-remittance workflow that connects payroll inputs, PAYE, pension schedules, NSITF records, federal tax evidence, payment references, receipts, and owner deadlines. It prepares the reconciliation; finance, HR, tax professionals, and regulators retain the decisions.
Pattern demonstration / regulator decisions remain human
The Nigerian enterprise pain
The recurring problem is not only calculation. It is consistency across systems, formats, owners, and payment proof.
Maintain names, TINs, PayerIDs, RSA PINs, PFA, emoluments, dates, and payroll changes under controlled access.
Prepare LIRS CSV, PenCom xlsx, NSITF schedules, and federal inputs without retyping or silent partial submissions.
Join bill references, Remita/PSSP receipts, acknowledgements, certificates, missing months, and owner sign-off.
One workflow, separate authorities
Lagos payroll schedules, Form H1, PayerID, e-TCC, and the state eTax path remain distinct.
Employee PINs, monthly remittance, PSSP evidence, group life, and certificate records follow PenCom's route.
Payroll basis, forms, Remita evidence, certificate, incidents, and HSE records follow NSITF's route.
A statutory reconciliation workflow
Use one controlled source for fields that feed payroll, LIRS, PenCom, NSITF, and evidence packs.
Check uniqueness, required fields, dates, formats, totals, PINs, TINs, and current portal templates.
Match payment references, receipts, filing acknowledgements, certificates, missing months, and penalties.
Send mismatches to HR, payroll, finance, tax, PFA, LIRS, PenCom, NSITF, or another responsible owner.
Pricing / fixed scope
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One workflow for a small team, with training and handover.
See the one-workflow packageMultiple sources, roles, integrations, and admin handover.
See the deploymentStandard 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?
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.
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
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
No. It connects approved payroll data to the preparation, validation, reconciliation, and evidence work around the official submissions.
It can prepare calculations or files under the current approved rules for review. Qualified payroll and tax owners approve the result.
No. State tax routes differ. This core can begin with Lagos and expand only where the official process and local workflow are verified.
Own your knowledge base
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.
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Start with the employee master
Tell us the source, portals, schedules, receipts, and owners. We will map a consolidated preparation layer.