A Practical Accounting Approach for Heritage Assets under Accrual Accounting: With Special Focus on Egypt
Bibliographic record
Abstract
Whilst the last 25 years have witnessed some efforts over how heritage assets might be accounted for and whether the heritage assets are sufficiently different to merit different treatment, there is no uniformity of accounting treatment for heritage assets in the public sector accounting literature and among the countries that have already adopted full accrual accounting in their public sector (such as, New Zealand, UK, Australia, USA and Canada). In addition, even though the debate of accounting for heritage has proposed different accounting approaches for heritage assets, it did not consider the impact of adoption of these accounting approaches on Net Worth and Statement of Financial Performance. The paper aims to examine the current accounting approaches for heritage assets and their impact on the Net Worth and Performance Statement and to suggest a Practical Accounting Approach for heritage assets, by which the exaggeration of net worth and performance statement distortions may be overcome. The proposed practical accounting approach for heritage assets is based on two subapproaches: 1- Assets-Liabilities Matching Approach: Capitalize if the information on cost or value of heritage assets is available and heritage assets can be disposed, and hence they can be used to match the liabilities (Unrestricted Heritage Assets). According to this approach, heritage assets should be included in the statement of financial position and their revenues and costs should be included in the statement of financial performance. 2- Non- Assets-Liabilities Matching Approach: Do not capitalize if the heritage assets cannot be disposed, and hence they cannot be used to match the liabilities even if information on cost or value is available. (Restricted Heritage Assets). According to this approach, heritage assets should not be included in statement of financial position and should be treated as trust/agent assets. Therefore, each country should create a Trust/Agent Assets Statement where heritage assets are stated in physical units and not in financial values. So in order to account for the revenues and costs related to heritage assets, each county should create a Trust Fund (Agent Fund). This fund includes all the revenues and costs related to heritage assets in each country. The resulting trust fund balance would be reported as either a liability or an asset in the balance sheet.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.004 | 0.005 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.007 | 0.007 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.005 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".