Payments Academy
camt.060: asking for a report on demand NOW Camt.060 Camt.060 request contents Request versus Camt.060 in reconciliation BA requirements MESSAGE TRACE Camt.060 A treasury team needs to know the balance of its euro account at 11 in the morning, before it decides whether Step 1 of 5 camt.060: asking for a report on demand 1 NOW Camt.060 2 Camt.060 request contents 3 Request versus 4 Camt.060 in reconciliation 5 BA requirements A treasury team needs to know the balance of its euro account at 11 in the morning, before it decides whether to fund a large payment. Step 1 of 5
camt.060 request contents Camt.060 NOW Camt.060 request contents Request versus Camt.060 in reconciliation BA requirements MESSAGE TRACE Camt.060 > Camt.060 request contents The camt.060 carries four things. Step 2 of 5 camt.060 request contents 1 Camt.060 2 NOW Camt.060 request contents 3 Request versus 4 Camt.060 in reconciliation 5 BA requirements The camt.060 carries four things. Step 2 of 5
Request versus report: camt.060 against camt.052 and camt.053 Camt.060 Camt.060 request contents NOW Request versus Camt.060 in reconciliation BA requirements MESSAGE TRACE Camt.060 > Camt.060 request contents > Request versus The difference between camt.060 and the other camt messages is the direction. camt.052 Step 3 of 5 Request versus report: camt.060 against camt.052 and camt.053 1 Camt.060 2 Camt.060 request contents 3 NOW Request versus 4 Camt.060 in reconciliation 5 BA requirements The difference between camt.060 and the other camt messages is the direction. camt.052 Step 3 of 5
camt.060 in reconciliation: a second source to check Camt.060 Camt.060 request contents Request versus NOW Camt.060 in reconciliation BA requirements MESSAGE TRACE Camt.060 > Camt.060 request contents > Request versus > Camt.060 in reconciliation The camt.060 also matters for reconciliation, because a report requested on demand can be compared with Step 4 of 5 camt.060 in reconciliation: a second source to check 1 Camt.060 2 Camt.060 request contents 3 Request versus 4 NOW Camt.060 in reconciliation 5 BA requirements The camt.060 also matters for reconciliation, because a report requested on demand can be compared with the report received on schedule. Step 4 of 5
BA requirements for camt.060 Camt.060 Camt.060 request contents Request versus Camt.060 in reconciliation NOW BA requirements MESSAGE TRACE Camt.060 > Camt.060 request contents > Request versus > Camt.060 in reconciliation > BA requirements For a business analyst, the camt.060 is a small message with a clear use case, and the requirements around it Step 5 of 5 BA requirements for camt.060 1 Camt.060 2 Camt.060 request contents 3 Request versus 4 Camt.060 in reconciliation 5 NOW BA requirements For a business analyst, the camt.060 is a small message with a clear use case, and the requirements around it are straightforward. Step 5 of 5

Steps of this lesson, in order.

0:00 / 3:45 Step 1 of 5

camt.060: the account reporting request

Complete ISO 20022 Catalogue, Lesson 8 of 8, Narration 3:45, D04 Messaging and standards

ReconciliationValue dateISO 20022

What you will learn

Your objective. By the end of this lesson, you will be able to explain camt.060: the account reporting request. A treasury team needs to know the balance of its euro account at 11 in the morning, before it decides whether to fund a large payment.

Why it matters. For a business analyst, the camt.060 is a small message with a clear use case, and the requirements around it are straightforward.

Chapter objective: Learner navigates the complete ISO 20022 catalogue, selecting the right message for each business scenario across payments, cash management, securities, and reporting. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.

Key learning points

  • camt.060: asking for a report on demand
  • camt.060 request contents
  • Request versus report: camt.060 against camt.052 and camt.053
  • camt.060 in reconciliation: a second source to check
  • BA requirements for camt.060

Key terms

Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.

Value date: The date on which funds become available to the beneficiary and on which interest starts to accrue. It is the date used for settlement and for nostro posting.

ISO 20022: An international standard for financial messaging that defines XML message formats for payments, securities and trade.

Clearing and settlement timeline showing camt.060: the account reporting request.

Practise this lesson

Exercise

Read the camt.060 message described in this lesson and identify its key parts.

Use the message structure, fields and example in this lesson.

  1. What to do. List the main blocks of the message, name the field that carries the amount, and name the field that identifies the payment.

Correct result. The message is made of blocks, each carrying a part of the payment instruction. The amount field and the identification field are the two a receiving bank checks first, because without them it cannot process or reconcile the payment.

Why. A message is only useful if you can read it. The blocks tell the receiving bank what to do, and the amount and identification fields are what it checks first.

Check your understanding

Practice question

Which of the following best describes camt.060: the account reporting request?

Takeaway and next step

What to remember

For a business analyst, the camt.060 is a small message with a clear use case, and the requirements around it are straightforward.

Open the message type from this lesson and inspect its fields, then find the field that carries the amount.

Open the ISO 20022 Message Explorer →

Builds on "Practical Exercise: Transform an MT103 into pacs.008".

Transcript and full text

Show transcript

camt.060 is the account reporting request. It is the message a customer sends to its bank to ask for a statement, a report, or a notification. It is the request that causes the bank to send a camt.052, a camt.053, or a camt.054. The camt.060 has a group header, GrpHdr, which carries the message identification, MsgId, the creation date and time, CreDtTm, and the message recipient, MsgRcpt. It has a reporting request block, RptgReq, which carries the requested message name identification, ReqstdMsgNmId, which states the message requested, for example camt.053.001.08 for a statement, the account, Acct, the account owner, AcctOwnr, the account servicer, AcctSvcr, and the reporting period, RptgPrd, which states the from date and time, FrDtTm, and the to date and time, ToDtTm, and the reporting sequence, RptgSeq, which states the range, FrToSeq, and the sequence number, SeqNb. The requested message name identification is the field that states which message the customer wants. If the customer wants a statement, it requests camt.053.001.08. If it wants an intraday report, it requests camt.052.001.08. If it wants a debit credit notification, it requests camt.054.001.08. The bank will send the requested message, for the account and the period stated in the request. The customer can request a statement for a specific period, for example from 1 May 2026 to 31 May 2026, or it can request a statement for the current day, or it can request a report from a specific sequence number. The reporting period and the reporting sequence are the controls that define what the bank sends back. The account in a camt.060 is identified by the account identification, Acct, which carries the IBAN or the account number, and the account owner, AcctOwnr, which names the customer, and the account servicer, AcctSvcr, which names the bank. The customer may request a statement for one account, or it may request statements for several accounts, by sending one camt.060 per account, or by sending one camt.060 with several reporting request blocks. The bank will send a separate camt.053 for each account, because each statement is for one account. A corporate with 20 accounts will send 20 camt.060 requests, or one request with 20 blocks, and will receive 20 camt.053 statements, one per account. The reporting period is stated as a from date and time and a to date and time. The from date and time is the start of the period, and the to date and time is the end of the period. The bank will include in the statement all entries with a booking date within the period, and it will state the opening balance at the from date and the closing balance at the to date. The customer should request a period that matches its reconciliation cycle, normally daily, weekly, or monthly. A daily statement covers one day, a weekly statement covers one week, and a monthly statement covers one month. The customer can also request a statement for a custom period, for example from 15 May to 20 May, if it needs to investigate a specific entry. The reporting sequence is an alternative to the reporting period. The customer can request a statement from a specific sequence number, for example from sequence number 100 to sequence number 150, where the sequence number is the electronic sequence number, ElctrncSeqNb, that the bank assigns to each statement. The sequence number is a control that ensures the customer receives every statement in order, and that it does not miss one. If the customer receives sequence number 101 after sequence number 99, it knows that sequence number 100 is missing, and it can request it with a camt.060. The sequence number is therefore a reconciliation control, and it is important for a corporate that receives statements automatically. The bank response to a camt.060 is the requested message, sent as a separate message. The bank does not send a confirmation that it received the camt.060, it sends the statement or the report. If the bank cannot provide the requested statement, for example because the account does not exist, or because the period is too long, it will send a rejection, normally as an admi.002 message system event acknowledgement, or as a free format message, stating the reason. The customer should check that it receives the requested statement within the expected time, and should re-send the camt.060 if it does not. A statement that is not received is a gap in the reconciliation, and it must be followed up. For a business analyst, the camt.060 requirement must state the requested message, the account, the period, and the sequence. The requirement should say that the system generates a camt.060 with the requested message name identification, the account, and the reporting period or the reporting sequence, that it sends the request to the bank, that it checks that the requested statement is received, and that it re-sends the request if the statement is not received within the agreed time. A system that cannot request a statement by sequence number cannot detect a missing statement, and a system that cannot request a statement for a custom period cannot investigate a specific entry.

camt.060 is the account reporting request. It is the message a customer sends to its bank to ask for a statement, a report, or a notification. It is the request that causes the bank to send a camt.052, a camt.053, or a camt.054. The camt.060 has a group header, GrpHdr, which carries the message identification, MsgId, the creation date and time, CreDtTm, and the message recipient, MsgRcpt. It has a reporting request block, RptgReq, which carries the requested message name identification, ReqstdMsgNmId, which states the message requested, for example camt.053.001.08 for a statement, the account, Acct, the account owner, AcctOwnr, the account servicer, AcctSvcr, and the reporting period, RptgPrd, which states the from date and time, FrDtTm, and the to date and time, ToDtTm, and the reporting sequence, RptgSeq, which states the range, FrToSeq, and the sequence number, SeqNb.

The requested message name identification is the field that states which message the customer wants. If the customer wants a statement, it requests camt.053.001.08. If it wants an intraday report, it requests camt.052.001.08. If it wants a debit credit notification, it requests camt.054.001.08. The bank will send the requested message, for the account and the period stated in the request. The customer can request a statement for a specific period, for example from 1 May 2026 to 31 May 2026, or it can request a statement for the current day, or it can request a report from a specific sequence number. The reporting period and the reporting sequence are the controls that define what the bank sends back.

The account in a camt.060 is identified by the account identification, Acct, which carries the IBAN or the account number, and the account owner, AcctOwnr, which names the customer, and the account servicer, AcctSvcr, which names the bank. The customer may request a statement for one account, or it may request statements for several accounts, by sending one camt.060 per account, or by sending one camt.060 with several reporting request blocks. The bank will send a separate camt.053 for each account, because each statement is for one account. A corporate with 20 accounts will send 20 camt.060 requests, or one request with 20 blocks, and will receive 20 camt.053 statements, one per account.

The reporting period is stated as a from date and time and a to date and time. The from date and time is the start of the period, and the to date and time is the end of the period. The bank will include in the statement all entries with a booking date within the period, and it will state the opening balance at the from date and the closing balance at the to date. The customer should request a period that matches its reconciliation cycle, normally daily, weekly, or monthly. A daily statement covers one day, a weekly statement covers one week, and a monthly statement covers one month. The customer can also request a statement for a custom period, for example from 15 May to 20 May, if it needs to investigate a specific entry.

The reporting sequence is an alternative to the reporting period. The customer can request a statement from a specific sequence number, for example from sequence number 100 to sequence number 150, where the sequence number is the electronic sequence number, ElctrncSeqNb, that the bank assigns to each statement. The sequence number is a control that ensures the customer receives every statement in order, and that it does not miss one. If the customer receives sequence number 101 after sequence number 99, it knows that sequence number 100 is missing, and it can request it with a camt.060. The sequence number is therefore a reconciliation control, and it is important for a corporate that receives statements automatically.

The bank response to a camt.060 is the requested message, sent as a separate message. The bank does not send a confirmation that it received the camt.060, it sends the statement or the report. If the bank cannot provide the requested statement, for example because the account does not exist, or because the period is too long, it will send a rejection, normally as an admi.002 message system event acknowledgement, or as a free format message, stating the reason. The customer should check that it receives the requested statement within the expected time, and should re-send the camt.060 if it does not. A statement that is not received is a gap in the reconciliation, and it must be followed up.

For a business analyst, the camt.060 requirement must state the requested message, the account, the period, and the sequence. The requirement should say that the system generates a camt.060 with the requested message name identification, the account, and the reporting period or the reporting sequence, that it sends the request to the bank, that it checks that the requested statement is received, and that it re-sends the request if the statement is not received within the agreed time. A system that cannot request a statement by sequence number cannot detect a missing statement, and a system that cannot request a statement for a custom period cannot investigate a specific entry.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.