Map Unmapped Accounts in the Statement Data Models

Before you begin… 

To help think through how to map an unmapped account, ask yourself the following questions. 

1. Which line items should these accounts be related to?
2. Which column would I filter to capture that row?
3. Which period is it in? (Make sure its the right period.)

Once you've answered these questions, review the existing local rules and either...

1. Refine an existing local rule
2. Create a new local rule to map it. 

Click either option above to navigate directly to it. To navigate to the other sections of the article, select them below.

• Troubleshooting
• Frequently Asked Questions (FAQs)

Map Unmapped Accounts with Existing Local Rules Walkthrough

Select Next to move through the guide. You can also zoom in and out of the image by selecting the Magnifying Glass in the bottom right-hand corner. You can view the full guide by selecting the External Link icon. 

Step-by-Step Instructions

1. From the Map section of a Data Model in the MDFM, review your Unmapped accounts to determine which account it applies to.
2. Click the Local Rules tab to review current mapping. In this example, we have a local rule that is missing the L12 Account Type.
   • Note: If there is not a local rule that applies, create a new one.
3. Click the Edit (pencil) icon for the selected local rule.
4. Select the Edit (pencil) icon to edit an existing field.
5. Click within the Value section to open the value list and select the value(s) or type in the value(s) as needed.
6. Click the Save (Floppy Disk) icon to save the updated Account Type rule.
7. Click OK to confirm the rule changes.
8. Important: Click the link icon in the upper right hand corner to map the unmapped accounts. If you do not do this, your statements will not update.
9. Navigate back to the Accounts tab to ensure the local rule mapped the unmapped accounts.

Create a New Local Rule to Map Walkthrough

Select Next to move through the guide. You can also zoom in and out of the image by selecting the Magnifying Glass in the bottom right-hand corner. You can view the full guide by selecting the External Link icon. 

Step-by-Step Instructions

If you have unmapped accounts, but no local rules to map them, create a new local rule.

1. Click the Local Rules tab to begin.
2. Click the Add rule (blue plus) button.
   • Note: The Fiscal Period field will automatically populate based on the period set within the Map section. 
3. Click the Add condition (grey plus) button.
4. Select a Field to add values to map the accounts.
5. Under the Type field, select the appropriate operator for the field.
   • Tip: Use the different operator types to match patterns within your accounts. Select the operator that helps you to build out a rule with dynamic logic ensuring that you don't need to ensure you have every value listed or need to edit the rule for future updates.
6. Select the specific values that will be mapped within this rule for the field.
7. Select Save (floppy disk icon) to save the condition.
   • Tip: Continue to add as many conditions as needed to help map the accounts appropriately.
8. Once ready, click "OK" to create the local rule.
   • Tip: After you create the rule, if you click on the rule, it will show all the matched accounts that were matched to that rule for review. 
9. Important: Click the link icon in the upper right hand corner to map the unmapped accounts.
10. Navigate back to the Accounts tab to ensure the local rule mapped the unmapped accounts.

Troubleshooting

Issue: I cannot select the Plus (+) to create a new local rule.

Solution: You can only create a local rule on the lowest level of the GL. You may be on a higher level (or folder) for the GL accounts. 

Issue: Rule Conflict

Solution: Click the Resolve Conflict button and review the rules affected by the conflict. Determine what rule would be the most effective and adjust the rule as needed by editing it. Delete any other rules that are no longer needed. 

Tip: Click into each conflicting rule and download the excel files. Check which rows appear twice among the files. These will be your conflicts. 

Issue: I can no longer see my unmapped accounts or local rules.

Solution: First, make sure you are working on the relevant period. Otherwise, the data model may be filtered too heavily. Check the breadcrumb trail at the top of the page to see what it is currently filtered to and select the Clear Selection (X with a circle) button next to search in the left side bar navigation to reset it. 

Frequently Asked Questions (FAQs)

Q: What is a local rule and why is it different from a shared rule?

A: A local rule is a custom configuration you create to map your unique Account Codes or Object Codes to specific Financial Statement Lines. Think of it as a bridge that tells the system: "Whenever you see this specific local account, place its value in this specific section of the report." 

Shared rules are the baseline that will assist us to filter your data (e.g trial balance accounts for ACFR) to the relevant models. Think of it as the first filter where funds are dispersed to the different data models to be filtered further. 

Q: Why are accounts unmapped?

A: A local rule wasn’t able to automatically link them to a line item which means we need to either refine an existing rule or create a new local rule to ensure it is part of the statement.

Q: Can a line item have multiple local rules attached to it?

Yes! In real situations, not all departments or funds follow the same mapping logic. Some might have exceptions or unique requirements. This is the reason why the system allows you to add a second rule for the same line item. The second rule uses AND logic, meaning both conditions must be met for the mapping to apply.

For example, if you set:

Object 101 for Fund 100, and Object 110 for Fund 200: The system will map Object 101 only for Fund 100, and Object 110 only for Fund 200. 

In other words, each condition adds further restrictions to the rule. 

Q: Can a local rule have multiple values listed in the rule?

Yes! Instead of creating a separate rule for each value, you can list several values together in one rule by separating them with commas. 

Tip: When you press the Enter/Return key on your keyboard, the system will automatically split them and treat each object as a separate entry. This helps you work faster and stay consistent, especially when you have many values that follow the same rule.