--- schema_version: "1" id: f167922da061a6b9e76c00f3dbb56752d34c7182d000d581e5d7166b98ecc0f5 title: Map Your Source Data to Accounting Sets collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/asl_map_your_source_data_to_accounting_sets.md canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.asl_map_your_source_data_to_accounting_sets.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: f5af30f65df725da0a84d30fed2db113d5bab6f565401d49210fd845e306c07d description: Choose which source record fields to use for transaction journal records generation by mapping them to accounting set fields. products: - Education - Cross Cloud release: "264" --- # Map Your Source Data to Accounting Sets Choose which source record fields to use for transaction journal records generation by mapping them to accounting set fields.
REQUIRED EDITIONS AND USER PERMISSIONS
Available in: Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions with Accounting Subledger
| User Permissions Needed |   | | --- | --- | | To set up accounting sets: | Manage Accounting Subledger | Before you start setting up accounting sets, make sure that the values on your source records don't exceed the allowed size in the target fields on the Transaction Journal object. For example, a Long Text Area field can contain values that are too large to store in a regular text field. Such values cause errors when the Accounting Subledger job runs. Also make sure that the source fields that you're planning to map to accounting sets exist and are of the expected type. For example, your source object must have a date type field to map to the accounting set's payment date. For examples of accounting set configurations, see [Accounting Set Example Configurations](https://help.salesforce.com/s/articleView?id=sfdo.asl_acct_set_example_config.htm&release=264.0.0&type=5 "Review recommended accounting set mappings for common use cases."). ## Specify the Source Objects 1. From Setup, in the Quick Find box, enter Accounting Sets, and then select **Accounting Sets**. 2. Enter a name for your accounting set. 3. Select the number of source objects based on the object model that you want for the accounting set. See [Object Models for Accounting Sets](https://help.salesforce.com/s/articleView?id=sfdo.asl_object_models.htm&release=264.0.0&type=5 "Accounting sets enable you to specify which objects and fields store your source data and how to generate transaction journal records from it. It's a flexible approach that lets you map your financial data model to a logical data model, supporting from one to four objects, including the Fund Account object. Each accounting set represents a set of financial data, such as revenue from gifts or expenses from fees."). 4. Select the primary object and additional objects as needed, keeping in mind these requirements. - Each object that you select after the primary object must be related to the previously selected objects. - The secondary object must have a lookup or master-detail relationship to the primary object. - The tertiary object must have a lookup or master-detail relationship to both the primary and secondary objects. - The object that you choose as the fund object must have a lookup relationship to the tertiary object's fund object and is always the last object that you select. - You can select an object only one time. For example, if you map the Account object to the primary object, you can't select it for another object. 5. Click **Next**. ## Specify the Source Fields Next, for each source object, map its fields to the accounting set's target fields. 1. If you're not already editing an accounting set, from Setup, in the Quick Find box, enter Accounting Sets, and then select **Accounting Sets**. 2. Next to the accounting set to configure, 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 **Edit**. 3. Click **Next**. 4. Select the name of the field on the source object that contains the data. The expected data type is indicated in parentheses, such as (Date) or (Checkbox). The dropdown only lists the source fields that match that data type.
Accounting Set Field Purpose

Amount

(One- or two-object model)

 The primary object's revenue or expense amount.

Amount

(Three-object model)

 The primary object's revenue or expense amount, and the secondary object's allocation amount.

Amount

(Four-object model)

 The primary object's overall amount, the secondary object's revenue or expense amount, and the tertiary object's allocation amount.
Check/Reference Number The check or reference number that's recorded when the record is marked paid or written off. Make sure that the source data value is less than or equal to 40 characters.
Committed Date The date on which the revenue or expense is first promised. If left empty, the default value is the date on which the Accounting Subledger job runs.
Fund Name The name of the fund account to which the revenue or expense is allocated. It can also be an account number. Salesforce uses this value as the GL code. Make sure that the source data value is less than or equal to 100 characters.
Generate Expected Revenue/Expense

Controls whether to apply accrual accounting or cash accounting to generate transaction journal records.

  • If this checkbox is selected on the source record, Salesforce generates records for both scheduled and paid revenue and expenses.
  • If this checkbox is deselected on the source record, Salesforce generates records only for paid revenue and expenses.

By default, this value is deselected.
Payment is Paid If selected, the source record was marked as paid.
Payment Method The payment method used. Make sure that the source data value is less than or equal to 255 characters.
Payment Paid Date The date on which the record was paid.
Scheduled Date The date on which the record is scheduled to be paid.
Transaction Date

The date on which the revenue or expense is expected, received, or adjusted. The required mapping depends on the type of revenue or expense and the object model.

  • Paid revenue or expense: In the four-object model, map an additional transaction date for the secondary object. Salesforce only uses this date for that payment or expense. Otherwise, it uses a single transaction date field for all source records. In all other object models, map the transaction date for the primary object.
  • Expected revenue or expense: For all object models, Salesforce uses the transaction date that you mapped for the primary object for all source records.
Note
Note If you mapped your own dates to the Transaction Date field, we recommend that you configure automation tools to set that date accordingly on your source records in response to other changes. For example, you can use Process Builder or Flow Builder to update the transaction date to the current date when someone creates a record or updates the payment date. Otherwise, Salesforce sets the transaction date to the date on which the accounting scheduled job runs.
Written-Off If selected, the source record was marked as written off. By default, this value is deselected.