Receiving Fails with eConnect Error 4612 "Invalid Account Index"

Receiving Fails with eConnect Error 4612 "Invalid Account Index"

Receiving Fails with eConnect Error 4612 "Invalid Account Index"

When submitting a Receiving transaction from PanatrackerGP, the transaction is rejected by eConnect with SQL procedure error 4612 from taPopRcptLineInsert. This article explains why it happens and how to fix it.

Symptom

The Receiving transaction submits from the handheld or portal, then fails. The failed-transaction details (or the error email sent from the portal) show eConnect rejecting the transaction with an error like this:

An error occurred performing the Receiving transaction.
eConnect rejected this transaction.
Sql procedure error codes returned:

Error Number = 4612  Stored Procedure = taPopRcptLineInsert  Error Description = Invalid Account Index

Node Identifier Parameters: taPopRcptLineInsert
POPTYPE = 1
POPRCTNM = RCV0000XX
PONUMBER = PO0000XX
ITEMNMBR = ITEM-0001

Related Error Code Parameters for Node : taPopRcptLineInsert
INVINDX = Note: This parameter was not passed in, no value for the parameter will be returned.

The key line is INVINDX not being passed in — eConnect needs an inventory/purchases account index for the line and doesn't have one.

Cause

The Purchase Order line for the item being received doesn't have a Purchase (inventory) Account assigned, and Dynamics GP has no default posting account to fall back on. Without one or the other, eConnect has no account index to send with the receipt and the transaction is rejected.

This most often shows up on newly set-up items: if an item was created without a Class ID, GP never populated its default GL accounts, so any PO line for that item has nothing to fall back to. It can also happen if the account assigned to the item is simply incorrect.

NOTE: If your Transaction Details also show a different error number alongside 4612 (for example, one referencing an active PO Approval workflow), that's a separate condition with its own fix. Address it separately — don't assume it's related to the missing account.

How to Fix

  1. In Dynamics GP, open the Purchase Order named in the error (PONUMBER) and find the line for the item named in the error (ITEMNMBR).
  2. Confirm that line has a Purchase Account assigned. If it doesn't, assign one directly on the PO line.
  3. If the item was recently set up, open its Item Card, assign it a Class ID, and accept the prompt to apply default accounts — this populates the item's default GL accounts, including the one eConnect needs.
  4. If you'd rather not fix it line-by-line, configure a default posting account in Dynamics GP so future POs fall back to it automatically when a line has none assigned. Ask your GP administrator if you're not sure where your company's default posting accounts are set up.
  5. Once the account is in place, resubmit the failed transaction — either from the Transaction Log in the Panatracker portal, or by submitting the receipt again.
IMPORTANT: Assigning the account in GP does not automatically retry the transaction. You still need to resubmit it from the portal after the account is fixed.

How to Prevent It

  • When setting up new items in GP, assign a Class ID and apply default accounts right away, rather than leaving it for the first PO or receipt.
  • Set up a default posting account in Dynamics GP so a PO line that's missing an account still has somewhere to post, instead of failing at receipt time.

Questions? Contact Panatrack Support.

Related articles