Revenue Authority Keeps Filing and Payment Services Available Through Deadlines With Ollandi
Summary
A national revenue authority deployed Ollandi across its filing portal, identity verification, bank payment links and in-country data centre. Deadline periods are now managed from one view of the filing journey, and privileged access to taxpayer records is reviewed continuously rather than quarterly.
Before Ollandi
- Most taxpayers file in the final days before a deadline, concentrating load on the portal.
- The filing journey depends on national identity verification, taxpayer records and payment links to several banks.
- Slowdowns during deadline week led to public complaints and extension requests.
- Privileged access to taxpayer records was reviewed quarterly from spreadsheets.
After Ollandi
- The filing journey is mapped from login and identity verification through submission and payment.
- During deadlines, the step under strain and its owner (the authority, the identity service or a specific bank) are identified.
- Bank payment confirmations are tracked per bank; delays are raised before taxpayers report missing receipts.
- Staff access that does not match role, location or working hours is raised for review with its event history.
Deployment
- Product: Ollandi, reasoning over infrastructure state and access events. It does not read tax return content.
- Data residency: the deployment respects the authority's in-country data requirements.
- Operating control: Observe & Notify.
By the numbers
Measured across Glemad's production deployments and published in the ADT research paper:
- Mean time to detect: 0.8 minutes, against an industry average of 287 minutes.
- False positive rate: 1.2%, against an industry average of 23.5%.
These figures come from environments with mature telemetry and defined policy baselines. Results depend on the quality of the telemetry available.
