I was wondering how everyone validates their accounts? For example, we have Account - Department - Program - Project - Other as part of our GL Account code. We are using Dynamics SL and have turned on Acct-SubAcct validations.
In Concur, a user can select the Expense Type (Account) then choose Cpst Tracking for each of the other four segments of our Acct-SubAcct string. Each segment is correct but there is no validation that the combination of the segments is an active/valid account string. How does everyone ensure that the data entered will eventually pass through to the underlying Financial System without errors or manual intervention?
We put some validate tables in Concur. It in no way to do all our validation as we have some complex accounting. However, these validations ensure that over most entries import without issue.
What is the process to add the tables? Once you have the tables:
1. How do you link them to validate?
2. What warnings/messages do the end users receive?
3. What is your process to add new account combinations?
This is a great question, and I'm interested in seeing others' responses, but have you looked into the Linked Lists feature in Concur?
This function would only allow specific codes in secondary / tertiary / etc. tiers based on the preceding value. For instance:
Let's say you have Departments A and B, and Programs 1, 2, 3, and 4. Programs 1 and 2 are only valid for Department A, and Programs 3 and 4 only for Department B. You could create a Linked List that would only populate the Programs field based on the value in the Department field.
So if a user were to choose Department A, they would only be able to select Programs 1 or 2. Same for Department B with Programs 3 and 4.
This could get complex with 5 segments, and if you had a shared code (i.e. Program 5 that would be valid for either Department) you would need to have it entered in twice - one for each Linked List, but I wanted to mention it as a potential solution.
For my company, we looked into this, but we have 8 segments, and I believe the limit is 5 tiers. Some Concur folks on here may have more resources for you, but if you wanted to check it out, it's in the Cost Tracking section of the Settings page, under 2 Linked Lists. There's a 'Show me More' button that gives a detailed explanation about how it functions.
We have daily accounting imports. This includes valid company, departments, etc. with connected list. We also send value projects/tasks that we use in Conur.
Additionally we have custom audit rules and validation rules set up. For example,
Error message are flagged that these combinations are not valid.
We worked with Concur to set these up during implementation.
Email me if you would like to discuss further email@example.com
Thank you for the reply... I do have a note to check into linked lists. I will review the help section. We have two possible outcomes:
1. I queried our financial system database and extracted all the account codes that were hit last year (237). My presumption is that we likely (>=85% ) hit the same account codes this year.
2. I also queried our financial system and got all the possible valid combinations of account codes (1,476).
So, do I then create linked lists just for those that have been used? Or do I create the lists for the entire population? Will this list be available/used when we start the Invoice implementation?
Are there huge maintenance issues going either way? Can these just be uploaded into Concur? (My apologies if this is in the help section)
We don't use these Linked Lists, so I'm not sure on some of these questions, but I'll do my best! Maybe some Concur folks can chime in... haha
Creating lists for just codes that have been used vs. all combinations would likely just depend on whether you want your users coding expenses to them. If you want to give them the options to code to any code, then the entire gamut of code combinations might be needed to import. If you have a specific section of codes (i.e. all Account codes in the 1XX range) that are restricted to revenue or something like that, you wouldn't need to import them, as users wouldn't likely be coding expenses to revenue accounts - or maybe they would? Whatever works best for your processes.
I believe (again, not super familiar with it) you would create a list file for each tier, and specific to the preceding value. So here's an example:
Import file 1 (Department)
Import file 2 (Programs for Admin)
Import file 3 (Programs for Finance)
Import file 4 (Programs for IT)
Import file 5 (Projects for Program A)
Import file 6 (Projects for Program B)
And so on, and so on. So each branch would need an import file that is designated as linked to a specific value in the preceding field. Again, there might be a better or easier way to do this, but this is just my understanding of it from my research into it.
As for maintenance, it might be as simple as uploading a new file for each Linked List branch, but I'm not certain. I'd suggest checking out the Get Assistance button the Linked List page for more info. For that amount of account iterations, it may not be too tedious to do this, but if you start seeing more and more unique account strings added, it might get hairy.
A couple of weeks ago you asked about the differences between the Standard and Professional versions. Validation tables and Validation rules are one of those differences and are currently only available in Professional. The reasoning is the vast majority of our customers simply do not need them; We have companies with tens of thousands of users that run just fine without validation rules.
What most customers do is what one of the topics further down references: linked lists. This feature enables you to maintain the list of valid cost objects and combinations of those cost objects.
For example if you had two business units (BU) and each of those BUs had a separate list of Cost Centers (CC) the linked list makes sure I can't choose an invalid combination of BU and CC.
It is also possible to maintain the linked list through a fairly straightforward Excel-based import, available to download from within the system.
This same issue came up for me recently and after countless hours spent trying to find ways to ensure accuracy, we ended up freezing those fields. Each situation is unique so it may not be an option but other than expense type, my employees had no idea how to code an expense correctly. With everyone doing their own thing based on their understanding of what it meant, it made it impossible to pull accurate reports. The two biggest ones were department and location. Each employee was assigned their dept and loc and that's what they were changing in an effort to allocate to other departments. We also had project codes but kept those to a minimum. They could still use the allocate function but those we could report on and review easier and it made the review process much easier on the accounting side.
Basically, we didn't give them the option to change codes in Concur which allowed it to flow to the accounting system where it could be broken down accurately on that side.