Bulk transfer for Income Management 101-09010070
For Account Management Team staff only
This document outlines the process when completing a bulk transfer of customer deductions from one business to another business, or service reason to service reason within the same business.
Completing a bulk transfer for Income Management
This table describes the steps for the Account Management team to action a bulk transfer from one business to another, or from one service reason to another for the same business.
Step |
Action |
1 |
Check the criteria + Read more ... Check for the following criteria:
If all of the above criteria been met, go to Step 2. Otherwise, approval from the Deduction and Confirmation Branch - Business Design Team is required:
|
2 |
Access the gaining business’ record + Read more ... Go to the Org Service Contact Summary (OSCS) screen and check that the service reason to be transferred to is current. Is the service reason current? |
3 |
Access the record + Read more ... Access the losing business' record or the record the transfer is taking place if only transferring between service reasons:
Where deductions are being transferred between the businesses, or to another business record, both service reasons must be current. |
4 |
Transferring deductions + Read more ... A 'transfer to' section will now display. This shows how many linked customers are found on the losing record. If a change in:
|
5 |
Change in business CRN + Read more ... In the 'Transfer to' section:
The gaining business details will auto populate.
Note: the Senior Account Manager determines whether letters are required to be sent. For example, letters should not be sent to the customer for transfers to a new CRN for the same business. An export may be required where additional information linked to each customer needs to be confirmed or changed, for example, unique Account Reference numbers for each customer deduction. Is customer export required?
|
6 |
Customer export + Read more ... Customer export will send a Comma Separated Variable (CSV) file via email to the email address of the person conducting the transfer. Note: additional recipients can be included to receive the email. Positional mailboxes are listed in the dropdown menu for additional recipient to be added. Select Finalise to clear out of the business record. |
7 |
Email containing exported CSV file + Read more ... The Service Officer as well as any additional recipients selected will receive an email containing the exported CSV file. Open the attachment to review/make any required changes. Accepted changes include:
|
8 |
Transfer statuses + Read more ... The following statuses may be attached to a bulk transfer request at any time from the losing business’s record:
Go to the Organisation Bulk Deduction Transfer (OSTD) screen to clear out of the business record. Note: the transfer will not complete while in the business record. An email including a transfer report for the bulk transfer should be received within 24 hours. The report will advise of successful transfers as well as any failed transfers. If there are failed transactions, there will also be an attached Excel spreadsheet with details. |
9 |
Transfer outcome + Read more ... In all instances, ensure there is a DOC on all impacted records to ensure information is available at a later date and if customer or business contact is received following a transfer, information can be easily accessed. Transfer successful The email received will contain no failed transfers. To view details and check status for completion go to the losing business record. The request and history details of the bulk transfer are only visible from the losing business record. The transfer/updates will now be made to the gaining record. Do not remove service reasons until the bulk transfer has successfully finalised. Removal before the bulk transfer has successfully completed will result in all deductions to that service reason cancelling. Transfer unsuccessful If the transfer encountered errors, manual investigation will be required for the unsuccessful transfer. For details of error messages, see the Resources page.
|