> For the complete documentation index, see [llms.txt](https://krimkopi.gitbook.io/krimkopi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://krimkopi.gitbook.io/krimkopi-docs/articles/04-mt103-vs-mt202-vs-pacs008.md).

# MT103 vs MT202 vs pacs.008 — Peta Pesan Transfer Lintas Border

> **Ringkasan:** MT103 untuk dana nasabah, MT202 untuk dana bank, dan pacs.008 adalah penerus ISO 20022 keduanya di koridor cross-border. Plus: beda metode *serial* vs *cover payment* — konsep yang menjelaskan kenapa satu transfer bisa "pecah" jadi dua pesan berbeda.

**Kategori:** Teknis · **Level:** Menengah–Mahir · **Estimasi baca:** 8 menit

***

## 1. Tabel Perbandingan

| Aspek                          | MT103                   | MT202 / MT202COV                       | pacs.008 (CBPR+)                                               |
| ------------------------------ | ----------------------- | -------------------------------------- | -------------------------------------------------------------- |
| Kategori standar               | MT cat. 1 (customer)    | MT cat. 2 (financial institution)      | ISO 20022 MX                                                   |
| Untuk siapa                    | Dana **nasabah**        | Dana **antar bank** / cover            | Dana nasabah (penerus MT103)                                   |
| Data nasabah                   | :50a: & :59a: wajib     | 202COV wajib bawa salinan data nasabah | Terstruktur penuh (`Dbtr`/`Cdtr`)                              |
| Format                         | Teks blok field         | Teks blok field                        | XML/JSON berlapis                                              |
| Kaya data                      | 4×35 karakter per field | Sama                                   | Kali lipat lebih besar, terstruktur, bisa bawa invoice lengkap |
| Status 2026 (cross-border FIN) | **Pensiun Nov 2025**    | **Pensiun Nov 2025**                   | Aktif — standar utama                                          |

## 2. Serial vs Cover — Dua Cara Mengantar Instruksi

### Serial method (rantai)

MT103 berjalan menyusuri rantai bank satu per satu, tiap bank maju meneruskan MT103 baru ke bank berikutnya. Instruksi dan dana bergerak di jalur yang sama.

```
Bank A ──MT103──> Bank B ──MT103──> Bank C (bank penerima)
```

### Cover method (pesan + penutup)

Instruksi nasabah (MT103) dikirim langsung ke bank penerima, sementara **pemindahan dana** dilakukan terpisah lewat MT202COV ke lewat correspondent. Ekonomis (lebih sedikit bank "menyentuh" instruksi), tapi dulu bermasalah untuk transparansi: bank di jalur cover tidak selalu melihat nama nasabah.

```
Bank A ──MT103──────────────────> Bank C (instruksi)
Bank A ──MT202COV──> Bank B ──> (settlement) Bank C (dana + data cover)
```

> **Wolfsberg & FATF:** Kekurangan transparansi cover payment dimanfaatkan untuk menghindari screening sanksi. Solusinya, sejak Standards Release 2018, **MT202COV wajib** membawa salinan data nasabah pengirim (:50a:) dan penerima (:59a:) dari MT103 yang dicovernya. Di era ISO 20022, padanannya **pacs.009 COV** dengan disiplin data yang sama.

## 3. Kenapa Satu Transfer Bisa Terlihat "Hilang" di Tengah?

Karena kombinasi serial + cover + correspondent berlapis:

* Bank penerima menunggu **dana** (jalur cover/MT202-family) yang datang dari bank lain, sementara **instruksi** (MT103/pacs.008) sudah lama sampai.
* Cut-off correspondent terlewat → nilai tanggal bergesir ke hari kerja berikut.
* Screening/compliance men-flag nama mirip daftar sanksi → investigasi manual (bisa berhari-hari, tanpa pemberitahuan otomatis ke nasabah).
* Field rekening penerima salah → dana parkir sambil menunggu repair/amendmen.

Kunci pencarian posisi dana: **UETR** via gpi Tracker — hanya bank yang punya akses; nasabah harus melapor ke bank pengirim (prosedur di [artikel 08](/krimkopi-docs/articles/08-verifikasi-mt103.md)).

## 4. Era pacs.008 — Apa yang Berubah Praktisnya?

| Dulu (MT103)                        | Sekarang (pacs.008)                                                      |
| ----------------------------------- | ------------------------------------------------------------------------ |
| Keterangan :70: 4×35 karakter       | Remittance terstruktur: invoice, item, diskon, pajak per baris           |
| Biaya :71A: OUR/BEN/SHA + :71F:     | Elemen biaya terstruktur per level (`ChrgBr`, `Chrgs`)                   |
| UETR di user header :121:           | `<UETR>` elemen baku                                                     |
| Perbaikan data via MT19x/n99 manual | camt.056 (cancel), camt.029 (resolve), pacs.002 (status) terstruktur     |
| Screening parsing teks bebas        | Data terstruktur = screening lebih presisi, lebih sedikit false positive |

Dampak bagi profesional: investigasi payment lebih cepat, laporan compliance lebih kaya, tapi **integrasi sistem internal** (core banking, ERP treasury) harus paham XML CBPR+ — inilah kenapa migrasi Nov 2025 adalah proyek multi-tahun perbankan dunia.

## 5. Cheat Sheet Cepat

* Nasabah kirim dana ke luar negeri → pesan yang relevan (era MT): **MT103**; era sekarang: **pacs.008**.
* Bank memindahkan dana sendiri / cover → **MT202 / MT202COV** → sekarang **pacs.009 / pacs.009 COV**.
* Mau batalkan → dulu MT192/cancel request → sekarang **camt.056** (dan resolusinya camt.029).
* Mau lacak → **UETR** + gpi Tracker via bank.
* Minta bukti → minta **confirmed credit**/statement rekening penerima — bukan sekadar "copy MT103".

## 6. Sumber

1. SWIFT — ISO 20022 payment migration (CBPR+) — <https://www.swift.com/our-initiatives/iso-20022-payment-migration> (diakses 28 Agu 2026)
2. Wolfsberg Group — Payment Transparency Standards — <https://www.wolfsberg-group.org> (diakses 28 Agu 2026)
3. FATF — panduan transparansi pembayaran — <https://www.fatf-gafi.org> (diakses 28 Agu 2026)
4. ISO 20022 RA — katalog pesan pacs/camt — <https://www.iso20022.org> (diakses 28 Agu 2026)

***

*Artikel ini bagian dari knowledge base* [*krimkopi.my.id*](https://krimkopi.my.id)*. Berikutnya:* [*UETR & SWIFT gpi →*](/krimkopi-docs/articles/05-uetr-swift-gpi.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://krimkopi.gitbook.io/krimkopi-docs/articles/04-mt103-vs-mt202-vs-pacs008.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.