Budget of the City of Tampere 2014

Open data API in a single place

Provided by Finnish Digital Agency / Population Register Centre

Get early access to Budget of the City of Tampere 2014 API!

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

Dataset information

Country of origin
Updated
Created
2014.11.26
Available languages
Finnish
Keywords
Julkinen-talous, Menot, Talousarvio, Kunnallistalous, Talous
Quality scoring
170

Dataset description

The data includes all items in the income statement of the municipality, i.e. operating and financial income and expenses, tax revenue, central government shares, depreciation, profit treatment items and extraordinary income and expenses. The concepts of ## picking: ### Company The highest monitoring level of the city organisation after the city level. As a rule, the enterprise corresponds to the level for separate financial statements and notional separations in the financial statements in the organisational structure. Similarly, intra-city transactions are carried out between the companies concerned, cf. partner company below. The City of Tampere’s operations are organised according to the subscriber-producer model, which is why the financial statements and budget data contain a lot of intra-city transactions. As an exception to the organisational structure for the same reason, company 1110 Decision-making and Group steering includes the core processes of the Group administration and the subscriber-producer model in which the main acquisition of services takes place. ### Conversion Unit The lowest level of monitoring of the city’s organisational structure to which accounting transactions are made. The output units are attached to the result unit hierarchy. ### Ty hierarchy The city organisation is structured in the city’s ERP system as a hierarchy by result unit. The units mentioned above are not in numerical order in the hierarchy. By means of the Ty Hierarchy of Reason variable, the result units are organised in the order of the city’s official result unit hierarchy. ### Ty hierarchy level 1-7 The hierarchy of output units describes the organisational structure. The Ty Hierarchical Level 2 describes, as a rule, which production area or business establishment (e.g. Specialised Nursing or Tampere Meal Enterprise) is involved. The following levels describe the internal structure of each enterprise. The hierarchy of output units is a separate annex. ###Principal Account Group Group the ledger accounts into revenue and expenditure items in the profit and loss account. ###Principal Account Transactions are recorded according to the subject matter in different accounting accounts. For example, the purchase of a book is recorded in the Literature Purchases account in the Items, Supplies and Goods Account in the income statement (No 461200). The City of Tampere’s account list and instructions for recording the accounts are attached and details the contents of the accounts. ### Partner Company Indicates the counterparty to the transaction: in the seller’s accounts, the partner company tells to whom the goods/services have been sold, in the buyer’s accounts the code indicates from whom the goods/services were purchased. For business transactions between different units of the city, partners starting with the number one (1) are used. Other codes are used for various statistical purposes and for transactions between entities belonging to the City Group. Attached a list of the codes in use. As a rule, budgets and annual plans only use in-city partners (principals). ### TA 2014 Initial 2014 budget approved by the City Council on 18 November 2013 (EUR)
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
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.

Didn't find the API you need?

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

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks