You might receive errors or have issues before, during and after the year end procedure. This article contains these errors or issues and the solutions.
We have divided the errors and issues according to before, during and after the year end procedure for your convenience.
NOTE: We have used collapse to make the content easier to read. You will need to click on each error or issue to expand and see more details.
Check below steps you can take to troubleshoot and resolve the issues before year end procedure.
Open batches message when trying to run year end
You might get messages as below about open batches.
Ensure all open batches have been updated. Refer to the step above "Update open batches and place documents on hold" for assistance with open batches.
There might be open batches for users that have been deleted. You will need to recreate these users so you can see the open batch under Open Batches screen. When you go to View...Open Batches, you will get message as below. Click Yes, for the batch to be copied to current user. 
Once the batches has been copied you can access these and update or delete the batch.
CAUTION: If you delete batch for documents e.g. tax invoice, you still need to update the documents batch to clear the open batch message.
Deleting batch files from the company folder
If you still get the error you can delete open batch files for cash book batches, journal batches and inventory journal batches from the company folder as per steps below.
For POS open batches, ensure all open batches have been updated. Refer to the step above "Update open batches and place documents on hold" for assistance with open batches. If you still get error, there might be POS documents that are on hold or COD. To update documents that are On Hold and COD transactions do the following:
CAUTION: Please ensure you deselect this after updating the POS open batches for the user.

Follow steps below to access POS COD or On Hold transaction and update it.
CAUTION: If the documents do not show after clicking Edit, close the Search screen, click on <F9> On Account, select customer account with on hold or COD document as per report above and the click Edit. If there is more than one customer you will need to do this for each customer account.

If the error persists it could be due to corruption in the General Ledger Parameter file. The errors can be fixed via Data Fix. The Data Fix can be done by a Certified Pastel Dealer that specialize in data fixing or Log a ticket with support for assistance to upload the data for a Data Fix.
The first thing is to ensure that you are selecting the correct filters when running reports to check if inventory count quantities were updated correctly.
We recommend that you print the count variance report when processing count variance. You can print the count variance report from the Count Inventory Assistant.
NOTE: Ensure you select all items and all store when printing the report.
The report will show as below with the count variances. These are the quantities that will will show on the Inventory History Item Sequence report under Transaction Type Inventory Count.
NOTE: A variance of 0.00 will not be posted.

Also take note of period and date that you wish the quantities to be adjusted in. This is the date that you need to select when viewing the Inventory History Item Sequence report to check if quantities were updated.

Next you will need to view reports after processing count inventory.
You will need to view the Inventory History Item Sequence report by going to View...Inventory...History...Item Sequence menu option to check if adjustments were processed and updated. You can print the report using the options as illustrated below.

The report will display as below with the quantities that showed on the count variance report.
NOTE: If the variance was 0.00 on the count variance report no transactions are posted and will not show on this report.

If the inventory count transactions are showing, you will need to view the Inventory Activity Summary Report by going to View...Inventory...Activity Summary menu option to check if adjustments were processed and updated in the correct period. You can print the report using the options as illustrated below.

The report will display as below with the adjust quantities for each period. You can drilldown to get more details.

If the inventory count transactions are not showing, you will need to clear the snapshot and run stock fix.
Refer to article How to use the stock fix utility? for steps on how to run stock fix.
After running stock fix successfully, you can reprocess count inventory again. If you still have issue Log a ticket with support for further assistance.
When running the Data Integrity, you may receive an error report showing errors e.g Verify Balances and Transactions.
If you get the error that there are missing accounts as shown, you will need to recreate the missing customer, supplier or general ledger accounts. After having created the account, run the data integrity again because, the process was stopped when the missing accounts were detected.

The errors can be fixed via Data Fix. The Data Fix can be done by a Certified Pastel Dealer that specialise in data fixing or Log a ticket with support for assistance to upload the data for a Data Fix.
Runtime error 6149 or runtime error -2147417848(80010108) when creating Period 13 under Setup Periods
These errors sometimes occur when the dates for the periods are selected from the calendar. You can try entering the dates manually, i.e., typing them in physically, instead of selecting the date from the drop-down calendar.
If the error persists it could be due to corruption in the General Ledger Parameter file. The errors can be fixed via Data Fix. The Data Fix can be done by a Certified Pastel Dealer that specialise in data fixing or Log a ticket with support for assistance to upload the data for a Data Fix.
Financial periods are not compatible with the Tax Manager when trying to setup 13th period
Changes made to the financial periods are not compatible with the Tax Manager when trying to setup 13th period
Should you wish to change your Financial Year and getting the below error when you are busy changing your periods you would need to Log a ticket with support for assistance as the solution will differ for each company.

Check below steps you can take to troubleshoot and resolve the issues during year end procedure.
The number of This Year Periods and Last Year Periods are not the same
The error can come up for example when you have 13 periods under last year and the dates for 13th period last year is same as first period this year. You will need to Log a ticket with support for further assistance.

This error will occur when running the Year End over a network or there are missing files needed to run the Year End.
NOTE: Make sure you run the Year End for the server machine.
To check if the company is accessed locally:
C:\Pastel19

If you are running the year end on the server and the error occurs then, please follow the steps below.
Create a copy and run year end on the copy company. To create a copy company, please follow the steps below.


These errors occur when something is blocking the Year End process.
To check if the company is accessed locally:
Permissions on the Company folder:
![]()


Full Control added to the Pastel folder:
![]()
![]()


Runtime Error 5 When Opening a Company
This error occurs when the company folder name exceeds 8 characters or there is a special character in the company folder name
To check the Company Folder Name:
![]()

Correcting the company folder:
![]()

Runtime Error 6
Please follow the steps below to resolve the error
Rebuild the ACCTRN.DAT, ACCMAS.DAT and ACCOI.DAT files through the Rebuild Utility.
Refer to article How do I rebuild a Btrieve file using the Rebuild Utility on how to
If the error persists after the rebuild, please run a Data Integrity test
If there are any errors on the Data Integrity, the data needs to be fixed by our Data Fix team. Log a ticket with support, the turnaround time is 24 to 48 hours excluding weekends and holidays from the time the data is received.
NOTE: No processing can take place while our team is fixing the data.
If there are no errors, please follow steps below
![]()

NOTE: This Copy Company will be the ccompany that will be used to do the Year End. Please ensure this folder name is appropriate for the new financial year.
Check below steps you can take to troubleshoot and resolve the issues after year end procedure.
Incorrect financial periods
You need to restore backup that was done before processing the year end and process year end again.
Follow the steps below to restore backup.




Errors detected on Data Integrity
You need to restore backup that was done before processing the year end and process year end again.
Follow the steps below to restore backup.




If there were no errors before running year end but errors are being detected after running year end again, Log a ticket with support for further assistance.
Year End ran in wrong company
This error normally occurs when the client select the option to create a new company and forget to tick the option to run the year end in the new company.
During the Year End process you have the options:
If the Year End has been run in the incorrect company you have two options:
NOTE: Ensure you select the option to Run the Year End in the New company.
EXAMPLE: Company A is called Demo2019 Company B is called Demo2020. The Year End was run in company A but it should have been company B. You will need to rename Demo2019 to Demo2020 and Demo2020 to Demo2019.