Integration field capabilities
The Integration capabilities tab at /settings/integrationFieldCapability is a read-only reference matrix. It shows which property and listing (unit) detail fields from the booking-engine payload editor are supported for each connected marketplace integration, and whether a partner marks a field as required when publishing.
Use it when you are preparing Property & listing details (booking engine) content and need to know what a channel expects before you edit fields in Listings → Full integration pill. Credentials, toggles, and calendar rules still live on Integrations and per-unit Channels.
Read this matrix during Getting Started — Recommended Setup Sequence steps 11–12 alongside Integrations and Tenant categories default for integrations before you link units on Listings → Channels in step 13 — full tab map: Recommended setup order. Finish steps 14–15 and Onboarding a New Property — Step 7. Partner payload reference: API Reference — Property & Unit Mapping. Workflow pairing after go-live: Account Settings — Setup sequence after go-live.
Use Filters to narrow by integration, then read Reading the matrix for required vs supported fields. Credentials still live on Integrations — see How this relates to other settings. Non-linear operator habits (Lockout catch-up, Pending manual receipt approval, Reject/revert mistaken receipts, Portfolio segmentation by tenant category, 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) have matching Related subsections below. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Tab cross-reference.
Open Account Settings → System → Integration capabilities at platform.vivin.app/settings/integrationFieldCapability. Requires the same integration-related settings permission as the Integrations tab (account_settings.integrations). See Deep Links — Account Settings.
Read-only matrix — connect platforms on Integrations first, then link units on Listings → Channels using external IDs this matrix references. Month-end partner payload triage pairs with Portfolio KPI review — Step 7 and optional AI usage API (landlord_chat when AI Chat helped close field gaps). Section-to-doc pairing: Integration field capabilities section cross-reference. Hub tab matrix: Account Settings — Tab cross-reference.
Who can open it
Same integration-settings permission family as Integrations — audit Users and roles — Role Permissions before sharing the matrix URL with channel coordinators. Full pairing matrix: Integration field capabilities section cross-reference.
The sidebar entry appears under Account Settings → System when your role includes integration settings access (same permission family as Integrations). Without it, the tab is hidden and the URL shows the standard permission state.
Filters
Integration depth switches between partial calendar feeds and full outbound payloads — see Integrations & Distribution and API Reference — partial vs full feeds before narrowing columns. Full pairing matrix: Integration field capabilities section cross-reference.
Three controls narrow the matrix:
| Filter | Purpose |
|---|---|
| Integration depth | Full integration — outbound full-feed payloads and property/listing details entities (with optional Details entity filter). Partial integration — calendar/listing pull surfaces; combines all detail layers and hides the entity filter. |
| Integration | Multi-select marketplace columns (for example Uniplaces, Spotahome, Housing Anywhere). All shows every platform in the matrix. |
| Details entity | (Full integration only.) All, Property details, or Listing details to limit rows to one payload layer. |
The hint text under the filters explains how to read checkmarks and Req labels for the active depth mode.
Reading the matrix
Amber warning cells mean a partner-required field is missing from Vivin's payload — fill gaps in Property & listing details (booking engine) or on Listings — Channels before publishing. Full pairing matrix: Integration field capabilities section cross-reference.
Each row is a field (and, when Details entity is All, the entity layer is shown in the first column). Each column is an integration platform.
| Cell | Meaning |
|---|---|
| Checkmark | The field is supported for at least one sync direction (inbound or outbound) for that platform in the current mode. |
| Req under a check | The partner feed marks the field as required when publishing, and the field is present in the integration payload. |
| Warning icon (Full integration only) | The partner requires the field, but it is not yet included in this integration payload — a coverage gap to address in product data or engineering. |
| Empty cell (Partial integration) | Partner-required fields that are outside the partial payload may appear empty; switch to Full integration to see gap warnings and filter by entity. |
On Full integration, an amber warning triangle in a cell means the partner marks that field required for publishing, but the field is not yet present in Vivin’s outbound payload for that platform. Fix the data in Property & listing details (booking engine) (the Full integration pill on the property or unit) or escalate to engineering when the matrix shows a gap you cannot fill from Listings. Empty cells on Partial integration may hide the same issue — switch depth to Full and read the warning row.


The capture above uses Full integration with all platforms and entities visible at desktop width (~1536px). Scroll horizontally when many integrations are selected.
Partial integration view
Partial depth hides entity filters — pair calendar-style surfaces with API Reference — Listings & Availability and API Reference — iCal feeds when full-feed warnings are empty. Full pairing matrix: Integration field capabilities section cross-reference.
Partial integration lists fields supported on calendar-style or partial listing feeds, or flagged as partner-required for that depth. There is no Details entity filter — all layers are combined in one table.

Property-only rows
Property-layer rows match the Full integration pill on buildings in Listings — complete them during Onboarding a New Property before linking unit channel IDs. Full pairing matrix: Integration field capabilities section cross-reference.
On Full integration, set Details entity to Property details to limit rows to the property payload layer — the same fields you edit with the Full integration pill on a property in Listings (Profile & copy, Location & geography, Rules & host, and related tabs).
Property entity filter and gap warning cell captures refreshed 2026-06-12 14:10 UTC (VIVIN_DOCS_BASE_URL=http://localhost:5173 VIVIN_DOCS_RECORD_API=$VITE_API_BASE_URL npx tsx tools/capture-settings-integration-field-capability-screenshots.ts).

Listing-only rows
Unit-scoped rows align with Sales → Channel Manager sync actions and API Reference — Full listing feeds outbound payloads. Full pairing matrix: Integration field capabilities section cross-reference.
On Full integration, set Details entity to Listing details to focus on unit-scoped payload fields (the same layer you edit with the Full integration pill on a unit in Listings).

How this relates to other settings
Credentials and calendar cutoffs stay on Integrations — set Tenant categories default for integrations and Emails audiences before high-volume channel imports assign segments automatically. Full pairing matrix: Integration field capabilities section cross-reference.
| Surface | Role |
|---|---|
| Integrations | Connect platforms, API keys, markups, and account-wide calendar cutoffs. |
| Listings → Channels | Link each unit to external listing IDs. |
| Booking engine details | Edit the property/listing payload fields this matrix describes (the Full integration pill). |
| Sales → Channel Manager | Day-to-day per-listing channel status and sync actions. |
The matrix data is maintained in the product codebase; operators cannot edit cells from this screen. If filters produce No matrix rows, widen Integration or Details entity, or switch Integration depth — empty results usually mean no rows match the current filter combination, not that integrations are disconnected.
Integration field capabilities section cross-reference
Use this table when one Integration capabilities topic naturally leads into another Account Settings tab, operator module, workflow, or API guide — each row links to the docs you should read before or after reading the matrix.
| Integration capabilities topic | Pair with these docs |
| --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Who can open it | Integrations, Users and roles |
| Filters | Integrations & Distribution, API Reference — partial vs full feeds |
| Reading the matrix | Property & listing details (booking engine), Listings — Channels tab |
| Partial integration view | API Reference — Listings & Availability, API Reference — iCal feeds |
| Property-only rows | Listings module, Onboarding a New Property |
| Listing-only rows | Sales → Channel Manager, API Reference — Full listing feeds |
| How this relates to other settings | Integrations, Tenant categories, Emails, Handling a Late Payment — Step 1, Notifications — Payment overdue alerts |
| Lockout catch-up after password recovery | Resetting a Management User Password, Getting Started — Lockout catch-up, Common Workflows — Lockout catch-up |
| Pending manual receipt approval | Integrations, Users and roles — Role permissions (Approve payments), Finance — Pending manual payments |
| Reject/revert mistaken receipts | Payment Allocation — Correcting mistaken receipts, Processing a New Booking (duplicate-import triage) |
| Notification row-click navigation | /notifications row-click after import field errors | Account Settings — Notification row-click navigation, Common Workflows — Notification row-click navigation, Notifications module — Notification row-click navigation |
| Payment alert to receivables triage | payment overdue on partial partner payloads | Account Settings — Payment alert to receivables triage, Common Workflows — Payment alert to receivables triage, Handling a Late Payment — Step 1 |
| Confirmation alert triage | Upcoming alerts on field-incomplete imports | Account Settings — Confirmation alert triage, Common Workflows — Confirmation alert triage, Processing a New Booking — Step 5b |
| Finance debt receivables triage | Portfolio Top debtors / Debt Aging after settings on this tab | Account Settings — Finance debt receivables triage, Common Workflows — Finance debt receivables triage, Finance module — Finance debt receivables triage |
| Finance Income status drill-down | Income → In debt vs Debt Aging after settings on this tab | Account Settings — Finance Income status drill-down, Common Workflows — Finance Income status drill-down, FAQ — Finance Income status drill-down hub |
| Cash flow forecast drill-down | Cash flow forecast month bars vs Income segments | Account Settings — Cash flow forecast drill-down, Common Workflows — Cash flow forecast drill-down, FAQ — Cash flow forecast drill-down hub |
| Portfolio segmentation by tenant category | Tenant categories — Default for integrations, Bookings — Other filters, Common Workflows — Portfolio segmentation |
| API & companion guides | AI usage API (management JWT ledger — partner Bearer keys return 401) |
Related
Related below links this Account Settings tab to modules, workflows, concepts, and escalation paths. Pair Documentation map & escalation with Account Settings hub — Documentation map & escalation; pair Upstream & downstream workflows with Account Settings — Tab cross-reference. Topic-to-section pairing in sections above: Integration field capabilities section cross-reference. Full hub matrix: Account Settings — Section cross-reference.
Documentation map & escalation
Documentation-map bullets pair with Introduction — Section cross-reference and FAQ — Section cross-reference. Hub parity: Account Settings hub — Documentation map & escalation. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Account Settings hub — Tab pairing matrix across workspace configuration
- Deep Links — Account Settings — Bookmarkable
/settings/integrationFieldCapability - FAQ & Troubleshooting — Operator questions when matrix filters or channel sync disagree with Listings
- Glossary — Term definitions used across settings and module docs
Upstream & downstream workflows
Workflow bullets pair with Common Workflows — Workflow cross-reference for inter-guide step pairing. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Onboarding a New Property (section cross-reference; Deeper workflow reads; hub) — Connect integrations (Step 5) before linking unit channel IDs
- Processing a New Booking (section cross-reference; Deeper workflow reads; hub) — Verify partner-mapped fields before the first channel import confirms
- Cancelling a Booking (section cross-reference; Deeper workflow reads; hub) — Availability webhooks after early termination changes partner calendars
- Managing a Check-out & Deposit Refund (section cross-reference; Deeper workflow reads; hub) — Channel calendar release after partner stays reach Ended status
- Manual block hygiene (section cross-reference; Deeper workflow reads; hub) — Calendar holds reflected in partial vs full partner payloads
- 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) — Identify overdue charges when partner field gaps cause payment-plan mismatches after sync or a payment overdue alert row-click brought you here
- Notifications — Payment overdue alerts (in-app) — Operator Payments category rows when scheduled charges are overdue on channel-imported bookings
Deeper workflow reads
Workflow reads pair with Common Workflows hub subsection index and Workflow cross-reference. Each workflow sub-guide reciprocates with [Deeper workflow reads](./integration-field-capability.md#deeper-workflow-reads) anchors on Account Settings bullets — hub parity: Account Settings hub — Deeper workflow reads. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Onboarding a New Property — Connect integrations (Step 5) before linking unit channel IDs (section cross-reference; Deeper API reads; hub)
- Processing a New Booking — Verify partner-mapped fields before the first channel import confirms (section cross-reference; Deeper API reads; hub)
- Cancelling a Booking — Availability webhooks after early termination changes partner calendars (section cross-reference; Deeper API reads; hub)
- Managing a Check-out & Deposit Refund — Channel calendar release after partner stays reach Ended status (section cross-reference; Deeper API reads; hub)
- Manual block hygiene — Calendar holds reflected in partial vs full partner payloads (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 — Identify overdue charges when partner field gaps cause payment-plan mismatches after sync or a payment overdue alert row-click brought you here (section cross-reference; Deeper API reads; hub)
Related Account Settings tabs
Tab bullets pair with Account Settings — Tab cross-reference and Recommended setup order. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Integrations — Platform connections and credentials
- Tenant categories — Default for integration-created tenants before channel imports assign segments automatically
- Emails — Lifecycle emails fire for imported bookings once field-capability gaps are resolved
- Preferences — In-app notifications — Account-wide integration or listing alerts after field-capability edits sync to partners
- Services — Partner imports do not create portal service catalogue entries; configure separately
Operator modules
Module bullets pair with Modules — Module cross-reference. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Listings — Channels tab — Unit-level external IDs after matrix confirms required partner fields
- Listings module — Portfolio inventory where operator-edited fields sync to partner payloads
- Sales → Channel Manager — Day-to-day per-listing sync after platforms are connected
- Booking engine details — Payload editor from Listings (Full integration pill)
- Audit — Discounts tab — Cross-portfolio discount export when partner field gaps cause contract-value mismatches after sync
Deeper concept reads
Concept reads pair with Concepts hub subsection index and Concept cross-reference. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Integrations & Distribution — Partial vs full partner feeds and calendar strategy (section cross-reference; hub)
- Tenant Portal — Field-capability matrix describes partner payloads; portal modules and branding are configured under Preferences and General Information (section cross-reference; 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
- Services Marketplace — Partner imports do not create portal service catalogue entries (section cross-reference; hub)
- Payment Allocation — Two-layer receipts, invoiced-floor rent edits, and credit note reject/revert warnings (section cross-reference; hub)
- Booking Lifecycle — Computed Upcoming → Ongoing → Ended / Canceled status model (section cross-reference; hub)
API & companion guides
API bullets pair with API Reference hub. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- API Reference — Property & unit mapping — UUID ↔ external ID lookups that full partner feeds depend on
- API Reference — Full listing feeds — HTTP surface for full-integration payloads this matrix describes
- API Reference — Listings & Availability — Partial
ListingDtoreads when Integration depth is partial - API Reference — iCal feeds — Calendar export depth when matrix shows partial sync only
- API Reference — Creating Bookings — Write surface after field-capability mapping is verified
- API Reference — Booking Engine API — White-label
PUT /listingfields this matrix describes for the booking engine integration - API Reference — Webhooks & notifications — Inbound events when field-capability gaps block partner payloads
- AI usage API — Operator JWT ledger when month-end partner payload triage used AI Chat (
landlord_chat) (section cross-reference; hub)
Lockout catch-up after password recovery
Operational backlog after sign-in recovery pairs with Resetting a Management User Password — Step 3 before you resume partner field triage on this matrix. Hub parity: Common Workflows — Lockout catch-up after password recovery. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Common Workflows — Lockout catch-up after password recovery — Hub matrix when sign-in was restored mid-setup before steps 11–12 integration field review
- Getting Started — Lockout catch-up after password recovery — Canonical operational backlog mesh (notification triage, Pending Steps 6b, portal gates)
- Integrations — Connect platforms before reading required fields on this matrix
- Pending manual receipt approval — Month-end Pending mesh when channel-imported confirmation receipts await Approve payments
Pending manual receipt approval
Receipt approval pairs with Integrations channel imports and Users and roles (Approve payments permission). Hub parity: Common Workflows — Pending manual receipt approval. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Common Workflows — Pending manual receipt approval — Hub matrix when partner-imported bookings still show pending confirmation receipts until Approve payments
- Finance — Pending manual payments — Amber Pending chip on channel-sourced Finance → Transactions
- Users and roles — Role permissions — Approve payments gates bulk approval after import triage
- Processing a New Booking — Verify channel imports before creating duplicate manual bookings
Reject/revert mistaken receipts
Receipt cleanup pairs with How this relates to other settings duplicate-import triage and Invoicing & Payments export providers. Hub parity: Common Workflows — Reject/revert mistaken receipts. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Common Workflows — Reject/revert mistaken receipts — Hub matrix when duplicate channel imports produced twin confirmation receipts needing Reject / Revert
- Payment Allocation — Correcting mistaken receipts — Two-layer model and credit note accounting follow-up
- Finance — Row actions on in-payment rows — Bulk Reject selected on imported stays
- Listings — Channels tab — Per-unit external IDs this matrix references before imports land in Finance
Portfolio segmentation by tenant category
Segment filters pair with Tenant categories — Default for integrations before high-volume imports and Portfolio KPI review — Step 6. Hub parity: Common Workflows — Portfolio segmentation by tenant category. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Common Workflows — Portfolio segmentation by tenant category — Hub matrix when segment filters must align across channel-imported reservations and tenant profiles
- Tenant categories — Default for integrations before bulk marketplace onboarding
- Bookings — Other filters — Tenant category on imported stays
- Finance — Tenant category filter — Ledger segmentation when reconciling channel-sourced Contract Values
Notification row-click navigation
Partner field requirements do not change /notifications routing — row-click import alerts into Bookings before fixing missing payload fields on this reference page. Hub parity: Account Settings — Notification row-click navigation. Full pairing matrix: Integration field capability section cross-reference · Account Settings — Section cross-reference.
- Account Settings — Notification row-click navigation — Hub matrix (
notifications-module-row-click-target.png,notifications-row-navigation-flow.mp4) - Common Workflows — Notification row-click navigation — Operator procedure hub
- Notifications module — Notification row-click navigation — Canonical
/notificationsinbox pairing - FAQ — Notification row-click navigation hub — Symptom table
Payment alert to receivables triage
Incomplete partner payloads may delay bookings but do not replace payment overdue triage — row-click alerts on live reservations first. Hub parity: Account Settings — Payment alert to receivables triage. Full pairing matrix: Integration field capability section cross-reference · Account Settings — Section cross-reference.
- Account Settings — Payment alert to receivables triage — Hub matrix (
notifications-row-navigate-to-booking-detail.png,notifications-row-navigation-flow.mp4) - Common Workflows — Payment alert to receivables triage — Operator procedure hub
- Handling a Late Payment — Step 1 — Collections follow-through after row-click
- FAQ — Payment alert to receivables triage hub — Symptom table
Confirmation alert triage
Field-capability gaps on imports surface as Upcoming Booking created alerts — finish confirmation Steps 5b / 6 before bulk field-mapping review. Hub parity: Account Settings — Confirmation alert triage. Full pairing matrix: Integration field capability section cross-reference · Account Settings — Section cross-reference.
- Account Settings — Confirmation alert triage — Hub matrix (
notifications-row-navigate-to-booking-detail.png,bookings-detail-transactions-approve-payment-modal.png) - Common Workflows — Confirmation alert triage — Operator procedure hub
- Processing a New Booking — Step 5b / Step 6 — Canonical confirmation gates
- FAQ — Confirmation alert triage hub — Symptom table
Finance debt receivables triage
Required partner fields do not change Debt Aging buckets — triage receivables on Finance → Overview after import errors delay settlement. Hub parity: Account Settings — Finance debt receivables triage. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Account Settings — Finance debt receivables triage — Hub matrix (
finance-overview-income-chart-debt-aging.png,finance-overview-debt-aging-walkthrough-flow.mp4) - Common Workflows — Finance debt receivables triage — Operator procedure hub
- Finance module — Finance debt receivables triage — Canonical Finance → Overview surface
- FAQ — Finance debt receivables triage hub — Symptom table
Handling a Late Payment collections
Required partner fields do not change Debt Aging buckets — triage receivables on Finance → Overview after import errors delay settlement Hub parity: Account Settings — Handling a Late Payment collections. Full pairing matrix: Integration field capability section cross-reference · Account Settings — Section cross-reference.
- Account Settings — Handling a Late Payment collections — Hub matrix (
finance-overview-income-chart-debt-aging.png,notifications-row-navigate-to-booking-detail.png,finance-overview-debt-aging-walkthrough-flow.mp4) - Common Workflows — Handling a Late Payment collections hub — Operator procedure hub
- Finance debt receivables triage — Debt Aging before Step 1
- Pending manual receipt approval — Clear amber Pending before collections outreach
- FAQ — Handling a Late Payment collections hub — Symptom table
- Glossary — Handling a Late Payment collections hub — Surface table + per-guide/module mesh
Finance Income status drill-down
Field-capability gaps do not explain Income segment drift — open segment drill-down when imports leave charges In debt. Hub parity: Account Settings — Finance Income status drill-down. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Account Settings — Finance Income status drill-down — Hub matrix (
finance-overview-income-chart-debt-aging.png,finance-overview-debt-aging-walkthrough-flow.mp4) - Common Workflows — Finance Income status drill-down — Operator procedure hub
- Finance module — Income status drill-down — Canonical Finance → Overview surface
- FAQ — Finance Income status drill-down hub — Symptom table
Cash flow forecast drill-down
Partner feed delays may skew Cash flow forecast month totals — confirm All payments lines after integration-check cron recovers. Hub parity: Account Settings — Cash flow forecast drill-down. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Account Settings — Cash flow forecast drill-down — Hub matrix (
finance-overview-income-chart-debt-aging.png,finance-overview-debt-aging-walkthrough-flow.mp4) - Common Workflows — Cash flow forecast drill-down — Operator procedure hub
- Finance module — Cash flow forecast drill-down — Canonical Finance → Overview surface
- FAQ — Cash flow forecast drill-down hub — Symptom table
Key glossary terms
Glossary rows pair with Glossary cluster cross-reference. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
-
Credit note (payment reject/revert) — Accounting follow-up when partner payload edits follow already-invoiced import receipts; concept walkthrough: Payment Allocation — Correcting mistaken receipts; workflow hub: Common Workflows — Reject/revert mistaken receipts
-
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)
-
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
-
Deposit lifecycle status — Partner
extraDepositPerTenantfields in import payloads feed deposit collection; refund states are operator-managed after import -
Finance — Deposit status filter — Other filters → Deposit status multi-select on Bookings and Finance (#2090)
-
Finance — Deposit lifecycle status cards — Deposit lifecycle status row on Finance → Deposits; click Partial paid for collection shortfalls (#2091)
-
FAQ — Partly collected security deposit — Paid above zero but below Amount on booking Deposit; Partial paid card on Finance → Deposits (#2090 / #2091)
-
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
-
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)
-
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
-
Invoiced floor (rent) — Rent edits blocked below exported invoice totals after Issue allocation / Invoice selected
-
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 — Bulk Hostkit invoicing hub — Symptom table + per-guide mesh
-
FAQ — Lower rent below invoiced — Change monthly rent clamps and Contract Values → Edit amount blocks net below exported invoice totals; use credit notes in accounting when you truly need a reduction
-
Glossary — Fixed invoice date — Account-wide Invoice date before bulk Issue allocation / Invoice selected; amber banner on Finance → Transactions until you turn Use today as invoice date back on
-
FAQ — Month-end invoicing (fixed date) hub — Symptom table + toggle reset after batch
-
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 — Manual receipt still pending — Operator-recorded receipts stay pending until Approve payments; triage on Finance → Transactions (Pending chip) or booking Transactions; Total Debt and Manual Payments KPI lag until approval
-
FAQ — Finance Income status drill-down hub — Symptom table for segment vs Debt Aging
-
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 — Cash flow forecast drill-down hub — Symptom table for collections vs Income / Dashboard
-
FAQ — Cash flow forecast drill-down — Month / Day bar-click habit
-
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 openslink,bookingId,tenantId,listingId, orpropertyId(first match); Dashboard bell General rows stay in-panel unlesslinkis 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
Module documentation hubs
Module hub bullets pair with Modules — Module cross-reference. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.
- Integration field capabilities — Read-only partner payload matrix (this page)
- Utilities module — Bills Included ceiling model, Connections, AI bill upload, and tenant overage charges on payment plans (hub)
- Operations module — Maintenance tickets, cash flows, check-in/out coordination, Draft ticket queues, and linked cash flows (hub)
- Dashboard module — Post-login Today, Total debt, Vacant Units, and forecast KPI snapshot with bell notification triage (hub)
- Analytics module — Month-range portfolio KPI charts (Overview, Revenue, Occupancy, ADR, RevPAR, Maintenance) with rankings and heatmaps (hub)
- Listings module — Property wizard, Channels tab, Archived inventory, and unit management (hub)
- Properties workspace — Legacy
/propertiesURL redirects into Listings (hub) - Finance module — Portfolio ledgers (Overview, Income, Contract Values, Transactions, Payouts, Deposits) with payment approval and deposit settlement (hub)
- Tenants module — Tenant directory, profile sidebars, With Debt segmentation, and table expand for linked bookings (hub)
- Sales module — Portfolio availability, monthly rent editing, and channel manager connections (hub)
- Inbox module — Portfolio-wide WhatsApp workspace with Dashboard bell Inbox sub-tab deep links (hub)
- Notifications module — Full
/notificationshistory with search, filters, and row-click navigation (hub) - AI Chat module — Vivin-internal AI Assistant using Landlord MCP tools for portfolio Q&A (hub)
- Audit module — Portfolio-wide Manual Blocks and Discounts contract-value review (hub)
- 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)