Annual Budget 2011 Table FCC

Open data API in a single place

Provided by Fingal County Council

Get early access to Annual Budget 2011 Table FCC API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.02.09 23:00
Created
2021.06.28
Available languages
English
Keywords
2011, Annual Budget 2011, Public, Finance, Budget, Public Finance, Economy, 2011 Annual Budget, Annual Budget, Economy and Innovation, Public Publication, Economy Innovation and Enterprise, Annual Publication, Corporate Publication, Publication Public
Quality scoring

Dataset description

<p>This dataset contains the data from the Council’s Annual Budget. The budget is comprised of Tables A to F and Appendix 1. Each table is represented by a separate data file.</p><p></p><p>Table F is the Expenditure and Income for the Budget Year, and Adopted Budget and Estimated Outturn for the previous Year. It contains –</p><ul><li>‘Expenditure’ and ‘Income’ Adopted by the Council for the Budget Year</li><li>'Expenditure’ and ‘Income’ Estimated by the Manager for the Budget Year</li><li>'Expenditure’ and ‘Income’ Adopted by the Council for the previous Year</li><li>‘Expenditure’ and ‘Income’ Estimated Outturn for the previous Year.</li></ul><p>Table F provides a breakdown of the Expenditure to Sub-Service level and Income to Income Source per Council Division contained in Table A.</p><p>In the published Annual Budget document, Table F is published as a separate table for each Division.</p><ul><li>Section 1 of Table F contains Expenditure broken down by ‘Division’, ‘Service’ and ‘Sub-Service’</li><li>Section 2 of Table F contains Income broken down by ‘Division’, ‘Income Type’ and ‘Income Source’</li></ul><p>This dataset is used to create Table F in the published Annual Budget document, which can be found at www.fingal.ie</p><p>The data is best understood by comparing it to Table F.</p><p>Data fields for Table F are as follows –</p><p><strong>Doc</strong> : Table Reference<br /><strong>Heading</strong> : Indicates sections in the Table - Table F is comprised of two sections : Income and Expenditure. Heading = 1 for all Expenditure records; Heading = 2 for all Income records.<br /><strong>Ref</strong> : Division Reference<br /><strong>Ref_Desc</strong> : Division Description<br /><strong>Ref1</strong> : Service Reference for all Expenditure records (i.e. Heading = 1) or Income Type for all Income records (i.e. Heading = 2)<br /><strong>Ref1_Desc</strong> : Service Description for all Expenditure records (i.e. Heading = 1) or Income Type for all Income records (i.e. Heading = 2)<br /><strong>Ref2</strong> : Sub-Service Reference for all Expenditure records (i.e. Heading = 1) or Income Source for all Income records (i.e. Heading = 2)<br /><strong>Ref2_Desc</strong> : Sub-Service Description for all Expenditure records (i.e. Heading = 1) or Income Source for all Income records (i.e. Heading = 2)<br /><strong>Adop</strong> : Amount Adopted by Council for Budget Year<br /><strong>EstMgr</strong> : Amount Estimated by Manager for Budget Year<br /><strong>PY_Adop</strong> : Amount Adopted by Council for previous Financial Year<br /><strong>PY_Outturn</strong> : Amount Estimated Outturn for previous Financial Year</p>
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks