Custom fields enable users to append specific, company-relevant data to transactions. This capability is particularly useful across various sectors, from general business needs like assigning specific variables (e.g. locations, markets, departments, client ids..:) and to transactions, to specialised requirements in the travel industry, such as enriching transaction data with airline/train ticket numbers or hotel booking references. It's also helpful for accountants who want to document e.g.participant details in business meals or other data points that are part of the pre-accounting/accounting workflow.

Custom fields can be activated by navigating to the Modules page and selecting this option from the available modules list. Please note that the feature is part of our Standard plan and higher.

Once active, custom fields are set up within the accounting settings, accessible through Settings > Accounting. As of now, the system supports only text-based fields. When creating a custom field, you will need to provide a name to identify the field, a short description to clarify its purpose, and an optional default value that can be automatically applied in certain actions, like card-based automations.

There are two important settings for each custom field:

Custom fields can be deactivated or deleted provided they are not linked to any existing transactions.

You can assign or modify values in custom fields on any page where transactions are listed. This includes the transaction pages in both the cardholder and admin apps, as well as during the export flow in the admin app.

Once a transaction is split into multiple accounting transactions its possible to assign different values to each accounting transaction.

When exporting transactions, whether directly via download button on the transactions page, through the export flow, or in conjunction with monthly credit card statements, the custom fields appear as additional columns at the end of the CSV file. Please note that once a transaction is exported, it, along with its custom fields, becomes immutable.

Currently, the automatic assignment of default custom field values based on card is available. The default values will apply to all future transactions made with that card, although they can be overwritten on an individual transaction basis. To set up default values simply provide them during the card issuance flow (Step: card attributes) or anytime later (for existing cards) via the cards context menu (Edit custom fields).

Custom fields and their values are displayed in both the admin apps card's detail view and the wallet view within the cardholder app.

Custom fields can also be configured through our API solutions, including the CAAS API and Pro API. For more information on how to set this up and integrate it with your systems, please contact our support team at support@getpliant.com.