The financial ledger has transactions of different types for multiple organizations at multiple locations in multiple currencies. Account balances and transactions are recorded for any combination of organization(s), location(s), type(s) and currency. Each account has a subsidiary ledger, which provides additional detail. For example, the receivables account has a subsidiary ledger of customers, inventory has a subsidiary ledger of products, etcetera. The preloaded standard chart of accounts can be extended or reduced as required.

Journals record values posted to the ledger, and each includes a unique reference, the posting accounts, the affected company, division, branch or other organization, the user responsible, the date on which it took effect, and the debit and/or credit amounts and currency. A journal may also have quantity, unit of measure and location if affects a physical resource such as inventory. Posting rules specify how values are posted to the ledger. While most rules are standardised to conform to generally accepted accounting principles, others may be adapted or added for specific information needs.

Appointments include meetings, professional consultations, lectures, trade shows, conferences and other events which people attend. A tabular calendar displays appointments to show their locations, attendees, start and end times and status. A user can drill down from the calendar to an appointment by clicking in the appropriate cell.

Attendees for an appointment are reminded, and may be invoiced prior to confirmation. Materials, equipment and services used are recorded. Revenues and costs are summarised and reported from these transactions. Profitability is calculated by comparing these revenues and costs. Regular appointments may be scheduled automatically, and their attendees reminded accordingly. For example, your dentist can automatically remind you of your next check up!

Each asset has a unique name and code eg: building or room number, vehicle registration, etcetera. Other information includes the depreciation type and term, the physical location, the model and make, and the owner and supplier of the asset.

Account balance and transactions of the asset, including depreciation, maintenance and running costs, are displayed to authorised users.

Each asset has attributes by which it is classified for search and reporting purposes.

Cash, bank and investment accounts record financial balances and transactions in any currency, and automatically reconcile them with statements.

Payments record a reference number or code which can be automatically generated, the account from which payment is made, the date on which the payment is due and is made, and the payee, typically a supplier or employee.

Receipts similarly record the reference number or code, the account to which the receipt is deposited, the date of receipt, and the payer, typically a party of type customer. Adjustments to finance accounts are done by journal transactions.

The maintenance process is designed for scheduled service and unscheduled repair of assets. A maintenance procedure defines the type and frequency of work to be done on assets that serviced regularly, usually based on the manufacturer's recommendations. Maintenance is scheduled by reference to these procedures and by requests created in response to breakdowns.

The materials and labour and equipment required are allocated to a maintenance order when it is confirmed, and are used when it is released and is done. Maintenance costs are summarised and reported from these transactions. Asset availability is calculated by comparing the time between failure and time to repair.

The party database records the name, email address, phone, mobile and fax numbers, residential or business location and postal and physical addresses of each organization and individual with which business may be conducted. In certain cases sales, value added or income tax identification, and the web address or URL of the party for marketing purposes, is recorded.

Accounts receivable, accounts payable and loan account balances and transactions for the party are displayed to authorised users.

Each party has attributes by which it is classified for search and reporting purposes. Users are also parties and are added to the database on registration. Attributes are used to record their preferences.

Employees are parties so have the information described immediately above. In addition, flexible payroll rules enable salaries and wages to be calculated and posted to the general ledger. This data is printed on a payslip for each employee, and is summarised for payment and payroll tax purposes. Standard rules allow for multiple benefits and deductions, for overtime work, for ad hoc payments and loans, each of which is posted to the appropriate account in the ledger. The rules are easily adapted to particular needs without programming.

Other features record leave due and taken, and incidents such as training, awards and disciplinary action.

The product list records the name, UPC or other code to identify the product, default unit of measure (stock keeping unit SKU), physical or inventory location, current owner and preferred supplier, web address or URL for marketing, technical, supply or other purposes, and its lead time the duration in days between order and delivery of the product from its supplier.

Inventory on-hand and account balances and transactions are displayed for each product to authorised users. Inventory is maintained at multiple locations in multiple SKUs. Actual inventory costs are recorded, which allows actual, FIFO, LIFO and average costing for accounting and estimating purposes.

Prices and discounts may be set for each combination of product, date, quantity, SKU, currency and contract type (eg: retail, trade, wholesale). Contracts allocate these types to specific customers so that the appropriate price is chosen when quoting or selling to that customer. Tabular price lists are published by contract type.

Production procedures define how a standard product is made via a bill of resources. Resources include materials, components, assemblies, machinery, tools and labour. In a jobbing environment a production request uses estimated resource quantities for costing and planning. These may be joined in a sequence or network of related procedures for complex production processes and projects.

A tabular schedule displays production orders to show their resources, start and end times and current status. A user can drill down from the schedule to a production order by clicking in the appropriate cell.

Materials and labour and equipment are allocated to a production order when it is confirmed, and are used after it is released into work in process. Costs are summarised and reported from these transactions. Production efficiency is calculated by comparing actual times and costs with estimated values.

All phases of a purchase process, from request to payment, are recorded and guided by work flow to the correct user. Each phase records the date on which it was due and when it occurred, by whom it was done, and for which organization. A purchase can have an unlimited number of lite items, each of which records the expense or control account against which it is made, and where appropriate, the finance account from which payment was made. Other details include the supplier, quantity, SKU, price, currency, discount and tax category for each product.

Documents are available for each phase including: Request for quote (RFQ), quotation, purchase order, and goods or service receipt.

Accounts payable reports list amounts payable to each supplier, including the amounts payable to tax authorities.

A multidimensional data warehouse provides historical, current, and predictive business information directly from operational data in real time. Data is partitioned in the data warehouse into facts, which are generally numeric values, and dimensions, which are properties that give context to the facts. For example, a sale is measured by quantity and price values (facts) and SKU, currency, date, location, and product, customer and salesperson identities (dimensions).

Report content may be selected by name or code for a range of dates and for one or more organizations, locations and event types. Reports are created in PDF, HTML or CSV formats, and may be printed, stored locally, and emailed from the user's web browser. The report generator enables sophisticated users to create their own report designs.

Reservations are displayed in a tabular schedule which is designed to help guests and agents to find accommodation, and to show property owners and managers the reservation status. Accommodation searches are by location, date and attribute(s), where attributes include such things as room size, views, air conditioning etcetera. A user can drill down from the schedule to a reservation by clicking in the appropriate cell. All aspects of an accommodation reservation process from request to departure are recorded and guided by work flow to the appropriate user, including guests and agents.

Each reservation has a unique reference number, the guest and/or agent which made the reservation, the person or manager responsible, the arrival and departure dates and times, and the date on which it was made. Rack and STO rates are automatically calculated to take account of season and length of stay. For serviced accommodation the service agent, frequency of service, and service notes are also recorded.

All phases of a sales process, from request to receipt, are recorded and guided by work flow to the correct user. Each phase records the date on which it was due and when it occurred, by whom it was done, and for which organization. A sale can have an unlimited number of lite items, each of which records the product, quantity, SKU, price, currency, discount and tax category for each customer.

Documents are available for each phase including: Request for quote (RFQ), quotation, sales order, delivery note, invoice and credit note.

Accounts receivable reports list amounts receivable from each customer, and the amounts payable to sales tax authorities.

System administration is mainly concerned with controlling access by users and the permissions that they have. Within an organization, roles are created for various job functions. The permissions to perform certain operations are assigned to specific roles. Members of staff or other system users are assigned particular roles, and through those role assignments acquire the permissions to access particular system functions. Roles also define the flow of work in a business process between users, both within and between organizations.

Users are also allocated one or more organizations for which they have access. One user might be allowed access only to the data for a single branch, while another may have access to all branches of all companies within a group. Each user has a password which is stored in a secure form in the database, and can be changed by the user at login or by the system administrator at any time. An optional registration form allows new users to register themselves onto the system with limited access to particular functions.

A user can set the level of on-line help at login, which controls the frequency, type and detail of messages displayed during the session. A new user may wish the system to be verbose, giving a running commentary of what is happening, while an old hand may require only error messages to be displayed. A record of all sessions with login and logout dates and times is kept for each user. A user's access is blocked if all its roles are removed.