Digitalising a Pradeshiya Sabha: what an integrated council system looks like

Sri Lanka has 341 local authorities — Pradeshiya Sabhas, Urban Councils and Municipal Councils — and between them they are the layer of government most people actually deal with. Rates, trade licences, building approval, a blocked drain, a burial permit, a street lamp that has been out for three weeks. None of it goes to Colombo. All of it goes to the council office.

And in most councils, it still runs on paper. The assessment register is a ledger. Receipts come from a counter book. Vouchers move between desks in a file. Complaints are written in a register that nobody can search. When the Auditor General asks a question, somebody goes to a cupboard.

Digital Sri Lanka is usually discussed at the level of national platforms and identity systems. But for a citizen in Badalgama or Marandagahamula, "digital government" means something much more ordinary: being able to pay rates without taking a morning off work, and knowing that the complaint they made last Tuesday actually went somewhere.

What a council actually has to do

The reason generic office software never quite fits a Pradeshiya Sabha is that a council is not a generic organisation. It is a statutory body, and most of what it does is prescribed — who may approve a payment, how long an objection period runs, when a warrant may issue, what has to be minuted.

The Pradeshiya Sabhas Act No. 15 of 1987 is not background reading here; it is the specification. Assessment rates sit in sections 134–146. Arrears recovery and warrants in 155–166 and 182. Budget and votes in 168–171. Accounts and audit in 171–172. Meetings and committees in 10–15.

Software that ignores this produces a system staff cannot legally use. Software built around it can carry the time limits and approval chains itself, so the rules are enforced by the system rather than remembered by whoever has been there longest.

One system, not twenty registers

WorkSuite for Councils brings the council's work into a single integrated system — 24 applications over one database, rather than a revenue package here, an accounts package there, and spreadsheets filling the gaps.

What that integration buys is simple to state and hard to achieve with separate systems: a receipt written at the counter lands in the cash book; a voucher approved by the Secretary moves the vote balance; a complaint closed in the field updates the SLA board. Nobody re-keys anything, and the Chairman can see where the council stands without asking four people for four reports.

The apps cover revenue (assessment tax, cashier counters, trade licences, rents), finance (votes, vouchers, cheques, cash book, budget, audit), council business (meetings, agendas, minutes, mail register, files and the seal), staff (HR, attendance, payroll on government scales), field operations (crews, jobs, solid waste, street lamps, fleet and fuel), citizen services (permits, relief, bookings and tokens), procurement and contracts, and the public website and portal.

Rates: the part that pays for everything else

Assessment tax is where most councils feel the pain first, because it is both the largest revenue head and the one with the most arrears. The register has to hold every assessment in every ward, carry the annual value and the quarterly bill, track what has been paid, age the arrears, and then follow a statutory path through demand, warrant and court certification.

Two details matter more than they look. The register knows how many assessments in the ward are in arrears, which turns recovery from an annual scramble into routine work. And the bill breaks down by quarter with its own status — paid, overdue, open — so a counter clerk can answer "what do I owe?" in one screen instead of reading back through a ledger.

Sinhala, Tamil and English — properly

A council system that only works in English is not a council system. Staff work in Sinhala or Tamil, citizens read notices in their own language, and bilingual service is a statutory obligation, not a feature request.

This is the whole interface, not a translated front page: navigation, labels, figures and queues. Notices and the public portal run in all three languages too, so a citizen receives correspondence in the language they actually read.

Built for Sri Lankan conditions, not ideal ones

A council office is not a data centre, and a line that drops for an hour is a normal Tuesday. A design that assumes constant connectivity means a counter that stops issuing receipts whenever the link goes down — which, in practice, means the counter goes back to the receipt book and somebody re-keys it all later.

So the architecture is deliberately split. A cloud node carries the citizen portal, online payments, the mobile API and off-site backups. An office node runs on the council LAN and keeps the counters working whether or not the internet is up, with per-counter receipt number ranges so nothing collides, and a two-way sync that reconciles when the link returns.

Field officers get Android apps that work offline all day — serving notices with a photo and GPS, recording job completion, reading meters — and sync through the office node when they return. It is the same principle we apply to fleet tracking and to remote access: assume the network will fail, and make sure the work does not stop when it does.

What digitalising a council actually involves

The software is the smaller half. The harder parts are the ones that have nothing to do with code:

• Getting the register in. Every assessment, every arrear, every trade licence, usually from ledgers of varying quality. This is the step that determines whether staff trust the system, and it cannot be rushed.
• Training people who have done it on paper for twenty years. Counter staff, the accounts branch, field officers and members all need different training, in their own language.
• Running in parallel until the new figures reconcile with the old ones, because the first month's collection report has to be defensible.
• Deciding who may do what — the approval chains in the system should match the delegations the council has actually made.

Done properly, from signing to go-live is a matter of months rather than weeks, with close support through the first reporting cycle.

Talk to us about your council

Digitalising a Pradeshiya Sabha is not a software purchase; it is a change to how the council works, and it needs a supplier who will sit with the accounts branch and the counter staff rather than deliver a licence key.

Livezen Technologies (Pvt) Ltd builds and supports WorkSuite, our own integrated business platform, from our office in Kaduwela. If your council is considering an integrated information system — or wants to see what one looks like with your own wards and revenue heads in it — get in touch and we will arrange a demonstration.