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.

Improve the way expense receipts and expense claims deal with taxes

1) The Tax Zone is determined from the Employee, and can only be overriden at document level. In a VAT context what really matters is where the expense was made, and not where the employee lives. This means that an employee working in more than one Canadian province would need to file multiple expense receipts. This is a true concern for them as their employees work in multiple provinces. I think that in this particular case, expense receipts (and expense claim line) should have a tax zone field. It can get defaulted from employee, but should still be overridable.

2) There is no way to control the taxable amount of expenses. Assume following scenario: you go to restaurant, and have a 100$ bill + 15% tax. You add 10$ for service (which is always exempt of VAT), giving 125$ total charged to your credit card. The only way to handle that is to split the expense claim in two lines, one that is taxable, and one that is exempt. A simple solution could be to have a "Taxable Amount" field with the expense, however this wouldn't cover every single scenario - in Quebec there's more than one VAT tax applicable, and some products like books are PST exempt but not GST exempt.

  • Gabriel Michaud
  • Mar 5 2015
  • Shipped
  • Attach files
  • Admin
    Feedback Admins commented
    September 20, 2018 11:17

    Shipped long time ago (should be available in 2018R1/2018R2).

  • Amir Friedman commented
    March 16, 2015 20:52

    Having read your email again, I’d like to clarify that, in this scenario, the use tax has already been paid as part of the amount on that line, so it should be extracted from the total amount and debited to the liability account set up for that use tax code.

  • Amir Friedman commented
    March 16, 2015 20:48

    Ideally we’d be able to select the tax code; the system can then calculate the amount based on that code’s setup. The code would obviously also determine whether it’s sales or use tax.

    I believe that this approach would be less error prone than letting the user enter the tax amount.

  • Gabriel Michaud commented
    March 16, 2015 20:43

    Amir, in this context, do you need to be able to specify the amount of use tax per line, or simply whether there should be use tax to pay or not?

  • Amir Friedman commented
    March 16, 2015 15:41

    Another challenge is accounting for Use Tax paid as part of the expense amount (if the item is to be used in-house, as opposed to purchased for resale).