A5.24 : Duplicate Document Number Error when save transaction

Question:

Why can’t I save new payment voucher? There is a message prompted “Duplicate document number: “PV-000017” (if document number is auto generated, please check Numbering format’s Next Number.)”

Possible Reason:

This indicates that the document number PV-000017 is already used.

As document number is unique, it will not allow to have duplicated number. 

 

Solution:

1) At Cash Book Entry grid, click on Doc.No. to sort, and check the last used PV number. The last PV number was PV-000022, so you should change the next number to 23.

2) Go to Master Data(1) > Numbering Format(2).

3) Click 'Edit' on Payment Voucher numbering format and change Next Number to 23 and Save.

Now you should be able to save the Payment Voucher. 

--Source from AutoCount Wiki --

• Related Articles

• A1.10 : Save Invoice error - 'Invalid account no'

  Question: When I try to save a new invoice, an error message 'Invalid account no' prompted? why I couldn't save a new invoice? Version: 1.8 / 1.9 / 2.0 Possible Reason: 1. Sales Account No is not defined. Solution: There are 4 places you may assign ...

• UBSA1.2 : Access UBS (Accounting): Error: 'This transaction has been locked in Access UBS'

  Description : Access UBS (Accounting): Error: 'This transaction has been locked in Access UBS' Environment : Access UBS Accounting Solution : To resolve the locked transaction error message: Go to Housekeeping, Administrative Tools, Tools Select ...

• A5.81 : Accounting - Reports : Journal of Transaction

  This function allows you to generate Journal of Transaction report. Journal of Transaction is used to show double entry posting of each transaction by journal type. It has a built-in function to search for specific document number or key word if ...

• A1.117 : Prompted Message: Error during upgrade to 2.0-Invalid Data Definition Language Statement, error message is Violation of PRIMARY KEY constraint … The duplicate key value is (CR Default)

  Question: When upgrade database from 1.9 to 2.0, error message prompted “Invalid Data Definition Language Statement, error message is Violation of PRMIARY KEY constraint … The duplicate key value is (CR Default). Why? After clicking OK, another ...

• UBSA1.163 : Access UBS (Accounting): Error: 'Transaction no. missing'

  DescriptionError- Transaction no. missing appears when running a scan batch. EnvironmentAccess UBS (Accounting) Solution To resolve this issue follow the below steps: Go to Housekeeping, then File Organization. Select Mark All. Click Ok. --Source ...