FREQUENTLY ASKED QUESTIONS

Does this system allow receipting of cash, cheque and credit cards?
Yes.  These common tenders are available plus other options like 'already banked', vouchers and integrated EFTPOS.

Does this system allow for mulitple tenders in one transaction?
Yes.

Is OneStopSecure quick and easy to use for operators?
Yes.

Does the system use hotkeys to minise key stokes?
Yes. A toolbar can be used to access any task easily and the register uses hotkeys for transactions as well as using the 12 function keys to assist with speed during all receipting functions.  It is our policy that a mouse should not be required by any cashier completing a normal receipting transaction.

Does the system maintain an audit of each transaction, e.g. operator, time, register used etc?
Yes.  All transactions record these details.  Multi-organisation details are also recorded, where required.  All details are stored for access during transaction enquiry and are also available on individual electronic cashiering journals.

Does this system print a receipt, can this receipt format be modified for our organisational needs?
Yes.  A receipt is printed for each transaction. 
Yes. The receipt can be modified with your organisation's details, logo and detail/information required to be printed on the receipt.

How does this system handle GST?
GST is defined by a tax code table.  Rules are then placed against each transaction type.

Does this system allow for the seperating of GST into different General Ledger codes?
Yes.

Does this system allow for daily reconciliation between amounts in each register and receipts/payments?
Yes.  Reconciliation can be done at each cashiering point and also at a central point for group of registers.  The interfaces and log reports can also be reconciled to these reports, as required.

Does OneStopSecure allow us to make enquiries on transactions based on a number of fields?
Yes.  All transactions can be looked up using the Transaction Enquiry task.  This can be done from any OnestopSecure client PC anywhere in the network immediately after the transaction occurs.  This is extremely valuable for departments that may not have an interface available (such as the library).  This allows them the ability to check that a payment has been made successfully.

Can OneStopSecure restrict access to functions based on staff roles?
Yes. Every OneStopSecure task/function is restricted by the user and their logon roles.

Can OneStopSecure use SQL as the database server?
Yes.

Can OneStopSecure use ORACLE as the database server?
Yes.

Does OneStopSecure have a recommended platform?
OneStopSecure is designed based on Microsoft .Net framework and therefore SQL server is normally recommended for the storage of the 'cashiering' internal data.  Oracle databases are often referenced for validation and interface output, but thought should be given to the restriction of 'case sensitive' searching before deciding on the use of Oracle for transactional storage.

Does this system interface with major finance systems like Finance One, SAP and Peoplesoft?
Yes.

Does this sytem work in a Terminal Services environment (such as Citrix)?
Yes.  The software does work in this environment however please note, some integrated EFTPOS is not supported by the banks in this environment.  Please check with your Bank.

Does this system interface with student systems like Callista?
Yes.  Interfaces can be done via batch uploads or an SQL view of the required validation data.  Each transaction can then be optionally parameterised for mandatory validatio, where required.

How long does it take to install/implement OneStopSecure?
It would normally take approximately 6-12 weeks to implement depending on the complexity of the job.  This includes the planning, software and hardware installations and training.  It also includes time to design and agree interfaces.  Some organisations will implement sooner by splitting the project into smaller tasks.