I keep receiving error messages when I try to import my batches into Adagio Ledger. I have received the following message:

"Invalid Data '123456/1' for field called 'Acct/Dept' of record 1. Account master record for 123456/1 does not exist."

This doesn't make any sense to me because I don't have any field 'Acct/Dept' available in the Import Field Selection. I am getting the same error with Header Detail and Detail Only. I have compared my files to those in the sample database and can't seem to figure it out. Any suggestions?

I'm having the same problem for the payroll import from Easypay. It worked fine in April.

I get the same error message for every record.

The error message on the import batch is reporting an error that the combination of Account 123456 and dept 1 does not exist, when looking at the Edit Accounts grid. Indeed there is no 'Acct/Dept' import field - this is taking a combination of the Account and the Department field and morphing into a single message.

Do you have an account code 123456 and attached department code 1 when looking at Edit Accounts? If not then that is the reason for the error.

What changed recently? Did you install an Adagio Ledger upgrade or service pack? If so then what version were you running previously and what version are you running now?

What is the format of the file being imported? Excel? CSV? Another? How is the file created, and is it edited prior to importing?

Yes, we recently uploaded 9.0C but I can't remember what version we had prior to that. I would think it was 8.1B.

Our export file, from Easy Pay, is a .DEL file. It is not edited prior to importing but I'm also not sure if it's supposed to be.

My employee passed away a week ago after being ill for the last month so I was unable to document his procedures for the importing of the payroll data into Adagio.

Hi Rebecca,

Our condolences on your employee's passing.

In the error message that describes an invalid account-department pair, are the listed codes actually valid? Or are they perhaps truncated from actual account codes and the truncated account portions are the invalid checking? Since the errors are on every record, it is unlikely that every account would all of a sudden be missing. Rather, the import template is in some way not matching the file.

You shouldn't be required to edit a file prior to importing. Perhaps you could attempt to open it with Notepad (just to look, not to make any changes) and see if the account and department codes appear valid and also match what are displayed in the error messages.

You may want to have your Adagio consultant come along side and assist in investigating whether the file matches the template or where it no longer does, if all of this starts to become a little overwhelming.

I looked for a template but I'm not sure what the extension should be or where the import mechanism looks for the file. (ie: /softrak/????/templatename.???

I'll look at the file in Notepad but without knowing where the original template is I'm not sure how that will help.

ETA: this is what the first line looks like.

"E", 1, "100617", 1, " 1040", " ", " ", "002410 ", "100419", "1.010 SURNAME, GIVEN I. ", -1266.19

Great, thanks.

Because the first field is an 'E', this would be a 'Detail only' style import. So to get this into an Adagio Ledger batch, you would go to File / Import / Batches / Detail only in order to load the template. There could be more than one that can be selected from the top of the screen.

From here, the template will contain the path to the Easy Pay file you want to import. The second tab will contain the field layout, which is supposed to match the file layout you indicated above. What you posted looks like the same as the Default layout.

So to start with, perhaps try going to the Detail Only area for importing batches and perhaps there is a template already set up to bring in the Easy Pay files.

If the default layout is used, then the 5th and 6th fields contain the account and department codes. Based on this first record, that would be account 1040 and no department. Is this a valid account?

I tested the default Detail Only template against a file that looks like yours, and it worked with no errors.

Hey! Looks like I figured out my problem. The Account/Dept codes that I was using had been deleted and the journal entries had not been updated. I would have figured this out had I not been told that no G/L Accounts had been deleted in recent times. Oh well, at least it's working now. Thanks!