Adding Custom Mappings

PSA – Accounting Connector enables you to create custom field-level mappings for each flow. This is useful when you want to:

  • Map additional fields or values from the source object and its child object to the target object and its child object.
  • Override a default (managed) mapping with a custom mapping.

In either case, you must create a new mapping. If a mapping for the target field already exists, it is overridden.

The sections below provide more information about the supported mapping types and examples with steps on how to create mappings.

Supported Mapping Types

PSA – Accounting Connector supports all mapping types supported by Foundations mappings. For more information, see Adding Custom Mappings from the FDN Mappings Component.


The Sales Invoice to Sales Credit Note mapping process only supports basic value to value mappings. Complex mappings, such as name to lookup or path mappings, are not supported for this process.

Name to Lookup Mappings

You can map a text field to a lookup field. If the text value matches the name of a record, the lookup is populated on the resulting record. Otherwise, an error displays and the resulting record is not created.

This can be useful if you have records of different objects with the same name. For example, if your regions have the same names as your dimension 1 records. In that case, you can map Region Name to Dimension 1. When creating the Accounting document, PSA – Accounting Connector tries to match the region to a dimension 1. If a matching dimension 1 isn't found or multiple dimension 1 records with the same name exist, the Accounting document is not created. Before using name to lookup mappings, you must ensure that the relevant records exist.

Return Mappings

After creating an Accounting record from a PSA record or vice-versa, PSA – Accounting Connector updates the originating record. For most flows a checkbox field is selected on the originating records to mark the record as processed. For the Billing Events to Sales Invoices or Credit Notes flow, several fields are updated on the billing event. These are defined as return mappings.

You can customize the return mappings for a flow to update additional fields on the originating record. These can be static values or values from a field on the resulting record. See Example 5: Due Date from the Payable Invoice Populated Back on the Vendor Invoice.

  • You can only add return mappings for the parent records used to trigger a flow, for example, a billing event. You cannot add a return mapping for the child records, for example, billing event items. Similarly, you can only use values from the parent record, for example, from a sales invoice. You cannot use a value from a child record, for example, a sales invoice line item.
  • For the Payable Invoice Expense Line Items to Miscellaneous Adjustments and Payable Credit Note Expense Line Items to Miscellaneous Adjustments flows, you might define return mappings that target the same field on the expense line item from both a cost and a recharge miscellaneous adjustment. In that case, when a recharge miscellaneous adjustment is created, the recharge return mappings are used. Otherwise, the cost return mappings are used. This only applies for mappings with the same target field.


The following examples provide steps for creating different types of mappings. For a full list of the options available in the FDN Mappings Lightning component, see Adding Custom Mappings from the FDN Mappings Component.


When creating a mapping, only the fields that you have access to are displayed. If a field is not displayed, ensure that you have access to it.