Total spending
630,100 RON
2 suppliers · spent between 2018 and 2024
Direct purchases
0 RON
0 purchases
Offline purchases
0 RON
0 purchases
Tenders
630,100 RON
2 procedures · 2 contracts
Single-bidder rate
—
Below indicator #06's minimum of 5 counted lots
DSI index
—
Below indicator #09's minimum spending
HHI
—
Below indicator #10's money and award thresholds
In county context: 0.00% of everything spent in BUCUREȘTI county · Ranked 1,267 of 1,648 authorities with purchases in the county
Risk indicators
Spending by year
The year is the one the money was spent in: the finalisation date for direct purchases and offline purchases, the contract date for tenders.
What it buys
The 1 largest CPV groups, out of 1; the other 0 are added into a single tile. A tender contract has no CPV code of its own, so its money goes to the notice's main code. For notices with several lots this is an approximation.
Main suppliers
| # | Supplier | Direct purchases | Offline purchases | Tenders | Contract value | Share | Contracts |
|---|---|---|---|---|---|---|---|
| 1 | TGS ROMANIA ASSURANCE & ADVISORY BUSINESS SERVICES SRL CUI: 6641616 | — | — | 320,100 | 320,100 | 50.8% | 1 |
| 2 | PKF FINCONTA SRL CUI: 6383983 | — | — | 310,000 | 310,000 | 49.2% | 1 |
The share is taken of the 630,100 RON this table can assign to a supplier: direct purchases, offline purchases and tender contracts with a named winner.
Each amount leads to the purchases it was computed from. For direct purchases and offline purchases the rows add up exactly to the figure; for tenders the notices the supplier won open, with the whole notice's value, not only its share.
- Direct purchases
- What the authority paid the supplier through direct purchases. The link opens exactly those purchases.
- Offline purchases
- What the authority paid the supplier through offline purchases.
- Tenders
- The supplier's share of the authority's tender contracts. In an association each member has its own share.
- Contract value
- The three streams added up. The table is ordered by this column by default.
- Share
- The supplier's share of the money this table can assign (the amount under the table). Above 40% is highlighted; see indicator #04 too.
- Contracts
- How many direct purchases, offline purchases and tender contracts the two share.
Latest purchases
Latest tenders
See all| SEAP no. | Procedure | CPV code | Date | Value |
|---|---|---|---|---|
| SCNA1102864 | procedura simplificata | 79212100-4 | 25.04.2024 | 320,100 |
| Contract object: audit statutar ce se efectueaza in conformitate cu standardele internationale de audit (isa), asupra situatiilor financiare incheiate la 31 decembrie 2023, 2024 si 2025 ale societatii nationala a sarii sa, intocmite in baza prevederilor omfp nr. 2844/2016 pentru aprobarea reglementarilor contabile conforme cu standardele internationale de raportare financiare (ifrs) | ||||
| SCNA1002902 | procedura simplificata | 79212100-4 | 16.08.2018 | 310,000 |
| Contract object: servicii de auditare a situatiilor financiare in conformitate cu reglementarile contabile conform standardelor internationale de audit (isa), pentru exercitiile financiare 2017, 2018 si 2019, in baza prevederilor omfp nr.1802/2014, omfp nr.666/2015 si omfp 2844/2016. | ||||
- SEAP no.
- The purchase's SEAP number, linked to its record on e-licitatie.ro.
- Supplier
- The company the purchase was made from. The name leads to its profile.
- Procedure
- The award procedure. Procedures without prior publication leave less room for competition.
- CPV code
- The CPV code: what was bought. Hover it for the name; a click filters the list on it and the codes below it.
- Finalisation date
- The finalisation date, that is, when the money was spent. The list is ordered by it and the year filter applies to it.
- Date
- The date of publication in SEAP.
- Value
- The value of the purchase, excluding VAT, rounded to the leu.
- Contract object
- The object of the purchase as the authority described it, on the line under the figures.
The same data, through the API
Every figure on this page comes from the public API, through the endpoints below. The parameters each one takes are in the documentation; each needs an access key.
/api/v1/authorities/1590430/api/v1/authorities/1590430/spend/api/v1/authorities/1590430/scores/api/v1/authorities/1590430/benchmarks/api/v1/authorities/1590430/county/api/v1/red-flags/by-authority/1590430/api/v1/authorities/1590430/years/api/v1/authorities/1590430/cpv/api/v1/authorities/1590430/suppliers/api/v1/acquisitions/direct/api/v1/acquisitions/awards/api/v1/acquisitions/tenders