PTP Important Known Issues

It is important to us that we resolve any problems that are found in the PTP Software.

If your problem is listed below, we are working hard to resolve these as quickly as possible.
Issues that have been fixed or are due to be fixed in the next release, are identified as such.
For information on the next release dates, click here.

PTP Accounts Production
PTP Tax Platform
PTP CT Platform
PTP Tax Expense
Microsoft Windows 10


PTP Accounts Production

Resolved Issues

‘Xero Import Authentication’ screen unresponsive when linking client from Xero to Accounts Production
Where 2 factor authentication is enabled in Xero some users are reporting issues linking Xero to Accounts Production.

Xero Import – brings back wrong period
When importing from Xero the trial balance returned is always that of the latest period rather than the period which has been selected.

Electronic Submission to Companies House – number of employees – Limited Companies
As of 13/10/2020 Companies House will be validating the 'average number of employees' note on all electronic submissions of statutory accounts.
This disclosure is now mandatory. Currently if the note is replaced using the 'additional/replacement' note, the submission will fail with the Error code 9999.

Electronic Submission to Companies House – number of employees – Incorporated Charities
As of 13/10/2020 Companies House will be validating the 'average number of employees' note on all electronic submissions of statutory accounts. This disclosure is now mandatory.


PTP Share Register

Issue resolved in the Autumn 2020 (20.3.11) release

Made up to dates – extended
When importing clients from Companies House into PTP Share Register there have been reports that the incorrect date is appearing in the Next CS/AR made up to field.


PTP Tax Platform

Outstanding Issues

Dividend database issue
It has been reported that, in some cases, there appears to be an issue with the Dividend Database service in PTP Tax Platform.
The issue affects individuals' SA100 Tax Returns only, the Partnership and Trust & Estate Tax Returns are unaffected.

When the dividend data entry schedule is accessed in the 2019-20 SA100 tax return, any existing 2018-19 dividend sources are brought forward, and the 2019-20 dates and values are applied. However, we have identified an intermittent mapping problem with the data and as a result, whilst the software will show the correct dividend company name, the dividend payment dates and values may not be correct for that company.

The issue also affects dividends that have been manually added to the dividend database. This will manifest itself by adding dividend payment dates and/or dividend amounts that cannot be reconciled to that source.

In addition, we have identified that earlier years’ dividends may also be affected by this issue (confined to 2017-18 and 2018-19) Therefore, when reviewing or re-printing an earlier year’s return, you may experience this issue. Please contact a member of our Support team if you think you may be affected.

We included some additional checks in from the Spring 2020 Service Pack release (v20.1.398) onward, which will display a message where a discrepancy is detected in the data. However, these additional checks may not cover all scenarios. Therefore, where the system has identified a potential issue with the data or where you believe you may be affected, we would recommend carrying out the following actions:

  • please review your clients' dividend entries against supplied vouchers or brokers' schedules, and where you believe they may be affected by this issue, delete that company and then re-add it. This will correct the issue and import the correct data.
  • where companies have previously been added manually, delete and re-add the source and data. This will correct the issue and retain the values entered.
  • where a client's SA100 is in any FBI state, please review the return and, where necessary, remove the FBI status and apply any corrections as detailed above.
  • where a client's SA100 is in any FBI state, please review the return and, where necessary, remove the FBI status and apply any corrections as detailed above
  • where a client's SA100 has been submitted to HMRC, please review the return and, where necessary, remove the FBI status and apply any corrections, as detailed above, before submitting an amendment to HMRC

For more information, click here.
We apologise for any inconvenience this issue has caused.

SA105 – Refresh issue for edited Number of Properties field
This issue affects returns where the Number of Properties automatic field value has been overridden using the Edit option. When viewing the UK Property forms after editing the value, instead of displaying the edited value it will display the number of properties from the most recently viewed return. If no UK Property have been viewed since opening the software, then the field will populate with zero.
Workaround
View the UK property pages immediately prior to preparing the return for online submission and enter a valid number of properties in the field at the top of the UK Property screen.
This issue is due to be fixed in the Spring 2021 release.

SA100 – Capital losses not correctly reflected on the supporting CG schedule
Carried forward capital losses are not being reflected correctly on the Capital Gains and Losses Summary backing schedule.
Workaround
There is currently no workaround for this issue.
For more information, click here.
This issue is due to be fixed in the Spring 2021 release.

SA100 – Adding company to Dividend Database triggers an exception error
When attempting to add a new dividend company to the Dividend Database via the ellipsis button to the right of the Company field in the Dividend backing schedule for box 4 on page TR 3 an exception error is displayed.
Workaround
Add a dummy Trust return and add the new company via the UK Dividend companies backing schedule on Page 5. Run the recalculate dividend option via the Maintenance (Spanner) | Dividends tab and the added company will then be available to select from the list in the SA100.
For more information, click here.
This issue is due to be fixed in the Spring 2021 release.

SA103S – Negative entries not being displayed
The Self-employment data entry will automatically determine whether to output the full or short SE pages depending on the entries made. Where negative entries have been made in the fields that allow this then those negative values will not be reflected in either the printed SA103S or in the submission file resulting in pre-filing validations.
Workaround
It is possible to force the SA103F full SE pages via an option in the Business Details tab of the Self-employment data entry form which will cater for the negative values.
For more information, click here.
This issue is due to be fixed in the Spring 2021 release.

SA100 – Incorrect state pension age validation in later (2021) tax year
If the taxpayer reached state pension age during 2019-20 an next year’s tax return is being completed in advance then an incorrect validation is being displayed when state pension details are added stating that ‘You have entered state pension in box TR3/8 for a man/woman less than state pension age’.
Workaround
The warning message can be ignored.
For more information, click here.
This issue is due to be fixed in the Spring 2021 release.

SA100 – Class 4 NIC liability not included in the tax calculation
In a previous release (20.2144) we resolved an issue where Class 4 NIC was being suppressed in the tax calculation based on incorrect date of birth criteria. However, despite the fix the Class 4 NIC may still not appear in the tax calculation where the liability is related to a Partnership or Lloyds Underwriter income.
Workaround
The workaround is to view the Partnership or Lloyds Underwriter supplement prior to running the tax calculation.
For more information on this issue, click here.

General – Unable to collect FBI responses where Govt. Gateway password contains an apostrophe
HMRC have introduced password hardening as part of their security improvement, which includes an expansion of supported characters, and the PTP products have been updated accordingly. However, we have found that if your new or updated Govt. Gateway password contains an apostrophe then where the FBI option to ‘Collect responses later’ is selected then this will result in the return submission not being recognised on the HMRC server when polling for a response. This option is only available when submitting via the FBI option in the program tool bar.
Note: You should still receive the HMRC confirmation e-mail, but the acceptance or rejection will not be reflected in the software.
Workaround
Either deselect the FBI ‘Collect responses later’ option when submitting returns or avoid using apostrophes in your Govt. Gateway password.
For more information, click here.
This issue is due to be fixed in the Spring 2021 release.

Issues resolved in the Winter 2021 (20.315-0) release

Tax Platform & CT Platform - Software not accepting manually entered dates beyond 31/12/2020
During the FBI process, when entering the date a client signed a return, the software is not accepting any dates after 31/12/2020. This is under investigation by the Development team.
Workaround
Leave the date blank and click Update Client.  The software auto populates the date with today’s date and allows the submission to proceed. 
Note: This date is not reported to HMRC and is recorded internally in PTP only.
For more information, click here.

Issues resolved in the Autumn 2020 (20.3.144-0) release

SA100 – Issue with reducing Payments on Account
Where the SA102 employment supplement has been completed and associated Foreign Tax Credit Relief has been claimed on page F 6 of the SA106 Foreign supplement then an attempt to claim to reduce the payments on account on the Tax Calculation Summary supplement is not correctly reflected and PoAs are reduced to nil .

General – Online filing Error 1046 due to HMRC Government Gateway password hardening
In the rare situation where it may be necessary to reset the existing Government Gateway password and that password is subsequently updated in the PTP applications (part of the FBI credentials) then it is possible that you will receive a 1046 error when you attempt to submit an online tax return.
This is because HMRC now allow a much broader range of characters than before when compiling your password and some of these characters are deemed ‘illegal’ by the PTP applications and are consequently stripped from the submission file ahead of filing. This results in the error 1046 authentication failure.

Issue resolved in the Autumn 2020 (20.3.56-0) release

SA100 – Refresh issue with data passed from SA800 Partnership return to SA104F supplement
Where the SA801 Partnership UK Property supplement has been completed as part of the SA800 Partnership return and the profit allocated to the partners, the partner shares for the property income is not included in the partnership income when running the tax calculation.

SA108 – Deleting an empty Captal Gains Summary supplement generates an error
Where the SA108 Capital Gains Summary supplement is added and subsequently deleted without adding any data then a Record is deleted error is generated.


PTP CT Platform

Outstanding Issues

FBI - Preparing FBI Files
A small number of users have reported problems when preparing FBI files for multiple returns at the same time.  This has manifested as pre filing validations indicating that numbers are not adding up correctly, or even as the number from box 155 or 190 appearing on the other return being processed at the same time.  This is intermittent but is currently being investigated. 
Workaround
The current workaround is to process one return at a time through the FBI process.
For more information on this issue, click here.
This issue is currently under investigation.


PTP Tax Expense

Outstanding Issues

Interest-free and Low Interest Loans Working Sheet – Incorrect validation
Where there are three or more loans in existence during the tax year and loan 3 is not in existence for the full year then a validation error will be displayed stating that no entry has been included for date loan made or discharged, despite the date being present.
Workaround
The workaround is to bypass the loan 3 column, where possible.
For more information on this issue, click here.
This issue is due to be fixed in the Spring 2021 release.

Issue resolved in the Autumn 2020 (20.3.56) release

Car and Car Fuel Benefit Working Sheet 2 – wrong rate applied for low emission car
When adding a 2021 Car and Car Fuel Benefit Working Sheet 2 for a car with CO2 emissions between 1 to 50 g/km then the appropriate benefit percentage is applied automatically. However, once saved, if the working sheet is subsequently re-opened the appropriate benefit percentage is incorrectly re-calculated to be 16%.

Duplicate rolled forward Car and Car Fuel Benefit Working Sheet 2 and/or 2b is showing calculated benefit
Where a 2020 Car and Car Fuel Benefit Working Sheet (2 and/or 2b) has been added manually for an existing 2019 car and the application’s Roll Forward option is subsequently run, a duplicate 2020 working sheet 2 and/or 2b is created based on the 2019 entries. This duplicate working sheet is showing a calculated benefit even though it may not have been accessed and finalised and is also being included on the P11D.