A report from the Ministry of Finance, Planning and Economic Development forecasts that the 2026 Yala paddy crop will be 2.01 million metric tonnes, 12.9 per cent below the 2.31 million tonnes of the 2025 Yala season, Divaina reported on Saturday.

This is a forecast, not a harvest result. Divaina said it rests on 508,793 hectares of paddy sown by the end of June 2026. The report blames pressure on farmers from higher input costs after the conflict in the Middle East. To ease that pressure, the government had given an additional Rs 5.5 billion fertiliser subsidy for the 2026 Yala season as part of a temporary relief package, the paper said.

How to read the figure

The 12.9 per cent is Divaina’s figure; the rounded tonnages work out to about 13 per cent.

The 2025 comparator was a large crop. The Ministry’s own weekly bulletin, which tabulates Department of Census and Statistics data, gives provisional Yala output of 2.31 million tonnes for 2025, against 1.98 million for 2024 and 1.82 million for 2023. A 2.01 million tonne crop would still exceed both earlier years.

The UN Food and Agriculture Organization’s Sri Lanka country brief (the page carries no date) takes a more positive view of the season. It describes conditions before the 2026 Yala harvest as generally favourable, the planted area as above average, and 2026 cereal output as about 9 per cent above the average. That compares with an average, not with 2025, so the two assessments are not directly comparable.

Not reported

Divaina does not name or date the Ministry report, or say whether the forecast has been updated since the end-June sowing figure. The Central Bank also publishes Yala estimates in its monthly agriculture data bulletin, but this desk could not open it (HTTP 403), so it cannot say whether the Ministry’s figure matches the Bank’s latest.

Sourcing

One verified source: Divaina (Sinhala, published at 11.54 p.m. Colombo time on 21 November), translated by this desk. A search of other verified outlets found no second report, and the Ministry report itself could not be located.