Reporting & Disclosure6 min read
MB
Editorial Team
·October 25, 2026

Can Token Decimals Corrupt an RWA Subscription Amount?

ERC-20 decimal reconciliation is the process of mapping integer token amounts to the units shown in an investor instruction. Asset tokens and fund shares can use different precision. Confusing those scales can corrupt a subscription, valuation or statement even when the underlying transfer and share issuance are valid.

TL;DR — Key Takeaways

  • ✓Retain raw integer quantities together with token identity and precision.
  • ✓Convert asset units and share units independently before applying a price.
  • ✓Do not infer precision or currency equivalence from a token symbol.

Ready to get started?

Join others who are already using our platform.

Can Token Decimals Corrupt an RWA Subscription Amount?

Why can the same integer mean different amounts?

Token balances are integer quantities. The decimals metadata describes a display scale, so the same raw integer can represent very different human-readable amounts for different contracts.

An illustrative raw balance of 1,000,000 represents 1 token at 6 decimals and 0.000000000001 token at 18 decimals. The arithmetic is amount / 10^decimals. Neither representation establishes a currency price; a token display unit is a separate concept from the value assigned to it.

The ERC-20 specification treats decimals as optional metadata. An integration that cannot read it needs a verified configuration or a review exception, rather than an unexplained default of 18. Save where the precision value came from so an auditor can reconstruct the amount displayed at instruction time.

The same integer, 1,000,000, displays as 1 at 6 decimals and 0.000000000001 at 18 decimals. These are unit conversions, not market prices.

ERC-20 decimals definition; editorial calculation

How should asset and share units be separated?

An asset amount and a share amount belong to different token scales. Normalize each using its own precision before calculating or presenting a human-readable asset-per-share value.

Consider a purely illustrative allocation of 100 tokens of an asset with 6 decimals into 80 fund shares with 18 decimals. The raw asset amount is 100,000,000 and the raw share amount is 80,000,000,000,000,000,000. The human-readable allocation rate is 1.25 asset tokens per share, not the unadjusted ratio of those integers.

Use the contract conversion or preview appropriate to the operation and retain the raw outputs. Do not reproduce the share calculation from the display rate alone: fees, rounding and implementation rules can change execution. A screen is a presentation of the allocation evidence, not a replacement for it.

The choice between conversion previews and executable limits remains separate from getting their units right.

Where do precision errors enter the workflow?

Precision errors enter when an API, spreadsheet or ledger drops the token scale and later reconstructs an amount from a bare number. The correction is an explicit amount-and-unit contract between systems.

Every imported field should say whether it contains raw base units, human-readable tokens, shares or a currency value. Preserve exact integers and decimal strings through API and file boundaries. Avoid binary floating-point arithmetic for settlement amounts that must round-trip without changing a base unit.

An export containing 100000000 with a column titled amount leaves the receiving team to guess. Include contract address, network, precision and amount type. When converting to accounting currency, add the price source and valuation time as separate fields rather than silently treating one token as one currency unit. Fees computed in base units round the same way, which is why an ERC-3643 transfer fee can round to zero on small transfers.

In the 100-asset/80-share example, the display rate is 1.25 despite the different raw integer scales. Asset and share precision must be applied independently.

ERC-4626 asset and share definitions; editorial calculation

What should a reconciliation test cover?

The test should round-trip the instruction, transaction and statement without losing a base unit. Include different asset and share precision, missing metadata and amounts near a display rounding boundary.

For the example allocation, start with the human instruction, produce the raw transaction amount, record the actual shares and export the statement. Reimport that statement and compare the original integers. If the display rounds 79.999999999999999999 shares to 80, retain the precise ledger amount even though the abbreviated screen is acceptable for browsing.

Test the smallest supported investment and a large amount beyond the exact integer range of a typical JavaScript Number. The purpose is to demonstrate that the data pipeline preserves quantities; these are proposed integration checks, not evidence of errors at a named issuer.

Also confirm the balance is read from the right contract when the vault uses an external share token. Correct arithmetic on the wrong balance source still produces a wrong statement.

Who should approve a precision change?

Treat a changed precision source or token mapping as a controlled data change. Operations and engineering should reconcile affected historical instructions before adopting a newly displayed amount.

Capture the old mapping, new mapping and the block or configuration version used. A change in an API response should not silently restate prior investor holdings. Determine whether the underlying quantity changed or only the interpretation in a downstream system changed.

This guide is for fund administrators, custody adapters and reporting teams. It does not determine NAV or whether an asset token is redeemable at par. Connect the amount record to RWA reporting and investor disclosure controls so each statement can be reconstructed from the original allocation and valuation evidence.

Sources: ERC-20 optional metadata; ERC-4626 asset and share units; OpenZeppelin ERC-20 implementation reference. Sources checked October 25, 2026. Numerical scenarios and acceptance procedures are editorial analysis, not reports of live fund incidents.

Frequently Asked Questions

Does decimals change the integer token balance?

The metadata describes the scale used to display an integer amount. Changing an interpretation in an application does not itself move tokens. A reconciliation must distinguish a different displayed value from a real balance change and preserve the raw quantity with the exact token and network identity.

Must asset and share tokens have the same decimals?

No. Do not assume matching precision when converting or displaying asset and share quantities. Normalize each amount independently and use the supported contract methods for the intended operation. A human-readable price and a ratio of raw token integers are different values when the scales differ.

What if the decimals call is missing?

ERC-20 defines decimals as optional metadata. Obtain a verified value through the approved asset configuration or hold the integration for review. Do not silently guess from the token symbol, a familiar stablecoin or another deployment with a similar name. Retain the source used for the accepted precision.

Can I use rounded values in an investor statement?

A statement can display a readable rounded amount if the underlying ledger preserves exact quantities and the rounding policy is clear. Imports, reconciliation and settlement should use the precise record. A rounded display of 80 shares must not overwrite an actual allocation slightly below 80 in the source ledger.

Ready to get started?

Join others who are already using our platform.