Strict Mode adds a bank-confirmation check when releasing bookings. Use it with a regular reconciliation process so relevant receipts and refunds are checked against the bank before release.
Fully Paid and bank-confirmed are different
A booking can balance in the Payment Record while a receipt or refund still needs bank confirmation. Strict Mode checks relevant unconfirmed payment transactions when you select Release.
On this page: What Strict Mode does · Turn it on · Resolve a warning · Common questions
What Strict Mode does
| With Strict Mode enabled | What you still need to do |
|---|---|
| Relevant unconfirmed receipt/refund entries can block booking release. | Match the actual money movement to the bank statement and confirm the appropriate records through Daily bank reconciliation. |
| A release attempt can display There are unconfirmed transactions on this booking. | Investigate the entries. The warning alone does not tell you whether the money is missing, still pending or received but not yet confirmed. |
| The bank-confirmation check is applied during release. | Still review charges, fees, refunds and allocations. Strict Mode does not resolve an incorrect booking balance or an allocation mismatch. |
Strict Mode does not make bank payments, import missing money or reconcile the account automatically. Whether it is enabled depends on your account’s setting.
Turn on Strict Mode
- Go to Profile > Bank Accounts.
- Find your trust/host account and select Edit. Use the existing account record; do not create or remove bank accounts to enable this setting.
- Select the Strict Mode checkbox and Save.
- Log out and log back in so the account setting is loaded for your session.
If you cannot find the setting or are unsure which bank-account record to use, contact support. Keep your reconciliation up to date before relying on the release check.
If a booking has unconfirmed transactions
- Open the booking’s Statement and Payment Record. Identify the receipt, refund or pending entry involved.
- Compare it with the actual payment and bank statement. If it has occurred, match and confirm the correct record through your normal bank-reconciliation process.
- If the money has not arrived or a refund has not been paid, keep the record accurate and resolve the outstanding item. Do not confirm it as though it appeared on the bank statement.
- If a duplicate or stale pending entry is suspected, ask support to verify the appropriate correction. Once the records are correct, retry release and follow Booking Release.
Balance Transfer entries: follow the paired internal-allocation procedure, such as correcting a suspense allocation, and confirm the supported pair. These records do not represent a new bank deposit or refund; do not create another bank movement to confirm them.
Resolve the record rather than bypass the warning
Do not turn Strict Mode off, delete a genuine transaction or add a balancing credit simply to force release. Contact support if the booking and bank records do not agree.
Common questions
Does Strict Mode confirm transactions for me?
No. You still need to match the entries to the actual bank activity and confirm them as part of reconciliation.
Will it fix a guest-charge or refund-allocation mismatch?
No. Allocation checks are separate from bank confirmation. Review the Payment Record and ask support if you cannot explain the difference.
Why does release behave differently on another account?
Strict Mode is an account setting. Check the relevant trust/host account and ask support if the release behaviour is unexpected.