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.

AP Recurring Transaction shouldn't use the 'Warn for duplicate vendor reference' setting or use a separate setting such as by vendor but have a default on the setting

I had to change AP Preferences screen for the field 'Raise an Error On Duplicate Vendor Reference Number' to unchecked to allow the AP recurring transactions process to work without an error on vendor reference cannot be blank (vendor reference set to required).  Your software uses this setting for also AP recurring transactions when often they are duplicate vendor references based on the processing logic.  The parameter in AP preferences ' Raise an error on duplicate vendor reference' infers a message but still allow you to enter a duplicate vendor references, so why should AP recurring transaction use this parameter?   There is nothing in the help for AP Preferences related to this field I changed about recurring transactions in 4.2 version.

  • Guest
  • Dec 6 2014
  • Shipped
  • Apr 20, 2015

    Admin Response

    This has been fixed in Acumatica 5.1. The system will no longer give an error if processing recurring transactions.

  • Attach files
  • Gabriel Michaud commented
    20 Apr, 2015 01:17pm

    This issue has been resolved in Acumatica 5.1, released earlier this month. I just updated the status of the item to indicate it has been implemented.

  • Mae Church commented
    18 Apr, 2015 02:48pm


    Do you have any idea how long it will be before there is an option to use Recurring AP without necessitating turning off the Require Vendor Reference and Validate for duplicates flags in AP Preferences.  The user's are reluctant to use Recurring AP for this reason.  However, Recurring AP is a very valuable processing tool. I would like to tell our customer's when this may be fixed.  thank you

  • Gabriel Michaud commented
    18 Mar, 2015 07:03am

    Quick update: we're working on it.

  • Guest commented
    8 Feb, 2015 11:06pm

    Add a Sequence part to the AR Recurring Transaction process, or include a date-check to insure that the new recurring invoice has a date different than the 'matching' error created by the current process.  If you don't do this then the Recurring process makes the validation process unusable.

  • Gregg Mercede commented
    30 Jan, 2015 04:59pm

    BTW, we autosequence the payment reference number on the A/R side when using Generate Payments...why is this any different?

  • Gregg Mercede commented
    30 Jan, 2015 04:58pm


    Why not autosequence the vendor reference number.  Or disable the check for bills created from status Scheduled.

  • Gabriel Michaud commented
    10 Dec, 2014 07:56am


    When you enable "Raise an error on duplicate vendor reference", the system does not allow you to save the AP Bill if the number is duplicate. If you are able to save anyway, it's not normal. If you want to use recurring transactions - you need to disable this setting. The system will still warn you if you try to enter a transaction manually, but will warn you of any duplicate bill number.