> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/notification-routing.md).

# 通知路由

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-5d819fb673d1dc3b2990b49cf8edcd87f53ac8c0%2Feinvoice-notification-routing.png?alt=media" alt="通知路由"><figcaption><p>将验证结果映射到代理</p></figcaption></figure>

**通知路由**页面（**电子文档 → 操作**）用于将验证结果映射到**AI Workforce 代理**。每个阻止性结果只会触发一个代理：其代码前缀与结果匹配度最高的代理。没有匹配项时，将回退到默认供应商通知代理。

## 通知路由

选择由谁处理各类发票问题。未列出的情况将交由默认代理处理：

| 路由                | 涵盖的结果                           |
| ----------------- | ------------------------------- |
| **哥伦比亚业务规则**      | 哥伦比亚特定业务规则的验证结果。                |
| **德国业务规则**        | 德国特定业务规则的验证结果。                  |
| **IBAN / 银行账户检查** | 付款数据相关的验证结果（IBAN 校验和、长度、国家/地区）。 |
| **VAT ID 检查**     | VAT/税号格式相关的验证结果。                |
| **其他所有情况**        | 未匹配上述路由时使用的默认回退选项。              |

对于每条路由，请从下拉列表中选择处理代理。需要更精细的控制时，可使用 **高级（自定义代码规则）**，按完全匹配的结果代码进行路由。

## 可用代理

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-3c4712f21cee79b43db0ca82c884140da397e823%2Feinvoice-notification-agents.png?alt=media" alt="可用代理注册表"><figcaption><p>AI Workforce 代理的只读注册表</p></figcaption></figure>

**可用代理**部分是随部署提供的 AI Workforce 代理只读注册表，例如：

| 代理          | 用途                              |
| ----------- | ------------------------------- |
| **默认供应商通知** | 通用供应商通知电子邮件；没有更具体的代理匹配时使用的兜底选项。 |
| **银行机器人**   | 用于付款数据相关验证结果的专用模板（IBAN/BIC 更正）。 |
| **税务机器人**   | 用于 VAT/税号相关供应商通知。               |
| **合规机器人**   | 处理合规相关的验证结果。                    |

每个代理都会显示其 Celery 任务，以及默认处理的结果代码前缀。


---

# 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.docbits.com/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/notification-routing.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.
