This article is intended for Employee, Manager, Administrator & Partner User Roles. What is a User Role? 
We have built Veroxos to be as intuitive as possible but as with all software, we have our own set of terminology. It helps to learn these to easily navigate the platform.
Key Veroxos Terms
In alphabetical order, see below a list of terms and their meanings in the context of Veroxos:
| Account | This refers to a vendor/supplier billing Account. A Vendor can have multiple Accounts and an Account has multiple Services within it. |
| AP Feed | Account Payable (AP) Feeds are used to process Vendor Invoices in batches. Veroxos integrates into most accounting solutions to directly push financial data for streamlined invoice creation, payment and internal recharging. |
| Asset | An Asset is a physical device or appliance. Assets can be associated with a Service. For example, an iPhone would be an Asset and could be associated with a Service on Verizon, a Vendor. |
| Client | The contracted customer leveraging the Veroxos service. |
| Cost Center | Veroxos offers the ability to store a code against a specific Service. This code is used to recharge the business area for the use of a specific technology service. |
| Dispute | When an Invoice error is identified, a Dispute is raised with a Vendor. |
| Employee | Veroxos stores Employee data, we refer to these data points as Employees. |
| GL Code | General Ledger (GL) Codes are numerical or alphanumeric identifiers that businesses can use to categorize and track financial transactions. |
| ID (various) | Everything in Veroxos has its own ID value. This is separate from your internal ID values. |
| Invoice | Invoices are from your Vendors and are specific to an Account in Veroxos. Invoices contain Services. |
| Plan | Plans are predetermined pricing structures provided by your Vendors. Plans are applied to a Service. |
| Service | A Service is a unique billing line on a Vendor Account. On a mobile phone Invoice, a Service would be an individual line. |
| Service Type | A Service Type is the parent classification of a Service. Service Types include: CCaaS, Cable TV, Conferencing, Data Center, Data Circuit, Voice, Microsoft 365, Mobile, PBX Voice, Public Cloud, Service Management, UCaaS, Unknown, Virtual Fax, and Other. |
| Service Description | Service Descriptions are the child category for a Service. These are determined by the Service Type. |
| Site | A Site is a physical location, usually an office location or similar. |
| Ticket | A Ticket is the result of a support request. Any faults, orders or requests generate a Ticket in Veroxos and the unique ID is used to track Ticket activity and status. |
| Vendor | A Vendor is the supplier of the technology services. For example, Verizon, AT&T or T-Mobile are major US vendors for mobility services. |
| Vendor Documents | These include contracts, amendments, service levels etc and are stored within Veroxos. Documents can be associated to a specific Vendor or Account (or both). |
Data Relationships Explained
The diagrams below visually represent the relationships between these key points of data.
The diagram illustrates the high-level structure of Veroxos. It shows that the Client is at the core. Each Client has Employees, Sites, and a Vendor. The Vendor has various Accounts, and each Account has different Services. These Services are associated with either the Employees or the Sites. This setup ensures that everything is well-organised and efficiently managed within Veroxos.
High Level - Data Relationship Diagram
The detailed diagram provides an in-depth view of the relationships within the Veroxos. At the centre, we have a Client, who has Employees, Sites, and a Vendor. The Vendor provide Accounts, and each Account offers various Services. These Services are linked to either Employees or Sites and involve specific Assets.
Additionally, the system includes detailed components such as Vendor Documents, AP Feeds, and Invoices, which are connected to the Vendor. On the other side, the Services are further detailed by Plans, Service Types, Cost Centres/GL Codes, and Service Descriptions. This comprehensive structure ensures efficient management and smooth operation of all elements within the Veroxos.
Detailed Data Relationship Diagram