Employee EFT Import Scenario

The “<Line Number> = -1” is a command to insert a new line. “<Line Number> = -2” is a command to delete a line.

<Line Number> = 1 is not a command to update line 1. I’m sure we’ve all made this mistake at one point. 

So, if you are adding 4 rows on a record you need to have the command “<Line Number> = -1” 4 times in your import scenario, each right before the appropriate values.

To Update a specific line that already exists, you need to use the @@ command.

@johnythevara48 Go back to @@DetailID. That's the documented way to update Payment Instructions, and the Employees screen exposes the same custom key you already saw.

The mapping is a pair of rows per instruction: @@DetailID with the ID, then Value with your source column. Three things have to be true or it misbehaves:

1. The value in @@DetailID is the ID column from your EFT payment method on Payment Methods (CA204000), Settings for Use in AP tab. It's a string, so ='1', not =1, and not the description or the grid position.
2. Commit is checked on every @@DetailID row.
3. The <Line Number> = -1 row the system adds under the first @@DetailID stays in the scenario, but with Active cleared. Left active, it inserts a new row instead of finding the existing one. That's the "cannot be empty" error in the vendor thread below.

Your current version picks rows by position with <Line Number> = 0, 1, 2, 3. That only works if the grid order matches your source exactly, and it isn't what the help example uses.

Acumatica's worked example is for vendors, but the mapping is identical: Importing Payment Instructions (Vendors). A Canadian EFT version with a screenshot of the finished mapping is in this thread.

Run it against a test tenant first. Each record ends with a Save on the employee.

Thank you. I have already updated the Vendors with @@DetailID and that is where I started for Employees. I will try that again.