Reporting and Confirmations via Swift

This section provides brief guidance on receiving payment confirmations and account reporting via Swift, including the formats and details available.

Through these messages, you can monitor payment activity and support reconciliation processes, all delivered directly to your registered Swift BIC.

Payment Confirmations and Reporting Overview

The table below summarizes the Swift messages available for each client solution types, including payment confirmations, status updates, and account statements.

Client Solution Type	pacs.008/MT103 confirmations	MT900 / MT910 (Debit & Credit confirmations)	MT199 (Status updates)	MT940, MT942, MT950
Receiving Payments	✅ Supported	✅ Supported	❌ Not Supported	✅ Supported
Sending Payments	❌ Not Supported	✅ Supported	✅ Supported	✅ Supported

Note: pacs.008/MT103 confirmations are generated and sent to you only when a payment is received that references your underlying customer account.

Reporting

Reporting messages provide account information that can be used for reconciliation. These reports are delivered directly to you via Swift using standard MT9xx message formats.

You can be configured to receive MT950 or MT940 end-of-day account statements, as well as MT942 intraday statements.

The MT950 specification is provided below. Specifications for other reporting formats are available upon request.

MT950 Specification

Tag	Field Name	Content / Options	Tag details
20	Transaction Reference Number	16x	16x Unique reference generated by Banking Circle for each message.
25	Account Identification	35x	DK IBAN account number of the settlement account.
28C	Statement Number/ Sequence Number	5n[/5n]	Statement number is populated with sequential number of account statement. If there are more than one statement per day, then sequence number is populated starting with 1 and incremented by 1 per sub message.
60 F/M	Opening Balance	1!a6!n3!a15 d	Contains opening balance of account in statement.
----➔			*Below tag is repeat based on number of transactions on account in statement.*
61	Statement line	6!n[4!n]2a[1 !a]15d1!a3!c 16x[//16x]	Contains details of each transaction in below order: Value date of transaction in YYMMDD Booking date of transaction in MMDD D= Debit or C= Credit Funds Code – the 3 rd character of the currency code Amount of the transaction Transaction Type – always NMSC Reference for Account Holder: A) For Credits – `InstrId` of pacs.008 or field 20 of MT103 B) For Debits – Your Reference provided in `InstrId` of pacs.008 or field 20 of MT103. Banking Circle’s internal unique payment reference, linked to the Reference for Account Holder
62 F/M	Closing Balance (Booked Funds)	1!a6!n3!a15 d	Closing balance of statement
64	Closing Available Balance (Available Funds)	1!a6!n3!a15 d	Available balance on account on statement date

Note: The 61 tag repeats for each transaction in the statement.

Debit and Credit Confirmations

You can receive debit and credit confirmations via standard Swift messages sent to your registered BIC.

To enable debit and credit confirmations (MT900 and MT910 respectively), please contact our team.

Sample confirmation message

20: transaction reference
:21: NONREF
:25:17055234
:13D:2501140806+0000
:32A:250114USD100000,
:50K://
Your IBAN
:52A: Your BIC
:56D: Banking Circle
:72:

Status updates

Certain payment events, such as insufficient funds in your settlement account or other validation issues, may result in rejection notifications. These are communicated via Swift MT199 messages.

An MT199 message is sent in the following format:

Field name	Comment	MT199 tag
Transaction Reference Number	Contains our unique message reference	20
Related Reference	Contains the transaction reference of that original message (`InstrId` of pacs.008 or field 20 of MT103)	21
Narrative	Line 1 contains code /REJT/ followed by the field number of the original message that failed validation. Line 2 contains the reject code and reason. (See Swift rejection codes1 for MT199 reject codes and reasons.) Line 3 contains code /MREF/ followed by the sender's transaction reference in `InstrId` of pacs.008 or field 20 of the original MT103. Line 4 contains /TEXT/ followed by fields/lines from the original pacs.008 or MT103 message.	79

Missing funding

If there are insufficient funds in your settlement account at the time of payment instruction, we will send a MT199 rejection message with error code AM04, which means that the payment is pending, but not yet rejected.

The payment will remain in pending status until the next business day. If the settlement account is not funded in time, the payment will be rejected, and we will send an MT199 referencing error code XA01.