COBOLing Together UI Benefits: How Delays in Fiscal Stabilizers Impact Aggregate Consumption
preprint
OA: closed
Abstract
The United States experienced an unprecedented increase in unemployment insurance (UI) claims starting in March 2020, mainly due to layoffs caused by COVID-19. State unemployment insurance systems were inadequately prepared to process these claims. Those states using an antiquated programming language, COBOL, to process UI claims experienced an increase in administrative burdens for potential claimants, which led to longer delays in benefit disbursement and an increase in discouraged filers. Using daily card consumption data from Affinity Solutions, I employ a two-way fixed effects estimator to estimate the causal impact of having an antiquated UI benefit system on aggregate consumption. The antiquated UI systems caused a 3.7 percentage point relative decline in total card consumption in COBOL states relative to non-COBOL states. This effect can be decomposed into three types: (1) delays in a claimant filing a claim, (2) delays in a UI benefit system processing a claim, and (3) an increase in discouraged filers. I find a 1.4 percentage point increase in the share of claims that experience a processing delay over 70 days in COBOL states relative to non-COBOL states. I also find suggestive evidence that the increase in administrative burdens for claimants in COBOL states led to an additional 5.4 million discouraged filers relative to non-COBOL states. These discouraged filers would have claimed UI benefits in COBOL states if the administrative burdens in their COBOL states had been as low as in non-COBOL states. Performing a back-of-the-envelope calculation using 2019 data, I find that a 3.7 percentage point decline in consumption in COBOL states in 2020 after the emergency declaration corresponds to a real GDP decline of $230 billion (in 2012 dollars).
My notes (saved in your browser only)
Citation neighborhood (no data yet)
We don't have any in-corpus citations linked to this paper yet. The paper's references may be in our DB but unresolved to ``paper_id`` (resolution happens at ingest when the cited DOI matches a row we already have). Run the cross-source citation reconcile pass to retry.
Source provenance
- europepmc
- last seen: 2026-05-19T01:45:01.086888+00:00
- unpaywall
- last seen: 2026-06-02T02:00:03.124865+00:00