> For the complete documentation index, see [llms.txt](https://docs.unimarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unimarket.com/documentation/master-data/update-account-code-format-integration.md).

# Update Account Code Format Integration

The **Update Account Code Format** integration is an inbound process used to receive General Ledger (GL) or Project account code formats, values, and descriptions from an external system (e.g., a customer's ERP or Finance solution). This integration ensures that GL master data held in your financial system is accurately replicated into Unimarket.

## Intent

* **Data Replication**: To populate Unimarket with current financial structure data from an external ERP.
* **Frequency**: This process is typically run periodically, such as nightly, to keep systems synchronized.
* **Checkout Accuracy**: The replicated codes are used to code requisition lines during the checkout process, ensuring users select valid financial data.

## Key Data Elements

The integration populates Unimarket with the following structural and master data:

* **Account Code Part Options**: Defines the segments of your account string, such as Organization, Team, or Account.
* **Part Types and Dependencies**: Establishes the relationships and hierarchies between different account code segments.
* **Account Code Part Data**: Imports the specific codes and their corresponding descriptions.

## Troubleshooting

If the account code data does not appear to be updating:

1. Verify the connection status of your **Workato On-Premise Agent** or **Unimarket Connector**.
2. Check the **Administration > File Processing** module (if using File Automation) to view any error logs.
3. Ensure the external ERP triggered the scheduled export, as expected.


---

# 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.unimarket.com/documentation/master-data/update-account-code-format-integration.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.