--- title: Daily Wire payments slug: ops-and-admin/reports/accounts-and-payments/daily-wire-payments description: The daily wire payment file drop by partner report. Use COS for both domestic and international wire transfers through the Fedwire system. docTags: createdAt: 2024-08-12T13:14:46.589Z --- ## Report description Using the Cross River Operating System (COS) [wires APIs](docId\:Mm_yqgvcWNtsGDLnNX-og), you can both originate and receive wire transfers through the Fedwire system. The level of information required varies depending on whether the transaction is purely domestic or international. Domestic wire payments require less information. The Daily Wire Payment File Drop By Partner report lets you see all wire payments for a single given Cross River Operating System (COS) partner. You can use this report to reconcile between what you requested from COS and what COS actually processed. [Learn more about wires](docId\:hFNmQa22W2BNqAJijpAVT) ## Report in detail The table below shows the different columns included in the report and explanations of the information each represents. | Column | Description | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Id | The unique payment ID in the Cross River system assigned when the payment is sent | | AccountNumber | Partner account or subaccount number used in the transaction | | CoreTransactionId | The payment-related core transaction ID | | ReferenceId | Unique Cross River reference ID for the payment | | ClientBatchId | Identifier used to group related client payments in batch submissions, if you originate the client batch. Otherwise blank. | | ClientBatchSequence | Sequence number of the payment in the batch, if you originate the client batch. Otherwise blank. | | FedBatchId | Unique identifier in GUID format for the Federal Reserve batch the payment went out on (or came in on for inbound payments) | | FedBatchSequence | Sequence number of payment in the Federal Reserve batch | | Direction | The direction of this transfer:
* **Inbound**: a payment received from another bank * **Outbound**: a payment being sent to another bank | | Source | How the payment originated:
* Api * Phone * Fax * Email * File * Partner Portal (when a partner user enters a payment request in COS Explorer) * Ops Portal (when Cross River Ops enters a payment request in COS Explorer) * MQ (for inbound transfers) | | Status | The status of the payment at the time the report was generated:
* **Created**: the payment has been received but hasn’t been processed yet. This status will only appear briefly. * **Pending**: the payment is waiting to be batched and sent to the through the Fedwire system. * **Hold**: the payment is currently being held and is being reviewed by Cross River's Operations team. * **Batched**: the payment has been batched, and CRB is carrying out a final review before the payment is sent in a batch file through the Fedwire system. * **Processing**: For inbound payments, we are attempting to post the payment to the receiving account. For outbound payments, the payment has been sent to the FRB, but has not been posted yet. An outbound standard payment may remain in this status for a day or more. * **Completed**: the payment has been posted and accepted by the FRB (in the case of outbound payments). This is a final status. * **Canceled**: Indicates that an outbound payment has been canceled at the Partner’s request. A payment can only be canceled while either pending or on hold. This is a final status. * **Rejected**: Cross River's Operations team was unable to process the payment and has rejected it. For inbound payments, the payment request is returned to the originating bank. This is a final status. | | PaymentType | A description of the payment type:
* **Transfer**: New payment originating from either Cross River or another bank. Most payments are of this type. * **Drawdown**: Request for a drawdown * **DrawdownResponse**: Payment is a response to a drawdown request * **ServiceMessage**: An informational message transferred between banks and not an actual payment. This is used when there’s a relationship to a previously processed wire. * **Reversal**: Reversal of a previously sent wire payment | | Posting | Status of the related core transaction for the payment. Values include:
\* **Pending**: Transaction is pending posting
\* **Posted**: Transaction has been posted to the account
\* **Failed**: Transaction posting failed
\* **Canceled**: Transaction was canceled | | Purpose | Reason for the wire transfer. For internal Cross River use only. The data is not included with the outgoing FedWire message. | | Amount | The transaction amount in integral cents. For example, $1.00 appears as 100. | | Currency | The currency the payment is being or was made in. | | Imad/Omad | The mandatory unique number given to each Fedwire payment when using the Federal Reserve Bank Service. You can use this number to track your wire transfer.
* **IMAD** indicates an inbound transfer * **OMAD** indicates an outbound transfer | | ReceiptDate | Date payment was received | | ReceiptTime | Time of day payment was received | | BusinessFunctionCode | Always CTR, for a customer transfer | | TypeCode | Type of transfer taking place. See [Request and response codes: Wires](docId\:dNVmZA82yPq34WBpmrPyj) for information about type codes. | | SenderRoutingNumber | Sender’s ABA number | | SenderName | Name of the party sending the transfer | | SenderReference | Sender's assigned reference number | | ReceiverRoutingNumber | Receiver’s ABA number | | ReceiverName | Name of the party receiving the transfer | | OriginatorToBeneficiary1 | Optional free-text information included by the originator to the beneficiary. For example:
`"originatorToBeneficiary1": "THANK",`
`"originatorToBeneficiary2": "YOU",`
`"originatorToBeneficiary3": "PAID",`
`"orginatorToBeneficiary4": "IN FULL",` | | OriginatorToBeneficiary2 | | | OriginatorToBeneficiary3 | | | OriginatorToBeneficiary4 | | | OriginatingFiIdCode | The single-character code (**F**inancial **I**nstitution **ID** **code**) indicating the originating institution ID type as follows:
* **B** - SWIFT Bank Identifier Code (BIC) * **C** - CHIPS Participant * **D** - Demand Deposit Account (DDA) Number * **F** - Fed Routing Number * **T** - SWIFT BIC or Bank Entity Identifier (BEI) and account number * **U** - CHIPS Identifier | | OriginatingFiIdentifier | The originating institution’s identifier as per the selected FiIdCode | | OriginatingFiName | Name of the originating party’s financial institution | | OriginatingFiAddress1 | Address details of the originating party’s financial institution | | OriginatingFiAddress2 | | | OriginatingFiAddress3 | | | OriginatorIdCode | The single-character code to indicate the originator type. The code selected determines which identifier information must be used:
* **B** - SWIFT Bank Identifier Code (BIC) * **C** - CHIPS Participant * **D** - Demand Deposit Account (DDA) Number * **F** - Fed Routing Number * **T** - SWIFT BIC or Bank Entity Identifier (BEI) and account number * **U** - CHIPS Identifier * **1** - Passport Number * **2** - Tax Identification Number * **3** - Driver’s License Number * **4** - Alien Registration Number * **5** - Corporate Identification * **9** - Other Identification | | OriginatorIdentifier | This is the originator’s ID informationas per the selected `FiIdCode` | | OriginatorName | Name of the party originating the transfer | | OriginatorAddress1 | Address details of the originating party | | OriginatorAddress2 | | | OriginatorAddress3 | | | IntermediaryFiIdCode | The single-character code to indicate the intermediary institution type. The code selected determines which identifier information must be used:
* **B** - SWIFT Bank Identifier Code (BIC) * **C** - CHIPS Participant * **D** - Demand Deposit Account (DDA) Number * **F** - Fed Routing Number * **T** - SWIFT BIC or Bank Entity Identifier (BEI) and account number * **U** - CHIPS Identifier | | IntermediaryFiIdentifier | The intermediary institution’s identifier as per the selected `FiIdCode` | | IntermediaryFiName | Name of the intermediary financial institution. This will be empty if an intermediary institution is not being used for this transaction. | | IntermediaryFiAddress1 | Address details of the intermediary financial institution | | IntermediaryFiAddress2 | | | IntermediaryFiAddress3 | | | BeneficiaryFiIdCode | The single-character code to indicate the beneficiary institution type. The code selected determines which identifier information must be used:
* **B** - SWIFT Bank Identifier Code (BIC) * **C** - CHIPS Participant * **D** - Demand Deposit Account (DDA) Number * **F** - Fed Routing Number * **T** - SWIFT BIC or Bank Entity Identifier (BEI) and account number * **U** - CHIPS Identifier | | BeneficiaryFiIdentifier | The beneficiary institution’s identifier as per the selected `FiIdCode` | | BeneficiaryFiName | Name of the beneficiary party’s financial institution. | | BeneficiaryFiAddress1 | Address details of the beneficiary’s financial institution. | | BeneficiaryFiAddress2 | | | BeneficiaryFiAddress3 | | | BeneficiaryIdCode | The single-character code to indicate the beneficiary type. The code selected determines which identifier information must be used:
* **B** - SWIFT Bank Identifier Code (BIC) * **C** - CHIPS Participant * **D** - Demand Deposit Account (DDA) Number * **F** - Fed Routing Number * **T** - SWIFT BIC or Bank Entity Identifier (BEI) and account number * **U **- CHIPS Identifier * **1** - Passport Number * **2 **- Tax Identification Number * **3 **- Driver’s License Number * **4** - Alien Registration Number * **5** - Corporate Identification * **9** - Other Identification | | BeneficiaryIdentifier | The beneficiary’s ID information as per the selected `FiIdCode` | | BeneficiaryName | Name of the beneficiary party. | | BeneficiaryAddress1 | Address details of the beneficiary party | | BeneficiaryAddress2 | | | BeneficiaryAddress3 | | | BeneficiaryReference | Optional information provided by transfer initiator | | ReleasedAt | The date and time the payment was **released** | | ProcessedAt | The date and time the payment was **processed** | | EffectiveDate | The actual date the transaction was **posted** | | CreatedAt | The date and time the payment was **initiated** | | CanceledAt | The date and time the payment was **canceled** | | RejectedAt | The date and time the payment was **rejected** | | CompletedAt | The date and time the payment was **completed** | | PostedAt | The date and time the payment was **posted** | | OriginalPaymentId | Payment ID of a previously sent wire that was reversed. Otherwise, the same as the `Id` column. | | ProductId | The product identifier for the account involved in the wire transfer | | PartnerId | Your unique identification number as a partner in the Cross River system | | LastModifiedAt | Internal Cross River value. Date and time the database entry was last modified. | | InsertedAt | Internal to Cross River | ## Sample report ::File{src="https://api.archbee.com/api/presign/4hvUOg5mU1sCngl0n0Has/FAyB-z_rXH1q4aK30WCec_yourcompanyname-daily-wire-payment-yyyy-mm-dd-hhmmss.csv" label="[YourCompanyName]_Daily_Wire_Payment_[YYYY]_[MM]_[DD]_[HHMMSS].csv"}