Cross-Servicing Debt Collection System:
Glossary of Terminology
Table may scroll on smaller screens
Account |
An account is a representation of a debt or receivable owed by one or more responsible parties |
Account Change Maintenance |
Functionality within the product that allows for changes to be applied to all accounts based on specified parameters |
Account Representative |
Term often used instead of Collector in the agency market |
Account Set |
Group of accounts that have been matched and tied together based on pre-defined criteria |
Action Code |
An identifier that represents an activity that a user can perform on a record (for example, an account or a responsible party) |
Action Group |
A way to group certain actions together when more than one activity is desired to occur on the account |
Add on Fees |
A portion of the debtor payment that the agency keeps (Due Us) |
Agency Payment |
The debtor sends a payment to the agency (Paid Us) |
Batch |
A group of records in a file that you use during a process. For example, you can use financial transactions in the debtor cash batch process, letter requests in the letter batch process, or vendor transactions in the vendor account placement process |
Cache |
Database that stores all of the tables that have account information |
Cancel Code |
Indicates the reason for canceling or inactivating an account |
Check Writer |
Allows account representative to request a check, which is then approved by a supervisor, and printed within the system. This reduces the time spent waiting for a check to be mailed by a debtor |
CHUI |
Character User Interface – users interact with the system by text commands |
Client |
A client is a representation of an external person or business that contracted the agency to work accounts payable. For example, the agency might list accounts from a first party company that grants consumer credit and student loans |
Client Entity Number |
The Artiva ID number for the Entity (Program) similar to our Program Code. |
Client Cash |
Money that flows between the agency and the client when either the agency or the client collects from the debtor |
Client Reference Number |
The old Agency Debt ID number |
Client Statement Check |
Remits the money that the agency collected on the accounts of a client during the statement period |
Client Statement Reports |
Formats the financial transaction information that the system compiles during a client statement process |
Command Procedure |
Series of keystrokes that the system stores to perform a task. Typically used to automate business tasks that are performed regularly |
Contingency Fees |
Money that is added onto the debtors account to cover the cost of the collection services |
Control List |
Defines the items to include or exclude when the system displays a list to users |
Costing |
The calculation of the cost to collect on an account |
CT Term |
Tool used to connect to Artiva servers (similar to PuTTY) |
Debtor |
Person who owes the client for the goods or services |
Debtor Cash |
Money that flows from the debtor to the client or agency to pay off a debt |
Department |
Departments are a group of collectors that specialize in collecting similar types of accounts |
Dialer |
Product that is used to increase collector productivity by providing a continual flow of live contacts |
Direct Payment (DP) |
The debtor sends a payment directly to the client (Paid You) |
Due Us |
Agency’s portion of the payment from the debtor |
Due You (Remit Amount) |
Client’s portion of the payment from the debtor |
Elements |
Smallest manageable unit that provides functionality in the system (i.e. field) |
Entity |
Party associated to an account. Typically a person or business |
Events |
Something that occurs on an account during the lifecycle. Example: Payment received, phase changed, mail returned |
Fee Distribution |
Determines the contingency fee by using the sub-balance types of an account that you apply a monetary transaction toward |
Field |
Units of data within Artiva that are grouped together based on similarity to create tables within the database |
Follow-up Date |
Next date to work a specific account |
Forwarding |
Occurs when an account is passed along to an agency |
Gross Payment |
Client receives the entire amount collected and then will reimburse the agencies for their collection efforts |
GUI |
Graphical User Interface – allows users to interact with the system using graphical icons and visual indicators instead of text commands |
Hosted |
Artiva is located at our hosting partner’s facility and will be accessed by the agency via a VPN connection |
Initial Phase Action |
Action(s) to be triggered when an account moves into a new phase |
Interface |
Logic developed within the system that allows data to flow into (import) or out of (export) the system. Examples are loading new business, payment information, reconciliation files, etc. |
IVR |
Interactive Voice Response – system that allows debtors and clients to check balance information, make payment arrangements, and other transactions through a touch-tone phone without human intervention |
Job Schedule |
One or more jobs or command procedures that can be scheduled to occur automatically |
Link |
Allows collection tasks, such as mailing letters, to be easily outsourced to service providers directly from Artiva |
Listed Sub-balance |
The balance on an account when it is created |
Matching |
The process of identifying like Entity records and having all accounts for the same Entity point to the same Entity record |
Namespace |
A separate instance of Artiva. Each agency will have multiple instances (i.e. DEV, TEST, PROD) |
Net Payment |
Client receives only their portion of the amount collected. The agency will remove their fees and provide the client with the remaining amount |
New Business |
Process for bringing new accounts into Artiva |
Options |
Workflow rules for actions on an account. Example: Payment credit to go to the account representative that is assigned the account, or the person that places the account in a payment arrangement |
Paid Us |
Money that the agency receives from the debtor |
Paid You |
Money that the client receives from the debtor |
Payment Arrangement |
A promise-to-pay agreement between the agency and a responsible party to collect the balance due on an account or on a set |
Pool |
List of accounts to present to the Account Representative. The list of accounts is the result of a query. The accounts can then be called predictively, progressively, or manually. Users can also work assigned accounts in a manual work queue |
Premise |
Artiva is physically located at the client’s facility |
PuTTY |
SSH tool used to connect to Artiva servers |
Relation Type |
Identifies how a party relates to an account. An account must have one responsible party with a primary relation type, and can have multiple responsible parties with other relation types (i.e. COMAK, DEPEND, SPOUSE, OWNER, BUSINESS) |
Relationship |
Record that exists in the ARRELATIONSHIPSHIP table and relates records from different tables. A relationship record contains unique properties that the system uses to move relationships through the account lifecycle |
Relationship Role |
A value on a relationship that determines functional attributes of the relationship and how the system classifies the relationship |
Relationship Role Class |
Defines how the system creates and uses a relationship |
Responsible Party |
A responsible party is a representation of a person on a record (for example, an account or a case) |
Result Code |
An identifier that represents the outcome of collection activity performed on a record (for example, an account or a responsible party) |
Route |
Routes represents the inventory of accounts assigned to a specific Account Representative |
Scoring |
The assignment of a numeric value to scoring criteria that you set for a responsible party and account to forecast collections |
Script |
Coding that allows Artiva to handle complex scenarios that may require customized solutions. There are delivered scripts that allow the system to function properly, but custom versions can be developed based upon business needs |
Server |
Hardware that houses the Artiva namespaces for 1 (premise) or many (hosted) clients |
Statement |
Displays all financial activity involving the accounts, clients, and vendors of the agency |
Status |
Current condition of an account in a specific phase |
Studio |
System that is used for customizing Artiva |
Table |
An area where similar fields are stored within the Artiva database. Tables can be created, or added to depending upon the business need |
Tying |
The process of synching up accounts for the same entity (as in, they have been matched) with the same user assignment, status, follow-up date, workflow, phase. These tied accounts are then treated as one account in the application. Two accounts have to be matched in order to tie, but matching does not imply the accounts are tied |
User |
A representation of a person who can access the system |
User Interface |
Also known as UI, this is the term for the way that features and functionality within Artiva is displayed for the end user |
Version Manager |
System that is used to track the customization of Artiva |
View |
User interface component that displays multiple, often similar, windows |
View Group |
User interface component that displays multiple, often similar, views |
View Set |
User interface component that displays multiple, often similar, view groups |
Window |
User interface component that displays similar fields in meaningful groupings |
Workflow |
Prescribes the general account flow as accounts progress through the collection lifecycle |
Workflow Action |
Specified act that occurs on accounts at a certain point within the workflow |
Workflow Event |
An event is something that has happened during the life of an account and can be used to trigger specific actions |
Workflow Monitor |
A background process that executes entries in the workflow schedule |
Workflow Option |
Control that indicates how the system processes a record in a workflow or workflow phase |
Workflow Phase |
Stage in the life of an account. (New Business, Letter, Regular, Pre-legal, Legal, Recovery, Audit, Inactive) |
Workstation |
Graphical interface used to access the features within Artiva |
Workstation Profile |
Server information and login credentials used for accessing Artiva |
Return to Cross-Servicing: Resources for Agencies