> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/admin-panel/conversion-rules/how-to-convert-xls-and-x12-to-xml.md).

# How to Convert XLS and X12 to XML

This document explains how to convert .xls, .xlsx, and X12 files (.xml or .txt) into envelopes using the built-in converter

Convert `.xls`, `.xlsx`, and X12 files (`.xml` or `.txt`) to envelopes.

This uses the built-in converter.

### Create a conversion rule

1. Create a new conversion rule.
2. In the first window, upload a sample file in the required format.
3. In the second window, write the conversion rule.
   * Use XPath to map values into the target fields.
4. Run the rule.
5. Check the output in the third window.
6. In the **Name** field, add a regexp for matching input files.
7. Save the conversion rule.

### Convert files automatically

Put files with matching names into the `inbox` or `outbox` folder.

They will be converted to envelopes automatically.


---

# 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://support.docstudio.com/admin-panel/conversion-rules/how-to-convert-xls-and-x12-to-xml.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.
