---
title: "MakersHub Custom Fields"
slug: "internal-custom-fields"
updated: 2026-09-02T17:12:56Z
published: 2026-09-02T17:12:56Z
canonical: "support.makershub.ai/internal-custom-fields"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.makershub.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MakersHub Custom Fields

Users may find that they need to pull in information that does not translate to their ERP but that they need for the automation of coding (integration mapping) within MakersHub. This article will go over how to add custom fields and a use case for them

## Internal Custom Fields

Sometimes you need to pull a specific value off the bill to drive an automation or track something on its own. You can do this by configuring an internal custom field - at the header level or line level - and train MakersHub to capture the data you need.

> [!WARNING]
> Note:
> 
> Data tracked through internal custom fields does not sync to your ERP.

To set them up, navigate to your *Name > Bill Settings > Data Processing tab*, then click **Configure** to build a custom field.

![](https://cdn.document360.io/1b554e23-2d1e-483c-9fb1-9be0ba01e89c/Images/Documentation/image(254).png)

Say you need to track the Warehouse field on a batch of New Balance bills, with the goal of having the system read that warehouse and automatically assign a class or account through integration mapping. Create the Warehouse field, then click **Update Settings** to save.

![](https://cdn.document360.io/1b554e23-2d1e-483c-9fb1-9be0ba01e89c/Images/Documentation/image(255).png)

Once configured, these trainable fields appear on your bills. Reliably capturing a field like this expands what you can automate - anything on the bill can become a trigger for coding automations elsewhere through integration mapping.

For more information on our OCR Training, see the following article: [OCR Training Overview](https://support.makershub.ai/docs/ocr-training).

![](https://cdn.document360.io/1b554e23-2d1e-483c-9fb1-9be0ba01e89c/Images/Documentation/image(256).png)

## Example: Account Number

Many clients have multiple accounts that they manage through utility companies, with this additional field we can now pull in the account number to automate coding of data such as location, class, account, etc… Please see the steps of our example below.

First click into the Account field, from here you can select the magnifying glass and train MakersHub to extract the Account Number field from the bill.

![](https://cdn.document360.io/1b554e23-2d1e-483c-9fb1-9be0ba01e89c/Images/Documentation/Select field.png)

![](https://cdn.document360.io/1b554e23-2d1e-483c-9fb1-9be0ba01e89c/Images/Documentation/Account number coding.png)

Once we have the field trained we can use integration mapping under the **Custom Extraction Fields** to automatically code any number of fields. Such as when you see XYZ account number code in a certain Class or Location.

![](https://cdn.document360.io/1b554e23-2d1e-483c-9fb1-9be0ba01e89c/Images/Documentation/Integration mapping account.png)

For more integration mapping help please see our article [here](/v1/docs/ocr-training).