Payment Locking Feature

Index



Overview

Originally payments could only be locked on archive. This displays the payment lines as grey and cannot be edited.
There is now an interim locking system which locks the payment on commit if particular payment combinations are selected.
These combinations are set by the respax client and are customisable.

Locking Rules

The standard payments provided in respax are:

Agent

On Account

Refund (Agent)

POB

On Account

Pre Payment

Reservations

Cash

Credit Card

Direct Deposit

EFTPOS

Refund (Pax)

Travellers Cheque

Outside Operator

On Account

Second Agent

On Account

The standard payments with locking are:

Agent

On Account

Refund (Agent)

Voucher

Lock

POB

On Account

Pre Payment

Reservations

Cash

Lock

Credit Card

Lock

Direct Deposit

Lock

EFTPOS

Lock

Refund (Pax)

Lock

Travellers Cheque

Lock

Outside Operator

On Account

Second Agent

On Account

Voucher

Lock

How the payment behaves when locked

When a payment has been locked on commit, re-opening the booking will display the line as blue:

Clicking on a locked line shows the locking
The form shows (This Payment can not be edited according to payment rules)

Once a payment is locked, it can not be unlocked.
And selecting any of the locking combinations above (paid to / paid by) will lock the payment on commit

Reversing an incorrect payment

To reverse an incorrect payment, hit the "Refund" button
Enter a refund reason

Choose Yes for Payment Reversal

Enter a reference number/text

The payment will display as a negative


Process

Some clients use respax to check in their passengers before they board a vessel or bus.
In the case where each respax user has a till, a report can be run on the respax user at a particular time to balance this till.
Locking makes it easy to reconcile money using the last update date/time on the payment as this can not change


r4a howtos managingbookings paymentlocking (last edited 2010-12-01 01:39:19 by ppp214-33)