SRT Tax System

  • Land and building tax
  • Government
  • Web application

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.

Platform
  • Web app
  • Thai and English
Target audience
  • Central Office
  • Local Area Departments
  • Finance & Accounting

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

  1. Everyone sees the status

    One status per assessment, the same for every team.

  2. Record once, share at once

    One upload replaces the paper and the post.

  3. Pay only what’s confirmed

    Finance pays after the Local Area Department confirms.

  4. Show only what’s wrong

    Compare the notice with GIS and point at the difference.

  5. 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

post post post Yes letter No weeks by post Local office Issue thetax notice Central Office Receive it,post it on Local Area Dept. Receive it,post to Finance Finance Pay thelocal office Local Area Dept. Check itby hand Correct? Finance Compare taxwith rent Local Area Dept. Collect fromthe tenant Local Area Dept. Objectionletter
  1. Local office Issue the tax notice
  2. Central Office Receive it, post it on
  3. Local Area Dept. Receive it, post to Finance
  4. Finance Pay the local office
  5. Local Area Dept. Check it by hand
  6. Finance Compare tax with rent
  7. Local Area Dept. Collect from the tenant
  8. Local Area Dept. Objection letter

Now: one status, every team sees it

Yes Yes No revised notice No Notice arrives Central Office Upload thenotice Under verification Local Area Dept. Check againstGIS and MIS Correct? Local Area Dept. Confirmthe data Under payment Finance Pay, thenmark as paid Paid Tax morethan rent? Local Area Dept. Collect fromthe tenant Closed Closed Local Area Dept. Dispute it,send objection Disputed Local office Revise thenotice Closed
  1. Central Office Upload the notice → Under verification
  2. Local Area Dept. Check against GIS and MIS
  3. Local Area Dept. Confirm the data → Under payment
  4. Finance Pay, then mark as paid → Paid
  5. Local Area Dept. Collect from the tenant → Closed
  6. Local Area Dept. Dispute it, send objection → Disputed
  7. Local office Revise the notice

Final design

Every role opens on where every assessment is.

Central Office

Records each notice and follows where it goes.

Assessments: the status, and who has it.
Step 1: upload the notice; the land is found.
Step 2: check what was read, then submit.
The same list in Thai.

Local Area Department

Verifies each notice, disputes the wrong ones, and collects from tenants.

Overview: what to verify, dispute and collect.
Open a dispute with proof and a deadline.
Tenant settlements, after Finance pays.
One tenant: what they owe and why.

Finance & Accounting

Sees every status, and records payments once a notice is confirmed.

Overview: what’s ready to pay.
A confirmed notice, ready to pay.
Record a payment made outside the system.
Reports: preview, then download.

System admin

Gives each person a role and the areas they work on.

Users: roles and areas from HRIS.
Sign in for SRT staff.

© 2026 Sree Harini. All rights reserved.