---
schema_version: "1"
id: 79670830f96507ef4d8f01fca5589453e3123e31fb18be86c76602480ac1814e
title: Create Accounting Field Mappings
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/asl_create_accounting_field_mappings.md
canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.asl_create_accounting_field_mappings.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 411e1584e47f1d121ade1a0a20a920c94e6a25cd9ed6b2c0a89d94db75e3728b
description: Generate financial data beyond the default transaction journal record fields with accounting field mappings.
products:
  - Education
  - Cross Cloud
release: "264"
---
# Create Accounting Field Mappings

Generate financial data beyond the default transaction journal record fields with accounting field mappings.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small " summary="REQUIRED EDITIONS"><caption>REQUIRED EDITIONS</caption> <colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Accounting Subledger</td></tr></tbody></table>

 
| User Permissions Needed |   |
| --- | --- |
| To set up accounting field mappings: | Manage Accounting Subledger |

Before you create accounting field mappings, here are a few things to consider:

- You can create up to 10 accounting field mappings in an accounting set.
- You can’t edit or delete accounting field mappings used in active accounting sets. See [Manage Accounting Sets](https://help.salesforce.com/s/articleView?id=sfdo.asl_manage_accounting_sets.htm&release=264.0.0&type=5 "When you're done configuring accounting sets, activate them. After you do so, you can no longer change the object model but you can deactivate it in order to update its other settings.").
- Deleting an accounting set via API or changing its object model also deletes its related accounting field mappings.
- You must create and add the custom fields to use as target fields on the Transaction Journal object. See [Create Custom Fields](https://help.salesforce.com/s/articleview?id=platform.adding_fields.htm&type=5).

To create accounting field mappings:

1. From Setup, in the Quick Find box, enter Accounting Sets, and then select **Accounting Sets**.
2. Next to the accounting set to which you want to add an accounting field mapping, click ![Show Actions icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-accounting_subledger-264-0-0-production-enus/157531ff-70d1-4f66-a3f6-8bad55ae5e5d/resources-product/images/show_more_actions_icon.png), and then select **View**.
3. Click **New Accounting Field Mapping**.
4. Select the source object to copy data from. The dropdown only lists the source objects that you included in the related accounting set’s object model.
5. Select the source field to copy data from.
6. Select a transaction journal target field to which you want to copy the data. The target field must meet these requirements:
    - Its data type matches the selected source field. See [Accounting Field Mappings](https://help.salesforce.com/s/articleView?id=sfdo.asl_accounting_field_mappings.htm&release=264.0.0&type=5 "Create accounting field mappings to bring your data to custom fields on transaction journal records.").
    - It’s not used in another accounting field mapping within the same accounting set.
7. Click **Next**.
8. Select a mapping behavior.

If you choose Current Value, don’t add automation that updates transaction journal record values. If you do, Accounting Subledger sometimes creates unnecessary reversals and transaction journal records. Instead, create a second field outside of any accounting field mapping to store the transaction journal record value, and add automation to that second field. Use the source value on the transaction journal record only for mapping and comparison. Some objects such as the Fund object don't support the current value behavior.