> 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/setup/testing/auto-accounting/m3.md).

# M3

验证并导出文档后，登录 INFOR 并输入 APS450 命令。

![](https://lh7-us.googleusercontent.com/i4iRIFS78R3roSyp5i6TK8VCp3_GLgdet13ZyWRgUJjaTkLnl4Kfm-fv_xky2Pu-LHmvrjLHhv1es_MpBZAQV0fZPmYa7fsEye9IyNGkLsJNwPIRlSWKZ8BOitnImB6szvGZfaqu-gzVL8vbBhsmpHA)

系统会带您进入以下页面，在这里可以看到刚刚导出的文档。

![](https://lh7-us.googleusercontent.com/zvHZ3f9eVk04gFXYvmCFJZH4zXY9HnuK5BwU-iO7aemf9fVXWDa7Yy6j9F6fIuN0Nx5mlBsRBVbYexe4D547kkgWMMWfEx1sjjEmfORq6cf1gel94LchPvBdPP6htbcCe0bveKRIUlQjr13HPXn49yM)

找到文档后，右键单击文档，选择“Related”，然后选择“Lines”选项。

![](https://lh7-us.googleusercontent.com/BTIGc1czaZLPysu1BMTr1hUL_u0RlnuP0wV7xghtfpyw4L1VEDukpVPJt2VYyD88_-dQGJ5zaYn4mPKbmJal52-9TwkGzJNBCZ7bgWStiJrWHAIsTGp-BM9TCY328ysf1LJINXKVEOBkdCPFXPxLrzI)

系统会带您进入一个菜单，其中显示了您导出的发票中的所有行项目。请确认所有行项目均已显示且信息正确。最后，请确认所有这些行项目的类型均为 Type 8，可通过查看表格中的以下列进行确认。

![](https://lh7-us.googleusercontent.com/IpuwyIzt9yF5s1DKF1XkbsU5fAtpEu5Ap8pQoOub_r39xXX5YeLGZCbN817HSiynyjBLFR6Ll97TTYdESAwWaI_2ifiN0uzPypxmbggbtbSXmcJsTLwfecNQ3jFrJZvD8rvN3fAM0WmVem5xkPRURR0)


---

# 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/setup/testing/auto-accounting/m3.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.