SRT Tax System
A land and building tax system for the State Railway of Thailand, where every team can see the status of every tax assessment, from the day the notice arrives to the day it’s paid.
Overview
The State Railway of Thailand owns land and buildings all over the country, much of it leased to tenants. Every year each local administrative office sends SRT a land and building tax assessment for the plots in its area, and four teams have to act on it. They used to pass the paper notice between them by post. This system gives every assessment one status that every team can see: the Central Office uploads it, the Local Area Department verifies it against SRT’s GIS and MIS records or disputes it, Finance pays it once it’s confirmed, and the difference is collected from the tenant when the tax is more than the rent.
User goals
-
Central Office
Record each notice once, then follow where it goes.
-
Local Area Dept.
Verify each notice and dispute the wrong ones.
-
Finance & Accounting
See every status, and record payments once confirmed.
-
System admins
Give each person the right role and areas.
Problem
Nobody could see where a tax notice was.
Paper notices went by post between four offices, and one could take months to finish.
-
Central Office
Posting paper on
- Receives each notice and posts it on
- No record of what came in
- Can’t answer “where is it now?”
-
Local Area Departments
Waiting for paper
- Waits 5–6 days for each notice
- Checks it against GIS by hand
- Objections go back by post
-
Finance & Accounting
Paying in the dark
- Can’t tell if a notice was checked
- Compares tax and rent by hand
- No shared record of what’s paid
Design goals
-
Everyone sees the status
One status per assessment, the same for every team.
-
Record once, share at once
One upload replaces the paper and the post.
-
Pay only what’s confirmed
Finance pays after the Local Area Department confirms.
-
Show only what’s wrong
Compare the notice with GIS and point at the difference.
-
Track every dispute
Reasons, letters and the office’s reply in one place.
Solution
One status for every assessment, and every team can see it.
The Central Office uploads the local office’s notice; the system reads it and finds the land in SRT’s records. The Local Area Department checks it against GIS and either confirms it or disputes it with the local office. Once it’s confirmed, Finance pays it outside the system and marks it as paid. At every step the status changes for everyone, so nobody has to ask where a notice is.
Structure
Information architecture
Central OfficeWeb app
- Overview
- Assessments
- New assessment
- Review extracted data
- Reports
Local Area DepartmentWeb app
- Overview
- Assessments
- Verify
- Open dispute
- Disputes
- Track reply
- Confirm revised tax
- Settlements
- Collection letter
- Record payment
- Reports
Finance & AccountingWeb app
- Overview
- Assessments
- Every status
- Mark as paid
- Payments
- Reports
System adminWeb app
- Overview
- Users
- Add user
- Roles and areas
- Reports
Before: paper, passed on by post
- Local office Issue the tax notice
- Central Office Receive it, post it on
- Local Area Dept. Receive it, post to Finance
- Finance Pay the local office
- Local Area Dept. Check it by hand
- Finance Compare tax with rent
- Local Area Dept. Collect from the tenant
- Local Area Dept. Objection letter
Now: one status, every team sees it
- Central Office Upload the notice → Under verification
- Local Area Dept. Check against GIS and MIS
- Local Area Dept. Confirm the data → Under payment
- Finance Pay, then mark as paid → Paid
- Local Area Dept. Collect from the tenant → Closed
- Local Area Dept. Dispute it, send objection → Disputed
- Local office Revise the notice
Final design
Central Office
Records each notice and follows where it goes.
Local Area Department
Verifies each notice, disputes the wrong ones, and collects from tenants.
Finance & Accounting
Sees every status, and records payments once a notice is confirmed.
System admin
Gives each person a role and the areas they work on.
© 2026 Sree Harini. All rights reserved.