Skip to main content

How to Define Custom Field Rules

Learn how to set up custom field rules to automatically populate custom fields on credit memos created by Confido in your ERP

N
Written by Nico Langlois

What is a custom field rule?

When Confido creates a credit memo for a deduction, it can pass along additional data to custom fields in your ERP — things like brand, region, or product line. A custom field rule defines exactly what value gets written to a given custom field, and under what conditions.

Example: You want deductions tied to certain product families to automatically populate a "Brand" field on the credit memo in your ERP. You'd create a rule that maps a Confido product family value to your ERP's Brand custom field.


Before you begin

You'll need:

  • The name of the custom field in your ERP that you want to populate

  • An understanding of which Confido field (e.g., product family, customer) should drive the value


How to create a custom field rule

Step 1: Open Custom Field Rules settings

Navigate to Settings → GL Accounting Customization in Confido and scroll to the Custom Field Rules section.


Step 2: Create a new custom field rule

Scroll to "Custom Field Rules" and click Add Custom Rule


Step 3: Configure the rule

  1. Give your rule a clear, descriptive name so it's easy to identify later

  2. Select the Confido field and the ERP custom field to populate

  3. Map the Confido field values to the corresponding ERP custom field values

Field

Description

Confido field

The field in Confido that holds the source value (e.g., Product Family)

ERP custom field

The name of the custom field on the credit memo in your ERP that should be populated

Example: Map Confido's Product Family field → ERP custom field Brand


Tips

  • Rules are evaluated at credit memo creation time. Changes to a rule won't retroactively update previously created memos.

  • Use filters when rules conflict. If different customers require different mappings for the same custom field, create separate rules with filters to scope each one appropriately.

  • Name rules consistently. A naming convention like [Confido Field] → [ERP Field] makes the rules list easier to manage as it grows.

Did this answer your question?