MétaCan
Menu
Back to cohort
Record W1989305126 · doi:10.1177/103237320000500104

The development of management accounting at the Hudsonís Bay Company, 1670-1820

2000· article· en· W1989305126 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueAccounting History · 2000
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicAccounting and Organizational Management
Canadian institutionsYork University
Fundersnot available
KeywordsManagement accountingAccountingCost accountingGovernorWork (physics)Database transactionAccounting information systemTransaction costEconomicsProject accountingManagementBusinessPositive accountingFinancial accountingFinanceEngineeringComputer science

Abstract

fetched live from OpenAlex

In their archival study, Roy and Spraakman (1996) found that the Hudson's Bay Company had developed extensive management accounting techniques by the 1820s. However, they did not concern themselves with the origins of the management accounting techniques employed in the 1820s. Based on the Company's archives for 1670 to 1820, it is clear that the basic components of the management accounting techniques were in place from the Company's beginnings or by 1700. These practices were changed significantly in 1810 as the Company grappled with declining profits and the need for new management accounting techniques that allowed for efficiency in inland trading. This trading had different requirements than trading from a few posts with easy ocean access to London. Although the successful techniques were put in place in 1810, it took until the 1820s and the efforts of Governor George Simpson for them to work effectively as a system. This paper also tests hypotheses developed from transaction cost economics and makes suggestions for a transaction cost economics theory of management accounting.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies, Insufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.315
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0020.000
Scholarly communication0.0000.001
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0030.003

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.

Opus teacher head0.011
GPT teacher head0.185
Teacher spread0.173 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it