One use case now. Many later. 先做一个场景，日后可扩展更多。
The payment bot handles one shape of work: a receipt matched to a Xero invoice. Your next needs do not fit that shape, so instead of building each one separately, the portal gains trackers that you configure. 现有付款机器人只处理一种工作：收据对应 Xero 发票。接下来的需求并不属于这种形式，因此不再逐个单独开发，而是在门户中加入可由您自行设定的追踪器。
From the moment a client posts the MetaQuotes statement in the group to the moment JY sends the payment proof, with a summary in Teams.从客户在群里发送 MetaQuotes 账单，到 JY 发出付款凭证，全程跟进，并在 Teams 发送汇总。
Several trackers, each with its own steps, rules and checks, set up in the portal.可建立多个追踪器，每个都有各自的步骤、规则和核对项目，在门户内设定。
Describe a new tracker in plain words. The AI drafts it and tests it on a past chat. A person publishes it.用一般文字描述新的追踪器，AI 起草设定并用过往群聊测试，最后由人员发布。
| Question问题 | Your answer您的回复 | What it means in the build对系统的影响 |
|---|---|---|
| Who may move an MQ invoice forward谁可推进 MQ 发票状态 | Only JY staff仅限 JY 员工 | Only JY staff can move an invoice to Quoted, Confirmed or Completed. Staff are known by phone number (AY Filing is JY staff), never guessed.只有 JY 员工能把发票推进到"已报价"、"已确认"或"已完成"。员工按电话号码识别（AY Filing 为 JY 员工），绝不猜测。 |
| When a person must act何时需要人工 | Only at key points仅在关键环节 | Clean steps move by themselves, marked "AI-read". A person signs off once per invoice, at Confirmed, and acts on anything a check flags.核对无误的步骤自动推进，并标记为"AI 读取"。每张发票在"已确认"时由人员确认一次；任何核对不通过的情况都需人员处理。 |
| Two MQ invoices open in one group同一群多张未完成 MQ 发票 | Possible有可能 | A message is matched by invoice number, by the message it replies to, or by an exact amount. If still unclear, it waits for a person.按发票号码、所回复的消息或准确金额对应。仍不清楚时，交由人员处理。 |
| The TXID交易哈希 (TXID) | A person checks it at first初期由人员核实 | The reviewer checks it on tronscan when signing off. An automatic on-chain check is part of this scope.审核人员确认时在 tronscan 上核实。链上自动核实也包含在本范围内。 |
| The payment-proof PDF付款凭证 PDF | Read it and check it读取并核对 | Its invoice number and amount are checked against the record, not just attached.核对其中的发票号码与金额，而不只是附件存档。 |
| Cases that wait too long等待过久的案件 | Not tracked for MQMQ 不需跟进 | No "stalled" alerts for MQ invoices.MQ 发票不设"停滞"警报。 |
| One group, several trackers一个群对应多个追踪器 | Yes可以 | A client group can feed MQ Invoices and Payments at the same time.一个客户群可同时用于 MQ 发票与付款审核。 |
| What reaches the AI哪些消息交给 AI | Either, per tracker每个追踪器可选 | By default only messages that look relevant (words, wallet and TXID patterns, files). "Every message" is available but needs your written approval first.默认只把看似相关的消息（关键词、钱包与 TXID 格式、文件）交给 AI。"全部消息"选项可用，但需贵司先书面同意。 |
| The existing payment bot现有付款机器人 | Move it into a tracker改为追踪器 | Payment review becomes the Payments tracker, listed under Trackers. Same cases, numbers, checks and permissions."付款审核"改为"付款"追踪器，列于侧栏"追踪器"下。案件、编号、核对项目与权限不变。 |
| Where the Xero invoices liveXero 发票放在哪里 | Their own page, in CRMCRM 下独立页面 | Invoices stays a page of its own and links both ways with the Payments tracker. Room is left for a second Xero organisation, which is not planned."发票"保留为独立页面，并与付款追踪器互相链接。系统预留第二个 Xero 组织的空间，但目前不在计划内。 |
| Telegram | Yes, after WhatsApp需要，在 WhatsApp 之后 | Telegram groups feed trackers the same way, through Telegram's official bot.Telegram 群以相同方式接入，使用 Telegram 官方机器人。 |
| Who builds new trackers谁可建立新追踪器 | Owners and admins所有者与管理员 | Tracker Setup and the AI tracker builder are for owners and admins only."追踪器设定"与 AI 起草功能仅限所有者与管理员使用。 |
The AI reads. Code checks. People decide. AI 读取，程序核对，人员决定。
Every tracker runs the same way. Only its steps, fields and checks differ, and those are set in the portal. 每个追踪器的运作方式相同，只是步骤、字段与核对项目不同，而这些都在门户中设定。
Which groups feed it, and what reaches the AI.接入哪些群，以及哪些消息交给 AI。
What to pick up, such as invoice number, rate, TXID, with a hint for where to find it.需要提取的内容，例如发票号码、汇率、TXID，并注明在哪里找到。
In plain words: "move here when JY staff post the calculation". Who may trigger each step, and which ones a person signs off.用一般文字描述，例如"JY 员工发出计算后进入此步骤"；设定谁可触发每个步骤，以及哪些步骤需人员确认。
Picked from a library, all run in code: sums, matching fields, lists, duplicates.从核对库中选择，全部由程序执行：金额计算、字段比对、名单、重复检查。
Which Teams channel gets the exception cards, and when the daily summary goes out.异常卡片发送到哪个 Teams 频道，以及每日汇总的发送时间。
Its sidebar entry, its table columns, and which roles may open it.侧栏名称、表格栏位，以及哪些角色可以查看。
One MQ invoice, start to finish. 一张 MQ 发票，从头到尾。
This follows your SOP: the client sends the MQ invoice, JY gives the quote and wallet, the client pays and sends the TXID, JY confirms, then sends the payment proof. On step 4 the buttons work: sign it off, or press Edit first. 按照贵司的标准流程：客户发送 MQ 发票，JY 提供公司名称、报价与钱包地址，客户付款并提供 TXID，JY 确认后发出付款凭证。第 4 步的按钮可点击：直接确认，或先点击修改。
Illustrative only. Company names, amounts, the wallet and the TXID are examples.仅为示意。公司名称、金额、钱包地址与 TXID 均为示例。
Seven checks on every MQ invoice. 每张 MQ 发票七项核对。
All of them run in code, never by the AI. A failed check stops the invoice from moving on by itself and sends a card to Teams straight away. 全部由程序执行，从不交由 AI 判断。任何一项不通过，发票都不会自动推进，并立即在 Teams 发出卡片。
| Check核对项目 | The rule规则 | If it fails不通过时 |
|---|---|---|
| Calculation adds up计算正确 | Amount to pay ÷ rate + process fee = total USDT. The division is rounded to cents, then compared exactly.应付金额 ÷ 汇率 + 手续费 = USDT 总额。除法结果先四舍五入到分，再精确比对。 | QUOTE ERROR报价错误 |
| Quote is for this invoice报价对应此发票 | The "invoice" line of the calculation equals the total on the MetaQuotes statement.计算中的"发票"金额等于 MetaQuotes 账单的总额。 | AMOUNT MISMATCH金额不符 |
| Paid the quoted amount支付金额与报价一致 | The net amount on the client's screenshot equals the total USDT quoted.客户截图上的实收金额等于报价的 USDT 总额。 | AMOUNT MISMATCH金额不符 |
| Wallet is a JY wallet钱包属于 JY | The address posted is on JY Global's list of receiving wallets, matched in full.所发地址完整匹配 JY Global 的收款钱包名单。 | UNKNOWN WALLET未知钱包 |
| TXID used onceTXID 仅使用一次 | The transaction hash has not appeared on any other MQ invoice.该交易哈希未在其他 MQ 发票上出现。 | DUPLICATE重复 |
| Proof is for this invoice凭证对应此发票 | The invoice number in the payment-proof PDF equals the record's invoice number.付款凭证 PDF 中的发票号码与记录一致。 | PROOF MISMATCH凭证不符 |
| Proof amount matches凭证金额一致 | The amount on the payment proof equals the amount to pay. Which figure on the proof is used is confirmed with a real proof (see What we need).付款凭证上的金额等于应付金额。具体采用凭证上的哪一个数字，将以真实凭证确认（见"所需配合"）。 | PROOF MISMATCH凭证不符 |
| Paid on-chain链上核实 | The TXID is looked up on the TRON network: confirmed, genuine USDT, the full JY wallet, the right amount. Until it is switched on, the reviewer checks tronscan.在 TRON 网络上查询 TXID：已确认、为真实 USDT、完整的 JY 钱包地址、金额正确。启用前由审核人员在 tronscan 上核实。 | AFTER LAUNCH上线后启用 |
Your payment bot becomes a tracker. 现有付款机器人改为追踪器。
Nothing your reviewers rely on changes. The Payments tracker is today's Payment review, running on the same engine as MQ Invoices. 审核人员依赖的功能都不会改变。付款追踪器就是现在的"付款审核"，与 MQ 发票使用同一套运作机制。
- Every existing case, with its PC- number and history.所有现有案件，连同 PC- 编号与历史记录。
- The eight checks against Xero: amount, currency, payer, date, still open, first time seen, paid to a JY account, read confidently.与 Xero 比对的八项核对：金额、币种、付款人、日期、发票未付、首次出现、付至 JY 账户、识别可信。
- A reviewer confirms each receipt. It completes when Xero shows the invoice paid.每张收据由审核人员确认，Xero 显示发票已付后自动完成。
- A confirmed payment Xero has not shown paid after 3 days becomes an exception.已确认但 Xero 3 天后仍未显示已付的付款，列为异常。
- The same Payments · View / Edit permissions, and each person still sees only their clients.沿用相同的付款 · 查看 / 编辑权限，每人仍只看到自己的客户。
Invoices stays a page of its own: the read-only copy of Xero, with what is owed, what is overdue and the ageing. It links both ways with Payments: an invoice opens its payment case, and a case opens its invoice."发票"保留为独立页面：Xero 的只读副本，显示应收、逾期与账龄。它与付款追踪器互相链接：发票可打开对应的付款案件，案件也可打开对应的发票。
Set it up. Test it. Then publish. 设定、测试，然后发布。
Owners and admins build new trackers in Tracker Setup. Nothing they change reaches staff or the groups until it is published. 所有者与管理员在"追踪器设定"中建立新追踪器。所有修改在发布前都不会影响员工或群组。
From a template or blank: sources, fields, steps, checks, alerts and access. Every edit is saved as a draft.从模板或空白开始：来源、字段、步骤、核对、警报与权限。每次修改都保存为草稿。
Upload an exported group chat. See which step each message would reach, and why. Nothing is saved or sent.上传导出的群聊记录，查看每条消息会进入哪个步骤及原因。不会保存或发送任何内容。
Each correction joins the tracker's test set, which runs again before every publish, so a fix never quietly breaks.每次更正都加入该追踪器的测试集，每次发布前重新运行，确保修正不会被悄悄破坏。
It appears in the sidebar for the roles you chose. Then approve groups for it in Connections.发布后在侧栏向指定角色显示，然后在"连接"中为其批准群组。
For owners and admins. The AI only writes a draft. A person reviews it, tests it and publishes it.仅限所有者与管理员使用。AI 只负责起草，由人员审阅、测试并发布。
One engine. Every tracker runs on it. 一套机制，所有追踪器共用。
Everything runs inside the AI portal you already use, on its server in Singapore. A new tracker is new settings, not new software. 所有功能都在贵司现有的 AI 门户内运行，服务器位于新加坡。新增追踪器只是新增设定，而非新开发软件。
The number already linked for the payment bot. Reads only.沿用付款机器人已关联的号码，只读。
Telegram's official bot, added to a group by its admin. Reads only.Telegram 官方机器人，由群管理员加入，只读。
The read-only copy you already have, used by the Payments tracker.沿用现有的只读副本，供付款追踪器使用。
Public transaction data, for the on-chain USDT check.公开交易数据，用于链上 USDT 核实。
One per MetaQuotes invoice, with every message it used.每张 MetaQuotes 发票一条记录，附带所使用的每条消息。
One per receipt, linked to its Xero invoice.每张收据一条，对应其 Xero 发票。
Every step, who moved it or signed it off, and the AI's original reading.每个步骤、由谁推进或确认，以及 AI 的原始读取结果。
The records, the steps, what needs a person, and the sign-off.记录、步骤、需人员处理的事项，以及确认操作。
Exception cards as they happen, and a daily summary.异常卡片即时发送，另有每日汇总。
The Xero copy, linked to the Payments tracker.Xero 副本，与付款追踪器互相链接。
Hosted in Singapore. Connection secrets encrypted at rest. AI calls go from the server only, never from a browser or phone.托管于新加坡，连接凭据加密存储。AI 只由服务器调用，从不经浏览器或手机。
Every screen, clickable. Before we build. 每个界面都可点击，开发前先确认。
These screens are part of your portal's prototype, with sample data. Nothing is connected, so click freely. The finished product is built to match the screens you approve. 以下界面属于贵司门户原型，使用示例数据，未连接任何真实系统，可随意点击。正式系统将按贵司确认的界面开发。
Every MQ invoice and its status. Open invoice 10699120 to sign it off, or 10701455 to see an amount mismatch.所有 MQ 发票及其状态。打开发票 10699120 进行确认，或打开 10701455 查看金额不符。
Open screen打开界面How MQ Invoices is set up: its steps in plain words, its checks, and a test run on a past chat (tab 7).MQ 发票的设定方式：用一般文字描述的步骤、核对项目，以及用过往群聊测试（第 7 个标签）。
Open screen打开界面Today's Payment review as a tracker: the same tabs, the eight checks, Confirm, Edit and Dismiss.现在的"付款审核"改为追踪器：相同的标签、八项核对，以及确认、修改与排除。
Open screen打开界面The Xero copy on its own page in CRM. Each payment case links into the Payments tracker.Xero 副本在 CRM 下的独立页面，每个付款案件都链接到付款追踪器。
Open screen打开界面Approve a group for one or more trackers, mark who is JY staff, and keep the list of JY wallets.为群组批准一个或多个追踪器、标记 JY 员工，并维护 JY 钱包名单。
Open screen打开界面Best viewed on a desktop.建议在电脑上浏览。
Built on the portal's existing rules. 沿用门户现有的安全规则。
Trackers only read. They never reply, react or mark messages as read.追踪器只读取，从不回复、回应或标记已读。
A message is stored only if a tracker used it. Ordinary chat is never stored, and unapproved groups are never read.只有被追踪器使用的消息才会保存。一般聊天不会储存，未批准的群也不会被读取。
Values the AI read are tagged "AI-read" until a person signs them off, and are left out of the summary's money figures until then.AI 读取的数值在人员确认前都标记为"AI 读取"，确认前不计入汇总中的金额。
Statements, screenshots and proofs go through the same scan as every other upload to the portal.账单、截图与凭证与门户其他上传文件一样经过病毒扫描。
All AI calls go from the portal's server in Singapore. Data sent to the AI provider through its API is not used for training.所有 AI 调用均从门户位于新加坡的服务器发出。经 API 发送给 AI 服务商的数据不会用于模型训练。
Each tracker chooses which roles may open it, checked on every page and every request. Client logins never see trackers.每个追踪器可指定哪些角色能查看，每个页面与每次请求都会检查。客户账号永远看不到追踪器。
What this delivery includes. 本次交付包含的内容。
Please check each item against what you need. Anything missing, or anything you do not need, is easiest to change now. 请逐项核对是否符合贵司需求。如有遗漏或不需要的项目，现在调整最为方便。
- Five statuses from your SOP, plus Cancelled按贵司流程设五个状态，另加"已取消"
- The invoice record created from the MetaQuotes statement根据 MetaQuotes 账单建立发票记录
- The seven checks, including the payment-proof PDF七项核对，包括付款凭证 PDF
- One sign-off per invoice, at Confirmed每张发票在"已确认"时确认一次
- The on-chain USDT check (TRC20), switched on after launch链上 USDT 核实（TRC20），上线后启用
- Accuracy measured on 20–30 of your past MQ chats before go-live上线前以 20–30 个过往 MQ 群聊测试准确度
- Every existing case carried over, PC- numbers kept所有现有案件迁移，保留 PC- 编号
- Run side by side first, and compared with your reviewers' decisions先并行运行，并与审核人员的决定比对
- Completed by Xero; the 3-day unpaid exception由 Xero 完成；3 天未付异常
- Invoices kept in CRM, linked both ways"发票"保留在 CRM 下，并互相链接
- The AI assistant's payment questions keep workingAI 助手的付款查询功能保持可用
- Approve each group for one or more trackers为每个群批准一个或多个追踪器
- Sender roles (JY staff, Client) by phone number按电话号码设定发送人身份（JY 员工、客户）
- Lists, such as JY receiving wallets and invoice issuers名单，例如 JY 收款钱包与发票开具方
- Telegram groups, through Telegram's official bot通过 Telegram 官方机器人接入 Telegram 群
- Tracker Setup, for owners and admins"追踪器设定"，供所有者与管理员使用
- Test on a past chat, and a saved test set per tracker用过往群聊测试，每个追踪器保存测试集
- The AI tracker builder: describe, draft, test, publishAI 起草追踪器：描述、起草、测试、发布
- Templates: MQ invoices, and receipts matched to Xero模板：MQ 发票，以及收据对应 Xero
Ten things to confirm. 需确认的十项。
The screens:界面： click through the prototype and tell us what to change. Building starts from the screens you approve.请浏览原型并告知需要修改之处。开发将以贵司确认的界面为准。
JY staff:JY 员工： the phone numbers of everyone who counts as JY staff in the MQ groups. We know AY Filing. Are Bryan Mq and Suzie MQ payment JY staff?MQ 群内所有 JY 员工的电话号码。我们已知 AY Filing；请问 Bryan Mq 与 Suzie MQ payment 是否为 JY 员工？
Wallets:钱包： JY Global's receiving wallet addresses, and whether TRC20 is the only network. Public addresses only, never private keys.JY Global 的收款钱包地址，以及是否只使用 TRC20 网络。只需公开地址，切勿提供私钥。
A real payment proof:真实付款凭证： one or two "Pymt Proof" PDFs, to fix which amount on the proof is checked.一至两份"Pymt Proof" PDF，用于确定凭证上核对的是哪一个金额。
Past MQ chats:过往 MQ 群聊： 20–30 exported MQ group chats, to measure accuracy before go-live.20–30 个导出的 MQ 群聊记录，用于上线前测试准确度。
Teams: the channel for exception cards and the daily summary, the time it should go out, and a Teams user to create the channel's webhook.接收异常卡片与每日汇总的频道、发送时间，以及一位负责建立该频道 Webhook 的 Teams 用户。
Microsoft 365: your admin, to register the Teams bot, so the cards can carry Confirm and Edit buttons.贵司管理员注册 Teams 机器人，卡片才能加入确认与修改按钮。
Groups:群组： the MQ groups to start with, and whether they already include the number the payment bot reads from.首批接入的 MQ 群，以及这些群是否已包含付款机器人所用的号码。
Data:数据： how long tracker records and files are kept; whether labelled past chats may be kept as test sets; and whether any tracker may send every message to the AI.追踪器记录与文件的保存期限；已标记的过往群聊能否保存为测试集；以及是否允许任何追踪器把全部消息交给 AI。
