Print and Merge Customers

Once the list of customers to merge has been generated in Build Merge Customer List or in Customers To Merge, this option can be used to print the merge report, and to complete the merge process.
This utility can be accessed from Customers To Merge by clicking on the MERGE button, and then requesting the list to be merged.

If there are "Duplicate Invoices" for the two customers to be merged, the last character in one of the conflicting invoices is automatically changed to a number or letter in order to allow the merge to proceed.
If there are "Duplicate Checks" for the two customers to be merged, a default 'MRG######' value will be used to differentiate between check numbers.

The merge log is generated with the From and To customer numbers and if there are duplicate document numbers the report lists the "From Doc#" and "To Doc#" when it has to rename one of them to complete the merge.
Confirmation is required to proceed with the merge action.

If there are errors a message displays on the screen, and the errors are noted on the report with the customer numbers.
Errors caused by "Duplicate Info in Bad Debts File", print the write-off numbers on the report. This means that the customers to be merged, both have a record with this number on the same date, that prevents their merging.
If this error occurs, call Texada Support for assistance in completing the merge process.

If there are no errors on the report, the operator is asked to confirm the request to merge the customers, and to assign a credit rating code for the "old" customers. If the "old" customer numbers are not to be used anymore, then the credit rating should be set to a code that does NOT allow activity.
When this is accepted:

• All contracts, invoices, reservations, etc., are transferred to the new target customer number.

• The posted A/R invoices, payments, and customer purchases totals, are also transferred to the new customer.
  Unposted transactions will not be transferred.

• Contacts, follow up records, and profile information, logged in Customer Contact Information will also be moved to the new customer record.

• If Finance Charges on the same date exists for both customers, they are merged by adding the two dollar charges together and displaying the results as a single Finance Charge transaction for the Merge To customer.

• Because customers cannot have duplicate check numbers on the same date, a duplicate check number for the "From" customer will automatically be renamed to 'MRG######' in order to complete the merge and this will be reported on the 'Customer Merge Report'.

• A 'Duplicate Site Numbers' warning is generated with the Site numbers that could not be transferred because the "From" customer has a Site with the same number as the "To" customer.
  The Site for the target "To" customer will not be changed and the Site for the "From" customer will be deleted.
  To review the Sites before deleting them, accept the error log on the screen, and then abort the entire merge process.

• The credit rating for "old" merged customers is updated according to the rating selected from the drop-down list.

• A comment in Customer Information states that the customer has been merged, and advises to use the new customer number.

• The old merged customer numbers are displayed again on the screen, and are added automatically to Customers To Delete.

• The Delete Customer Report can be generated immediately , and the customers can then be deleted, or these customer records can be deleted later through Print And Delete Customers.

• If the Telematics processing has been activated in the Software Integration the service manager information defined in the customer's Superintendents window is transferred to the target customer, unless the same superintendent name is already assigned to the target customer and in that case the record is not transferred to prevent the original from being over-written.

Note: Special pricing is not merged and needs to be reviewed and updated manually, as the merge action could over-write the target customer's existing pricing setup.

Be advised that once executed, this operation cannot be undone.
Hence, prior to running this request, verify in the play environment that the results obtained from running this operation are as expected.