You can use a flex mapper to move data between PaymentNet and your organization’s accounting system, such as a general ledger (GL) or enterprise resource planning (ERP) system. A flex mapper is a data export file in a specific layout and format, usually a limited or fixed-length text file.
Flex mappers give you the option to set the mapper criteria by selecting fields from a predefined list. You can also use flex mappers to define the file layout and file format. You can manually run a flex mapper or schedule it to run automatically. Based on your organization settings, mappers either start processing at 7 p.m. ET or complete processing by 8 a.m. ET.
Whether you run a mapper manually or automatically, you can mark transactions as exported. Once you mark a transaction as exported, you cannot edit any information tied to the transaction and the flex mapper will not extract the transaction data again. This feature ensures that a transaction will not be fed to your internal system more than once.
For example, suppose you run a flex mapper for a billing cycle and request that only approved transactions be included in the output file. Those transactions that are not approved at the time the flex mapper is run will not be included in the file. When you run the same flex mapper again for the same billing cycle, the output file will provide you with only the transactions that have been approved since the last flex mapper run; it will exclude any previously exported transactions.
For flexibility, PaymentNet allows flex mappers to be shared with other program administrators within your organization. For more information, see Sharing Mappers.
This section explains the following: