Connect Furama iPMS

Quick Setup

Ask your Furama contact for all required connection details before you start. Setup takes about 10 minutes.

This guide helps you connect a property to Furama iPMS and confirm the connection is active.

Go to: Settings → Essentials → PMS Integration

Quick Reference

Setting	Required	What It Controls
iPMS Base URL	Yes	Points AVA to the iPMS API and service path
Organisation Unit	Yes	Identifies your hotel in iPMS
Control Unit	No	Overrides the unit AVA derives for catalogue lookups
User Code	Yes	Acquires the iPMS security token
Business User Code	No	Identifies the user on business requests
API Key	Yes	Authorises the iPMS connection

Optional values

AVA derives Control Unit from your Organisation Unit using Furama's unit hierarchy. Guest sources and payment types use the derived control unit. Enter Control Unit only when Furama confirms an override for your property. Business User Code defaults to User Code and preserves its letter case. Rate plans use the Organisation Unit value. Clear Control Unit and save to restore automatic resolution.

Before You Start

Confirm these requirements:

• Your property has been enabled for Furama iPMS
• Vouch has confirmed the published iPMS connection for your property
• You can edit Settings → Essentials
• You have the full iPMS API URL, including its service path
• You have the organisation unit, user code, and API key
• Furama has confirmed an override if your property needs one

Keep the API key private

Do not send the API key in screenshots or support messages. AVA masks the saved value after setup. AVA also redacts the API key in Audit Log details.

Connect the Property

1. Go to Settings → Essentials.
2. Open PMS Integration.
3. Select Furama iPMS as the PMS provider.
4. Enter the iPMS Base URL.
5. Enter the Organisation Unit.
6. Enter the User Code.
7. Enter the API Key.
8. Leave Control Unit blank unless Furama provided a confirmed override.
9. Add the optional Business User Code when it differs from User Code.
10. Click Save PMS Settings.

✓ The page shows "Furama Integration Configured." ✓ The API key stays masked after the page reloads.

✓ AVA derives the control unit when you leave that field blank.

Versionless connections use v2

AVA uses Furama iPMS v2 when the connection does not specify a version. You do not need to enter or maintain a version setting. Do not create a separate iPMS provider entry.

Use Furama iPMS for single- and multi-room stays

The published iPMS connection supports the main AVA steps for single- and multi-room stays.

Area	What AVA supports	Important limit
Reservations	Find, view, create, and edit reservations, including multi-room stays	New multi-room reservations use one room type, stay window, occupancy, and quoted rate
Operations View	Load Check-ins and Check-outs reads for daily work	Select the required business date before reviewing arrivals or departures
Check-in and check-out	Assign rooms, check guests in, and check guests out, including approved vacant dirty-room check-ins	Process multi-room stays one room at a time; AVA targets the selected room
Guests	Update the main guest and companions; add several room sharers together; upload travel documents, signed registration cards, and photos	Furama has no guest-profile directory, so attach guests using their details, not guest IDs
Rooms and housekeeping	View rooms, update conditions, and manage service blocks	Conditions and new blocks can take about 60 seconds to appear
Rate plans and quotes	View Furama rate plans and quote stays by room type, dates, and guest count	Plans are read-only; quotes contain room rates without tax or fee breakdowns
Billing	View stay-wide billing, post payments or charges, and view transactions	Select the room before posting; AVA combines every room's reported charges and payments
Sources	Load guest sources and payment types	AVA derives Control Unit from Organisation Unit

Confirm these limits before rollout

The published connection supports multi-room stays, but each room is processed separately. When you create a multi-room stay, every room must use the same room type, dates, guest counts, and quoted rate. It does not provide property currency or card authorization through Furama. Set the property currency in Settings → Essentials → Hotel Basic Details. Confirm final billing totals in Furama when AVA shows a synthesized bill.

How AVA handles Furama multi-room stays

Furama groups the rooms into one stay. AVA shows each room with its own room number and room-level reservation details. Select the room you need before assigning, checking in, checking out, changing guests, or reviewing billing. AVA keeps actions on that room instead of defaulting to the first room.

Furama stores each room as a separate iPMS order. AVA reads every room order when it calculates a multi-room stay balance. Payments and folio charges belong to one room. Open that room's row or card before posting either item. If AVA cannot identify the room, it stops the operation instead of guessing.

Create a multi-room Furama reservation

1. Open Operations View and click Create Reservation.

2. Enter the main guest, stay dates, room type, guest counts, and quoted Rate.

3. Click Add another room for each additional room.

4. Edit Room 1 when you need to change the room type, guest counts, or quoted rate. AVA copies those values to the other room cards. Rooms 2 and later are read-only and show Matches Room 1.

5. Click Create Reservation.

   ✓ AVA creates the stay, separates the rooms, and refreshes the stay before showing it.

AVA creates one separate room entry for each requested room. Assign each room separately after creation. See Create a Reservation for the general workflow.

Signed registration cards

Furama can receive the signed registration card through the PMS upload policy. Turn on Upload registration card to PMS in Settings → Check-In → Check-In Policy. AVA sends the rendered signed card as an attachment after the selected upload timing. Check Command Center → View Details when you need to confirm delivery.

Furama rate quotes

AVA folds Furama's per-night rows into one offer for each room type and rate plan. Offers missing any requested night are excluded. Furama does not provide tax or fee details, so the quote total is the room rate only. Some properties may return an internal currency code such as 001. Confirm the currency and final amount in Furama before collecting payment.

Use Furama in daily operations

Furama iPMS v2 supports the Check-ins and Check-outs tabs in Operations View. The tabs use the selected business date to load arrivals and departures.

1. Open Operations View.

2. Select Check-ins or Check-outs.

3. Choose the business date you need.

4. Click Refresh when you changed a reservation in Furama.

   ✓ The list shows Furama reservations for the selected arrival or departure window.

Change a Furama room assignment

Use Change room when a guest needs a different room before checkout.

1. Open the reservation from Operations View or Reservations.

2. Click Change room.

3. Review rooms with matching type, ready status, and no overlapping reservation.

4. Select a room, then click Confirm room change.

   ✓ AVA sends the new assignment through Furama and refreshes the reservation.

AVA checks room type, occupancy, housekeeping condition, lock state, and overlapping stays. Dirty or occupied rooms may not appear as candidates. Furama supports direct moves to a vacant matching room. It does not swap two reservations that are already assigned to rooms.

Check the new room before issuing access

Confirm the new room in AVA and Furama before encoding a key or sharing room instructions.

Check the PMS room before check-in

Furama uses the room assigned to the reservation order during check-in. AVA verifies that room before it completes the guest check-in. AVA requires Furama to confirm that the room is vacant. Unknown or missing vacancy data does not count as vacant. Occupied, locked, out-of-service, missing, or maintenance-blocked rooms are rejected before AVA writes an assignment.

For a multi-room stay, open the room you need before starting the action. AVA sends assignment and check-in requests to that room's Furama record. Process the remaining rooms separately.

• If the reservation has no room, AVA assigns the requested room first.
• If the requested room differs from Furama, AVA refuses the check-in.
• If the guest is already checked in, retrying returns the current PMS room.

Check the room in Furama before encoding a key or sharing room instructions.

Allow check-in to a vacant dirty room

Furama iPMS v2 accepts check-in to an assigned room with Dirty housekeeping status. Enable this only when your front desk has approved the room for immediate arrival.

1. Go to Settings → Check-In → Check-In Policy.

2. Open Room Automation and Room Status Rules.

3. Turn on Allow Vacant Dirty Rooms.

4. Click Save.

5. Confirm the room is vacant and safe before completing check-in.

   ✓ AVA can complete the Furama check-in while the room remains Dirty, when Furama confirms vacancy.

AVA rejects a Dirty room when vacancy is missing, unknown, or false. It also rejects maintenance-blocked rooms, even when dirty-room check-in is enabled.

Room status does not change automatically

Furama keeps the room's Dirty status after this check-in. Update housekeeping status separately when the room is ready.

Turn the setting off after the approved exception ends. See Check-In Policy for room-status guidance.

Update Furama housekeeping status

You can update Clean, Dirty, and Inspected conditions from Housekeeping. Furama applies these changes asynchronously after accepting them.

What you do	What to expect
Save a condition	AVA shows a success message when Furama accepts the request
Check the room immediately	The old condition may still appear
Refresh after about 60 seconds	The new condition should appear in Housekeeping and Operations View

1. Open Housekeeping.

2. Find the Furama room.

3. Select Clean, Dirty, or Inspected from Condition.

4. Wait about 60 seconds before checking the room in another AVA page.

5. Refresh Housekeeping and Operations View.

   ✓ The updated condition appears after Furama finishes processing the request.

Do not repeat a pending update

The success message confirms acceptance, not completed processing. Wait before sending another condition change for the same room.

Furama iPMS v2 supports service blocks through AVA when the capability is enabled. Use Take out of service for maintenance, deep cleaning, or renovation. Use Restore to service only for a block active at the current PMS business date. Furama can take about 60 seconds to show a new block after accepting it. Do not use Condition to represent a maintenance block.

Review Furama billing

AVA calculates the Furama balance from the charges and payments Furama reports. Furama does not include accommodation in every folio window. Extras remain visible even when their total is lower than the room rate.

For multi-room stays, AVA reads transactions from every room order. It combines those transactions with all room charges for the stay balance. When you post a payment or folio charge, AVA uses the selected room's order.

1. Open the reservation in AVA.
2. Review Balance Due and the folio rows.
3. Compare the final amount with the Furama folio before collecting payment.

Verify Daily Operations

After saving, verify the property with a safe test reservation.

1. Open Reservations.

2. Search for a known Furama booking.

3. Confirm its guest, room, stay dates, and status.

4. Open Rates & Availability and confirm expected rate plans appear.

5. Confirm all expected rooms, including occupied rooms, appear in Housekeeping.

6. Complete your approved test check-in and check-out flow.

   ✓ AVA shows only the actions supported by the connected iPMS property.

Capability-based controls

Some AVA actions depend on the active PMS connection. Unsupported controls stay hidden or disabled instead of sending an unsafe request.

Review Check-In/Out Logs

A complete Furama connection allows you to review guest activity in Command Center.

1. Open Main Menu → Command Center.

2. Select Status or Live.

3. Open a reservation and select View Details.

4. Review the check-in or check-out timeline.

   ✓ Furama properties can open Check-In/Out Logs after PMS setup completes.

Logs require a complete connection

If required Furama credentials are missing, Command Center shows a PMS recovery card. Finish the connection, then refresh Command Center.

Update Connection Details

1. Return to Settings → Essentials → PMS Integration.

2. Update the non-secret fields you need to change.

3. Click Edit Secret only when replacing the API Key.

4. Enter the new API key.

5. Click Save PMS Settings.

   ✓ Leaving the masked API key unchanged keeps the current secret. ✓ Clearing Control Unit restores automatic resolution. ✓ Clearing Business User Code restores its default.

Confirm API key rotation

Clicking Edit Secret clears the displayed API key. Enter the replacement key before saving the settings.

Troubleshooting

Furama iPMS is not listed

What you see: The provider list does not include Furama iPMS.

Fix:

1. Refresh Settings → Essentials.
2. Confirm you can edit PMS settings.
3. Ask your AVA administrator to confirm the property rollout.

The settings do not save

What you see: "Failed to save PMS Integration" appears.

Fix:

1. Complete every required field.
2. Confirm the base URL includes the iPMS service path.
3. Check the organisation unit and user code exactly.
4. Re-enter the API key, then save again.

Catalogue data is missing

What you see: Rate plans, sources, or payment types do not appear.

Fix:

1. Confirm the Organisation Unit with your Furama contact.
2. Leave Control Unit blank unless Furama confirmed an override.
3. If Furama confirmed an override, enter its exact value.
4. Click Save PMS Settings.
5. Reload the affected AVA page.

AVA derives the control unit automatically for guest sources and payment types. It never uses the organisation unit as a fallback for these catalogues.

Furama cannot resolve the catalogue unit

What you see: AVA reports that it cannot resolve the Furama control unit.

Fix:

1. Confirm the Organisation Unit matches your Furama property.
2. Save the connection again, leaving Control Unit blank.
3. Ask Furama to confirm the property's control-unit mapping.
4. Enter the confirmed value as Control Unit, then save again.
5. Reload the page that needs sources or payment types.

Do not guess a control-unit value. A wrong value can show another property's catalogue.

Business requests are rejected

What you see: Reads work, but reservation updates fail.

Fix:

1. Confirm the Business User Code.
2. Preserve its exact letter case.
3. Save the connection again.
4. Retry with the approved test reservation.

Check-in keeps the PMS room

What you see: AVA refuses a requested room or returns a different room after check-in.

Fix:

1. Open the reservation in Furama.
2. Confirm the room assigned to the order.
3. Use that room in AVA, or assign the requested room in Furama first.
4. Retry the check-in.

Do not encode a key until AVA and Furama show the same room.

An occupied room is missing

What you see: An occupied room does not appear in Housekeeping or the room list.

Fix:

1. Refresh Housekeeping or Operations.
2. Clear room-status and search filters.
3. Confirm the room exists in Furama's room inventory.
4. Contact support if the room remains missing.

Furama room reads load the complete room inventory before AVA applies pagination.

Check-in actions are unavailable

What you see: AVA shows reservations, but room assignment or check-in actions are missing.

Fix:

1. Confirm the connection shows "Furama Integration Configured."
2. Check that the connection uses the exact Organisation Unit.
3. Save the connection again with the published iPMS credentials.
4. Reload Operations and retry the approved test reservation.

AVA selects Furama iPMS v2 automatically when no version is specified.

Operations tabs fail or show no reservations

What you see: Check-ins or Check-outs fails to load, or expected stays are missing.

Fix:

1. Select the correct business date in Operations View.
2. Click Refresh and wait for the list to finish loading.
3. Clear the search and filters.
4. Confirm the reservation dates and status in Furama.
5. Confirm the Furama connection is configured, then retry.

Contact support if both tabs fail after the connection and dates are correct.

A multi-room action affects the wrong room

What you see: A multi-room action cannot identify the selected room, or an older session shows the first room.

Fix:

1. Close the current reservation details.
2. Refresh Operations View or Reservations.
3. Open the room's own row or room card.
4. Confirm the room number before starting the action again.
5. Contact support if AVA still targets another room.

For payments and folio charges, select the room before starting the action. AVA stops an ambiguous operation instead of writing to the first room.

Furama checkout cannot find a room

What you see: Furama checkout does not find the stay when you enter a room and last name.

Fix:

1. Enter the exact Room Number shown in Furama.
2. Enter the main guest's Last Name as it appears in Furama.
3. For a multi-room stay, repeat the lookup for the room being checked out.
4. Refresh the checkout screen and try again.
5. Use Furama or the front desk if the stay remains unavailable.

AVA uses both the room number and last name to identify the correct Furama room.

No room appears in Change room

What you see: Change room opens, but no room can be selected.

Fix:

1. Confirm the reservation dates and room type in Furama.
2. Check that a matching room is vacant and ready.
3. Check for another reservation overlapping the stay.
4. Refresh Operations View, then open Change room again.

Without Allow Vacant Dirty Rooms, AVA does not treat an unsold but dirty room as ready for assignment. For approved exceptions, enable the setting in Check-In Policy.

Housekeeping changes do not update

What you see: You saved a condition, but the old value still appears in AVA.

Fix:

1. Confirm AVA showed a success message after you selected Clean, Dirty, or Inspected.
2. Wait about 60 seconds for Furama to apply the change.
3. Refresh Housekeeping, then refresh Operations View.
4. Contact support if the old value remains after the wait and refresh.

Furama applies housekeeping changes asynchronously. Room lists and summary counts can update at different times.

Furama service block timing or release

What you see: A new block is not visible yet, or Furama refuses Restore to service.

Why this happens: Furama applies new blocks asynchronously. It only releases blocks active at the current PMS business date.

Fix:

1. Wait about 60 seconds after AVA confirms the block.
2. Refresh Housekeeping and Operations View.
3. Check the block window against Furama's current business date.
4. Release future or expired blocks in Furama.
5. Contact support if an active block still cannot be released.

The AVA bill needs confirmation

What you see: The AVA billing total differs from the Furama total.

Fix:

1. Refresh the reservation in AVA.
2. Compare charges and payments with the Furama folio.
3. Confirm the final amount in Furama before completing payment.

A reservation date filter shows the wrong stays

What you see: A date-filtered Furama list shows stays outside the selected range.

Fix:

1. Select the required arrival or departure date in Operations.
2. Click Refresh.
3. Use All dates when searching across the current date.
4. Contact support if unrelated stays remain after refresh.

AVA sends both ends of the Furama date range to the PMS.

A guest email or nationality looks different

What you see: A saved email is missing later, or nationality displays as a country name.

Fix:

1. Confirm the guest's phone, name, document, and nationality fields in Furama.
2. Treat a missing email as a Furama display limitation at the test property.
3. Ask Vouch for help if other guest fields fail to persist.

Reservations do not appear

What you see: A known Furama booking is missing from Reservations.

Fix:

1. Confirm the stay dates match the current search.
2. Clear filters and search again.
3. Check the booking in iPMS.
4. Review PMS Connection Errors.

Check-In/Out Logs are unavailable

What you see: Command Center shows a PMS setup recovery card instead of logs.

Fix:

1. Return to Settings → Essentials → PMS Integration.
2. Confirm iPMS Base URL, Organisation Unit, User Code, and API Key are complete.
3. Click Save PMS Settings.
4. Return to Command Center and refresh the page.

Furama does not block Check-In/Out Logs after its required credentials are configured.

Still Stuck?

Contact success@vouch-technologies.com if:

• ❌ Furama stays remain missing after reconnecting
• ❌ Required fields are correct but saving still fails
• ❌ Supported check-in or check-out actions stay unavailable

Helpful to include:

• Property name
• Organisation Unit
• Time of the failed test
• Exact error message
• Screenshot with the API key hidden

Related Guides

• Connect Your PMS
• Choose Your PMS
• PMS Connection Errors