Primary budget 2014 of the main budget of the City of Nantes
* * * The original budget, voted annually, is the forecast of expenditure and revenue for the year.
It is necessarily balanced and constitutes an enforcement authorisation.
The accounting nomenclature of the main budget of the municipality has been instruction M14 since 1 January 1997.
The budget is voted by accounting nature at chapter level.
Budget chapters (example: 012 “staff expenses”, 73 “taxes and taxes”, 23 assets in progress, etc.) include a set of accounting articles on which appropriations are allocated and budget implementation.
The primitive budget is the subject of a cross-submission by function. Each sub-function specifies the origin of a recipe 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),
* identification of the section (operation or investment) in column I_F:
the operating section (F) records current transactions that are regularly renewed and constitute final expenses and income (staff expenses, supplies, interest on debt, provision of services, etc.);
the investment section (I) retraces the operations relating to the City’s assets (acquisitions, sales, works,...).
These operations are often spread over several years.
* separation between actual and serial expenditure (or revenue) (column ORDRE_O_N):
budgetary expenditures (revenues) consist of actual expenditures (revenues) and general expenditures (revenues).
The order expenditure (revenue) corresponds to records not involving collection or actual disbursement.
These are, for example, allowances for depreciation.
Unlike order transactions, actual expenditure (revenue) gives rise to movements of funds.
* * *
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.