--- title: Daily exceptions slug: ops-and-admin/reports/card-payments/daily-exceptions description: The daily exceptions report flags irregular, unprocessed, or mismatched transactions and is securely delivered via SFTP to your designated folder. docTags: createdAt: 2024-08-12T08:25:08.606Z --- ## Report description The daily exceptions report lists the transactions that contain irregularities. This report includes unprocessed, incomplete, interrupted, or suspicious transactions. It also contains transactions with unusual balances. In addition, this report could hold mismatches or conflicts between data in the Cross River and the card networks. These could be, for example, transaction status, amounts, and so forth. Unlike the daily settlement report, where you trigger each transaction, exceptions are triggered by another person, event or action, and are unexpected. Cross River generates a daily exception report every day that we settle transactions with merchant partners. You receive this report using the Secure File Transfer Protocol (SFTP). [SFTP](docId\:vS2CkU9_W5BQQlbjsBq25) lets you receive and send information securely. This report is generated automatically, and pushed to your assigned subfolder on the secure server, where you access it. :::hint{type="warning"} **IMPORTANT** SFTP must be set up *before* you create a report request with Cross River’s Data Team. This allows the reporting team to automate the delivery of Settlement and Reconciliation reports to the appropriate folders. ::: ## Report distribution Recipients include user-partners only. ## Report structure Detailed daily exception reports have 2 structures: *basic* and *expanded*. The basic report filename uses this convention: **PartnerName\_CRBPayments\_Exceptions\_Itemized\_YYYY\_MM\_DD** The expanded report filename uses this convention: **PartnerName\_CRB\_Settlement\_Exceptions\_Expanded\_YYYY-MM-DD** ### Basic report structure | No. | Field | Default | Description | | --- | ------------------------------ | ------- | ------------------------------------------------------------------------------- | | 1 | ExceptionID | ✓ | | | 2 | ExceptionCode | ✓ | | | 3 | OriginalTransactionRequestId | ✓ | ID of the automatically created transaction associated with this settlement day | | 4 | Network | ✓ | | | 5 | ResponseCode | ✓ | | | 6 | TransactionType | ✓ | - Pull - Push - Chargeback - Reversal - Adjustment | | 7 | ResponseDescription | ✓ | | | 8 | TransactionRequestedAt | ✓ | | | 9 | OriginalTransactionRequestedAt | ✓ | | | 10 | CreditCardId | ✓ | | | 11 | RetrievalReference | ✓ | | | 12 | TraceNumber | ✓ | | | 13 | Destination\* | ✓ | * For AFT: Settlement * For OCT: Network | | 14 | TransactionAmount | ✓ | | | 15 | TransactionIndicator | ✓ | | | 16 | OriginalCurrency | ✓ | | | 17 | InterchangeFee | ✓ | | | 18 | InterchangeFeeIndicator | ✓ | | | 19 | InterchangeCategoryDescriptor | ✓ | | | 20 | EstimatedNetworkFee | ✓ | | | 21 | IntegrityNetworkFee | ✓ | | | 22 | IntegrityNetworkFee | ✓ | | | 23 | SettlementDate | ✓ | | | 24 | CutoffDate | ✓ | | ### Expanded report structure | No. | Field | Default | Description | | --- | ------------------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | ExceptionID | ✓ | | | 2 | ExceptionCode | ✓ | | | 3 | OriginalTransactionRequestId | ✓ | ID of the automatically created transaction associated with this settlement day | | 4 | Network | ✓ | | | 5 | ResponseCode | ✓ | | | 6 | TransactionType | ✓ | - Pull - Push - Chargeback - Reversal - Adjustment | | 7 | ResponseDescription | ✓ | | | 8 | TransactionRequestedAt | ✓ | | | 9 | OriginalTransactionRequestedAt | ✓ | | | 10 | CreditCardId | ✓ | | | 11 | RetrievalReference | ✓ | | | 12 | TraceNumber | ✓ | | | 13 | Destination\* | ✓ | * For AFT: Settlement * For OCT: Network | | 14 | TransactionAmount | ✓ | Transaction Amount | | 15 | TransactionIndicator | ✓ | - **D** - Debit the merchant - **C** - Credit the merchant | | 16 | OriginalCurrency | ✓ | | | 17 | InterchangeFee | ✓ | | | 18 | InterchangeFeeIndicator | ✓ | | | 19 | InterchangeCategoryDescriptor | ✓ | | | 20 | EstimatedNetworkFee | ✓ | | | 21 | IntegrityNetworkFee | ✓ | | | 22 | IntegrityNetworkFee | ✓ | | | 23 | SettlementDate | ✓ | CRB Settlement Date | | 24 | CutoffDate | ✓ | | | 25 | CardholderFirstName | ✓ | Cardholder First Name | | 26 | CardholderLastName | ✓ | Cardholder Last Name | | 27 | IssuerCountryCode | ✓ | Card issuer country code | | 28 | SystemTraceAuditNumber | ✓ | A unique Cross River reference number created in card transactions | | 29 | RetrievalReference | ✓ | The transaction identifier vs. all parties, including the card networks. Using this number, the partner can directly reach out to the network to get more info about the transaction. | | 30 | StatementDescriptor | | An arbitrary string attached to the transaction, often useful for displaying to information users | | 31 | CardType | ✓ | Debit/Credit/Prepaid | | 32 | Credit Card Id | ✓ | Token for the signed-up card. The partner gets this Id upon first-time card sign-up, per each card holder. | | 33 | First6 | ✓ | First 6 digits of the payment card | | 34 | Last4 | ✓ | Last 4 digits of the payment card | ## Related topics - [Daily settlement (detailed)](docId\:ID2xJOHUQ_SaDaUgT9Xhv) - [Daily settlement (summary)](docId\:gX6X18R6oXhV8ckidsmLM) - [Daily chargeback report](docId\:GjHgMGK1dOOQdccLsZg-o) - [Send funds to payee (push) API](docId\:q59J0rxBvNfQ-y92-TASq) - [Request funds from payer (pull) API](docId\:KVpHbesGRkxsFI6YyS8zD)