Purpose: This page describes data value crosswalks and data element mapping for the migration of Invoice data from Aleph to Alma. This video from ExLibris provides instructions to complete the migration form that we need to complete prior to the automated migration of Aleph data to Alma. The decisions we need to make about invoice data migration are outlined on this page.
Crosswalks: Aleph code values to Alma code values
Payment Methods
The following tables describe the crosswalk of Aleph code values for key order data elements to the target Alma code value.
Next Steps
1. Review the list of Alma Payment Methods below to become familiar with them.
| Alma Payment Methods | Description |
| ACCOUNTINGDEPARTMENT | The payment method is determined by the institutions accounting department (Invoice in Alma cannot be defined as Pre-Paid with this payment method). |
| CASH | Payment is done using cash. |
| CREDITCARD | Payment is done using a credit card. |
| BANKTRANSFERS | Payment is done using bank transfers. |
| DEPOSITACCOUNT | Payment is done using a deposit account where the institution deposits money with the vendor in advance. |
| PREPAYMENT | Payment is transferred before the actual purchases take place. |
| SPECIALPAYMENT | Special payment as decided between the institution and the vendor. |
| ATTACHMENT | Payment method is described within the Attachment tab at the vendor account/Invoice. |
2. Decide which values to enable, decide on the "Description" labels that are seen by users, and choose a default value.
| Aleph Invoice Type | Aleph Description | Count (6/30/23) | Draft Mapping to Alma Payment Method |
| REG | Regular | 183,718 | BANKTRANSFERS |
| INT | Internal | 25,240 | CREDITCARD |
| PRE | Prepaid | 4,784 | PREPAYMENT |
| PRO | Proforma | 1,304 | SPECIALPAYMENT? |
| VOI | Void | 10 | ? |
| DEP | Deposit | 1 | ? |
*Default when not mapped is ACCOUNTINGDEPARTMENT