Acme Treasury Ltd

Treasury Operations · Corporate Banking
LEI 999900DEMOACMETR0001 · TRCore in-cluster · style treasury

Register inbound · T2 record-keeping submission to TRCore

Host saw an on-chain transfer to one of its customers and is registering it with TRCore. Sanctions screening still runs; no correlation halt (T1-only). Case lands at TR_PENDING.
Ask first. Of the originator fields below, only the legal name is required — "they have to know at least the name, else it is not a valid transaction at all" (F-IN-1, 2026-08-27). Everything else is optional on inbound, because the originator is somebody else's customer. Even the name may be one the counterparty's own inquiry has already told TRCore: Check TRCore first asks with only what is on the ledger, and a hit is amended rather than re-entered.
Beneficiary (your customer)
Transaction
On-chain observation
Read off the same view that showed you the amount. The match keys on the address pair, so TRCore requires it — without a sender there is no key, and the four remaining fields are shared by any two deposits of this size to this customer.
Sent to TRCore. When set with no explicit onchain_state, backend infers state=confirmed.
Override the auto-detect (tx_hash → confirmed; no tx_hash → awaiting_confirmation). Sent to TRCore when non-empty.
Step 1 — ask TRCore
Everything above is what a ledger shows. Check TRCore first asks with exactly that — the two wallet addresses, chain, asset and amount, plus the hash if you have one — and nothing about who the originator is. Only a miss opens step 2.
Step 2 — what your customer says
Originator (counterparty)
Leave unknown rather than guessing. F-IN-1 (2026-08-27) made this optional on inbound for exactly that reason — "I know Vasia Pupkin sent me the money, I probably don't know where from he sent it". A guess is worse than an absence: custody and R2 never fires, self_custody and completeness demands a verification method nobody has. TRCore records the gap as incomplete:originator_wallet_type.
Required by TRCore when the wallet type is self_custody: your declaration about your own customer, never inferred. Left undeclared, TRCore answers 422 — which is the point.
Required for entity-type originators (both custody and non-custody-legal). TRCore's OriginatorBlock enforces this per FATF R.16.
Explicit override; leave blank for the default heuristic.
Supply what the host actually knows. Reg 2023/1113 Art 14(1) — national_id OR (DOB + POB) — is enforced on OUT only since F-IN-1 (2026-08-27): outbound, the originator is our own customer and holding their identity is the host's obligation; inbound, the originator belongs to somebody else and what arrives is a recollection. Missing values are recorded as incomplete:originator_identity, which blocks an automatic close — a Specialist can still approve the case.

Recent registered inbounds

Loading…