DMBM115060 - Create charges by IT system: Create charge in SAFE: Issue charge notification for manual charges
The majority of this manual will be archived on 1 July 2024. If there is content within this manual you use regularly, email hmrcmanualsteam@hmrc.gov.uk to let us know.
For some charge and duty types the SAFE system issues the charge notification (see DMBM115020). For the other charges and duties the user, havinginput the charge details, will prepare a paper charge notification following the relevantguidance. Generally paper Charge Notifications will continue to be completed where thenotification includes a calculation of the amount payable or a lengthy narrativeexplaining the basis of the charge.
For those charge/duty types where a paper charge notification is issued, the user mustalso include a payslip completed to include the SAFE charge reference (see DMBM201800). Once the charge has been created in SAFE the usercan view the charge reference. The payslip is created by selecting the Print Payslipfunction from the desktop and cutting and pasting the required details.
Agent Copies
For those charge types where SAFE issues the charge notifications and agent details areheld on the Customer Account Record (CAR), a copy is issued to the agent. Interest chargenotifications are excluded.
Re-issue of charge notifications
For those charge types where SAFE has issued the original charge notification the usercan request a re-issue by using the function Maintain Charge. For those charge types whereSAFE has not issued the charge notification the originating office must re-issue manuallyand change the charge notification issue date and interest due dates (if appropriate)using the Manage Charge function.
Notification issued by SAFE
Charge notifications issued by SAFE will show a date of issue two working days forwardfrom the date the charge is created on-line.
Notification issued by charge raiser
It is important that the charge raiser, when inputting the date of issue of the chargenotification, ensures that the actual date of issue is correctly recorded. Local delays inpreparing the notification and non-working days, when post will not be issued, should betaken into account.