Define Zengin Alternate Payer Name Mapping Rules

Define alternate payer name mapping rules to identify Japanese customers during Zengin lockbox processing.

During standard lockbox processing, Receivables transmission formats use the customer account number to identify the paying customer. Because the Zengin system doesn't include customer account information, lockbox instead identifies customers by alternate payer name and, if defined, the customer’s virtual account number (VAN).

Use the Manage Alternate Name Mapping Rules page to map customer accounts, sites, and bank information to designated alternate payer names and VANs to identify paying customers during lockbox processing of Zengin receipts. The Zengin transmission formats ORA_ZENGIN_LOCKBOX and ORA_ZENGIN_LOCKBOX_VAN use all the customer information in the mapping rule to identify a customer, create the customer receipts, and process the receipt applications.

By default, a mapping rule must contain a direct mapping between an alternate payer name or VAN and a customer account number. You can optionally include a customer bill-to site, Zengin paying customer bank and branch information, and the remittance bank and branch information.

Note: You can only set up mapping rules for the customer accounts and sites you have access to for lockbox payments.

To define an alternate name mapping rule for Zengin lockbox processing:

1. Navigate to the Manage Alternate Name Mapping Rules page.
2. Click the Create icon to open a new row.
3. In the Alternate Payer Name field, enter the alternate payer name that identifies the customer.
4. If applicable, enter in the Virtual Account Number field the virtual account number that identifies the paying customer's bank account.
   To maximize successful matching, set up unique individual mapping rules for each combination of VAN, alternate payer name, and customer bank/branch.
5. In the Customer Account Number field, search for and select the customer account for this paying customer.
6. In the Bill-to Site field, select a bill-to site belonging to the customer account, if processing receipts for this bill-to site only.
7. In the Zengin Customer Bank Name and Zengin Customer Bank Branch Name fields, optionally enter the name and branch of the paying customer's bank.
8. In the Remittance Bank Number and Remittance Bank Branch Number fields, optionally enter the bank number and branch number of the remittance bank that clears receipts and processes the remittances.
9. Enable the Active option.
10. Save your work.

What to do next

After Zengin lockbox processing, any receipt without an alternate payer name mapping rule or customer information is created as an unidentified receipt. When you assign customer information to an unidentified receipt, this automatically creates an alternate payer name mapping rule for that customer account.

You can assign customer information to an unidentified receipt using either the Manage Lockbox Transmission ADFdi worksheet or the Edit Receipt page:

• In the Manage Lockbox Transmission ADFdi worksheet, for each unidentified receipt enter in the Customer Account Number column and, if applicable, the Customer Site column the valid customer information. When you resubmit the completed worksheet, this automatically assigns alternate payer name mapping rules to these customers.
• In the Edit Receipt page, open an unidentified receipt and either enter customer information or apply an open receivable with customer information. When you save the receipt, this automatically assigns an alternate payer name mapping rule to this customer.

Establish best practices to periodically review and update your alternate payer name mapping rules to reflect changes to customer alternate payer names and VANs.

You can use the Alternate Name Mapping Rules REST API to create a regular schedule for maintaining alternate payer name mapping rules for Japanese customer bank accounts. The Alternate Name Mapping Rules REST API provides bulk upload of alternate payer name mapping rules for Japanese customer bank accounts. The upload process verifies and updates existing rules, creates new rules, and deletes obsolete rules.