> For the complete documentation index, see [llms.txt](https://docs.rainbird.ai/rainbird/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rainbird.ai/rainbird/getting-started/use-cases/trade-finance-document-compliance-check.md).

# Trade finance document compliance check

**Decision:** Banking — Trade finance.   **Pattern:** Document check

**Use case:** This solution checks documents presented under a letter of credit against UCP 600 and ISBP rules, flagging discrepancies and producing a compliant refusal notice — so document examiners spend their time on genuine judgement calls, not on comparing paperwork line by line. See the [UCP 600 Trade Finance Documentary Compliance accelerator](https://rainbird.ai/accelerators/trade-finance-documentary-compliance) for a ready-built starting point.

**End-user:** Trade finance document examiner

**The decision:** Whether the documents presented under a letter of credit comply with its terms and with UCP 600 / ISBP rules — and where they don't, which discrepancies to cite in a compliant refusal notice.

**The knowledge graph:** Encodes UCP 600 and ISBP rules alongside the bank's own documentary examination practice, so every presentation is checked against the same standard, whichever examiner or shift picks it up.

**Integration:** Documents are processed upstream by your own OCR/IDP pipeline. The extracted data — not the raw documents — is passed into Rainbird for checking. Rainbird returns a pass or fail against each rule, with a discrepancy list ready to go into a refusal notice where needed. Extraction errors route to a human for correction before re-checking.

**Evidence:** Every check returns the specific rule it was tested against and why it passed or failed, so an examiner — or an auditor reviewing the decision later — can see the reasoning behind every discrepancy raised.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rainbird.ai/rainbird/getting-started/use-cases/trade-finance-document-compliance-check.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.