...

1. GROUP HEADER (GrpHdr) - File Level

ProBill Source	ISO20022 XML Path	Required	Data Type	Notes
@FileID parameter	GrpHdr/MsgId	REQUIRED	String(35)	Unique message identifier for the file
SYSDATETIME()	GrpHdr/CreDtTm	REQUIRED	DateTime	ISO8601 format: YYYY-MM-DDTHH:MM:SS
COUNT all transactions	GrpHdr/NbOfTxs	REQUIRED	Integer	Total number of payment transactions in file
SUM(Amount) all transactions	GrpHdr/CtrlSum	REQUIRED	Decimal	Total of all transaction amounts (control sum)
Swedbank: \ PaymentAccount.SwedbankAgreementID \ \ Nordea: \ PaymentAccount.NordeaSignerID	GrpHdr/InitgPty/Id/OrgId/Othr/Id	REQUIRED	String(35)	Bank-specific initiating party identifier
Swedbank: 'BANK' \ Nordea: 'CUST'	GrpHdr/InitgPty/Id/OrgId/Othr/SchmeNm/Cd	REQUIRED	String(4)	Identification scheme code

...

2. PAYMENT INFORMATION (PmtInf) - Batch Level

ProBill Source	ISO20022 XML Path	Required	Data Type	Notes
@FileID parameter	PmtInf/PmtInfId	REQUIRED	String(35)	Payment information identifier
Based on PayoutTypeID: \ • 'TRF' = Transfers (1,3,4) \ • 'CHK' = Money orders (2)	PmtInf/PmtMtd	REQUIRED	String(3)	Payment method code
COUNT in batch	PmtInf/NbOfTxs	REQUIRED	Integer	Number of transactions in this payment batch
SUM(Amount) in batch	PmtInf/CtrlSum	REQUIRED	Decimal	Control sum for this payment batch
Literal: 'NORM'	PmtInf/PmtTpInf/InstrPrty	REQUIRED	String(4)	Instruction priority (Normal)
Literal: 'MPNS'	PmtInf/PmtTpInf/SvcLvl/Prtry	REQUIRED	String(35)	Proprietary service level (mandatory for BG/PG)
Literal: 'SUPP'	PmtInf/PmtTpInf/CtgyPurp/Cd	REQUIRED	String(4)	Category purpose code (Supplier payment)
CONVERT(VARCHAR(12), SYSDATETIME(), 23)	PmtInf/ReqdExctnDt	REQUIRED	Date	Requested execution date: YYYY-MM-DD
PaymentAccount.CustomerNumber	PmtInf/Dbtr/Nm	REQUIRED	String(140)	Debtor name (company/organization name)
Literal: 'SE'	PmtInf/Dbtr/PstlAdr/Ctry	REQUIRED	String(2)	Debtor country code (ISO 3166-1 alpha-2)
Nordea: \ PaymentAccount.NordeaOrgID \ Fallback: \ PaymentAccount.PayoutOrgID	PmtInf/Dbtr/Id/OrgId/Othr/Id	REQUIRED	String(35)	Debtor organization number
Literal: 'BANK'	PmtInf/Dbtr/Id/OrgId/Othr/SchmeNm/Cd	REQUIRED	String(4)	Organization ID scheme code
REPLACE(PaymentAccount.IBAN, ' ', '')	PmtInf/DbtrAcct/Id/IBAN	CONDITIONAL	String(34)	REQUIRED if using IBAN \ Mutually exclusive with Othr/Id
Swedbank: \ REPLACE(PaymentAccount.OutBankgiroNumber, '-', '') \ Nordea/Others: \ REPLACE(PaymentAccount.OutPlusgiroNumber, '-', '')	PmtInf/DbtrAcct/Id/Othr/Id	CONDITIONAL	String(34)	REQUIRED if not using IBAN \ Account number (cleaned)
'BBAN' (if not BG)	PmtInf/DbtrAcct/Id/Othr/SchmeNm/Cd	CONDITIONAL	String(4)	When using Othr/Id with BBAN format
'BGNR' (if Bankgiro)	PmtInf/DbtrAcct/Id/Othr/SchmeNm/Prtry	CONDITIONAL	String(35)	When using Bankgiro as debtor account
Currency.ExternalID \ Default: 'SEK'	PmtInf/DbtrAcct/Ccy	REQUIRED	String(3)	Debtor account currency (ISO 4217)
PaymentAccount.BIC	PmtInf/DbtrAgt/FinInstnId/BIC	REQUIRED	String(11)	Bank Identifier Code (SWIFT)
Literal: 'SE'	PmtInf/DbtrAgt/FinInstnId/PstlAdr/Ctry	REQUIRED	String(2)	Bank country code

...

3. CREDIT TRANSFER TRANSACTION (CdtTrfTxInf) - Per Payment

3.1 Payment Identification & Amount

ProBill Source	ISO20022 XML Path	Required	Data Type	Notes
LedgerPayout.ID	CdtTrfTxInf/PmtId/EndToEndId	REQUIRED	String(35)	Unique transaction identifier for tracking
Currency.ExternalID	CdtTrfTxInf/Amt/InstdAmt/@Ccy	REQUIRED	String(3)	Currency attribute (e.g., "SEK", "EUR")
ISNULL(LedgerPayout.CurrencyAmount, LedgerPayout.Amount)	CdtTrfTxInf/Amt/InstdAmt	REQUIRED	Decimal(18,2)	Instructed amount (use CurrencyAmount if foreign currency)

3.2 Creditor Agent (Recipient Bank)

ProBill Source	ISO20022 XML Path	Required	Data Type	Notes
Based on PayoutTypeID: \ • 'SESBA' if PG/BG/Bank with clearing	CdtTrfTxInf/CdtrAgt/FinInstnId/ClrSysMmbId/ClrSysId/Cd	CONDITIONAL	String(5)	Swedish Banking Association clearing system
Based on PayoutTypeID: \ • '9900' = Bankgiro (4) \ • '9960' = Plusgiro (3) \ • 4-digit = Bank clearing (1) \ • NULL = Money order (2)	CdtTrfTxInf/CdtrAgt/FinInstnId/ClrSysMmbId/MmbId	CONDITIONAL	String(35)	Clearing member ID \ Extracted via FnPrGetClearingsNrFromAccountNr()

3.3 Creditor (Recipient)

ProBill Source	ISO20022 XML Path	Required	Data Type	Notes
{{COALESCE( \ CustomerContactInformation.Name, \ Customer.DispName1 \ )}}	CdtTrfTxInf/Cdtr/Nm	REQUIRED	String(140)	Creditor/recipient name
{{ISNULL( \ CustomerContactInformation.Address, \ Customer.DispAddress \ )}}	CdtTrfTxInf/Cdtr/PstlAdr/StrtNm	CONDITIONAL	String(70)	REQUIRED for money orders (TypeID=2 only)
{{REPLACE( \ ISNULL( \ CustomerContactInformation.Zipcode, \ Customer.Zipcode \ ), ' ', '' \ )}}	CdtTrfTxInf/Cdtr/PstlAdr/PstCd	CONDITIONAL	String(16)	REQUIRED for money orders (TypeID=2 only) \ Spaces removed
{{ISNULL( \ CustomerContactInformation.City, \ Customer.City \ )}}	CdtTrfTxInf/Cdtr/PstlAdr/TwnNm	CONDITIONAL	String(35)	REQUIRED for money orders (TypeID=2 only)
{{COALESCE( \ Country.IsoCode, \ 'SE' \ )}}	CdtTrfTxInf/Cdtr/PstlAdr/Ctry	REQUIRED	String(2)	Creditor country code

3.4 Creditor Account (Recipient Account)

ProBill Source	ISO20022 XML Path	Required	Data Type	Notes
Money order (TypeID=2): \ Literal: 'NOTPROVIDED' \ \ Others: \ {{FnPrCleanPayoutAccountNumber( \ COALESCE( \ BillLocation.PayoutAccount, \ Customer.PayoutAccount, \ LedgerPayout.AccountNumber \ ) \ )}}	CdtTrfTxInf/CdtrAcct/Id/Othr/Id	REQUIRED	String(34)	Recipient account number \ Cleaned of dashes, spaces, special chars \ Money orders use literal 'NOTPROVIDED'
'BBAN' if Bank (1) or PG (3)	CdtTrfTxInf/CdtrAcct/Id/Othr/SchmeNm/Cd	CONDITIONAL	String(4)	Account scheme code for BBAN format
'BGNR' if Bankgiro (4)	CdtTrfTxInf/CdtrAcct/Id/Othr/SchmeNm/Prtry	CONDITIONAL	String(35)	Proprietary scheme for Bankgiro

3.5 Remittance Information (Payment Reference)

Structured Remittance (for Plusgiro/Bankgiro)

ProBill Source	ISO20022 XML Path	Required	Data Type	Notes
Swedbank: \ 'CINV' (if invoice exists) \ \ Nordea: \ 'SCOR' (if invoice exists)	Swedbank: \ CdtTrfTxInf/RmtInf/Strd/RfrdDocInf/Tp/CdOrPrtry/Cd \ \ Nordea: \ CdtTrfTxInf/RmtInf/Strd/CdtrRefInf/Tp/CdOrPrtry/Cd	OPTIONAL	String(4)	Document type code (if invoice reference provided)
{{COALESCE( \ CAST(Invoice.InvoiceNumber AS VARCHAR(100)), \ CAST(Invoice2.InvoiceNumber AS VARCHAR(100)), \ CAST(Payment.ReferenceID AS VARCHAR(100)) \ )}}	Swedbank: \ CdtTrfTxInf/RmtInf/Strd/RfrdDocInf/Nb \ \ Nordea: \ CdtTrfTxInf/RmtInf/Strd/CdtrRefInf/Ref	OPTIONAL	String(25/35)	Invoice/reference number \ Swedbank: max 25 chars \ Nordea: max 35 chars
Currency.ExternalID	CdtTrfTxInf/RmtInf/Strd/RfrdDocAmt/RmtdAmt/@Ccy	OPTIONAL	String(3)	Currency attribute for remitted amount
{{ISNULL( \ LedgerPayout.CurrencyAmount, \ LedgerPayout.Amount \ )}}	CdtTrfTxInf/RmtInf/Strd/RfrdDocAmt/RmtdAmt	OPTIONAL	Decimal(18,2)	Remitted document amount

Unstructured Remittance (for Bank accounts)

ProBill Source	ISO20022 XML Path	Required	Data Type	Notes
{{COALESCE( \ CAST(Invoice.InvoiceNumber AS VARCHAR(100)), \ CAST(Invoice2.InvoiceNumber AS VARCHAR(100)), \ CAST(Payment.ReferenceID AS VARCHAR(100)) \ )}}	CdtTrfTxInf/RmtInf/Ustrd	OPTIONAL	String(140)	Unstructured remittance information \ Shown only for bank account transfers

...

4. PayoutTypeID Logic & Account Format Rules

Payment Type Mapping

Account Number Cleaning Function

...

Document Version: 1.0
Last Updated: 2026-01-30
Based on: ProBillDB version 2.0.4751.0+

------------------------------------------------------------------------------------------------------------------------

Incoming Payments Mapping

ProBill handles AutoGiro, TotalIN, BgMax, and Camt.054 files for incoming payments.

Autogiro (if BIS will have an AG flow):

Flow description: Flöde autogiro i ProBill.xlsx
Old file layout according to: https://www.bankgirot.se/globalassets/dokument/tekniska-manualer/autogiro_tekniskmanual_sv.pdf

Requirements Specification – CAMT.054 Payments in ProBill

Date: 2026-03-04  |  Scope: Incoming payments and CAMT.054 outgoing payments. Pain.002 handling is covered by this specification above in this page.

1. Purpose and Scope

This requirements specification describes how ProBill interprets and stores payments from CAMT.054 files (ISO 20022 standard, message type BkToCstmrDbtCdtNtfctn, version camt.054.001.02).

Included:

• Identification of incoming and outgoing payment files
• Which XML tags are read
• Logic for calculating key variables (incoming payments)
• Mapping to dbo.Payment (incoming payments)
• Mapping to dbo.LedgerPayoutResult (outgoing payments)
• Error handling and status assignment (incoming payments)

2. Identification of File Type

A file is identified as CAMT.054 if the XML content contains the element name BkToCstmrDbtCdtNtfctn.

XML namespace: urn:iso:std:iso:20022:tech:xsd:camt.054.001.02

The file type is then determined by GrpHdr/AddtlInf:

3. XML Structure and Tags Read

The CAMT.054 file has a hierarchical structure with three levels that are read:

Document/BkToCstmrDbtCdtNtfctn
├── GrpHdr                          ← Message header (one per file)
└── Ntfctn                          ← Notification / account (one or more per file)
    ├── Id
    ├── CreDtTm
    ├── Acct                        ← Receiver account
    └── Ntry                        ← Transaction / entry (one or more per Ntfctn)
        ├── BookgDt/Dt
        ├── ValDt/Dt
        └── NtryDtls/TxDtls         ← Transaction details
            ├── Refs
            ├── AmtDtls
            ├── RltdPties           ← Involved parties
            ├── Purp
            ├── RltdDts
            └── RmtInf              ← Remittance information
                ├── Ustrd
                └── Strd            ← Structured remittance (one or more)

3.1 Message Header – GrpHdr

Read once per file from /Document/BkToCstmrDbtCdtNtfctn.

3.2 Account Information – Ntfctn

Read per Ntfctn node. Represents the receiving account (seller's account).

Note: A CAMT.054 file may contain multiple Ntfctn nodes. Each Ntfctn has a unique Id used to ensure each transaction is linked to the correct account.

3.3 Transaction Details – Ntry / TxDtls / Strd

Read per transaction. An Ntfctn can have multiple Ntry nodes, and each Ntry can have multiple TxDtls and/or Strd nodes. Transactions without a Strd element are still included (e.g. Swish payments).

4. Logic for Key Variables

4.1 Swish Identification (IsSwish)

A payment is classified as Swish (IsSwish = 1) if both of the following conditions are met:

Condition 1 – Prerequisite: TxDtls/Refs/EndToEndId is NOT NULL

Condition 2 – At least one of:

If EndToEndId is NULL, IsSwish = 0 is always returned.

4.2 ReferenceID

4.3 Amount

4.4 EntryDate

EntryDate = Ntfctn/Ntry/BookgDt/Dt (NULL if empty)

4.5 PaymentDate

5. Incoming Payments – Mapping to dbo.Payment

6. Incoming Payments – Error Handling and Status Assignment

6.1 ErrorID – Error Code

6.2 StatusID – Status

6.3 Handled – Direct Flagging

Records with an identified error are marked as handled immediately upon import (Handled = current timestamp). Records are flagged immediately if: ReferenceID is missing/non-numeric, Amount = 0, EntryDate is missing, or PaymentDate is missing. All other records are left unflagged (Handled = NULL).

7. Outgoing Payments – Mapping to dbo.LedgerPayoutResult

7.1 Identification

A record is treated as an outgoing payment if GrpHdr/AddtlInf contains the string DEBT.

7.2 Link to LedgerPayout

The outgoing payment is linked via TxDtls/Refs/EndToEndId cast as integer → matched against LedgerPayout.ID. CustomerID is retrieved from the matching record.

7.3 Mapping

7.4 Post-processing

After INSERT, each outgoing payment record is marked as handled (Handled = current timestamp). If outgoing payment records were inserted, a subsequent process for result handling is triggered.

...

Based on existing implementation in ProBill version: 2.0.4833.0. XML standard: ISO 20022 camt.054.001.02.