Read the source set
Pull figures and labels from statements, schedules, receipts, and prior returns with source links.
Tax workflow / source documents to return fields
Tax return season repeats with the same documents.
We build private workflows that extract figures from approved statements, schedules, receipts, and correspondence, map them to return fields, and prepare a review checklist for the tax owner.
Source extractionField mappingReview checklistTax owner review
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where return preparation loses time
The source documents are not the return.
The work is moving numbers from one set of records to another while keeping the source and the reasoning visible.
Connect to the return
Prepare a field map showing which source item supports each return line.
Build the review list
Surface missing, changed, uncertain, and unsupported figures for the responsible tax owner.
The tax boundary
The system prepares the draft. It does not file the return.
Keep the record attached
Every mapped figure remains linked to the source document, version, and page that produced it.
Advice stays expert
Tax position, treatment, and filing decisions remain with the qualified tax professional and the taxpayer.
No automatic submission
Return submission, payments, and regulator communication remain explicit human actions.
A first tax workflow
Start with one return type and one source set.
Choose the return
Pick the entity, jurisdiction, and return type with a known source package.
Define the mapping
List the source fields, return lines, assumptions, and exclusions the team uses.
Test with a completed cycle
Compare the extraction and mapping with a prior return and fix figure or label issues.
Hand over the checklist
Deliver the field map, extracted figures, and open questions to the responsible tax owner.
A tax return draft is faster when every figure still points back to its source.
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.
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
Straight answers
Common questions.
Does this file a tax return?
No. It extracts and maps figures. Filing, payment, and responsibility stay with the taxpayer and its tax professional.
Does it give tax advice?
No. It prepares the record. Tax position and treatment decisions stay with the qualified professional.
How is this different from the tax teams page?
That page covers tax workflow broadly. This page is the recurring preparation artifact: source extraction, field mapping, and review checklists.
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 return type
Which return takes the longest to assemble?
Tell us the entity, the return, the source package, and the tax owner. We will scope the extraction around the records you already hold.