> For the complete documentation index, see [llms.txt](https://host2host.onibonje.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://host2host.onibonje.com/docs/27-treasury-interfaces.md).

# Treasury and FX Interfaces

## 1. Overview

Treasury use cases from RFP §4.1: **liquidity reporting** and **FX position** data exchange with corporate treasury systems. Phase 4+ capability.

**Modules:** `h2h-treasury-routes` (optional), `h2h-finacle-wrapper`, `h2h-transform-core`

***

## 2. Use Cases

| Use case                  | Direction | Format             |
| ------------------------- | --------- | ------------------ |
| Liquidity position report | Outbound  | CSV / ISO camt.052 |
| FX deal confirmation      | Inbound   | XML / JSON         |
| Cash concentration status | Outbound  | CSV                |
| Treasury payment (FX)     | Inbound   | ISO pain.001       |

***

## 3. Architecture

```mermaid
flowchart LR
  Treasury[Treasury System]
  H2H[h2h-treasury-routes]
  Finacle[Finacle Treasury module]
  File[File Management]

  Treasury <-->|SFTP API| H2H
  H2H <--> Finacle
  H2H --> File
```

Same platform patterns: canonical model extensions, config-driven transforms, signed delivery.

***

## 4. Canonical Extensions

Extend [canonical model](/docs/29-canonical-data-model.md) `extensions` or `modelVersion 1.1`:

| Type                | Fields                                             |
| ------------------- | -------------------------------------------------- |
| `FxDeal`            | dealId, buyCurrency, sellCurrency, rate, valueDate |
| `LiquidityPosition` | accountId, availableBalance, currency, asAt        |

***

## 5. Finacle Mapping

Treasury operations via `CoreBankingOperationProvider` / `FinacleOperationProvider` SPI — market-specific treasury web services.

***

## 6. Scheduling

EOD jobs generate liquidity reports; event `h2h.treasury.report.generated` for ERP subscription.

***

## 7. Related Documents

* [22 Use Cases](/docs/22-use-cases-and-solutions.md)
* [24 Transformation and Messaging](/docs/24-transformation-and-messaging.md)
* [10 Implementation Roadmap](/docs/10-implementation-roadmap.md) Phase 4+


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://host2host.onibonje.com/docs/27-treasury-interfaces.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.