Processing camt.054 files
CAMT (Cash Management) is a set of bank statement messages defined by ISO 20022. There are different standards for different bank statement types. This article focuses specifically on camt.054.
The camt.054 is a bank to customer notification of credit and debit transactions for a given time period. The content is similar to camt.053, but does not include the account balance information covered by camt.053. Because the transaction details are the same, you typically use either camt.053 or camt.054 for reconciliation, not both.
There are multiple versions of camt.054 in use that have slight variations. FinDock supports:
- Camt.054.001.02
- Camt.054.001.04
Setting up targets for camt.054 processing
To be able to import and parse camt.054 files, FinDock needs to have the bank account (customer account) used in the files defined as a target. The target can be for any of the following FinDock native payment methods:
For each originating bank account of your camt.054 files, make sure you use select camt.054 for the CAMT message type in the target settings. You should also enable Duplication protection unless you have some specific testing scenario where it needs to be off.
Please note that for a given target (bank account), you can only import camt.053 or camt.054 files, not both. However, regardless of the format, the resulting Salesforce data after FinDock's default matching logic for reconciliation is the same.
Camt.054 file structure
The camt.054 has the same basic structure as camt.053. The main difference is the absence of a Balance element, but otherwise the one-to-none, one-to-one and one-to-many scenarios are used.
Camt.054 field mapping
The following tables outline the mapping between camt.054 XML elements and FinDock objects and fields. In some cases, the mapping includes file content evaluation logic that results in parsing that varies from the default mapping. This logic is not covered in these tables.
Group Header <GrpHdr>
Nothing from the group header is mapped by default. However, you can use Guided Matching rules to extract information if needed.
Notification <Ntfctn>
| XML Element | Name | Transaction Set Field |
|---|---|---|
| Id | Identification | Not Mapped (Id is used for deduplication on ProcessingHub File record) |
| ElctrncSeqNb | Electronic Sequence Number | Batch Identification |
| FrToDt / FrDtTm | From Date Time | From Date |
| FrToDt / ToDtTm | To Date Time | To Date |
| Acct / Id / IBAN (or Acct / Id / Othr / Id) | IBAN | Bank Account Number |
| TxsSummry / TtlCdtNtries / NbOfNtries | (Calculated) | Number of Credit Entries |
| TxsSummry / TtlCdtNtries / Sum | (Calculated) | Total Amount Credit |
| TxsSummry / TtlDbtNtries / NbOfNtries | (Calculated) | Number of Debit Entries |
| TxsSummry / TtlDbtNtries / Sum | (Calculated) | Total Amount Debit |
Entry <Ntry>
| XML Element | Name | Transaction Field |
|---|---|---|
| NtryRef | Entry Reference | Entry Reference |
| Amt | Amount | Amount |
| Amt | (Ccy attribute from Amount) | Currency |
| RvslInd | Reversal Indicator | Reversal Indicator |
| BookgDt / Dt | Date | Date |
| ValDt / Dt | Date | Value Date |
| AcctSvcrRef | Account Servicer Reference | Account Servicer Reference |
| BkTxCd / Prtry / Cd or NtryDtls / BkTxCd / Prtry / Cd | Code | Reported Payment Method Code |
| AmtDtls / InstdAmt / Amt | Amount | Amount |
| AmtDtls / InstdAmt / Amt | (Ccy attribute from Amount) | Currency |
| AddtlNtryInf | Additional Entry Information | Additional Entry Information |
Entry Details <NtryDtls> - Transaction
| XML Element | Name | Transaction Field |
|---|---|---|
| TxDtls / Refs / AcctSvcrRef | Account Servicer Reference | Account Servicer Reference |
| TxDtls / Refs / EndToEndId | End To End Id | End To End Id |
| TxDtls / Refs / MndtId | Mandate Identification | Mandate Reference |
| TxDtls / AmtDtls / InstdAmt / Amt or TxDtls / AmtDtls / TxAmt / Amt or TxDtls / Amt | Amount | Amount |
| TxDtls / RltdPties / Dbtr / Pty / Nm or TxDtls / RltdPties / UltmtDbtr / Pty / Nm | Name | Account Holder Name |
| TxDtls / RltdPties / Dbtr / Pty / PstlAdr / StrtNm or TxDtls / RltdPties / UltmtDbtr / Pty / PstlAdr / StrtNm | Street Name | Street |
| TxDtls / RltdPties / Dbtr / Pty / PstlAdr / BldgNb or TxDtls / RltdPties / UltmtDbtr / Pty / PstlAdr / BldgNb | Building Number | Building Number |
| TxDtls / RltdPties / Dbtr / Pty / PstlAdr / TwnNm or TxDtls / RltdPties / UltmtDbtr / Pty / PstlAdr / TwnNm | Town Name | City |
| TxDtls / RltdPties / Dbtr / Pty / PstlAdr / Ctry or TxDtls / RltdPties / UltmtDbtr / Pty / PstlAdr / Ctry | Country | Country |
| TxDtls / RltdPties / Dbtr / Pty / PstlAdr / AdrLine or TxDtls / RltdPties / UltmtDbtr / Pty / PstlAdr / AdrLine | Address Line | Address Line 1 |
| TxDtls / RltdPties / DbtrAcct / Id / IBAN or TxDtls / RltdPties / DbtrAcct / Id / Othr / Id | IBAN or Identification (in some cases under CdtrAcct instead of DbtrAcct) | Bank Account Number |
| TxDtls / RltdAgts / DbtrAgt / FinInstnId / BIC | BIC | BIC Code |
| TxDtls / RmtInf / Strd / CdtrRefInf / Ref or TxDtls / RmtInf / Ustrd or TxDtls / RmtInf / Strd / CdtrRefInf / Ref | Reference or Unstructured | Payment Reference |
| TxDtls / RmtInf / Ustrd | Remittance Information | Remittance Information, Remittance Information Long |
| TxDtls / RtrInf / Rsn / Cd | Code | Reason Code |
Extend camt.054 processing with Guided Matching
Out of the box, FinDock extracts the information from camt.054 files required to update payment records in Salesforce. However, the files may contain more information that you would like to use to enrich your CRM data.
Using Guided Matching, you can do just about anything you want with content of a camt.054 file. You can extract unique information for your own purposes as well as create rules that extend the logic of the parsed data on Transaction Set and Transaction records.