Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Ability to use longitude and latitude in project invoices to calculate taxes via Avalara

Dear partners and customers,

We need your feedback on whether this idea makes sense to you, and whether you are aware of a real business need to have this functionality supported in the system. It would be helpful if you can share examples of user scenarios that should be supported with regard to this feature.

Your input helps us prioritizing requests in the backlog. Thank you.


Idea: Construction projects could be performed at locations which have no address (for example, oil rigs). It should be possible to specify longitude and latitude information in project invoices and have these fields transferred to Avalara for tax calculation.

  • Ekaterina (Kate) Stepalina (Product Manager Project)
  • Aug 14 2018
  • Gathering Feedback
  • Attach files
  • Stefan Verwey commented
    10 Jun, 2019 07:41pm

    Hi Kate

    On the Customer Locations, can we please have the latitudes and longitudes?
    I will help and improve BI reports and dashboard reports.
    In the mobile phone industry with 64 000 towers in South Africa alone, does it make huge sense to have it there when the Acumatica user's staff visit each month a certain % of towers per month. Lastly, analysis reporting per region will also be a gained result.

  • Rick Bennett commented
    1 Feb, 2019 09:24pm

    @Anastasiya I would expect the lat/long would be stored with the customer master and their locations so when the sales order or whatever other screen loads it is prepopulated with that info.  The service module can also use the same functionality.

  • Michael Milligan commented
    30 Jan, 2019 10:22pm

    We just need to store the long/lat with the project for locations that do not have an address.

  • Anastasiya Obryvaeva Program Manager Distribution Team commented
    30 Jan, 2019 10:08pm

    Dear All,

    Could you please share what is the common way to put latitude/longitude in an order or in a shipment? Manually? 

  • Ron Fairchild commented
    30 Jan, 2019 09:57pm

    not all construction projects have a physical address or have a new address that would not be in the Avalara database

  • Guest commented
    26 Aug, 2018 01:14am

    Yes - this makes sense to me and will endorse this.  Not to hijack the thread, but I will say that adding Avalara company "locations" is equally important and far more widely applicable for more clients than the odd construction project requiring tax calculations.  

  • Michael Milligan commented
    22 Aug, 2018 05:16pm

    I am working with an engineering consulting firm.  They do soil testing for construction sites that often do not have a street address.  So in the project setup, the same customer works on multiple sites.  This engineering company often uses long/Lat to locate the site.   

  • Rick Bennett commented
    15 Aug, 2018 06:58pm

    Not only construction companies need this functionality but so do all companies that deliver and service rural areas.  Avalara will be able to calculate local sales tax rates if the latitude and longitude coordinates were used in rural areas instead of city, state, zip.  That's one of the many things that separates Avalara from other solutions.