# Export Reporting

## Export end-of-day pocket balances to a camt.053 brokerage statement

### Business Goal

Export end-of-day balances to make a daily update of treasury, accounting or reporting systems (datalake...).

Since Jiko automatically sweeps funds between the bank account and the associated brokerage account in a pocket, the bank account's end-of-day balance is always 0. The balance then needs to be retrieved from the brokerage account, using Jiko's Brokerage statement. This brokerage statement:

- is generated in format ISO 20022 camt.053,
- shows the pocket's end-of-day value as the statement's closing balance,
- also includes "transaction" records explaining the change between the opening and closing balance of the pocket, with:
  - Additions: new funds deposited into the brokerage account.
  - Subtractions: funds withdrawn from the brokerage account.
  - Gains/Losses from T-bills held in the account.
  - Fees charged and deducted from the brokerage account.


The end-of-day balance in the brokerage account corresponds to the value of held T-bills, using end-of-day market prices. Another export option is accordingly to export T-bill buy & sale trades, to import trades in a system that will calculate the corresponding position, using GET [`/api/v1/trades/`](/products/customer-api/reference/trades/list_trades_api_v1_trades__get).

### Business Workflow Example

Customer systems:

1. Get from Jiko the id of the pockets for which an end-of-day balance is needed.
2. Send to Jiko an API report request for a brokerage statement report.
3. Monitor the report generation status.
4. When the report is available, retrieve the report file from Jiko.
5. Integrate it into their databases.
6. Update cash and accounting positions.
7. Trigger downstream accounting or reporting workflows, such as closing the financial day, or preparing reports for accounting and auditor teams.


### Relevant API Endpoints

| Step | Purpose | Jiko API Endpoints |
|  --- | --- | --- |
| 1 | Launch Jiko's reporting API for a given reporting date and set of pockets (if no pocket is specified in filtering parameters then the statement includes all pockets): • passing a unique report request `id` for each report request • and using `type` = `BROKERAGE_STATEMENT_REPORT` | POST [`/api/v1/report-requests/`](/products/customer-api/reference/reports/create_customer_report_request_api_v1_report_requests__post) |
| 2 | Get the report request generation `status` for the report id passed in the previous step. The report is ready when `status` = `AVAILABLE`. Retrieve the corresponding `reports.id`. | GET [`/api/v1/report-requests/{report_request_id}/`](/products/customer-api/reference/reports/get_customer_report_request_api_v1_report_requests__report_request_id___get) |
| 3 | When the status of the launched report instance is `AVAILABLE`, get the report content through the `download_url`. | POST [`/api/v1/report/{report_id}/download/`](/products/customer-api/reference/reports/download_customer_report_api_v1_report__report_id__download__post) |


## Export end-of-day bank transactions to a camt.053 bank statement

### Business Goal

Receive an end-of-day bank statement in standard format that includes all bank transactions for a given day. Bank transactions include new fund deposits and withdrawals, incoming and outgoing third-party payments (when applicable), fees... Including the sweep transactions between the pocket's bank account and its linked brokerage account, resulting in opening and closing balances with a zero value.

### Business Workflow Example

Customer systems:

1. Identify the pocket(s) to query (store their Ids in the customer system or dynamically retrieve them from Jiko).
2. Send to Jiko an API report request for a bank statement report.
3. Monitor the report generation status.
4. When the report is available, retrieve the report file from Jiko.
5. Integrate it into their databases.
6. Trigger downstream reconciliation or reporting workflows, such as matching bank transactions to cash forecasts, closing the financial day, or preparing reports for auditors or accounting teams.


### Relevant API Endpoints

Same as in section [Export end-of-day balances](#export-end-of-day-bank-transactions-to-a-camt053-bank-statement) but using report type `BANK_STATEMENT_REPORT`.

## Export the end-of-day T-bill trade history (csv)

### Business Goal

Export T-bill trade data within a date range to a CSV format, for import into a treasury management system, to revalue T-bill holdings, monitor and manage positions, and generate accurate accounting entries. To support financial reporting across treasury and accounting workflows.

### Business Workflow Example

Customer systems:

1. Schedule the export, usually on an end-of-day basis.
2. Send to Jiko an API export request for a trade export.
3. Monitor the export generation status.
4. When the export is available, retrieve the export file from Jiko.
5. Integrate it into their databases.
6. Trigger downstream liquidity reporting and accounting processes.


### Relevant API Endpoints

Same as in section [Export end-of-day balances](#export-end-of-day-bank-transactions-to-a-camt053-bank-statement) but using report type `TRADE_REPORT`.

## Export end-of-day Security prices (csv)

### Business Goal

Provide treasury management systems with up-to-date T-bill security prices, enabling accurate revaluation of holdings, position monitoring, and the generation of accounting entries.

### Business Workflow Example

Customer systems:

1. Schedule the export, usually on an end-of-day basis.
2. Send to Jiko an export request for a security price export.
3. Monitor the export generation status.
4. When the export is available, retrieve the export file from Jiko.
5. Integrate it into their databases.
6. Trigger downstream liquidity reporting and accounting processes.


### Relevant API Endpoints

Same as in section [Export end-of-day balances](#export-end-of-day-bank-transactions-to-a-camt053-bank-statement) but using report type `SECURITY_PRICE_REPORT`.