> 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/administration-and-setup/settings/global-settings/document-types/fields/new-fields-with-charges.md).

# New Fields with Charges

\\

## Step 1: Access the Field Settings

1\. Navigate to Fields:

• From the main dashboard, click on the “Fields” option located in the sidebar.

• This will open the Field Settings page where you can manage document types and recognition settings.

2\. Select Document Type:

• Under the “DOCUMENT TYPES” section, select the specific document type you wish to add or modify a field for.

<div><figure><img src="/files/ppiu84B9WepI9VvVWPl8" alt=""><figcaption></figcaption></figure> <figure><img src="/files/U8YUjxvzlrIJYmIfwHNi" alt=""><figcaption></figcaption></figure></div>

## Step 2: Add a New Field

1\. Open the Add Field Dialog:

• Click on the “Create Field” button located in the respective section (e.g., Invoice Details, Payment Details, Purchase Order).

2\. Enter Field Details:

• A dialog box titled “Document field details” will appear.

• Fill in the required details:

• Name: Enter the name of the new field.

• Title: Enter a descriptive title for the field.

• Select field type: Choose the appropriate field type from the dropdown menu.

3\. Enable Charges Element:

• If this field is associated with a charge, check the “Enable charges element” box.

4\. Select Costing Mapping:

• Upon enabling charges, a dropdown menu will appear.

• Select the appropriate charge type from the list (e.g., ADD ON - ORIGIN, FUEL SURCHARGE, TOTAL FREIGHT).

\\

## Step 3: Save the New Field

1\. Save Settings:

• Click the “SAVE” button to add the new field with the specified charge mapping.

• If you need to make changes, click the “BACK” button to return to the previous screen.

2\. Finalize Field Creation:

• After saving, the new field will appear in the list under the specified document type.

• Ensure that the OCR and Match Score settings are configured as needed for accurate recognition.

3\. Complete the Setup:

• Once all desired fields are added and configured, click the “Save Settings” button at the bottom of the Field Settings page to apply your changes.

\\

## Additional Notes

• Required Fields:

• If a field is mandatory, check the “REQUIRED” box next to the field name.

• Editing Existing Fields:

• To edit an existing field, click on the field name, update the details, and save the changes.

• Reassign Field Group:

• Use the “Reassign Field Group” option to change the grouping of fields if necessary.

• Master Data Settings:

• For advanced configuration, access the “Master Data Settings” to manage overall field and document type settings.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/new-fields-with-charges.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
