Property & listing details (booking engine)

First-time workspace setup

Rich marketplace copy is edited from Listings (step 13) on the property or unit sidebar Full integration pill — complete Integrations (step 12) before partner feeds consume this payload. Workflow pairing: Modules — Setup sequence after go-live.

Finding your way in this guide

Confirm Who can open the details editor, then How to edit from the Setup / Full integration / Photos pills in the Listings sidebars. Tab reference: Tab reference (property details) and Tab reference (listing / unit details). Guide subsection map: Booking engine details guide subsection index (payload tabs + Related subsections). Non-linear operator habits (Lockout catch-up, Pending manual receipt approval, Reject/revert mistaken receipts, Notification row-click navigation, Payment alert to receivables triage, Confirmation alert triage, Finance debt receivables triage, Finance Income status drill-down, Cash flow forecast drill-down, Partly collected security deposit, Portfolio segmentation by tenant category) have matching Related subsections below. Full pairing matrix: Booking engine details section cross-reference · Modules — Module cross-reference.

Direct access

There is no standalone hub at /booking-engine-details anymore — start from Listings. Open a property or unit in the edit sidebar, then choose the Full integration or Photos pill. To bookmark or hand off a link that opens Full integration immediately, append ?propertyDetails=1 or ?listingDetails=1 as described in Deep Links > Booking engine details layer. Legacy /booking-engine-details/* URLs redirect into Listings with the same query flags.

Pair with other modules

Return to inventory setup in Listings; distribute through Sales → Channels and partner feeds in API Reference. White-label and channel bookings with unpaid schedules can surface payment overdue rows — row-click opens the booking for Handling a Late Payment — Step 1. When overdue rows cluster on one tenant category, scope Bookings — Other filters tenant category or Finance — Tenant category filter before account-wide portal or reminder changes — see Glossary — Tenant category. Partner PUT /listing routes use integration Bearer keys — contrast management JWT on AI usage API (operator cost ledger only, not partner traffic). Topic-to-tab pairing: Booking engine details section cross-reference. Full pairing matrix: Modules — Module cross-reference.

Rich property and listing (unit) information used by the white-label booking engine and distribution channels—descriptions, amenities, rules, multilingual copy, and related fields—is edited from the Listings module, not from a separate hub page.

Who can open the details editor

Every operator with Listings edit access can open the Full integration and Photos pills in the property and unit edit sidebars. Those pills edit the same integration and marketplace payload that powers the white-label booking engine and full partner feeds — you no longer need a separate full-page module or a Vivin-internal-only Full integration pill control.

The Setup pill on the same sidebar still holds operational fields (contract terms, payments, channels, calendar, and similar) documented under Listings — Editing Properties and Editing Units.

Full pairing matrix: Booking engine details section cross-reference.

How to edit

What this editor is

The product groups these fields under the Full integration pill because they shape the integration and marketplace payload for that property or unit. Section cards inside the pill (Profile, Location, Amenities, and so on) mirror how partner exports are structured — not the same grouping as the Setup pill’s operational tabs.

Property-level details

1. Open Listings and open a property (Edit property).
2. In the sidebar pill row, choose Full integration (or Photos for gallery-only work).
3. Use the grouped section cards (see Tab reference (property details) below) and the English / Portuguese language control where bilingual blocks exist.
4. Save from the sticky bar at the bottom of the Full integration view. Switch back to Setup with the Setup pill when you need contract or payment defaults.

Listing (unit)-level details

1. Open Listings and open a unit in the listing sidebar.
2. Choose Full integration or Photos in the pill row.
3. Use the grouped section cards (Tab reference (listing / unit details)) and bilingual fields as needed.
4. Save from the sticky bar; use Setup for rent, channels, and calendar work on the same unit.

Full pairing matrix: Booking engine details section cross-reference.

Legacy URLs (redirects)

Old bookmarks still work; they redirect into Listings:

Legacy path	Redirect
/booking-engine-details	/listings
/booking-engine-details/property/:propertyId	/listings/property/:propertyId/edit?propertyDetails=1
/booking-engine-details/listing/:listingId	/listings/property/:propertyId/unit/:listingId?listingDetails=1 (property id is resolved from the listing)

See Deep Links, including bookmarkable Listings URLs with propertyDetails=1 / listingDetails=1 when you want to open this layer without opening Full integration first.

Tab reference (property details)

Pair with other Booking engine details sections

Property tabs feed Full listing feeds and partner blocks — field support matrix: Integration field capabilities. Coliving toggle affects Spotahome/Inlife exports. Full pairing matrix: Booking engine details section cross-reference.

When you open the Full integration pill on a property, the editor uses a horizontal tab strip. English UI labels (default) are shown below; other interface languages translate the same tab keys.

Tab (English UI)	Typical content
Profile & copy	Titles, descriptions, marketing copy, notes, and bilingual headline fields
Location & geography	Address core, coordinates, neighbourhood and distance metadata
Building & layout	Capacity, room counts, layout characteristics, quality level
Amenities & services	Amenity selections, facilities, parking, cleaning and laundry-related fields
Rules & host	House rules, visit settings, host profile, refund and booking-window style data
Partner platforms	Partner-feed-specific blocks (for example Housing Anywhere, Spotahome)
Photos	Booking-engine photo gallery for the property

Under Facilities & Common Areas on the Amenities & services tab, the Coliving toggle marks the property as a coliving building in partner export payloads (for example Spotahome and Inlife feeds). Turn it on when the integration should classify the listing as coliving rather than a standard apartment or house.

On the same Rules & host tab, the Booking Engine Features card includes an Instant Booking toggle. When enabled at property level, partner full feeds (for example Spotahome) can export an instant_booking block for listings on that building. The toggle alone does not set every eligibility rule — unit-level fields on Listing Details → Partner platforms still control age limits, stay length, and how far ahead instant confirmation is allowed.

On Partner platforms, you edit partner-feed-specific blocks (for example Housing Anywhere or Spotahome sections) that apply at property level before units inherit or override them:

English / Portuguese fields appear where the product supports bilingual content for that surface.

Full pairing matrix: Booking engine details section cross-reference.

Tab reference (listing / unit details)

Pair with other Booking engine details sections

Unit tabs scope partner overrides below property defaults — Integration listings toggles pair with Settings > Integrations. Instant-booking eligibility: Instant Booking (property + unit). Full pairing matrix: Booking engine details section cross-reference.

For a unit (listing) opened via the Full integration pill, the tab strip is narrower than on the property. English UI labels (default):

Tab (English UI)	Typical content
Profile & copy	Listing headline, descriptions, and bilingual copy blocks
Room fixtures	Room characteristics, furniture, appliances, kitchen, bathroom, room rules
Partner platforms	Partner-feed fields scoped to this unit
Integration listings	Per-platform toggles for full integrations that expose this unit in outbound feeds
Photos	Booking-engine photo gallery for the unit

When Instant Booking is enabled on the parent property, configure unit-level eligibility in the Partner feed (common) section on this tab:

Field	Purpose
Min age / Max age	Tenant age window for instant confirmation on this unit.
Instant Booking — max. days before check-in	Latest day (relative to move-in) a tenant can still book instantly; leave empty when the partner should apply its own default.
Couples allowed	Whether couples are eligible under the instant-booking rules for this unit.

Housing Anywhere–specific fields on the same tab (for example HA bathroom and HA preferred gender) feed the partner payload separately; see Integration field capabilities.

Integration listings exposes per-platform toggles for full outbound feeds (which channels receive this unit in their full-integration export):

Use Save on the sticky bar before leaving; Back to setup returns you to the standard Listings editor for that property or unit.

Walkthrough: Full integration pill, switch to Integration listings, edit a field, Save, then Back to setup (example unit AA-11-5D-R1).

Drafts and bilingual fields

Work tab-by-tab as needed; the sticky Save persists changes for the whole details view. When both English and Portuguese fields exist for a block, fill the languages you publish — empty language-specific fields may leave gaps in localized booking surfaces.

Full pairing matrix: Booking engine details section cross-reference.

What you see in the app (no separate module)

There is no standalone Booking engine details list page — you always arrive from Listings (property or unit edit sidebar) or from a bookmark that includes propertyDetails=1 / listingDetails=1 (see Deep Links).

The screenshot above shows the Setup pill’s general-info fields. Above the scrollable body, a pill row switches between Setup, Full integration, and Photos:

• Setup — Operational property fields (this guide’s General Information, Contract, Payments, and related sections).
• Full integration — Partner payload editor with a Full integration readiness card, grouped section cards, bilingual copy controls, and Save / discard in a sticky bar. An amber dot on the pill means required partner fields are still missing.
• Photos — Drag-to-reorder gallery; the first image is the cover (also drives the portfolio thumbnail on the property row).

Once Full integration is active, the layout is consistent for both property and unit paths:

• Readiness card — Checklist of marketing title, description, address, coordinates, currency, photos, and (on units) area/description minimums before full feeds publish.
• Section cards — Profile, Location, Amenities, Partner platforms, and related blocks match the tab tables below; expand a card, edit fields, then Save that section or use the sticky Save for the whole pill.
• Language — Where bilingual blocks exist, use the English / Portuguese control before editing copy that is exported per language.
• Photos pill — Uploads save immediately; drag thumbnails to reorder. The first photo is labelled Main / cover.

The captures in Tab reference (property details) and Tab reference (listing / unit details) show the Full integration section layout at desktop width (~1536px). They complement the Listings entry screenshot above, which shows the Setup pill and where the integration pills sit.

Walkthrough: open property Full integration, switch to Setup and back, edit a field, Save, then return to Setup (example property AA-11-5D).

Instant Booking (property + unit)

Pair with other Booking engine details sections

Property toggle gates the partner instant_booking block — unit ages and stay windows live on Listing Details → Partner platforms. Channel status after sync: Sales — Channel Manager. Full pairing matrix: Booking engine details section cross-reference.

Instant Booking is a partner-export feature, not a separate management module. Operators configure it in two layers:

1. Property Details → Rules & host → Booking Engine Features — turn Instant Booking on for the building. When off, outbound full feeds omit the instant_booking block even if unit fields are filled in.
2. Listing Details → Partner platforms → Partner feed (common) — set per-unit rules (ages, couples, max. days before check-in) that partners embed inside instant_booking when the property toggle is on.

The white-label booking engine and partial partner GET /listings surfaces may expose related availability separately; this editor is the source of truth for full-feed instant-booking metadata. After changes, Save the details layer and allow integration sync to pick up the new payload.

Full pairing matrix: Booking engine details section cross-reference.

What gets configured

Same content as before at property and listing level (descriptions, amenities, rules, booking-engine flags, instant-booking eligibility, etc.). That data powers:

• The white-label booking engine on your site
• Marketplace integrations when listing data is synced
• Tenant-facing content where applicable

Booking engine details guide subsection index

Pair with other Booking engine details module guide sections

This index pairs payload-editor sections with Related subsections — use it when partner feeds disagree with Listings setup or Instant Booking needs Sales channel verification. Full pairing matrix: Booking engine details section cross-reference.

Subsection	When to open it	Pair with
Who can open the details editor	Full integration / Photos pills in Listings sidebars	Getting Started, Users and roles, Listings — Editing Properties
How to edit — property-level	Property Full integration workflow	Onboarding a New Property — Step 4, Listings — Creating a New Property
How to edit — listing (unit)	Unit Full integration workflow	Listings — Rent Value tab, Sales — Pricing tab
Tab reference (property details)	Property payload tabs (Profile through Photos)	Integration field capabilities, Full listing feeds
Tab reference (listing / unit details)	Unit payload tabs and Integration listings	Settings > Integrations, Booking Engine API
Instant Booking (property + unit)	Partner instant_booking export rules	Sales — Channel Manager, Integrations — White Label Booking Engine
What gets configured	White-label and marketplace surfaces	Tenant Portal, API Reference — Listings & Availability
Lockout catch-up after password recovery	Sign-in restored; module backlog accumulated	Common Workflows — Lockout catch-up, Getting Started — Lockout catch-up, Resetting a Management User Password — Step 3
Pending manual receipt approval	Recorded bank transfers still pending until Approve payments	Common Workflows — Pending manual receipt approval, Finance — Pending manual payments, FAQ — Manual receipt still pending
Reject/revert mistaken receipts	Duplicate or wrong-booking receipts after Approve	Common Workflows — Reject/revert mistaken receipts, Payment Allocation — Correcting mistaken receipts, Glossary — Credit note (payment reject/revert)
Notification row-click navigation	/notifications row-click before partner payload edits	Common Workflows — Notification row-click navigation, Notification triage — Step 4, How to edit
Payment alert to receivables triage	payment overdue on white-label or partner bookings	Common Workflows — Payment alert to receivables triage, Handling a Late Payment — Step 1, Notifications — Payment overdue alerts
Confirmation alert triage	Upcoming alerts before Full integration sync sign-off	Common Workflows — Confirmation alert triage, Processing a New Booking — Step 5b, Onboarding a New Property — Step 4
Portfolio segmentation by tenant category	Review one tenant segment across modules	Common Workflows — Portfolio segmentation, Settings > Tenant categories, Finance — Tenant category filter, Tenants — Tenant category filter
Finance debt receivables triage	Engine-sourced payment schedules behind high receivables — reconcile Debt Aging after Pending clears	Common Workflows — Finance debt receivables triage, Finance — Finance debt receivables triage, FAQ — Finance debt receivables triage hub, How to edit — listing (unit), Handling a Late Payment collections (finance-overview-debt-aging-expanded-bucket.png, finance-overview-debt-aging-walkthrough-flow.mp4)
Finance Income status drill-down	Engine-sourced rent schedules may inflate Scheduled segments — cross-check Income chart	Common Workflows — Finance Income status drill-down, Finance — Income status drill-down, FAQ — Finance Income status drill-down hub, How to edit — listing (unit), Listings — Finance Income status drill-down (finance-overview-income-status-in-debt-modal.png, finance-overview-income-drill-down-flow.mp4)
Cash flow forecast drill-down	Engine-sourced collections may lag Cash flow forecast month bars until bookings settle	Common Workflows — Cash flow forecast drill-down, Finance Income status drill-down, Finance — Income chart and cash flow forecast, FAQ — Cash flow forecast drill-down hub, How to edit — listing (unit), Finance — Income chart and cash flow forecast (finance-overview-cash-flow-all-payments-modal.png, finance-overview-cash-flow-day-view.png, finance-overview-cash-flow-drill-down-flow.mp4)
Booking engine details section cross-reference	Per-topic pairing matrix	Module cross-reference, Listings guide subsection index

Booking engine details section cross-reference

Use this table when one topic on this page naturally leads into another module, API guide, or workflow — each row links to the docs you should read before or after editing the booking-engine payload.

Topic / section	Pair with these docs
Who can open the details editor	Getting Started, Users and roles (Listings edit permission), Listings — Editing Properties
How to edit — property-level	Onboarding a New Property (Step 4 Full integration), Listings — Creating a New Property, Settings > Tenant categories (default segment on engine-sourced direct bookings)
How to edit — listing (unit)	Listings — Rent Value tab, Sales — Pricing tab, Bookings — Other filters tenant category
Tab reference (property details)	Integration field capabilities, Full listing feeds
Tab reference (listing / unit details)	Booking Engine API, Settings > Integrations
Instant Booking (property + unit)	Integrations & Distribution > White Label Booking Engine, Sales — Channel Manager, Notifications — Payment overdue alerts, Handling a Late Payment — Step 1, Bookings — Other filters tenant category, Finance — Tenant category filter, Glossary — Tenant category
What gets configured	Tenant Portal, API Reference — Listings & Availability, Notifications — Payment overdue alerts, Handling a Late Payment — Step 1, Settings > Tenant categories, Tenants — Tenant category filter

---

Related

Pair with other Booking engine details module guide sections

Related below links this module to settings, concepts, workflows, and escalation paths. Pair Documentation map & escalation with Modules hub — Documentation map & escalation; pair Upstream & downstream workflows with Common Workflows — Workflow cross-reference. Topic-to-section pairing in sections above: Booking engine details guide subsection index · Booking engine details section cross-reference. Full hub matrix: Module cross-reference · Modules hub subsection index.

Documentation map & escalation

Pair with other Booking engine details module guide sections

Documentation-map bullets pair with Introduction — Section cross-reference and FAQ — Section cross-reference. Hub parity: Modules hub — Documentation map & escalation. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Modules hub — Hub pairing matrix across operator workspaces
• Common Workflows — Task-oriented guides that reference the Full integration pill during onboarding
• Glossary — Term definitions referenced in payload and partner export docs
• FAQ & Troubleshooting — Quick answers when payload edits disagree with live partner feeds
• Get Help & Support — Escalate when integration sync or permissions block payload edits

Upstream & downstream workflows

Pair with other Booking engine details module guide sections

Workflow bullets pair with Common Workflows — Workflow cross-reference. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Onboarding a New Property (section cross-reference; Deeper workflow reads; hub) — Optional Step 4 Full integration pill after the property wizard saves
• Manual block hygiene (section cross-reference; Deeper workflow reads; hub) — Availability holds that still suppress partner calendars after payload sync
• Notification triage (section cross-reference; Deeper workflow reads; hub) — Clear integration or listing alerts after payload edits sync to partners
• Handling a Late Payment — Step 1 (section cross-reference; Deeper workflow reads; hub) — Collections on engine-sourced bookings with unpaid schedules; upstream path from Notifications — Payment overdue alerts
• Entering Monthly Utility Bills (section cross-reference; Deeper workflow reads; hub) — Monthly overage workflow after utility bills exceed Bills Included ceilings

Deeper workflow reads

Pair with other Booking engine details module guide sections

Workflow reads pair with Common Workflows hub subsection index and Workflow cross-reference. Each workflow sub-guide reciprocates with [Deeper workflow reads](../modules/booking-engine-details/index.md#deeper-workflow-reads) anchors on Module documentation hubs bullets — hub parity: Modules hub — Deeper workflow reads. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Onboarding a New Property — Optional Step 4 Full integration pill after the property wizard saves (section cross-reference; Deeper API reads; hub)
• Manual block hygiene — Availability holds that still suppress partner calendars after payload sync (section cross-reference; Deeper API reads; hub)
• Notification triage — Clear integration or listing alerts after payload edits sync to partners (section cross-reference; Deeper API reads; hub)
• Handling a Late Payment — Step 1 — Collections on engine-sourced bookings with unpaid schedules (section cross-reference; Deeper API reads; hub)
• Entering Monthly Utility Bills — Monthly overage workflow after utility bills exceed Bills Included ceilings (section cross-reference; Deeper API reads; hub)

Navigation & bookmarks

Pair with other Booking engine details module guide sections

Bookmark routes pair with Management Frontend Deep Links and Create New menu. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Deep Links — Booking engine query params — Bookmarkable ?propertyDetails=1 / ?listingDetails=1 routes
• Create New menu — Inlife Full Import — Bulk import shortcut into this editor (Vivin internal accounts)
• Listings module — Standard property and unit setup sidebars (Back to setup return path)

Concepts & settings that shape this module

Pair with other Booking engine details module guide sections

Settings bullets pair with Account Settings — Tab cross-reference. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Integrations & Distribution > White Label Booking Engine
• Notifications — Payment overdue alerts — Operator Payments category rows when white-label or partner bookings have unpaid schedules
• Settings > Tenant categories — Segment portal rules and Finance — Tenant category filter when engine-sourced overdue alerts cluster on one cohort
• Settings > Integrations
• Settings > Integration field capabilities — Which payload fields each marketplace supports (read-only matrix)
• Settings > Emails — Lifecycle check-in templates that append Access Lockers codes after payload sync
• Settings > Preferences — In-app notifications — Account-wide integration or listing alerts after payload edits sync to partners
• Booking lifecycle — Computed stay status partners expose separately from booking-engine marketing copy
• Payment Allocation — Two-layer receipts, invoiced-floor rent edits, and credit note reject/revert warnings (hub)

Lockout catch-up after password recovery

Pair with other Booking engine details module guide sections

Operational backlog after sign-in recovery pairs with Resetting a Management User Password — Step 3. Hub parity: Common Workflows — Lockout catch-up after password recovery. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Lockout catch-up after password recovery — Hub matrix when sign-in was restored before Full integration pill payload edits synced to partners
• Getting Started — Lockout catch-up after password recovery — Canonical operational backlog mesh
• Onboarding a New Property — Step 4 — Optional Full integration pill catch-up after lockout-delayed setup
• Notification triage — Clear integration alerts before payload edits
• Pending manual receipt approval — Engine-sourced booking debt may lag until Finance clears Pending receipts

Pending manual receipt approval

Pair with other Booking engine details module guide sections

Receipt approval pairs with Finance — Pending manual payments and Bookings — Transactions tab. Hub parity: Common Workflows — Pending manual receipt approval. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Pending manual receipt approval — Hub matrix when white-label bookings still show pending confirmation transfers until Approve payments confirms them

• Finance — Pending manual payments — Amber Pending chip on Finance → Transactions

• Bookings — Transactions tab — Per-row Approve payment on engine-sourced reservations

• Processing a New Booking — Step 5b — Confirmation receipt mesh on direct engine imports

• FAQ — Manual receipt still pending — Why partner booking debt may lag until approval

• FAQ — Pending manual receipt approval hub — Symptom table for Approve payments / amber Pending

Reject/revert mistaken receipts

Pair with other Booking engine details module guide sections

Receipt cleanup pairs with Finance — Row actions on in-payment rows and Bookings — Row actions on in-payment rows. Hub parity: Common Workflows — Reject/revert mistaken receipts. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Reject/revert mistaken receipts — Hub matrix when duplicate receipts on engine-sourced bookings need Reject / Revert

• Finance — Row actions on in-payment rows — Portfolio reject/revert after integration triage

• Payment Allocation — Correcting mistaken receipts — Two-layer model and credit note follow-up

• Handling a Late Payment — Step 1 — Collections on engine bookings with unpaid schedules

• Instant Booking (property + unit) — Partner export rules after finance lines are corrected

• FAQ — Reject/revert mistaken receipts hub — Symptom table for Reject / Revert / Issue credit notes

Check-out ledger cleanup before refund

Pair with other Booking engine details module guide sections

Duplicate-transfer cleanup pairs with Reject/revert mistaken receipts and Managing a Check-out. Hub parity: Common Workflows — Check-out ledger cleanup before refund. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Check-out ledger cleanup before refund — Hub matrix when engine-sourced bookings show duplicate departure transfers before deposit release

• Reject/revert mistaken receipts — Reject / Revert duplicate before Ready To Refund

• Managing a Check-out — Step 6 — Canonical departure-week duplicate cleanup before refund

• Common Workflows — Check-out collections before refund — Real arrears contrast (tenant did not pay)

• Bookings — Transactions tab — Per-row Reject / Revert on engine bookings

• Managing a Check-out — Departure settlement after ledger cleanup

• FAQ — Check-out ledger cleanup before refund hub — Symptom table for phantom In Debt / Ready To Refund blocked when tenant paid once

Utility overage collections

Pair with other Booking engine details module guide sections

Engine-sourced bookings carry utility overage In Debt after bill posting — verify Payment Plan before collections. Hub parity: Common Workflows — Utility overage collections. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Utility overage collections — Hub matrix when engine bookings show utility overage In Debt after bill posting

• Bookings — Payment Plan tab — Overage schedule lines on engine-sourced reservations

• Entering Monthly Utility Bills — Step 4 — Upstream posting before collections

• Utilities — Allocations tab — Overage math for engine inventory

• Handling a Late Payment — Step 1 — Collections after overage posts

• FAQ — Utility overage collections hub — Symptom table for unpaid utility overage on Payment Plan after bill posting

Cancellation collections before void

Pair with other Booking engine details module guide sections

Pre-cancel arrears on engine-sourced bookings pair with Cancelling a Booking. Hub parity: Common Workflows — Cancellation collections before void. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Cancellation collections before void — Hub matrix when engine-sourced bookings show pre-cancel arrears before policy void

• Cancelling a Booking — Step 2 — Settle engine booking before Step 4

• Handling a Late Payment — Steps 1–4 — Collections on engine imports

• Bookings — Payment Plan tab — Unpaid schedule on engine bookings

• Common Workflows — Check-out collections before refund — Departure-week contrast

• FAQ — Cancellation collections before void hub — Symptom table for In Debt blocking Cancel booking until Payment Plan settles

Check-out collections before refund

Pair with other Booking engine details module guide sections

Engine-sourced booking departure arrears pair with Managing a Check-out. Hub parity: Common Workflows — Check-out collections before refund. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Check-out collections before refund — Hub matrix when engine-sourced bookings show departure-week rent arrears

• Managing a Check-out — Step 6 — Settlement on engine booking before refund

• Handling a Late Payment — Steps 1–4 — Collections on engine imports

• Bookings — Payment Plan tab — Unpaid schedule on engine bookings

• Listings — Full integration — Property payload after settlement

• Common Workflows — Check-out ledger cleanup before refund — Duplicate transfer contrast

• Common Workflows — Cancellation collections before void — Pre-cancel void contrast

• FAQ — Check-out collections before refund hub — Symptom table for rent/fee In Debt blocking Ready To Refund before deposit release

Handling a Late Payment collections

Pair with other Booking engine details module guide sections

Engine-sourced booking schedules behind high receivables pair with Handling a Late Payment after Finance debt receivables triage. Hub parity: Common Workflows — Handling a Late Payment collections hub. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Handling a Late Payment collections hub — Hub matrix when engine-sourced receivables need collections Steps 1–6 (finance-overview-income-chart-debt-aging.png, bookings-detail-payment-plan-tab-schedule.png)
• Bookings — Payment Plan tab — Engine-import schedules behind arrears
• Finance debt receivables triage — Top debtors for engine-sourced debt
• Handling a Late Payment — Steps 1–4 — Collections on engine-import arrears
• Processing a New Booking — Unpaid confirmation on engine Upcoming stays
• Pending manual receipt approval — Pending on engine settlement transfers
• Common Workflows — Cancellation collections before void — Pre-cancel void on engine bookings
• FAQ — Handling a Late Payment collections hub — Symptom table for triage surface → collections step pairing

Check-out vs cancellation

Pair with other Booking engine details module guide sections

Engine-sourced bookings follow the same lifecycle exits — completed stay → Managing a Check-out Ended vs policy void → Cancelling a Booking Canceled. Hub parity: Common Workflows — Check-out vs cancellation. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Check-out vs cancellation — Hub matrix: engine booking lifecycle exits (booking-engine-details-editor.png, bookings-list-canceled-tab.png)
• Bookings — Check-out vs cancellation — Ended / Canceled on engine-sourced reservations
• Managing a Check-out — Completed engine booking closure
• Cancelling a Booking — Policy void on engine booking
• Processing a New Booking — Upstream import before exit routing
• Cancel Booking vs Delete Booking — Engine duplicate cleanup vs real void
• FAQ — Check-out vs cancellation — Symptom table for lifecycle exit routing

Deposit missing on Finance Deposits

Pair with other Booking engine details module guide sections

Engine-sourced bookings can show deposit data on the booking Deposit tab while Finance → Deposits hides the row — clear toolbar date range before marketplace deposit triage. Hub parity: Common Workflows — Deposit missing on Finance Deposits. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Deposit missing on Finance Deposits — Hub matrix (booking-engine-details-listing-editor.png, finance-deposits-date-range-clear-flow.mp4)
• Bookings — Deposit missing on Finance Deposits — Per-reservation deposit vs Finance row
• Processing a New Booking — Deposit missing on Finance Deposits — Confirmation deposit after Step 5
• Finance — Deposits tab — Portfolio refund queue
• Listings — Full integration pill — Rich payload editor entry from property sidebar
• FAQ — Deposit missing on Finance Deposits — Symptom table for toolbar date range triage

Notification row-click navigation

Pair with other Booking engine details module guide sections

White-label and partner bookings with unpaid schedules surface payment overdue rows — /notifications row-click usually lands on Bookings first; verify Full integration payload on the related property or unit only after Notification triage — Step 4. Hub parity: Common Workflows — Notification row-click navigation. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Notification row-click navigation — Hub matrix (notifications-row-navigate-to-booking-detail.png, notifications-row-navigation-flow.mp4)
• Notifications module — Notification row-click navigation — Canonical /notifications row-click pairing
• Dashboard — Notification row-click navigation — Bell General vs full /notifications row-click
• Bookings — Notification row-click navigation — Booking sidebar when alert carries bookingId (most engine-sourced alerts)
• Tenants — Notification row-click navigation — Tenant profile when alert carries tenantId
• Listings — Notification row-click navigation — Property or unit sidebar when alert carries listingId or propertyId
• Legacy /properties URLs — Notification row-click navigation — Legacy bookmarks that land in Listings during alert triage
• Audit — Notification row-click navigation — Discounts review after engine-sourced booking row-click
• Operations — Notification row-click navigation — Turnover-week alerts that row-click into Bookings first
• Utilities — Notification row-click navigation — Overage payment overdue alerts after bill cycle
• Sales — Notification row-click navigation — Channel-import alerts before Multicalendar review
• Analytics — Notification row-click navigation — Month-range KPI charts after row-click opens booking context
• AI Chat — Notification row-click navigation — Verify assistant-cited alerts by row-click before payload edits
• Inbox — Notification row-click navigation — Bell Inbox link deep-link vs General row-click
• How to edit — Full integration pill after row-click opens listing context
• Instant Booking (property + unit) — Partner instant_booking export after alert triage
• Notification triage — Step 4 — Row-click before Step 5
• Payment alert to receivables triage — Ongoing/Ended payment overdue row-click
• Confirmation alert triage — Upcoming Booking created / Payment received row-click
• Onboarding a New Property — Step 4 — Optional Full integration pill after go-live alerts
• FAQ — Notification row-click navigation — Target field order (link, bookingId, tenantId, listingId, propertyId)

Payment alert to receivables triage

Pair with other Booking engine details module guide sections

When white-label or partner bookings with unpaid schedules surface payment overdue rows, row-click into Bookings and finish Handling a Late Payment — Step 1 before you change Full integration marketing copy account-wide. Hub parity: Common Workflows — Payment alert to receivables triage. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Payment alert to receivables triage — Hub matrix (notifications-row-navigate-to-booking-detail.png, notifications-row-navigation-flow.mp4, finance-overview-debt-aging-walkthrough-flow.mp4)
• Notifications module — Payment alert to receivables triage — Payments category row-click entry
• Dashboard — Payment alert to receivables triage — Total Debt KPI after alert row-click
• Bookings — Payment alert to receivables triage — Payment Plan / Transactions on opened booking
• Finance — Payment alert to receivables triage — Overview → Debt Aging after single-booking triage
• Tenants — Payment alert to receivables triage — With Debt cross-check on tenant profile
• Listings — Payment alert to receivables triage — Property Payments Active portal charges on engine-enabled properties
• Legacy /properties URLs — Payment alert to receivables triage — Collections on bookings tied to redirected properties
• Audit — Payment alert to receivables triage — Discounts review when receivables lag behind goodwill lines
• Operations — Payment alert to receivables triage — Unpaid move-in lines before key handover
• Utilities — Payment alert to receivables triage — Utility overage lines behind overdue alerts
• Sales — Payment alert to receivables triage — Channel-import schedules behind overdue alerts
• Analytics — Payment alert to receivables triage — Revenue trend may lag until receivables clear
• AI Chat — Payment alert to receivables triage — Validate assistant debt answers after receivables triage
• Inbox — Payment alert to receivables triage — payment overdue on General before WhatsApp chase
• Instant Booking (property + unit) — Partner export rules after receivables triage
• Notification row-click navigation — Row-click on /notifications before payload edits
• Pending manual receipt approval — Amber Pending before debt KPI sign-off
• Confirmation alert triage — Contrast Upcoming vs Ongoing/Ended alerts
• Handling a Late Payment — Step 1 — Canonical receivables triage on engine-sourced bookings
• FAQ — Payment alert to receivables triage — Alert-type contrast table
• FAQ — Payment alert to receivables triage hub — Engine-sourced schedules behind overdue alerts symptom table

Finance debt receivables triage

Pair with other Booking engine details module guide sections

White-label engine-sourced payment schedules behind high receivables — reconcile Debt Aging after portal confirmation transfers clear Pending. Hub parity: Common Workflows — Finance debt receivables triage. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Finance debt receivables triage — Hub matrix (finance-overview-income-chart-debt-aging.png, finance-overview-debt-aging-walkthrough-flow.mp4)
• Payment alert to receivables triage — Single-booking alert triage before portfolio surfaces
• Finance — Finance debt receivables triage — Debt Aging Top debtors canonical surface
• Pending manual receipt approval — Clear amber Pending before Top debtors sign-off
• Dashboard — Finance debt receivables triage — Total Debt headline vs Finance drill-down
• Bookings — Finance debt receivables triage — Payment Plan on opened booking
• Handling a Late Payment — Finance debt receivables triage — Debt Aging on Step 1 before outreach
• Portfolio KPI review — Finance debt receivables triage — Month-end Top debtors on Step 7
• FAQ — Finance debt receivables triage hub — Symptom table for four-surface triage
• What gets configured — Engine-sourced schedules vs VIVIN ledger
• Bookings — Finance debt receivables triage — Opened booking from engine import

Finance Income status drill-down

Pair with other Booking engine details module guide sections

Engine-sourced rent schedules may inflate Scheduled segments — cross-check Income chart before portfolio KPI sign-off. Hub parity: Common Workflows — Finance Income status drill-down. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Finance Income status drill-down — Hub matrix (finance-overview-income-status-in-debt-modal.png, finance-overview-income-drill-down-flow.mp4)
• Finance debt receivables triage — Debt Aging Top debtors when payment-line modal is not enough
• Finance — Income status drill-down — Stacked Income chart canonical surface
• FAQ — Finance Income status drill-down hub — Symptom table for segment vs Debt Aging
• FAQ — Finance Income status drill-down — Paid / Scheduled / In debt segment-click habit
• Portfolio KPI review — Finance Income status drill-down — Month-end Income reconciliation on Step 7
• Booking engine details — Finance debt receivables triage — Engine-sourced schedules behind high receivables
• Listings — Finance Income status drill-down — Unit-level debt vs payment-line modal

Cash flow forecast drill-down

Pair with other Booking engine details module guide sections

Engine-sourced schedules may inflate Income → Scheduled — Cash flow forecast shows confirmed collections only. Hub parity: Common Workflows — Cash flow forecast drill-down. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Cash flow forecast drill-down — Hub matrix (finance-overview-cash-flow-all-payments-modal.png, finance-overview-cash-flow-day-view.png, finance-overview-cash-flow-drill-down-flow.mp4)
• Finance Income status drill-down — Paid / Scheduled / In debt segments — not collections history
• Finance — Income chart and cash flow forecast — Canonical Cash flow forecast chart surface
• FAQ — Cash flow forecast drill-down hub — Symptom table for collections vs Income / Dashboard
• FAQ — Cash flow forecast drill-down — Month / Day bar-click habit
• Portfolio KPI review — Cash flow forecast drill-down — Month-end collections reconciliation on Step 7
• Booking engine details — Finance debt receivables triage — Engine-sourced schedules behind high receivables
• Listings — Cash flow forecast drill-down — Unit-level collections vs portfolio month bars

Confirmation alert triage

Pair with other Booking engine details module guide sections

Upcoming Booking created / Payment received alerts on white-label or partner imports row-click into Bookings — finish Processing a New Booking — Step 5b and verify Full integration payload on Onboarding a New Property — Step 4 before bulk-clear on /notifications. Hub parity: Common Workflows — Confirmation alert triage. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Confirmation alert triage — Hub matrix (notifications-row-navigation-flow.mp4)
• Notifications module — Confirmation alert triage — Canonical inbox pairing
• Bookings — Confirmation alert triage — Transactions / Contract Info on Upcoming imports
• Dashboard — Confirmation alert triage — Post-login Upcoming alert backlog on bell
• Tenants — Confirmation alert triage — Tenant Info / Category on confirmation-week clusters
• Finance — Confirmation alert triage — Transactions amber Pending before Overview KPI refresh
• Listings — Confirmation alert triage — Channel import bookings on go-live properties
• Legacy /properties URLs — Confirmation alert triage — First alerts after legacy redirects land in Listings
• Audit — Confirmation alert triage — Month-end Discounts review after confirmation receipts approved
• Operations — Confirmation alert triage — Turnover prep after confirmation receipts approved
• Sales — Confirmation alert triage — Channel-import Upcoming alerts before Channels linking
• Analytics — Confirmation alert triage — Upcoming alerts during month-end KPI review
• AI Chat — Confirmation alert triage — Assistant-cited confirmation backlog before bulk mark-read
• Inbox — Confirmation alert triage — WhatsApp thread after Payment received row-click
• Utilities — Confirmation alert triage — First bill cycle after go-live alerts
• Tab reference (property details) — Property payload tabs after confirmation receipts approved
• Tab reference (listing / unit details) — Unit payload tabs on channel-linked imports
• Notification row-click navigation — Row-click on /notifications before mark-read
• Payment alert to receivables triage — Contrast Upcoming vs Ongoing/Ended payment overdue
• Pending manual receipt approval — Payment received alert until Approve payments
• Processing a New Booking — Step 5b / Step 6 — Canonical confirmation gates on engine imports
• Onboarding a New Property — Confirmation alert triage — First confirmation alerts on go-live (Step 4 Full integration)
• Notification triage — Confirmation alert triage — Steps 4 / 5 path
• FAQ — Confirmation alert triage — Alert-type table and bulk mark-read guard
• FAQ — Confirmation alert triage hub — White-label Upcoming alerts before payload sync symptom table

New inventory to first booking handoff

Pair with other Booking engine details module guide sections

Engine-sourced first Upcoming reservations on newly onboarded inventory still require Onboarding — Step 7 Listings pass before Processing a New Booking — Step 1 duplicate check — engine payload sync does not skip confirmation Steps 5b / 6. Hub parity: Common Workflows — New inventory to first booking handoff. Full pairing matrix: booking-engine-details-section-cross-reference · Module cross-reference.

• Listings — New inventory to first booking handoff — Portfolio verify after engine connect
• Bookings — New inventory to first booking handoff — Engine-sourced first Upcoming stay
• Onboarding a New Property — Step 7 — Upstream go-live verify
• Processing a New Booking — Step 1 — Duplicate check on engine import
• Common Workflows — New inventory to first booking handoff — Hub matrix (bookings-add-booking-modal.png, workflows-onboarding-property-wizard.mp4)
• Property setup to first arrival handoff — Downstream arrival week
• FAQ — New inventory to first booking handoff — Symptom table for property wizard → first reservation

Property setup to first arrival handoff

Pair with other Booking engine details module guide sections

Engine-sourced first Upcoming reservations on newly onboarded inventory still require Listings — Access Lockers and Managing a Check-in — Steps 1–4 — engine payload sync does not replace arrival-week ops. Hub parity: Common Workflows — Property setup to first arrival handoff. Full pairing matrix: booking-engine-details-section-cross-reference · Module cross-reference.

• Listings — Property setup to first arrival handoff — Access Lockers before key handover
• Bookings — Property setup to first arrival handoff — Engine-sourced first Upcoming stay
• Operations — Property setup to first arrival handoff — Check-in & Check-out arrival-week lists
• Onboarding a New Property — Step 7 — Upstream go-live verify after engine connect
• Managing a Check-in — Step 1 — Downstream arrival-week entry
• Common Workflows — Property setup to first arrival handoff — Hub matrix (listings-property-edit-access-lockers-tab.png, workflows-onboarding-property-wizard.mp4)
• FAQ — Property setup to first arrival handoff — Symptom table for go-live → first arrival week

Confirmation to check-in handoff

Pair with other Booking engine details module guide sections

Engine-sourced Upcoming reservations need Processing a New Booking — Step 6 portal gates before arrival-week planning on partner-fed inventory. Hub parity: Common Workflows — Confirmation to check-in handoff. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Listings — Editing properties — Property/unit setup before first engine booking arrival
• Confirmation alert triage — White-label Upcoming alerts before payload sync
• Bookings — Confirmation to check-in handoff — Contract Info portal gates on Upcoming imports
• Onboarding a New Property — Step 7 — First arrival after Step 7 go-live
• Common Workflows — Confirmation to check-in handoff — Hub matrix (bookings-detail-contract-method-of-payments.png, workflows-operations-check-in-out-planning-view.png, booking-lifecycle-status-tabs-flow.mp4)
• Processing a New Booking — Step 6 — Upstream portal sanity before handoff
• Managing a Check-in — Step 1 — Downstream arrival-week entry (~7 days out)
• Pending manual receipt approval — Step 5b confirmation receipts before handoff
• FAQ — Confirmation to check-in handoff — Symptom table for Upcoming → arrival week

Check-in to check-out handoff

Pair with other Booking engine details module guide sections

Engine-sourced Ongoing bookings entering departure week need the same Managing a Check-out — Step 1 handoff as direct imports — portal gates from Confirmation to check-in handoff are already closed. Hub parity: Common Workflows — Check-in to check-out handoff. Full pairing matrix: booking-engine-details-section-cross-reference · Module cross-reference.

• Bookings — Check-in to check-out handoff — Engine-sourced Ongoing departure planning
• Operations — Check-in to check-out handoff — Check-outs pill on engine imports
• Listings — Editing Properties — Full integration pill before departure week
• Managing a Check-in — Step 4 — Upstream keys handed over
• Managing a Check-out — Step 1 — Downstream departure-week entry
• Common Workflows — Check-in to check-out handoff — Hub matrix (operations-check-in-out-check-outs-next-7-days.png, bookings-timeline-view.png)
• FAQ — Check-in to check-out handoff — Symptom table for Ongoing → departure week

Check-out final utilities handoff

Pair with other Booking engine details module guide sections

Engine-sourced bookings entering departure week carry the same final utility overage mesh as direct imports — Bookings — Bills included ceiling on the linked reservation drives overage math. Hub parity: Common Workflows — Check-out final utilities handoff. Full pairing matrix: booking-engine-details-section-cross-reference · Module cross-reference.

• Listings — Editing Properties — Engine listing Bills Included context for final-cycle overage
• Bookings — Check-out final utilities handoff — Engine booking Payment Plan overage lines
• Utilities — Check-out final utilities handoff — Canonical bill posting upstream
• Listings — Check-out final utilities handoff — Unit ceiling context from inventory
• Entering Monthly Utility Bills — Step 4 — Upstream overage posting verification
• Managing a Check-out — Step 6 — Settlement before deposit release
• Common Workflows — Check-out final utilities handoff — Hub matrix (utilities-allocations-review-flow.mp4, bookings-detail-payment-plan-tab-schedule.png)
• FAQ — Check-out final utilities handoff — Symptom table for final utility overage blocking refund

Same-day turnover coordination

Pair with other Booking engine details module guide sections

Engine-sourced bookings on high-turnover units need the same Bookings — Timeline view overlap check as direct imports — hub parity: Common Workflows — Same-day turnover coordination. Full pairing matrix: booking-engine-details-section-cross-reference · Module cross-reference.

• Common Workflows — Same-day turnover coordination — Hub matrix (sales-multicalendar-tab.png, bookings-timeline-day-week-month-and-sidebar.mp4)
• Bookings — Same-day turnover coordination — Engine booking Timeline overlap
• Sales — Same-day turnover coordination — Multicalendar channel-scoped overlap
• Listings — Same-day turnover coordination — Unit calendar bars on engine inventory
• Onboarding a New Property — Same-day turnover coordination — First reservation turnover planning on Step 7
• Processing a New Booking — Same-day turnover coordination — Timeline overlap during Step 1 import check
• FAQ — Same-day turnovers — Four-step operator habit
• Glossary — Same-day turnover — Distinct from channel double-book

WhatsApp per-booking messaging

Pair with other Booking engine details module guide sections

Engine-sourced tenant threads pair with Bookings → Communication before Full integration payload edits — verify message traffic on the reservation before changing engine fields. Hub parity: Glossary — WhatsApp per-booking messaging hub · Common Workflows — WhatsApp per-booking messaging. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — WhatsApp per-booking messaging — Hub matrix (bookings-detail-communication-tab-whatsapp-thread.png, inbox-module-overview.png, inbox-module-triage-flow.mp4)
• Glossary — WhatsApp per-booking messaging hub — Surface table + per-guide/module mesh reciprocal hub
• Dashboard — WhatsApp per-booking messaging — Bell Inbox sub-tab vs General on post-login scan
• Notifications — WhatsApp per-booking messaging — Canonical /notifications message alert rows
• Bookings — WhatsApp per-booking messaging — Communication tab composer with Payment Plan context
• Inbox — WhatsApp per-booking messaging — Cross-booking triage and bell Inbox sub-tab
• Tenants — WhatsApp per-booking messaging — Tenant profile after Inbox name click
• Finance — WhatsApp per-booking messaging — Collections outreach with Transactions visible
• Operations — WhatsApp per-booking messaging — Maintenance ticket threads on Communication
• Listings — WhatsApp per-booking messaging — Go-live property tenant threads after channel import
• Utilities — WhatsApp per-booking messaging — Utility overage bill questions on Communication
• Sales — WhatsApp per-booking messaging — Channel-import message backlog during Multicalendar review
• Analytics — WhatsApp per-booking messaging — Month-end message backlog during KPI review
• AI Chat — WhatsApp per-booking messaging — Assistant-cited threads before operational follow-up
• Audit — WhatsApp per-booking messaging — Month-end communication review after Discounts audit
• Legacy /properties URLs — WhatsApp per-booking messaging — Legacy bookmarks during message triage
• Notification row-click navigation — Engine-sourced alerts before Full integration payload edits
• Common Workflows — Notification row-click navigation — New WhatsApp message from … on /notifications vs bell Inbox
• Notification triage — WhatsApp per-booking messaging — Message pings on bell Inbox / /notifications
• Handling a Late Payment — WhatsApp per-booking messaging — Collections outreach on Step 3
• Managing a Check-in — WhatsApp per-booking messaging — Arrival-week threads before Step 4
• Managing a Check-out — WhatsApp per-booking messaging — Departure settlement on Step 6
• Processing a New Booking — WhatsApp per-booking messaging — Confirmation follow-up on Step 6
• Cancelling a Booking — WhatsApp per-booking messaging — Void outreach before Step 4
• Entering Monthly Utility Bills — WhatsApp per-booking messaging — Overage bill questions on Step 4
• Portfolio KPI review — WhatsApp per-booking messaging — Month-end message backlog on Step 7
• Manual block hygiene — WhatsApp per-booking messaging — Blocked-date questions on Step 3
• Onboarding a New Property — WhatsApp per-booking messaging — First tenant threads on Step 7 go-live
• Using in-app support — WhatsApp per-booking messaging — Self-serve Inbox / Communication before filing
• Resetting a Management User Password — WhatsApp per-booking messaging — Lockout-delayed bell Inbox after Step 3
• FAQ — WhatsApp per-booking messaging hub — Engine-sourced tenant threads before Full integration payload sync symptom table

Bot reasoning (audit)

Pair with other Booking Engine Details module guide sections

Engine-sourced tenant bot threads before payload sync. Hub parity: Glossary — Bot reasoning (audit) hub · Common Workflows — Bot reasoning (audit). Full pairing matrix: Booking Engine Details section cross-reference · Module cross-reference.

• Common Workflows — Bot reasoning (audit) — Hub matrix (bookings-detail-communication-tab-bot-reasoning-expanded.png)
• Glossary — Bot reasoning (audit) hub — Surface table + per-guide/module mesh reciprocal hub
• Bookings — Bot reasoning (audit) — Canonical Communication Reasoning control
• ChatBot settings — Read-only audit vs editable persona / IF/THEN

ChatBot settings

Pair with other Booking Engine Details module guide sections

Account Settings → ChatBot pairs with Communication thread review — engine-sourced tenant bot threads before payload sync. Hub parity: Glossary — ChatBot settings hub · Common Workflows — ChatBot settings. Full pairing matrix: Booking Engine Details section cross-reference · Module cross-reference.

• Common Workflows — ChatBot settings — Hub matrix (settings-chatbot-tab-overview.png, settings-chatbot-status-bot-connected.png, settings-chatbot-save-rule-flow.mp4)
• Glossary — ChatBot settings hub — Surface table + per-guide/module mesh reciprocal hub
• ChatBot settings — Persona, IF/THEN rules, Status Bot pairing
• Glossary — Bot reasoning (audit) hub — Thread audit after rule changes

Rent reduction after invoicing

Pair with other Booking engine details module guide sections

Engine-sourced bookings may hit the invoiced floor on Change monthly rent after first Hostkit export — repricing starts on Bookings → Contract Info, not payload sync here. Pair Bulk Hostkit invoicing when relief needs Not issued credit note rows. Hub parity: Common Workflows — Rent reduction after invoicing. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Rent reduction after invoicing — Hub matrix (bookings-detail-change-monthly-rent-modal.png, bookings-rent-reduction-invoiced-floor-flow.mp4)
• Bookings — Changing contract dates and rent — Contract Info repricing entry point
• Bookings — Contract Values tab — Per-line Edit amount under the same floor
• Finance — Invoiced floor and rent edits — Why edits start on the booking, not Finance → Transactions
• How to edit — Full integration pill vs booking-sidebar repricing
• Processing a New Booking — Rent reduction after invoicing — Confirmation month already invoiced on Step 3
• Handling a Late Payment — Rent reduction after invoicing — Collections goodwill after Step 4
• Portfolio KPI review — Rent reduction after invoicing — Month-end repricing sign-off on Step 7
• Cancelling a Booking — Rent reduction after invoicing — Settlement repricing during Step 2b
• Managing a Check-in — Rent reduction after invoicing — Pre-move-in goodwill
• Managing a Check-out — Rent reduction after invoicing — Departure-week goodwill adjustments
• Notification triage — Rent reduction after invoicing — Row-click to invoiced booking on Step 4
• Entering Monthly Utility Bills — Rent reduction after invoicing — Month-end bill cycle on Step 5
• Manual block hygiene — Rent reduction after invoicing — Hold cleanup on Step 5
• Using in-app support — Rent reduction after invoicing — Self-serve before filing tickets
• Resetting a Management User Password — Rent reduction after invoicing — Lockout-delayed repricing after Step 3
• FAQ — Rent reduction after invoicing hub — Engine-sourced booking repricing blocked by invoiced floor symptom table

Month-end invoicing (fixed date)

Pair with other Booking engine details module guide sections

Engine-sourced bookings in month-end bulk Issue allocation batches share the same fixed Invoice date amber toolbar banner on Finance → Transactions. Hub parity: Common Workflows — Month-end invoicing (fixed date). Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Month-end invoicing (fixed date) — Hub matrix (settings-invoicing-invoice-date-toggle.png, finance-transactions-fixed-invoice-date-banner.png, finance-transactions-bulk-toolbar-fixed-invoice-date-banner.png)
• Invoicing — Default invoice date — Account-wide toggle + Save
• Common Workflows — Bulk Hostkit invoicing — Issue allocation after fixed date is saved
• Booking engine details guide subsection index — Engine-sourced rows before month-end export
• Finance — Month-end invoicing with a fixed date — Bulk toolbar reminder beside Issue allocation
• Processing a New Booking — Month-end invoicing (fixed date) — First-month bulk export after confirmation (Step 6b)
• Handling a Late Payment — Month-end invoicing (fixed date) — Collections batch during Step 6b
• Portfolio KPI review — Month-end invoicing (fixed date) — Step 7 sign-off mesh
• Notification triage — Month-end invoicing (fixed date) — Alert cleanup before bulk Issue allocation (Step 5)
• Entering Monthly Utility Bills — Month-end invoicing (fixed date) — Finish Missing data + overage Pending (Steps 4b–5)
• Manual block hygiene — Month-end invoicing (fixed date) — Clear stale holds before Issue allocation (Step 5)
• Using in-app support — Month-end invoicing (fixed date) — Self-serve before filing wrong-date tickets
• Resetting a Management User Password — Month-end invoicing (fixed date) — Lockout-delayed month-end export after Step 3
• FAQ — Month-end invoicing (fixed date) hub — Engine-sourced bookings in month-end bulk export with fixed Invoice date symptom table

Bulk Hostkit invoicing

Pair with other Booking engine details module guide sections

Engine-sourced bookings appear in month-end bulk Issue allocation rows on Finance → Transactions — same Hostkit pacing as direct reservations. Hub parity: Common Workflows — Bulk Hostkit invoicing. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Bulk Hostkit invoicing — Hub matrix (finance-transactions-bulk-selection-bar.png, settings-invoicing-hostkit-series.png)
• Common Workflows — Month-end invoicing (fixed date) — Fixed Invoice date before bulk Issue allocation
• Settings > Invoicing — Hostkit invoice series — Required FR code before Issue allocation
• Finance — Invoice automation — Bulk Issue allocation / Invoice selected toolbar
• Finance — Issuing credit notes (integrated invoicing) — Issue credit notes (N) after invoiced Reject / Revert
• What gets configured — Engine-sourced rows in bulk export
• Finance — Bulk Hostkit invoicing — Transactions toolbar reference
• Processing a New Booking — Bulk Hostkit invoicing — First-month Issue allocation after confirmation (Step 6b)
• Handling a Late Payment — Bulk Hostkit invoicing — Collections month-end mesh (Step 6b)
• Portfolio KPI review — Bulk Hostkit invoicing — Step 7 month-end sign-off
• Managing a Check-in — Bulk Hostkit invoicing — Move-in Pending mesh (Step 6b)
• Managing a Check-out — Bulk Hostkit invoicing — Departure-week mesh (Step 6b)
• Onboarding a New Property — Bulk Hostkit invoicing — First month-end on new inventory
• Cancelling a Booking — Bulk Hostkit invoicing — Settlement bulk export (Step 6b)
• Notification triage — Bulk Hostkit invoicing — Alert cleanup before bulk export (Step 5)
• Entering Monthly Utility Bills — Bulk Hostkit invoicing — Finish Missing data + overage Pending (Steps 4b–5)
• Manual block hygiene — Bulk Hostkit invoicing — Clear stale holds before Issue allocation (Step 5)
• Using in-app support — Bulk Hostkit invoicing — Self-serve Hostkit pacing before filing tickets
• Resetting a Management User Password — Bulk Hostkit invoicing — Lockout-delayed month-end export after Step 3
• FAQ — Bulk Hostkit invoicing slow — Hostkit HTTP 429 pacing and refresh-before-reissue habit
• FAQ — Bulk Hostkit invoicing hub — Engine-sourced bookings in month-end bulk Issue allocation Hostkit pacing symptom table

Directory list load failures

Pair with other Booking engine details module guide sections

Engine payload review often follows Bookings or Listings directory triage — use list-card Retry when the first fetch fails before you open Full integration editor rows. Hub parity: Common Workflows — Directory list load failures. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Directory list load failures — Hub matrix (notifications-module-load-failure.png)
• Processing a New Booking — Directory list load failures — Channel import triage on Step 1
• Listings — Directory list load failures — Portfolio Retry before engine unit edits
• Onboarding a New Property — Directory list load failures — Go-live verify on Step 7
• FAQ — Directory list load failures — Whole-module vs filter-empty state
• FAQ — Directory list load failures hub — Engine-sourced booking triage blocked by directory first-fetch failure symptom table
• Glossary — Directory list load failures hub — Surface table + per-guide/module mesh reciprocal hub

Occupancy KPI to block hygiene handoff

Pair with other Booking engine details module guide sections

Engine-sourced listings with suppressed Occupancy on partner feeds may still carry stale manual holds in Listings — pair hub Common Workflows — Occupancy KPI to block hygiene handoff before changing marketplace availability flags. Hub parity: Common Workflows — Occupancy KPI to block hygiene handoff. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Occupancy KPI to block hygiene handoff — Hub matrix (booking-engine-details-editor.png, audit-manual-blocks-filter-scroll.mp4)
• Listings — Occupancy KPI to block hygiene handoff — Unit Calendar hold cleanup
• Sales — Multicalendar tab — Channel availability vs holds
• Onboarding a New Property — Step 7 — Go-live Multicalendar hold check
• Manual block hygiene — Downstream Audit pass
• FAQ — Occupancy KPI to block hygiene handoff hub — Symptom table for engine listing availability dip
• Managing a Check-in — Occupancy KPI to block hygiene handoff — Timeline overlap from stale holds on Step 1
• Managing a Check-out — Occupancy KPI to block hygiene handoff — Calendar bars persist after Step 7
• Cancelling a Booking — Occupancy KPI to block hygiene handoff — Availability not restored on Step 5
• Entering Monthly Utility Bills — Occupancy KPI to block hygiene handoff — Dashboard vs Analytics vacancy mismatch on Step 5
• Notification triage — Occupancy KPI to block hygiene handoff — Vacant Units vs Analytics on Step 1
• Resetting a Management User Password — Occupancy KPI to block hygiene handoff — Lockout-delayed KPI review after Step 3
• Using in-app support — Occupancy KPI to block hygiene handoff — Calendar edit blocked after block hygiene
• Handling a Late Payment — Occupancy KPI to block hygiene handoff — Vacant Units vs Multicalendar holds on Step 1

Partly collected security deposit

Pair with other Booking Engine Details module guide sections

Deposit shortfalls pair with Finance — Deposits status summary cards and Bookings — Deposit tab. Hub parity: Common Workflows — Partly collected security deposit. Full pairing matrix: Booking Engine Details section cross-reference · Module cross-reference.

• Common Workflows — Partly collected security deposit — Hub matrix when Paid on the deposit is above zero but below Amount
• Finance — Deposit lifecycle status cards — Partial paid card for portfolio triage (#2091)
• Finance — Deposit status filter — Other filters → Deposit status → Partial paid on Bookings and Finance (#2090)
• Operations — Tickets toolbar search — Paste the full sequential ticket ID (for example S259, T27) in toolbar Search (#2074)
• FAQ — Find a ticket by its ID — Paste the full sequential ticket ID (for example S259, T27) in Operations → Tickets toolbar Search (#2074)
• FAQ — Skip automatic check-in/out tickets for one booking — Turn off Use unit contract rents and other contract details on Add booking to reveal CI/CO ticket checkboxes (#1140)
• FAQ — Same-day turnovers — Check-out + check-in on one unit same day: Operations → Check-in & Check-out, Timeline / Multicalendar, turnover tickets
• FAQ — Manual payments after Delete Booking — Delete Booking hides manual/provider_platform rows on Finance → Transactions; vIBAN and credit card stay visible (#1897)
• Glossary — Directory list load failures — First-fetch directory failures show Retry / Try again; distinct from filter-empty states and booking-sidebar tab errors
• Glossary — Vacant Unit Preference — Include manual blocks counts operator holds as free on Dashboard / Sales vacancy surfaces (#1427)
• FAQ — Communication or Tickets load failure — Tab-scoped Refresh (Communication) or Retry (Tickets); other booking sidebar tabs stay usable
• Bookings — Deposit tab — Partially paid badge and remaining helper on a single reservation
• FAQ — Partly collected security deposit — Distinct from Partial Paid rent on Payment Plan
• Finance — Deposit lifecycle status cards — Deposit lifecycle status row (#2091)
• Glossary — Deposit lifecycle status — depositStatus pill vocabulary (Partial Paid vs rent Partial Paid)
• Finance — Deposit lifecycle status cards — Deposit lifecycle status row on Finance → Deposits; click Partial paid for collection shortfalls (#2091)
• Manual block hygiene — Partly collected security deposit — Partial paid card when debt KPIs stay high after holds cleared (Step 5)
• Resetting a Management User Password — Partly collected security deposit — Lockout-delayed deposit triage after Step 3
• Using in-app support — Partly collected security deposit — File Finance module tickets when partial filter or badge behaviour is wrong

Portfolio segmentation by tenant category

Pair with other Booking engine details module guide sections

Segment filters pair with Settings > Tenant categories and Portfolio KPI review — Step 6. Hub parity: Common Workflows — Portfolio segmentation by tenant category. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Common Workflows — Portfolio segmentation by tenant category — Hub matrix when engine-sourced overdue alerts cluster on one tenant segment
• Settings > Tenant categories — Default segment on engine-sourced direct bookings
• Bookings — Other filters tenant category — Segment filter when payment alerts cluster on one cohort
• Finance — Tenant category filter — Ledger segmentation for engine booking debt
• Tenants — Tenant category filter — Profile-count cross-check before segment-wide portal changes
• Portfolio KPI review — Step 6 — Optional month-end segment pass on weak engine-sourced metrics

Key glossary terms

Pair with other Booking engine details module guide sections

Glossary rows pair with Glossary cluster cross-reference. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Glossary — End-of-Booking cost split — Charge Time → End of Booking splits daily overage across every occupied unit; still-staying roommates stay in the denominator (#2111)

• Operations — Property-level ticket search — Property-name matches share the top relevance tier with unit hits; building-scoped rows float first under an active Property filter (#2089)

• Glossary — Change history — Operator-initiated edits on Listings setup and Bookings Changelog; create-time defaults excluded (#2093)

• FAQ — Booking Changelog scope — Operator-initiated edits only; create-time defaults excluded (#2093)

• Glossary — Archived booking ledger visibility — Delete Booking hides manual/provider_platform rows on Finance → Transactions; vIBAN and credit card stay visible (#1897)

• Bookings — Provider platform payment — Non-rejected provider platform in-payment blocks Delete Booking until Reject or assign (#2076)

• FAQ — Delete Booking on integration reservation — Clear pending provider platform in-payment with Reject or assign before soft-archive (#2076)

• Listings — Property edit sidebar pills — Setup / Full integration / Photos pills on property and unit edit sidebars; replaced the old Go to details shortcut (#2082)

• Glossary — Finance tenant category cache refresh — Recategorizing a tenant on Tenants → Tenant Info force-refreshes Finance caches so Contract Values, Overview, and Deposits filters match within seconds (#2088)

• FAQ — Finance tenant category filter parity — Finance Other filters drawer lists segments on cached bookings only; mirror Bookings / Tenants when a segment is missing

• FAQ — Assign tenant category for direct booking — Add booking has no category field; assign on Tenants → Tenant Info or + Create New → Tenant before contract mail

• Glossary — SIMAR water contract ID — SIMAR (Loures e Odivelas) water bills use Cód. Local in Connections — not Nº de Contador; leading zeros stripped (#2110)

• FAQ — SIMAR water bill property match — Cód. Local in Connections — not Nº de Contador; strip leading zeros (#2110)

• Glossary — Per-booking maintenance ticket opt-out — Add booking checkboxes skip automatic CI/CO tickets for one reservation only; property rule unchanged (#1140)

• FAQ — Cancel Booking vs Delete Booking — Cancel for real stays with settlement; Delete soft-archives mistaken/test rows (#1897 / #2076)

• Glossary — Archived property — Archive retires a building to Listings → Archived without deleting bookings; distinct from Delete Booking (reservation soft-archive) — Listings — Archived properties

• FAQ — Archive a property — Edit property sidebar Archive / Unarchive on Listings; building-level — not Delete Booking or Cancel booking

• FAQ — Portfolio retirement decisions — Archive property (building) vs Cancel booking vs Delete Booking (reservation soft-archive) — three-way decision table

• Glossary — Invoiced floor (rent) — Rent edits on live bookings blocked below exported invoice totals

• FAQ — Bulk Hostkit invoicing slow — Vivin paces Hostkit API calls and retries HTTP 429 during bulk Issue allocation / Invoice selected; refresh Transactions before re-issuing

• FAQ — Lower rent below invoiced — Rent on live bookings is edited in Bookings, not here

• FAQ — AI token usage — Poll GET /ai-usage / GET /ai-usage/summary with management JWT; landlord_chat + utility_bill_extraction; no management UI screen yet

• FAQ — Automatic check-in email — Trigger matrix, 15-day cutoff, paper upload vs portal signing, Nuki-only toggle, Send / Resend on Contract Info

• FAQ — WhatsApp and email per booking — Bookings → Communication tab when tenant chatbot is enabled; Inbox for portfolio-wide triage

• FAQ — Deposit missing on Finance Deposits — Default ~3 months date range; clear or widen before triaging older move-outs or dispute row actions

• FAQ — Pending manual in-payment on /notifications — Alert persists until Approve payments clears Finance or booking Transactions

• FAQ — Uncovered Debt KPI — Finance Total Debt minus deposit offsets; pair with Debt Aging and In debt drill-down

• FAQ — Dashboard Total Debt subtitle — Post-login Total Debt card headline vs >15 days subtitle; ongoing bookings only

• FAQ — Analytics (KPI workspace) — Portfolio KPIs vs Sales/Listings/Dashboard; load-failure Try again

• FAQ — Reject or revert an incoming payment — Reject pending rows or Revert confirmed ones; Finance → Transactions uses Reject selected bulk-only; modals warn about credit notes when Finance already invoiced

• FAQ — Finance Income status drill-down — Overview Income chart (Paid / Scheduled / In debt); click a segment for month-scoped payment-line modal; Debt Aging for booking-level receivables

• FAQ — Permission denied toast — Red You do not have permission to perform this action. toast when RBAC blocks a save; fix in Users → Role Permissions

• FAQ — Phone shows Operations only — Mobile phone user agent locks operators with Operations access to /operations; iPads and narrow desktop browsers keep the full module list

• FAQ — Notification row-click navigation — On /notifications, row click marks unread then opens link, bookingId, tenantId, listingId, or propertyId (first match); Dashboard bell General rows stay in-panel unless link is set

• FAQ — Bookings that owe money — Top debtors and overdue buckets on Finance → Overview; Total Debt KPI is not a table

• FAQ — Fixed rent on variable unit — Variable listing + equal rent every contract month → booking stores fixed headline Monthly rent; payment plan unchanged

API & partner surfaces

Pair with other Booking engine details module guide sections

API bullets pair with API Reference hub. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Booking Engine API — Public PUT /listing and reservation endpoints that ingest this editor
• API Reference — Full listing feeds — Partner-shaped publish feeds that ingest this editor’s output
• API Reference — Listings & Availability — Partial GET /listings pulls that ingest marketing fields edited here
• API Reference — iCal feeds — Outbound calendar URLs partners copy after payload edits sync
• Property & unit mapping — externalId contract partners use before editing payloads here
• AI usage API — Management JWT cost ledger (contrast integration Bearer keys on partner listing routes above) (section cross-reference; hub)

Module documentation hubs

Pair with other Booking engine details module guide sections

Module hub bullets pair with Modules — Module cross-reference. Full pairing matrix: Booking engine details section cross-reference · Module cross-reference.

• Sales — Channel Manager — Marketplace links after payload edits sync to partners
• Sales — Pricing tab — Live rent operators edit after payload sync to partners
• Listings — Step 3 Extra payments — Bills Included ceilings are property setup fields, not booking-engine payload tabs
• Audit module — Portfolio-wide Manual Blocks and Discounts contract-value review (hub)
• Utilities module — Operator bill entry and tenant overage when actual supplier costs exceed billsIncludedMaxValue ceilings partners read from partial pulls (hub)
• Finance module — Portfolio ledgers once engine-sourced stays accumulate Contract Values (hub)
• Finance — Tenant category filter — Reconcile Contract Values In Debt for the same segment after engine-sourced overdue triage
• Bookings module — Reservation lifecycle after white-label or partner bookings land (hub)
• Bookings — Other filters tenant category — Mirror segment filter when Finance cache parity lags
• Tenants — Tenant category filter — Profile-count cross-check before changing portal rules account-wide
• Tenant Portal — Tenant-facing pages that render marketing fields edited here (hub)
• FAQ — Tenant contract signing blocked — No PDF yet, mandatory Your Details gates, category locks, or Lease purpose; portal signing vs paper upload on Contract Info
• Account Settings — Workspace-wide financial policies, templates, integrations, and operational defaults (hub)
• API Reference hub — Partner HTTP contracts, Swagger onboarding, and partial vs full feeds (hub)