Reconciliation report

Banking Circle offers three types of reconciliation reports, each designed for different reconciliation needs:

  1. Standard Reconciliation Report (GET /api/v1/reports/reconciliation-report)

  2. Paginated Reconciliation Report (GET /api/v1/reports/reconciliation-paged-report)

    • Single-day reconciliation for large volumes (>50,000 payments)
    • Customizable page sizes for efficient processing
    • No date range support
  3. Intraday Reconciliation Report (GET /api/v1/reports/reconciliation-intraday-report)

    • Same-day transaction monitoring with time-range filtering
    • Tracks transactions based on creation time
    • Note: Payments after 19:00 CET will appear in the next business day's report

All reports include payments with status processed and pendingProcessing, and are both available in JSON and CSV format. The generated report contains the following fields.

Report Fields

Mandatory Fields

The fields listed below are always included in the report by default.

Note: Field names use camelCase in JSON format (e.g. pIdChannelUser or pTxnDate), while CSV format uses capitals and underscores (e.g. P_ID_CHANNELUSER or P_TXNDATE).

Field NameField TypeExampleDescription
pIdChannelUserVarchar[email protected]User ID of the requesting client
pTxnDateDate (YYYY-MM-DD; MM/dd/yyyy HH:mm:ss.fff)2021-10-27T00:00:00.000+00:00Internal date that indicates when payment was instructed in BC Connect. It does not match the processing date.
reportDateDate (DDMMYYYY)29102021Date of when the report is generated
customerIdNumber15106Customer ID of the account
accountVarcharDKXXXX0000000XXXXXIBAN of the account
accountCurrencyText (3)EURISO currency of your account
debitAmountNumber, 2 decimals22.26The amount debited, it is only populated if DBIT. In case of reversal of a debit, the amount will be given as a negative equivalent of the original amount debited
creditAmountNumber, 2 decimals10.89The amount credited, it is only populated if CRDT. In case of reversal of a credit, the amount will be given as a negative equivalent of the original amount credited
valueDateDate (YYYY-MM-DD;DD/MM/YYYY)27/10/2021Value date for posting on the account
instructedAmountNumber22.26Only for DBIT. Equivalent in original currency to the amount transferred after currency exchange. The instructed amount based on the choice of "payment currency" as provided in the payment instruction
instructedAmountCurrencyText (3)EURISO currency of instruction. Contains the currency of the instructed amount as provided in the payment instruction
transactionAmountNumber18.78DBIT: actual amount transferred to beneficiary.

CRDT: actual amount received for credit to the beneficiary account
transactionAmountCurrencyText (3)GBPISO currency of transaction amount
exchangeRateNumber0.84367Currency exchange applied in the transaction, between the instructed amount and the transaction amount.
debtorBankCodeVarcharSXPYDKKKXXXBank Code of the debtor, only populated for CRDT
debtorAccountVarcharDKXXXX0000000XXXXXFor CRDT: Account of debtor.

For DBIT: Blank

For DBIT using VIBAN: VIBAN used for the transaction (DK representation)
debtorLine1VarcharDebtor NameFor CRDT: Line 1 details for debtor

For DBIT: Blank

For DBIT using VIBAN: Name associated with Virtual account
debtorLine2VarcharDebtor Address line 1For CRDT: Line 2 details for debtor

For DBIT: Blank
debtorLine3VarcharDebtor Address line 2For CRDT: Line 3 details for debtor

For DBIT: Blank
debtorLine4VarcharDebtor Address line 3For CRDT: Line 4 details for debtor

For DBIT: Blank
beneficiaryBankCodeVarcharSXPYDKKKXXXBank code of creditor, only populated for DBIT
beneficiaryAccountVarcharDKXXXX0000000XXXXXFor DBIT: Account of creditor

For CRDT using VIBAN: DK IBAN representation of VIBAN used in the transaction.

For CRDT: Blank
beneficiaryLine1VarcharCreditor NameFor DBIT: Line 1 details for Beneficiary.

For CRDT using VIBAN: Name associated with virtual account.

For CRDT: Blank
beneficiaryLine2VarcharCreditor Address Line 1For DBIT: Line 2 details for Beneficiary

For CRDT: Blank
beneficiaryLine3VarcharCreditor Address Line 2For DBIT: Line 3 details for Beneficiary

For CRDT: Blank
beneficiaryLine4VarcharCreditor Address Line 3For DBIT: Line 4 details for Beneficiary

For CRDT: Blank
paymentReferenceNumberVarchar010F10xxxx001007BC Connect reference number, unique identifier for processed transactions
fileReferenceNumber36 CHAR a-Za-Z0-9/-?:.+923578e7-7a58-4982-93f1-5862e687611dBulk id of instructed payment file, only populated for bulk payments
userReferenceNumbera-Za-Z0-9/-?:.+Debtor referenceProvides the reference number of each payment record as stated in payment instruction by the debtor (DebtorReference). In case of internal transfers between BC Connect accounts, this field would be blank.
paymentDetails1VarcharEnd to end id for beneficiaryLine 1 of payment details ( Remitter information line 1).Reference is propagated to beneficiary.
paymentDetails2VarcharInfo for beneficiary 2Line 2 of payment details
paymentDetails3VarcharInfo for beneficiary 3Line 3 of payment details
paymentDetails4VarcharInfo for beneficiary 4Line 4 of payment details
creditDebitIndicatorDBIT/CRDTDBITCRDT for credit, DBIT for debit
bankTrnsCodeDomainVarcharPMNTBank transaction code for payment type identification. PMNT= Payment transfer FORX= foreign exchange ACMT=Account management: fees, interest, teller bookings
bankTrnsCodeFamilyVarcharICDTBank transaction sub-code for payment type identification.

IDCT: Issued payment, sold leg FX or fee

RCDT: Incoming payment, bought FX leg, reversal of payment fee

Additional Optional Fields

These fields are only included when specifically requested via the PropertiesIncluded parameter, or excluded via the PropertiesExcluded parameter:

Field NameField TypeExampleDescription
bankTrnsCodeSubFamilyVarcharDMCTDMCT: Domestic Credit Transfer

XBCT: Cross Border Credit Transfer

RRTN: Reversal due to Payment Return
paymentId36 CHAR, Varchar4a1e5714-7ac3-9383-08a7-ffbadaa2f4bbUnique payment reference within BC Connect that can be used to match the transaction instructed via API with the booking in the reconciliation report
lastChangedTimestampYYYY-MM-DDTHH:MM:SS.00000000+00:002019-11-08T11:40:25.00000000+00:00Indicates the time stamp of when a transaction was last changed in the processing system.
createdAtYYYY-MM-DDTHH:MM:SS.00000000+00:002019-11-08T11:40:25.00000000+00:00Indicates the time stamp of when a transaction is created in the processing system.
additionalRemittanceInformation1Varchar/RETN/Additional remittance information. In case of incoming return, it may contain a return indicator.
additionalRemittanceInformation2Varchar/AC04/Closed Account NumberAdditional remittance information. In case of incoming return, it may contain a return reason code.
additionalRemittanceInformation3Varchar/MREF/010F10xxxx012345Additional remittance information. In case of incoming return, it may contain the original payment reference.
additionalRemittanceInformation4Varchar//informationAdditional remittance information
additionalRemittanceInformation5Varchar//informationAdditional remittance information
debtorAgentBankCodeVarcharBICCIEXXBank Identifier Code (BIC) of the financial institution, where the debtor account resides
ultimateDebtorLine1VarcharNameFor debits: Name of your customer

For credits: Blank
ultimateDebtorLine2VarcharAddress line 1For debits: Your customer's address line 1

For credits: Blank
ultimateDebtorLine3VarcharAddress line 2For debits: Your customer's address line 2

For credits: Blank
ultimateDebtorLine4VarcharAddress line 3For debits: Your customer's address line 3

For credits: Blank
ultimateDebtorAccountVarcharIE29AIBK93115212345678For debits: The debtor account number (i.e., an account number issued by you).

For credits: Blank
ultimateBeneficiaryAccountVarcharIE29AIBK93115212345678For debits: Blank

For credits: The creditor account number (i.e., an account number issued by you)
statusReasonCodeVarcharRR01Reason code in case of payment getting reversed
statusReasonDescriptionVarcharInsufficient sender account or unique identificationReason description for payment reversal
instructedChargeBearerVarcharOURCharge bearer instructed by client
chargeBearerVarcharSHAThe actual charge bearer used for payment processing
paymentRailVarcharSEPA (SCT)The payment rail used for executing the payment. You can read more about it here.
returnText (4)TruePossible values: true or null. The value will be true if the payment is an incoming return payment, otherwise the value will be null. This does not apply to incoming SEPA Direct Debits, where the value will always be null.
directDebitMandateIdVarchar41b9a62baa5a2320247841ef865c1001directDebitMandateId is a unique identifier assigned to a mandate issued by creditors under the SEPA Direct Debit scheme, such as a customer number
processedTimestampYYYY-MM-DDTHH:MM:SS.00000000+00:002024-05-08T11:40:25.00000000+00:00Indicates the timestamp of when the payment is processed.
latestStatusChangedTimestampYYYY-MM-DDTHH:MM:SS.00000000+00:002024-05-08T11:40:25.00000000+00:00Indicates the timestamp of latest status change on the payment.
clientOrderId35 CHAR, VarcharYourUniqueIdYour reference for your FX Trade executed via FX API.

Note: Only displayed for FX trades.