BEP-20 decimals and misleading raw balances

A token's decimals value determines how an integer balance is displayed as token units. It does not tell you the asset's dollar price, supply quality or economic value. BSC quote and receipt records must use the decimals of the exact token contract involved.

The BEP-20 specification defines the token metadata and balance interface. The basic conversion is displayed amount = raw integer / 10^decimals.

A worked conversion

For a hypothetical token using 18 decimals, the raw amount 2500000000000000000 represents 2.5 tokens. With six decimals, the raw amount 2500000 also represents 2.5 tokens. The integers differ by a trillion, while the displayed token quantity is the same.

This is why copying a raw amount between token contracts without unit conversion is not a harmless formatting mistake. It changes the intended quantity. Wallets usually present human-readable amounts, but exports, logs and developer tools may expose the integers.

Do not infer decimals from the ticker

PancakeSwap's list records 18 decimals for the Binance-pegged USDT contract on BSC. Another USDT representation can use a different convention. Chain and contract metadata should travel with an amount whenever data is moved between tools.

Unit price creates another common confusion. In a hypothetical redenomination, replacing each old token with 1,000 new units can divide the per-unit price by 1,000 without changing the holder's total value. A small price beside a BSC token is therefore not evidence of a cheaper economic claim.

When reviewing a completed swap, retain both the displayed quantity and enough identity information to reconstruct it: network, contract and decimals. This is especially useful when a spreadsheet, wallet and explorer format the same balance differently.