← Back to catalogue
Published

Enterprise Monetary Calculation

vr.profile.enterprise-monetary-calculation · enterprise-monetary-calculation

Preserve exact monetary inputs and reproduce a same-currency total under an explicit rounding policy, with residuals and immutable correction evidence.

Enterprise profiles Cross-cutting context EnterpriseMonetary calculations

Bundle → Layer → Finding → Questions Filled

4 bundles · 8 layers · 21 findings · 21 questions

Identity and host Identity and host for an optional monetary calculation receipt.

Receipt

Explicit recorded facts, questions and limits for receipt.

Which computation has independent identity?

Coverage: local plus host identity.

  1. Which computation has independent identity? mixed-guidance

Does another label imply a new subject?

Coverage: host/deferred.

  1. Does another label imply a new subject? host-guidance

Sources

Explicit recorded facts, questions and limits for sources.

Which exact monetary slots supplied the inputs?

Coverage: local structure/host resolution.

  1. Which exact monetary slots supplied the inputs? mixed-guidance

Are source values asserted exact and readable?

Coverage: host truth/local refusal.

  1. Are source values asserted exact and readable? host-guidance
Arithmetic and context Arithmetic and context for an optional monetary calculation receipt.

Admission

Explicit recorded facts, questions and limits for admission.

Are currency catalogue editions identical?

Coverage: local equality/host resolution.

  1. Are currency catalogue editions identical? mixed-guidance

Do valuation basis, role and instant agree?

Coverage: local plus host.

  1. Do valuation basis, role and instant agree? mixed-guidance

Are decimal precision and original scale preserved?

Coverage: local.

  1. Are decimal precision and original scale preserved? local-guidance

Rounding

Explicit recorded facts, questions and limits for rounding.

Who chose increment, mode and stage?

Coverage: local fields/host authority.

  1. Who chose increment, mode and stage? mixed-guidance

Was each item rounded or only the total?

Coverage: local.

  1. Was each item rounded or only the total? local-guidance

What changed through rounding?

Coverage: local.

  1. What changed through rounding? local-guidance

Can this total authorize a payment or posting?

Coverage: host/deferred.

  1. Can this total authorize a payment or posting? constant-guidance
History and exchange History and exchange for an optional monetary calculation receipt.

History

Explicit recorded facts, questions and limits for history.

Which instant is valuation and which computation/storage?

Coverage: local shape/host plausibility.

  1. Which instant is valuation and which computation/storage? mixed-guidance

How is an incorrect result corrected?

Coverage: local merge/host storage.

  1. How is an incorrect result corrected? local-guidance

Which conflicting successor is current?

Coverage: host/deferred.

  1. Which conflicting successor is current? host-guidance

Exchange

Explicit recorded facts, questions and limits for exchange.

Can a receipt be replayed after import?

Coverage: local.

  1. Can a receipt be replayed after import? local-guidance

Does V3 outer validation prove the nested result?

Coverage: local binding.

  1. Does V3 outer validation prove the nested result? constant-guidance

Can this package migrate an old schema?

Coverage: deferred.

  1. Can this package migrate an old schema? constant-guidance
Adoption and limits Adoption and limits for an optional monetary calculation receipt.

Governance

Explicit recorded facts, questions and limits for governance.

Who may issue, read and retain receipts?

Coverage: host.

  1. Who may issue, read and retain receipts? host-guidance

Does a reference pin prove source truth or license?

Coverage: host/expert.

  1. Does a reference pin prove source truth or license? constant-guidance

Limits

Explicit recorded facts, questions and limits for limits.

Can 256-record history scale indefinitely?

Coverage: local cap/deferred scaling.

  1. Can 256-record history scale indefinitely? constant-guidance

Are quantity, FX, calendar and localization cases implemented?

Coverage: deferred.

  1. Are quantity, FX, calendar and localization cases implemented? constant-guidance

Classifiers Filled

Family
Enterprise profiles
Category
Cross-cutting context
Entry kind
companion-contract
Navigation path
NAV.XCT
Domain
EnterpriseMonetary calculations
Industry
Cross-industry
Tags
EM-XCT-06moneydecimalroundingreceiptresidualcalculation
Also called
EM-XCT-06, Monetary calculation receipt, Money precision and rounding

What it is Filled

A companion contract for a Company Dimension that keeps exact decimal money inputs in one currency and reproduces their total under an explicit rounding policy, with residuals and immutable correction evidence.

Why it exists Filled

Preserve exact monetary inputs and reproduce a same-currency total under an explicit rounding policy, with residuals and immutable correction evidence.

Distinguishing features Filled

  • Reproduces a same-currency total exactly from the original inputs under an explicit rounding policy.
  • Keeps rounding residuals as records even when they cancel out.
  • Refuses mixed-currency arithmetic and never fetches or chooses an exchange rate.

What robots and AI may and may not do Filled

Must not

  • Replace an unknown amount with zero.
  • Use floating point, exponents or signed zero for money.
  • Select or fetch an exchange rate.
  • Overwrite an original input when correcting.

Only with a human decision

  • Choosing a rounding policy where none is declared.
  • Accepting a correction that changes a reported total.

May

  • Validate monetary inputs and replay a total per item or after sum.
  • Request a missing value or rounding policy from its owner.

Moral aspects Filled

  • Rounding errors across many transactions can quietly move money between parties.
  • Exact reproducibility protects customers and staff in disputes about amounts.

Who is affected

  • Customers and suppliers paying or receiving amounts
  • Finance staff and auditors

Owners Filled

Steward

The finance function owns rounding policies; amounts stay owned by the system that issued them.

Master systems

  • ERP or billing system
  • General ledger

Links to other meta-models Filled

references

  • WM-XCT-032 - 0.3.0-research.1

aligned

  • vr.wm-xct-032

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Immutable calculation key.
  • Source slot IDs for each input amount.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: it has no physical body to measure.

Recognition optional Filled

  • A calculation record lists exact decimal inputs in one currency, the rounding policy, the total and residuals.

Capabilities and actions required Filled

  • Check immutable key; use existing host records only through a separately specified mapping; no adapter shipped. Proposed action only within authenticated host authority.
  • Keep subject identity; designation belongs to a later profile. Proposed action only within authenticated host authority.
  • Validate unique source slots; resolve their authority externally. Proposed action only within authenticated host authority.
  • Request missing value/authority; never replace unknown with zero. Proposed action only within authenticated host authority.
  • Refuse mixed tuples; do not fetch or select FX. Proposed action only within authenticated host authority.
  • Refuse mismatches; ask policy owner about business comparability. Proposed action only within authenticated host authority.
  • Reject float, exponent, overcapacity and signed zero. Proposed action only within authenticated host authority.
  • Apply only explicit declaration; request unresolved policy. Proposed action only within authenticated host authority.
  • Replay per-item or after-sum without changing original inputs. Proposed action only within authenticated host authority.
  • Keep residuals even if they cancel. Proposed action only within authenticated host authority.
  • Return no operational permission; consult separate domain process. Proposed action only within authenticated host authority.
  • Preserve separate meanings; validate strict UTC shape. Proposed action only within authenticated host authority.
  • Append a successor after complete-register validation. Proposed action only within authenticated host authority.
  • Return a context gap; do not select newest or overwrite. Proposed action only within authenticated host authority.
  • load then validate; compare replay; reject dropped pins. Proposed action only within authenticated host authority.
  • Run each check explicitly; do not infer automatic dispatch. Proposed action only within authenticated host authority.
  • Refuse unknown versions; future mapping required. Proposed action only within authenticated host authority.
  • Require host controls; metadata is restricted. Proposed action only within authenticated host authority.
  • Report unresolved context; digest alone grants nothing. Proposed action only within authenticated host authority.
  • Refuse excess; require separately reviewed production storage. Proposed action only within authenticated host authority.
  • Keep these open; no default rates, unit conversions or availability. Proposed action only within authenticated host authority.

Hazards and failure modes required Filled

  • Silent loss through binary floating point.
  • Wrong totals from implicit currency conversion.

Standards and interfaces required Filled

  • ISO 4217 currency codes and minor units.
  • Decimal arithmetic (IEEE 754 decimal, arbitrary-precision decimals).

Context of use required Filled

  • Invoicing, pricing and reporting where totals must be reproducible.

Sources Filled

  1. Research record EM-XCT-06: independent provider studies, audits and reconciled findings - Evidence behind the release; claims in the card trace to it.
  2. Enterprise Monetary Calculation 0.1.0 specification - Normative release, digest sha256:1cf0eb0451ff09b449da724bbcc64afdc0e34385427c9df8b9b2335d83880c26

Open questions

  • Use the pinned companion schema/validator and trusted-host binding. Native outer validation alone does not enforce nested semantics. Consult the released adoption limits.

Machine files

Provenance

enterprise research · reviewable-draft

Built from: models/enterprise-monetary-calculation/versions/0.1.0/spec.json, models/enterprise-monetary-calculation/catalogue-entry.json, ver-cy/world-models/card-supplements/enterprise-monetary-calculation.json