Interface to ACCPAC Point of Sales Systems (Counter Sales and SuperClerk)

ACCPAC is typically a batch processing system. This means that transactions are passed between modules in batches which are created during day-end processing. This is of course not acceptable in a front office system, where a guest may wish to use some of the properties facilities in the morning and then check out and pay the outstanding account. To correct this RR provides an interface to the two Point of Sales Systems available for ACCPAC, CounterSales and SuperClerk - follow the links to the product web sites for further product information.

The RR interface is designed to prevent the user from having to run a day-end in these systems before the transaction appears on the guest account and will "fetch" transactions from these systems which has not yet been posted to the guest account by a day-end procedure. This will be done each time a guest account is accessed for view or print in RR.

Both CounterSales and SuperClerk provide systems specifically modified for UniResMan. The modifications make it possible for the POS clerk to find a guest account based on the room number rather than having to find the guest AR account number.

Interface to Non-ACCPAC external systems (Point of Sale, telephone management, video billing etc)

UniResMan (RR) was developed from ground up with the express knowledge that interfaces to external systems will be necessary.

Two distinct methods were provided for interfaces initiated by RR:

1. File transfer. If the external system has the ability to write an external file to a place on the network where it can be accessed by RR, this can be used to store data which will be used by RR to update guest records. The interface file is checked and guest records updated when any view or print of a guest invoice or statement record is done and also during the night audit. This ensures that guest records are always up to date when viewed or printer by RR. RR will process approximately 400 records per second (Pentium P200, local drive, Win 98 - but this will depend on the environment) so the process is largely transparent to the user.

   Advantages: Fast, stable, easy to modify and update by user, less expensive, requires no additional systems/hardware to implement, most external systems will write an external file, cannot affect the operation of RR, no protocols to consider, less chance of data being lost due to broken communication links or downtime of either system, no need to shut down during night audit or other maintenance functions.

   Disadvantages: Cannot do two way communication unless external system can read from ASCII file.

   Typical cost: US$2000.00

2. Via serial port (RS232) interface. This allows the two systems to communicate directly and pass information both ways. Provided the external system is capable, this method allows RR to pass data back to the external system to, for example, place a telephone extension on hold when the guest checks out of the room.

   Advantages: Allows two way communication.

   Disadvantages: Requires dedicated computer or session to run, more complex to create, may slow down RR system, less robust, may lose data during down time, has to be shut down during night audit, more expensive.

   Typical cost: US$5000.00

In both interface options the direct assistance of the dealer is required insofar as providing technical information from the manufacturer and also testing of the interface on-site. Remember UniDevCo does not have access to the equipment and has to rely on the dealer on-site to assist in development.

Interface to RR Guest records by external systems.

External systems (video account displays etc) can gain access to guest records via the ACCPAC Options ODBC driver (follow the link). There are two versions available with the professional version being able to write and update the guest records as well. For information on fields updated in records please contact UniDevCo with specific requirements.

or email info@unidevco.com with questions or comments about this web. Last modified: November 22, 2006 Copyright © 2000 - 2005 Uni Development Company Inc. All rights reserved.  All other marks are trademarks or registered trademarks of their respective companies.