Notices to Receive

The notice family: MT210 notices to receive to and from camt.057, one expected incoming amount per item.

Formats

Format	What it is	Versions accepted	Emitted by default
`mt210`	Notice to receive	n/a	n/a
`camt.057`	Notification to receive	`.001.06` – `.001.08`	`.001.06`

Pairs

From	To
`mt210`	`camt.057`
`camt.057`	`mt210`

A notice tells the account servicer that funds are expected; it is not a booked statement. It normalizes to a statement document of kind notice-to-receive but never converts to a statement format or an accounting file (mt210 → camt.053 and mt210 → ofx do not exist). There is no canonical source.

How fields map

Each expected amount becomes one credit entry; a notice has no balances.

MT210 to camt.057.

:20: becomes the message id and the notification id; :25: the account to be credited.
:30: becomes the expected value date. It applies to the whole message, so camt.057 carries it once at notification level.
Each repetition of :21: + :32B: becomes an item: :21: is both the item id and the end-to-end id, :32B: the expected amount.
The ordering customer (:50C: or :50F:) becomes the item's debtor; :52a: the debtor agent.

camt.057 to MT210. The reverse. Values given at notification level (debtor, debtor agent, expected value date) apply to every item that does not state its own.

Where information is lost

Situation	Warning
camt.057 creation time (MT210 carries none)	`MISSING_REQUIRED_DEFAULTED`
`:56a:` intermediary, or an intermediary in camt.057 (one agent per item)	`DROP_FIELD`
The debtor's own account going to camt.057 (its item account is the account to be credited, not the debtor's)	`DROP_FIELD`
A debtor that is only a name, going to MT210 (only options C and F exist)	`DROP_FIELD`
Remittance information going to MT210	`DROP_FIELD`
More than 10 items going to MT210; the rest are cut	`DROP_FIELD`
Items whose value date differs from the first one, going to MT210	`DROP_FIELD`
A non-credit entry (a notice only announces incoming funds)	`DROP_FIELD`
A reference longer than 16 characters	`TRUNC_REFERENCE`

Conventions

Credits only. Every item is a credit. A source entry that is a debit cannot be advised and is dropped; a notice with no credit entry left is refused.
One date per MT210. :30: is message level, so the first item's date wins and later items with another date are reported.
:50C: is a BIC. An ordering customer identified by BIC travels as the debtor's name, as in the example below, and converts back to :50C:.
At most 10 items per MT210. Larger camt.057 notifications are truncated on the way to MT, with a warning naming the count.

Example

curl -sS -X POST "https://api.transmute.403fin.io/v1/convert?to=camt.057" \
  -H "Authorization: Bearer $TRANSMUTE_KEY" \
  -H "Content-Type: text/plain" \
  --data-binary @- <<'MT'
:20:NOTICE-2026-001
:25:DE89370400440532013000
:30:260612
:21:EXPECT-REF-1
:32B:EUR25000,00
:50C:AAAADEFF
:52A:AAAADEFF
MT

The result document, formatted:

<Ntfctn>
  <Id>NOTICE-2026-001</Id>
  <Acct><Id><IBAN>DE89370400440532013000</IBAN></Id></Acct>
  <XpctdValDt>2026-06-12</XpctdValDt>
  <Itm>
    <Id>EXPECT-REF-1</Id>
    <EndToEndId>EXPECT-REF-1</EndToEndId>
    <Amt Ccy="EUR">25000.00</Amt>
    <Dbtr><Pty><Nm>AAAADEFF</Nm></Pty></Dbtr>
    <DbtrAgt><FinInstnId><BICFI>AAAADEFF</BICFI></FinInstnId></DbtrAgt>
  </Itm>
</Ntfctn>

The only warning is MISSING_REQUIRED_DEFAULTED (info) for GrpHdr/CreDtTm; meta.targetType is camt.057.001.06.

Was this page helpful?