A nine-digit bank code defined by the American Bankers Association (ABA) and used in the United States. The routing number is displayed on the bottom of a check and identifies the financial institution on which the check was drawn.
Accepted
The status of a supplier company who has agreed to accept Single-Use Account payables for a specific buyer.
Account
An individual credit card account that contains a record of financial transactions. The account contains the card account profile, including the current balance, available credit, hierarchy ID, credit limit, and address information.
Account Request Manager (ARM)
A tool that works with PaymentNet to assist in automating the end-to-end account creation and approval process. Using ARM, a user enters application information directly into PaymentNet. The application can then be routed through an approval process that allows up to three reviewers to review the information. Once approved, the final application is sent to the program administrator, who will then finalize the process and request a card for the cardholder.
A set of alphanumeric values that correspond to the internal entities, departments, divisions, and general ledger account codes for a company. PaymentNet has a custom accounting code system that can imitate your existing system with accounting code segments that you define and allocate to transactions in order to track spending. Accounting codes can be defaulted to new transactions based on set criteria that will help facilitate the allocation and approval process.
A financial institution or merchant bank (a merchant acquirer) that is contacted to authorize a credit card purchase.
Activity Pane
In the Payables module, a pane on the Vendor Details page that shows the activity with a vendor for the current year.
Addendum
Enhanced transaction detail information provided by a merchant; also referred to as addendum details. Cardholders can view this information (when it is available) by clicking the Addendum icon next to a transaction on the Transaction List screen.
The process of dividing transaction information into different lines of accounting so that costs are allocated to specific cost centers. Also see Splits.
The main component of PaymentNet used by program administrators to configure functionality for their organization. The configuration includes menu settings for hierarchy and its related features, chart of accounts, cycles, mappers, custom fields, customer code defaults, report setup, role setup, merchants, Merchant Category Codes, and Merchant Category Code Groups.
A type of search that allows the user to specify a complex set of criteria to locate accounts, employees, merchants, Merchant Category Codes, transactions, or payables. The search criteria for an advanced query can be saved as a custom query and reused. Also see Custom Query.
A hierarchy setting that determines the number of review and approval levels in the approval process for posted transactions. This approval workflow is typically done between the cardholder, who reviews the transaction, and their manager, who approves it. It can include additional approval levels when transactions exceed a specific amount. PaymentNet offers unlimited approval levels to promote accountability at various stages.
Audit Trail
See History.
Auditor
A user access role that identifies the person responsible for reviewing payments and processes for any abnormalities.
Authorization
An approval from a credit card association for a request to receive payment.
A credit card payment request that is settled by an automated process such that the vendor does not have to request authorization or "swipe" the card in order to receive funds; also known as AutoSettle or Straight-Through Processing (STP).
Banner Message
See Greeting.
Batch File
A text file used with Single-Use Accounts to communicate payment instructions, master vendor lists, and payment confirmations.
Begin Date
The date when a payable will allow authorizations. Upon reaching the begin date, the payable status will change to Open.
The period of time between billings based on the accounting needs of an organization. The cycle typically occurs 12 times a year for each client. Program administrators can select the day on which they would like to cycle (for example, the last business day of each month). Cycles can affect mappers and customized reports.
Billing Zip Code
The zip code associated with a purchasing card; the zip code associated with a buyer's corporate account and used to allow authorization of single-use accounts.
Buyer
The organization that is receiving purchase orders and sending a payment to the vendor.
Buyer Reference
A custom field (label and value) added to a payable to act as a unique reference number for a buyer. Changing the buyer reference field (by selecting a new custom field) or changing the label or value of a custom field will only impact new payables created after the change; existing payables will not be affected.
Card Number
The number provided by the issuer for use in a credit card association's payment network.
Card Settlement
The deposit of funds via the use of a commercial card account.
A three- or four-digit security code that is printed on the back of debit and credit cards. This code helps validate that a genuine card is being used during a transaction, especially in situations like mail orders, telephone orders, or Internet orders where the card is not present. Also called Card Verification Value (CVV) or Card ID (CID).
Card Verification Value
Category Code
See Merchant Category Code (MCC).
Central Bill
The consolidated billing statement issued for any of the credit cards that are attached to a central bill. It reflects the organization’s card accounts and the posted totals during the billing cycle. The use of a central bill allows organizations to make a single payment for multiple individual card accounts.
Certificate
See Digital Certificate.
A predefined accounting system that is compatible with an organization’s particular financial structure and is in agreement with the amount of detail required in its financial statements. A chart of accounts is made up of segments or groups that limit the specific accounting code values a user can enter. During implementation, an organization’s chart of accounts can be loaded into PaymentNet to contain the general ledger accounts, cost centers, and any other required fields. Also see Accounting Codes.
The entities in a hierarchy, which is a defined multi-level structure of parent and child entities. Multiple children can report up or roll up to a parent, and, in turn, parents can report up or roll up to a parent above them. There is no limit to the number of children hierarchies. See Hierarchy.
A simple file format used to move tabular data (numbers and text) between programs that operate on proprietary formats.
Comments
A buyer user's journal entries for payable and vendor details.
A unique number that is assigned to your organization by J.P. Morgan from the credit card processor. Also referred to as Bank Corp.
Complete Vendor
A vendor record with full information about the vendor, including the name, remittance address, email address(es), and Vendor ID.
Compliance Monitoring
Functionality that is used to track and monitor cardholder transactions by ensuring that they adhere to an organization’s card policy. It includes the ability to flag transactions when they are split by the merchant, exceed certain spending thresholds, or are used at questionable merchants or types of merchants.
Constraint
The link that a program administrator makes between specific charts of accounts and users. Constraints allow an organization to limit the chart of account values a user can assign based on hierarchy, role, account, or user ID. Constraints allow users to have access to the accounting code values they need, but at the same time restrict their access to accounting code values that are outside their scope of view.
Convenience Check
A check linked to the cardholder’s credit limit; it can be made in any amount, as long as it does not surpass a cardholder’s credit limit. Program administrators can give cardholders the option to manage their convenience checks, including allowing cardholders to order convenience checks and stop payments on existing convenience checks.
Cost Center
A defined area of business, such as a department, division, or unit of an organization whose managers are responsible for all direct and indirect costs.
Create Date
The date a payable is created.
Create Notification
A type of email notification that is sent upon certain types of events, such as when a payable is created, hits the begin date, or is revised.
Credit Limit
The maximum dollar amount for a card account. Also called Limit.
Custom Field
A field label and corresponding values that are defined for a specific implementation. Custom fields can be modified for each user access role in several categories across an organization, including accounts, employees, merchants, Merchant Category Codes, transactions, and payables. Transaction custom fields are typically intended for internal buyer use, and payable custom fields are intended for external use. See Payable Custom Field, Transaction Custom Field.
A set of advanced search criteria saved by a user for filtering a list of items in PaymentNet, such as accounts, employees, merchants, Merchant Category Codes, transactions, and payables. Custom queries are available only to the user who created them. Also see Advanced Query.
Customer Code
An identifier that indicates the industry a supplier is associated with and the specific business the supplier performs. With customer code information, PaymentNet can generate statements or invoices showing products and services aligned with that code.
CVC, CVV
Cycle
A customized billing structure for a period of time ending on the same date every month or having the same number of days. See Billing Cycle.
Days Payable Outstanding (DPO)
A measure of a company's average payable period; that is, a measure of how long it takes the company to pay its vendors.
Days Sales Outstanding (DSO)
A measure of the average number of days a company takes to collect revenue after a sale has been made. A high DSO implies that a company is selling a product (on credit) but waiting a long time for their cash (receivables).
Days to Process
A count of the number of days until the end date of a payable. See End Date.
Decline Reason
The explanation of why an authorization was declined.
Default Query
The query set by a user to be applied when first visiting any List screen in PaymentNet.
A form of electronic identification for electronic communications, serving to digitally authenticate that a message originated from the person whose signature is attached and that the message has not been altered, either intentionally or accidentally, since it was signed. The Single-Use Accounts API uses digital certificates to establish a secure connection between PaymentNet and clients, and to help identify the role and scope of the requestor.
Dispute
To call into question an incorrect charge on a card account. Disputes can be handled online through PaymentNet or through J.P. Morgan Customer Service.
Employee
Any user with a PaymentNet user access role, such as Card Holder, Manager, Auditor, or Program Administrator.
The date when a payable no longer allows authorizations. Upon reaching the end date, the payable status will change to Closed if it is not already closed.
Ending Payable
A payable that is going to reach its end date within the next 7 days. See End Date.
Enterprise Resource Planning (ERP)
A management information system that integrates areas such as planning, purchasing, inventory, sales, marketing, finance, and human resources.
Exception Status
An explanation of why a transaction failed to meet the criteria for the Included Total of a payable. A transaction may fail for multiple reasons; all reasons will be shown in the payable details. Also see Included Total.
Exclude Transactions
A status showing that a transaction has been excluded from the Included Total of a payable. Transactions can be excluded because they failed to meet the inclusion criteria or because a user excluded them by choice. Also see Included Total.
Expiration Date
The date an account is no longer valid.
Export File
A flat text file used to extract data from PaymentNet. Export files are typically used to export the transaction and credit card data out of PaymentNet and integrate that data into an organization’s financial system. Also referred to as a download file or mapper.
File Processing
A page in the Payables module that shows Payment Instruction Files and Master Vendor List batch files that have been processed in the past 30 days.
Fraud
Transactions made on a card or an account by a person other than the client or cardholder, who does not have actual, implied, or apparent authority for such use.
The percentage under the payable total that must be in the Included Total in order to consider a payable fulfilled. Also see Included Total.
Funding Account
The credit card account where settlement occurs for the single-use account tied to a payable.
Ghost Account
A purchasing account for which a non-working plastic card is issued. The card has a 16-digit account number, expiration date, and CVV code but no magnetic strip. It can be used to make purchases via phone or online. If used at point of sale, the card information must be key-entered instead of swiped.
Ghost Card
A credit card number that is provided to a vendor to cover all purchases made from that vendor by the buyer; also known as a Static Card.
An automated service that can be configured to post messages for employees. Program administrators use a hierarchy setting to define one or more greeting messages along with display start and display end dates. Greetings are directed to specific user roles and displayed in the Messages panel on the Welcome screen.
A pyramid-like group structure in which every group can have different access, permissions, and roles. PaymentNet supports a vertical limit of 25 levels deep and has no horizontal limit. A hierarchy allows organizations, departments, and users to have subordinate or parent-child relationships for access and reporting purposes. It does not need to match the company’s organizational structure, but can instead reflect how managers view and analyze transaction data. See Hierarchy ID, Children.
An identifier that represents an entity within the hierarchy structure. The hierarchy ID and its child relationships can be added, renamed, and moved, but they cannot be deleted. See Hierarchy, Children.
The list of changes that have been made to the details of an item in PaymentNet, such as hierarchy, account, employee, transaction, payment, or payable details; also known as the audit trail.
Import File
An external file that can be used to transfer data into PaymentNet. An import file can be used to create, modify, and in some cases remove or replace accounts, chart of accounts, employees, hierarchy, merchants, Merchant Category Codes, and transaction defaults.
Include Transactions
A status showing that a transaction is part of the Included Total of a payable. Transactions can be included because they meet the inclusion criteria or because a user included them by choice. Also see Included Total.
The sum of all transactions posted against a payable which have either met the inclusion criteria or been included by a user.
Inclusion Status
An indicator of whether a transaction has been included or excluded, automatically or manually. Options are Included - Auto, Included - Manual, Excluded - Auto, and Excluded - Manual.
Incomplete Vendor
A vendor record with a minimum of an email address used to communicate payment information.
A maximum dollar amount for a card account. Also called Credit Limit.
A credit card payment request that is settled by a person using a point-of-sale system. See Point-of-Sale (POS).
Mapper
An electronic file of transaction data originating from the issuer and interfaced with an organization’s financial management system, such as a general ledger or enterprise resource planning (ERP) system. This extractable data file is in a specific layout and format, usually a delimited or fixed-length text or XML file, for importing into internal accounting and reporting systems.
The act of applying an update or making a change to multiple items at one time, such as accounts, transactions, merchants, or employees within PaymentNet. For example, a mass update may include applying a modified chart of accounts to a specific department.
A list of vendor information that can be uploaded to PaymentNet in a CSV (comma-delimited) file format.
Matching Issues
A modifier indicating either that transactions posted to a payable have failed to meet the inclusion criteria, or that the Included Total is greater than the payable total plus any overage tolerance. Also see Included Total.
Merchant
A person or organization that provides goods or services to a buyer. Merchant information is provided by the processor at the time of transaction and comes from the acquirer. See Acquirer.
A four-digit number assigned to a business by MasterCard or Visa when the business first starts accepting credit cards as a form of payment. The code identifies the type of goods or services provided by the merchant.
Merchant Category Code Group (MCCG)
A group of related Merchant Category Codes (MCCs) defined by a program administrator. Using an MCCG can help control cardholders’ ability to purchase from particular types of merchants.
Merchant Details
A page in the Payables module showing the merchant details for a transacting merchant. Buyers may provide additional details for their own use or allow automated update when data is returned by the transaction.
Merchant List
A page in the Payables module showing the list of transacting merchants for an organization.
Merchant Name
The name reported from the merchant bank for a transacting merchant.
Missed Payable
A payable that has reached its end date and closed without being fully used. A missed payable can either be fully missed (meaning no transactions have been included) or partially missed (meaning at least one transaction has been included but the total is insufficient to reach the fulfillment tolerance). Also see End Date, Fulfillment Tolerance.
1.
An element within PaymentNet used to configure and manage aspects of a
card program such as transactions, employees, accounts, and so on. Modules
can be enabled or disabled by hierarchy by the program administrator.
Modules that are not in use by a company are disabled during the implementation.
2. Specific PaymentNet menu settings, accessible from the Administration
tab, such as hierarchy and its related features, chart of accounts, cycles,
mappers, custom fields, customer code defaults, report setup, role setup,
merchants, Merchant Category Codes, and Merchant Category Code Groups.
Notes
An editable field that can be used to communicate information about an account, employee, Merchant Category Code, transaction, payable, or vendor.
Notification
An email message that can be sent to notify a user when certain actions are complete or require attention; for example, completed reports, transactions awaiting review or approval, recurring payments, and bulk updates. For single-use accounts, an email notification can be sent to a merchant when a payable is created, activated, or modified, and can also be sent as a reminder to process a payment.
Notification Status
The status of a scheduled notification event.
Order Requestor
A role assigned to a PaymentNet user specifically to create and manage payables.
Order Status
The state of a payable using the older status terminology. See Payable Status, Payable Modifier.
Orphaned Transaction
A transaction posted to a single-use account which cannot be matched to a payable.
Overage Tolerance
The percentage over the payable total which represents the maximum amount that may be authorized for that payable. See Payable Total.
Page Banner
A hierarchy setting used to contain your organization’s logo or other graphic and customize the screen background color. The graphic and background color will display at the top of each PaymentNet screen.
Payable
A request for the issuance of a financial payment method, such as a single-use account, to settle a balance due. Formerly known as an Order.
A type of custom field typically intended for communicating to vendors.
Payable Details
All the information known about a payable. Also a page in the Payables module where payable information can be found.
Payable ID
A unique identifier in PaymentNet for each payable created for an organization (formerly known as Order ID). Buyers can provide this unique value when requesting a payable, or J.P. Morgan can create it upon processing the request.
Payable List
All payables belonging to the organization and hierarchy that a user can access. Also a page in the Payables module where payables can be queried, exported, and updated in bulk.
A summation of the state of the authorizations and declines for a payable or the transactions posted against a payable. Also see Payable Status.
Payable Request
A request to create a payable and assign a single-use account based on payment group criteria such as credit limit, begin and end dates, and Merchant Category Code Groups (MCCGs). Also allows additional information, such as custom fields, to be associated. See Merchant Category Code Group (MCCG), Payment Group.
Payable Slip
The section of the Payable Details screen where the payable ID, status, modifier, and action buttons reside.
An indicator showing the state of a payable and the single-use account assigned to it. Options are Created, Open, and Closed. Also see Payable Modifier.
The amount being paid, which is included in the credit limit applied to a single-use account.
The controls established for the creation and management of a set of payables. When a payable is created and a single-use account is assigned, the default settings for credit limit, daily transaction limits, and MCCGs are assigned from the associated Payment Group. Formerly known as Account Pool.
Payment Instruction File
A batch file used to communicate payable request criteria for the creation of payables.
A device used to request authorization of a transaction that leads to card settlement.
Post Date
The date a transaction posts to a credit card account.
Primary Contact
A person designated by a buyer or supplier to act as the contact for any issues regarding a payable. The primary contact can be assigned independently or inherited from parent to child hierarchies.
Provider
A person or organization that provides health goods or services to a buyer. Provider information comes from the providing business.
Purchasing Card
A form of company credit card that allows goods and services to be procured without using a traditional purchasing process; also known as a P-Card program.
Query
A request for specific information from PaymentNet using field labels and values to filter and sort the data relevant to a user’s workflow and management tasks. An advanced query allows for detailed searches by criteria, hierarchy, and order by fields. Also see Custom Query.
The process of reviewing and comparing card transactions to internal records of payments and receipts, including resolving discrepancies and validating or allocating transactions to appropriate accounting codes.
Reconciliation Mapper File
A file that associates transactional payment information returned by the card processor with key reconciliation values.
Registered
The status of a supplier company who has set up their access to SUA Connection, allowing the company to resolve many payable issues on their own. See SUA Connection.
Related Vendors
The set of vendors from your organization that share the same SUA Connection. See SUA Connection.
Remainder
The total credit remaining in a payable.
Reminder Notification
A type of payable notification designed to remind a vendor that the payment needs to be processed. Reminder notifications are typically sent on a scheduled basis throughout the life cycle of a payable.
Remittance
The process of sending money to remove an obligation. This is most often done through an electronic network or wire transfer, or by mail. The term also refers to the amount of money being sent to remove the obligation.
Remittance Data
The payment and invoice information associated to a payable.
Requestor
The person responsible for requesting the creation of a payable.
Review
The process of comparing card transactions to internal records of payments and receipts, including resolving discrepancies and validating or allocating transactions to the appropriate accounting codes.
See User Access Role.
Scheduled Notifications
A list of email messages that are scheduled to be sent during the life cycle of a payable, such weekly reminders.
Second Row of Embossing
An optional field that allows up to 21 (for MasterCard) or 19 (for Visa) alphanumeric characters to be embossed or displayed on the second row of a credit card. This could be, for example, a department name or business unit name that is displayed below the cardholder name.
Security Code
A security feature instituted to reduce the incidence of credit card fraud for "card not present" payment card transactions; also known as a card verification value (CVV).
Send Notification
An ad-hoc payable notification email that can be sent to a maximum of five email addresses.
Settlement
The funds transferred by an acquirer to a vendor as the result of processing an authorized card transaction. See Acquirer.
Settlement Method
The type of credit card that is being used. Options are Purchasing Card and Single-Use Account.
Settlement Process
The method used by the vendor to fund a credit card transaction. See Automated Settlement, Manual Settlement.
Single-Use Account (SUA)
A virtual credit card number typically issued for a single payable for a fixed amount and duration.
The process of dividing transaction information into different lines of accounting so that costs are allocated to specific cost centers. This is referred to as "adding lines" to transactions in PaymentNet. See Adding Lines.
Standard Queries
The set of queries available to all users. Also see Custom Query.
Statement
A chronological summary of all the transactions associated with an account during a stated period and their effects on the account.
Static Card
A credit card typically issued to a supplier for ongoing payments; also known as a Ghost Card. Limits are increased and decreased based on client payment instructions and reconciled payments clearing.
Straight Through Processing (STP)
The automated settlement of single-use account payments directly to a vendor's merchant account without requiring entry into a Point-of-Sale system; also known as Automated Settlement. Also see Point-of-Sale (POS).
A website for suppliers to manage payables from J.P. Morgan buyers. Suppliers are recruited to accept Single-Use Account payables and then register for the site to be able to self-service their payables.
Supplier
A person or organization that provides goods or services to a buyer. Supplier information comes from the supplying organization.
Transaction
The exchange of funds in response to a settlement request for a credit card purchase of goods or services provided by a vendor.
Transaction Allocation
The process of manually or automatically assigning accounting codes to each transaction based on transaction defaulting rules for employees, hierarchies, merchants, Merchant Category Codes, accounts, or customer codes. Allocating transactions allows cardholders to separate an asset’s value or expenditures among different organizations or line items.
A type of custom field typically intended for communicating information about a particular payable or transaction and used by the buyer for reconciliation.
Transaction Date
The date a transaction posts to a credit card account.
Transaction Flag
An icon that reflects functionality used to track and monitor cardholder transactions by ensuring that they adhere to an organization’s card policy. It is used on the Transaction List screen to identify transactions that are split by the merchant, exceed certain spending thresholds, or are completed at questionable merchants or types of merchants.
Transaction ID
The unique identifier assigned to a transaction.
TSYS
An external company that provides J.P. Morgan Chase with credit card processing functions, such as maintaining account transaction information and providing transaction authorizations.
A three-part structure defined by role, hierarchy ID, and scope of view that designates a user’s ability to perform specific functions with respect to their job. This structure allows organizations to manage access rules for groups of users by assigning permissions to each group as a unit. Role management handles authorization, which enables program administrators to specify the resources that users are allowed to access, including reports.
Velocity Controls
Settings that determine transaction thresholds for a particular payable. Examples include monthly transaction limits, daily amount limits, and single amount limits. Default velocity controls for a payable are set by the payment group but can be changed either during creation or by editing the payable. Also see Payment Group.
Vendor
A person or organization that provides goods or services to a buyer. Vendor information comes from the buyer.
Vendor Details
All information known about a vendor. Also a page in the Payables module where vendor information can be found.
Vendor Email
The email address(es) for a vendor where payable notifications can be sent.
Vendor Identifiers
ERP identifiers used to uniquely identify individual vendors. ERP IDs generally include a Vendor ID and may include additional Set IDs, Site IDs, or Site Name to form a unique identifier. See Enterprise Resource Planning (ERP).
Vendor List
A list of all the vendors belonging to an organization. Also a page in the Payables module where vendors can be queried and batch actions, such as uploading or downloading the Master Vendor List (MVL), can be taken. Also see Master Vendor List (MVL).
Vendor Name
The name provided by the buyer to identify a vendor. An incomplete vendor may have a blank vendor name.
Vendor Status
The current state of the vendor. Options are Enabled (can be paid), Disabled (cannot be paid), and Deactivated by JPMC (cannot be paid because the vendor failed sanction screening).
Web Service
An Internet-facing software application that allows buyers to take actions on payables, including create, inquire, modify, and close, via a messaging service communication using XML through the Internet.