Administrative Account (CA) 2020 of the City of Nantes

Open data API in a single place

Provided by Ville de Nantes

Get early access to Administrative Account (CA) 2020 of the City of Nantes API!

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

Dataset information

Country of origin
Updated
2021.09.23 12:26
Created
2021.09.22
Available languages
English
Keywords
citoyennete-institution, budget, compte-administratif
Quality scoring

Dataset description

Administrative account 2020 of the main budget of the City of Nantes * * * * The administrative account, voted annually, shows the implementation of the budget in terms of expenditure and revenue. The accounting nomenclature of the municipality’s main budget has been Instruction M14 since 1 January 1997. The budget shall be voted accounting by nature at chapter level.Budget chapters (example: 012 “staff expenses”, 73 “taxes and taxes”, 23 assets in progress, etc.) group together a set of accounting items covering the allocation of appropriations and the implementation of the budget. The administrative account is cross-presented by function. Each sub-function specifies the origin of a revenue or the destination of an expenditure (example: 413 “pools”, 33 “cultural action”, etc.). In addition, it allows: * the distinction between expenditure and revenue (column D_R), * the identification of the section (functioning or investment) in column I_F: the Operating Section (F) records current transactions that are regularly renewed and constitute final expenses and income (staff costs, supplies, interest on debt, services, etc.);the Investment Section (I) traces the operations relating to the City’s heritage (acquisitions, sales, works,...). These operations are often spread over several years. * the separation between actual expenditure (or revenue) and expenditure (or revenue) of order (column ORDRE_O_N): budgetary expenditures (revenues) consist of actual expenditures (revenues) and sequential expenditures (revenues). The order expenditure (revenue) corresponds to entries that do not involve receipts or actual disbursements.These include, for example, depreciation allowances. In contrast to order transactions, actual expenditure (revenue) gives rise to movements of funds. * * * *Administrative account 2020 of the main budget of the City of Nantes * * * * The administrative account, voted annually, shows the implementation of the budget in terms of expenditure and revenue. The accounting nomenclature of the municipality’s main budget has been Instruction M14 since 1 January 1997. The budget shall be voted accounting by nature at chapter level.Budget chapters (example: 012 “staff expenses”, 73 “taxes and taxes”, 23 assets in progress, etc.) group together a set of accounting items covering the allocation of appropriations and the implementation of the budget. The administrative account is cross-presented by function. Each sub-function specifies the origin of a revenue or the destination of an expenditure (example: 413 “pools”, 33 “cultural action”, etc.). In addition, it allows: * the distinction between expenditure and revenue (column D_R), * the identification of the section (functioning or investment) in column I_F:the Operating Section (F) records current transactions that are regularly renewed and constitute final expenses and income (staff costs, supplies, interest on debt, services, etc.); the Investment Section (I) traces the operations relating to the City’s heritage (acquisitions, sales, works,...). These operations are often spread over several years. * the separation between actual expenditure (or revenue) and expenditure (or revenue) of order (column ORDRE_O_N): budgetary expenditures (revenues) consist of actual expenditures (revenues) and sequential expenditures (revenues).The order expenditure (revenue) corresponds to entries that do not involve receipts or actual disbursements. These include, for example, depreciation allowances. In contrast to order transactions, actual expenditure (revenue) gives rise to movements of funds. * * * *
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