Error in AR Repetitive Invoice Entry

If we edit or add a line to an existing repetitive invoice we get an error:

Error 88: Invalid/unknown property name

O/S Error: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index (err/ret=2/0)

Program: SY_AVATAXCOMMON.PVC

State: 307

Class: SY_SalesTaxCalculation_bus

Method: ReadAvaTaxDetail

  • 0
    Any ideas?
    Sage support don't want to touch it since it says "AVATAX".
    Avatax are not responding and I've been waiting on their support line for a long time.
  • 0 in reply to 49153
    Unfortunately, Sage Support could not assist because it is not a Sage program, code could not be viewed and the only information in the Sage Knowledgebase refers to a recommendation to contact the manufacturer of the custom code, Avalara.

    I would recommend contacting your Sage Partner or Reseller regarding the error in the 3rd party program.

    You could also post on Avalara's forum in addition to contacting Avatax Support, here was a similar error from their forum: (but related to importing invoices not entering them)

    Question: Sage 100 receiving an error while attempting to import a batch of invoices into Sage 100 but it is receiving an error: Program sy_avataxcommon.pvc line 0297. It is preventing the upload of the documents.
    Answer: This happens when a transaction is imported via V/I that has either an invalid zip code, or country code. Fixing the address on the import will resolve.

    help.avalara.com/.../Why_is_Sage_100_Receiving_an_error_while_attempting_to_import_transactions?
  • 0 in reply to DGR
    That's all very charming.... but at the end of the day we cannot process monthly billing and Sage is failing us.
  • 0 in reply to 49153
    I can certainly understand your frustration since you cannot do your work.

    Avatax is having trouble due to bad data that is causing the error in Avatax ReadAvaTaxDetail process.
    Maybe you can locate the bad data in the AR data needed for the invoices in one of the fields linked to Avatax, possibly in the User Defined Fields added by Avatax?

    Your Sage Partner may be able to coordinate with Avalara to find out what data fields could contain the bad record that is causing Avatax to fail if you are not getting through to Avalara Support.
  • 0
    I have a client that is getting this error. What version are you on? It appears to happen to a range of zip codes, in this case all the ones we tested are in Tennessee, other zip codes are fine, just not ones in Tennessee.
  • 0 in reply to VanMan
    Sage 100 Advanced ERP 2015 (5.20.1.0) and Avatax connector 5.20.1.0||07.0
    These customers seem to be MO, strange you may be on to something.