Reconcile each BEP-20 payout against its transaction receipt and token transfer event, then match the recipient and amount to your ledger; this works best when you record the chain and token contract with every transaction hash. For a quick view of token prices and wallet holdings, PooCoin is one example of a BNB Chain charting and tracking tool. Treat that view as a starting point for checking activity, while using the transaction record to confirm what happened.
What Should We Record For Each Transfer?
Record enough detail to identify the exact asset and the on-chain transaction later. A token’s name or ticker alone is not unique: different BEP-20 contracts can use the same symbol.
- Network and chain ID, such as BNB Smart Chain mainnet (56).
- Token contract address, copied from your approved asset record.
- Transaction hash, sender address, recipient address, and timestamp.
- Amount sent and amount received, including the token’s decimal precision.
- Purpose, approver, and the corresponding payout or invoice reference.
Decimals determine how a token’s integer on-chain amount becomes a human-readable balance. For example, if a token uses 18 decimals, a raw transfer amount of 1,500,000,000,000,000,000 represents 1.5 tokens. Keep the raw value or the exact decoded value in your audit trail so rounding does not obscure small differences.
How Do We Check That The Recipient Got The Right Amount?
Look up the transaction hash on a BNB Chain block explorer and check that the transaction succeeded. Then inspect the receipt’s logs for the token contract’s Transfer event: confirm the contract, recipient, and decoded amount. A successful transaction can still be the wrong payment if it called an unexpected contract or sent tokens to the wrong address.
Compare two cases side by side. If your company sends 25 tokens to a supplier and the matching event records 25 for that supplier’s address, the ledger can usually be reconciled directly. If a token charges a transfer fee, the sender may transfer 25 while the recipient receives less; reconcile the amount actually credited, and confirm the token’s behavior before treating the difference as an error.
Native BNB transfers work differently: they move BNB as the transaction’s value and do not produce a BEP-20 token transfer event. Network fees are also paid in BNB, so record them separately from the token payout. A wallet view or token tracker, including PooCoin, can help you investigate balances and price context, but the receipt and event log are the evidence for the transfer itself.
What Should We Do When The Records Do Not Match?
First check the network, contract address, recipient, and token decimals; these explain many apparent mismatches. If the receipt shows no expected transfer event, or the recipient differs, pause reconciliation and investigate before marking the payout complete. Keep the hash and supporting records together so another team member can repeat the check.
Before acting, ask yourself: Can someone else verify this payment from its chain, contract, recipient, amount, and transaction hash?
Top comments (0)