Avalara told my customer it was their fault they had too many pings (they did NOT have address validation or anything else turned on). When the customer asked them what the could do to reduce pings in sage this is part of Avalara's reply:
3. Regarding the HIST concern; we checked the details and found that the "HIST" suffix at the end of an invoice number typically indicates that the transaction is part of the historical data or history. It generally means that the invoice has been finalized and is no longer active in the current period but has been archived for record-keeping purposes.
This can happen when the invoice has been processed, and the system marks it as part of the historical record for accounting or reporting. The "HIST" is essentially a tag that differentiates historical transactions from current, active ones.
To prevent "HIST" entries from being generated in Sage 100, you will need to adjust certain settings or processes within the system, particularly around how transactions are handled and how they move from active to historical status. Here are some steps you can consider addressing this:
a. Check the "Automatic History" Settings
Sage 100 often moves transactions like invoices into history automatically based on your period end or system settings. To adjust this:
Navigate to the Modules section where the invoices are generated (e.g., Accounts Receivable, Accounts Payable, or Sales Order).
Review the settings for posting to ensure the system isn't automatically creating historical records when invoices are processed.
You may need to disable or modify automatic processes related to history generation, such as automatic period-end processing or invoice history settings.
b. Period-End Processing
If the system is set to automatically move transactions into history during period-end processing, you might need to:
Disable automatic period-end processing or change the frequency. This can be done by navigating to the Period-End Processing settings and adjusting how often or when the system should archive transactions.
c. Check the Invoice History Option
Some versions of Sage 100 have options that can be enabled or disabled for keeping records in history:
Access the "Company" settings or System Configuration in the setup menu.
Look for options related to archiving or retaining invoices in history.
Adjust the settings to either prevent or delay archiving based on your needs.
d. Adjust Reports or Data Purging Settings
In some cases, reports or data purging settings might cause transactions to be marked as historical prematurely.
Check your data retention policies in the system configuration.
If you're running regular reports that pull data from the history file, you can adjust the parameters so the system doesn't automatically shift data to history too soon.
------------------------------
Kelley Johnson
Kelley Johnson Consulting
------------------------------
Original Message:
Sent: 07-07-2025 16:38
From: Wayne Schulz
Subject: AvaTax - unexplained high API calls from Sage 100
Same experience as Kelley.
Additional:
- The Avalara representative appeared to convince the customer they "needed" a Walmart connector which was installed but never explained to the customer exactly why/how it was used/needed.
- We though Visual Integrator jobs might contribute to increased transaction count
- Avalara didn't seem to understand why/how this could happen and the TLDR is the client negotiated with Avalara for a credit
I walked away with the belief Avalara didn't really know what made up the transaction count and unsure why this burden should be placed on the client
------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------
Original Message:
Sent: 07-07-2025 16:14
From: Kelley Johnson
Subject: AvaTax - unexplained high API calls from Sage 100
I had a customer complain about this as well and had much communication with Avalara and all their answers to my customer's questions were beyond ridiculous and completely inaccurate. Jon at DSD was very helpful and this is my understanding:
- Validating addresses or turning on enable ship to by sales order detail will add pings
- By default, in SO entry you will have 2 pings – one when you click the total screen and when you save it which pushes it to history which is the HIST ping you will see in Avalara
- If you change the lines, qty, add or subtract lines, then it pings every time you make changes.
- When you invoice the order, the same thing applies in data entry with pings
- When you print the Invoice sales Journal it pings as committed and then when you update the sales journal it pings as committed to posted
------------------------------
Kelley Johnson
Kelley Johnson Consulting
Original Message:
Sent: 07-07-2025 15:41
From: Bob Pfahnl
Subject: AvaTax - unexplained high API calls from Sage 100
Address Validations are controllable and trackable in their system.
Invoices are controllable and trackable, yet are creating unexplained API calls.
Orders are not trackable.
Certificate activity is not trackable.
Bob Pfahnl
Sent from mobile
| | | | | Sr. Business Analyst (GM Silicon Valley) |
|
|  | |
|
| |
|
|
Original Message:
Sent: 7/7/2025 3:17:00 PM
From: Beth Bowers
Subject: RE: AvaTax - unexplained high API calls from Sage 100
I had a client with this issue right before MOTM, but it MAY have been their fault because they were new to it and had ended up validating every customer in their customer file or some such thing. I have not heard from them that it's a continuing issue.
------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989