Sixto vs Mews: Colombian stay operations and hotel complexity
Sixto brings reservations, guest check-in, SIRE, TRA and DIAN invoicing workflows together for Colombian hospitality teams.
Use the same property, corporate payer and occupied-room migration scenario. Mews documents hotel billing and a broader hospitality ecosystem; Sixto focuses the configured Colombian stay workflow around the team. Confirm each country service and avoid assuming equivalent scope.
Published workflows, compared by scope
Reviewed 17 October 2026. Described capabilities are not independently tested; confirm your plan, property setup and integrations.
| Capability | Sixto | Mews |
|---|---|---|
| Reservations and channels | Sixto channel management; connected accounts required | Hotel reservations, booking engine and distribution connections |
| SIRE reporting | Preparation and filing; credentials and activation required | Confirm the Colombian submission route and activation |
| TRA reporting | Preparation and filing; property setup and activation required | Confirm the Colombian submission route and activation |
| Colombian electronic invoicing | Configured MATIAS integration; issuer enablement required | Confirm local fiscal connection and legal-entity eligibility |
| Online registration and identity checks | Guest and companion registration with document-review workflow | Guest profiles and check-in tools; confirm document verification |
| Smart-lock access | Supported connected locks; permissions and access rules required | Door-access integrations; confirm hardware and workflow |
| Colombian tax evidence | Evidence records for review; tax eligibility is case-specific | Demonstrate required evidence capture and retention |
| Cleaning and assigned work | Cleaning and team tasks | Housekeeping offering; confirm included product and setup |
| Staff time records | Time records and review workflows | Confirm time capture and approval, distinct from task status |
| Financial workflows | Expenses, receipts and invoicing workflows | Hotel billing, accounting categories and payment workflows |
Sixto publishes this comparison. “Confirm” identifies an unresolved scope question, not an absent feature. Native workflows, partner integrations and general product capabilities are different.
- Mews Operations product scope
- Mews Payments and regional scope
- Mews Marketplace
- Serviced apartments
- Preparing a PMS go-live
- Property-specific pricing
- POS country availability
Sixto next to Mews, workflow by workflow
Compare the documented scope of each workflow, the connections required and the work your team retains. Product versions, plans and activation requirements can differ.
Where to evaluate Sixto for your operation
- Connected hospitality workReview reservations, guest conversations, tasks, registration, reporting and financial workflows in one operating context. Confirm live connections and permissions.
- Drafts and controlled actionsSixto drafts replies and suggests next steps. Review the approval and automation settings that apply to each action and staff role.
- Colombian operating workflowsReview SIRE, TRA and configured Colombian invoicing alongside the daily work. Credentials, enablement and activation prerequisites still apply.
| Workflow | SixtoSixto workflow | MewsFrom its official page |
|---|---|---|
| Colombian compliance | ||
| TRA and SIRE | Sixto Sixto workflow Reports prepared from the guest's check-in data, with receipts and pending cases in one place. Credentials and go-live are set up with you during onboarding.Explore workflow |
Mews Confirm in demo Country-specific statutory services require an explicit Colombian scope check. |
| DIAN e-invoicing | Sixto Sixto workflow Prepare electronic-invoicing workflows from stay information through the configured MATIAS integration. Issuer enablement, numbering, credentials and tax configuration must be established; eligibility is case-specific.Explore workflow |
Mews Confirm in demo Demonstrate the local fiscal route and production prerequisites. |
| Guest journey | ||
| Guest registration | Sixto Sixto workflow Online check-in collects guest and companion details before arrival. Explore workflow |
Mews Described by provider Guest profiles and check-in are documented; inspect companion and verification scope. |
| Guest conversations | Sixto Sixto workflow Guest conversations from connected channels, with replies drafted for staff review. Your sending provider is connected with you during onboarding.Explore workflow |
Mews Described by provider Guest communication offerings are described; establish the included module and channels. |
| English and Spanish | Sixto Sixto workflow Guests and your team each use Sixto in English or Spanish, and replies are drafted in the guest's language. Explore workflow |
Mews Confirm in demo Test staff, guest, support and connected-module languages separately. |
| Daily operation | ||
| Reservation calendar | Sixto Sixto workflow Stays and physical units in one calendar, kept in sync with your channels. We connect your reservation source with you during onboarding.Explore workflow |
Mews Described by provider Hotel reservations and distribution connections are documented. |
| Cleaning and assigned tasks | Sixto Sixto workflow Assign work, record completion and keep its history. Explore workflow |
Mews Described by provider Housekeeping is offered; verify the configured product and handoff. |
| Expenses and receipts | Sixto Sixto workflow Record expenses, attach receipts and review the ledger. Explore workflow |
Mews Confirm in demo Distinguish hotel billing categories from supplier expenses and owner accounting. |
| Intelligence and connections | ||
| Replies and next steps from Sixto | Sixto Sixto workflow Sixto drafts replies and suggests next steps. Approval and automation follow the configured workflow and permissions. Permissions follow each person's role.Explore workflow |
Mews Described by provider Intelligent guest communication and reporting tools are marketed; confirm plan and controls. |
| Works with your tools | Sixto Sixto workflow Connect supported reservation sources, channels and compatible smart locks. Confirm the provider, supported actions, account setup and permissions before activation.Explore workflow |
Mews Described by provider Marketplace integrations need individual contracts, country and support checks. |
| Documented workflow coverage | Sixto10/10 documented0 need confirmation | Mews6/10 documented4 need confirmation |
Each of these 10 workflows counts once, including documented partner integrations. Counts describe documented scope, not an independent product test or a quality ranking. A workflow needing confirmation is an unresolved scope question, not a missing feature. Plan, country, setup and activation requirements still apply.
See your operation in Sixto
Bring an arrival, a cleaning task and an open case. We walk through the whole workflow and set it up with you during onboarding.
How to make the decision
Choose the system that handles the transactions your hotel actually performs with understandable exceptions and accountable staff. Sixto is a candidate for Colombian shared operations; Mews merits consideration when more complex hotel finance and connected services are central. Neither a feature count nor a reservation import replaces a reconciled operational pilot.
A hotel PMS can be a financial operating model
Mews is relevant when the hotel’s complexity lives in the relationships among stays, charges, payers and departments. A room can be occupied by one person, paid partly by a company and associated with extras handled elsewhere in the property. The important capability is preserving a coherent account as those relationships change. Our assessment is that this can justify a deeper hotel system even in a relatively small building. The tradeoff is organizational: configuration, finance ownership and training become part of the implementation. A richer model creates little value if staff cannot explain how an exception changes the guest balance.
Sixto’s comparison starts with Colombian operating work
For a Colombian aparthotel, the hardest problem may instead be getting the same arrival information to the people who need it and completing the work attached to the stay. Sixto is worth evaluating when that coordination is the core requirement. The decision should not presume that every hotel-finance or restaurant scenario has an equivalent Sixto workflow. Likewise, Mews’ broad product scope should not be mistaken for ready-to-use local services in every country. A credible proposal connects the property’s operating requirements to the available configuration, accountable people and any services that must remain outside the main system.
An occupied-property cutover is a finance event
Changing a hotel PMS while guests remain in house creates an overlap between two records of the business. The new system needs usable operational data, but the old system may still explain deposits, previous charges or documents already issued. That makes migration a shared responsibility between front office and finance, rather than a technical import alone. A staged plan can preserve historical evidence while assigning each open stay to a clear checkout and payment process. The cost of this work belongs in the comparison. The most convincing pilot proves both that a room can be sold correctly and that its final account can be reconciled.
Questions to take to a demonstration
Use real cases from your property. A successful demonstration should show the result, the person responsible and what happens when a step fails.
Can the system represent what you actually sell?
List rooms, apartments, combined units and any separately bookable services. Add a corporate stay extended twice and a reservation moved to another room mid-stay. Ask how availability, rate changes and the guest’s bill stay consistent. Mews describes an extended-stay use case; validate the configuration against your own contracts. In Sixto, test the actual supported unit and reservation workflow rather than assuming parity with every hotel space model. A proposed workaround deserves an owner, a time estimate and an explicit acceptance decision.
Who owes each charge, and who can change it?
Use a stay where an employer pays the room, the guest pays extras and a deposit must be applied at checkout. Ask reception to correct a charge without hiding the original event, then ask finance to reconcile the result. Mews documents hotel billing and accounting categories; the useful test is whether your staff can follow the complete transaction. Require the same clarity in Sixto’s available workflow. Distinguish a guest statement, a tax document, a payment transaction and the settlement received in the bank.
What changes when the guest is already in the building?
A future-booking import is not the whole migration. Prepare a cutover list of occupied rooms, out-of-order inventory, unpaid balances, deposits and departures on the switch date. Mews specifically warns that availability blocks are not transferred with reservation imports. Rebuild and verify such restrictions before reopening sales. Give front office and finance a shared sign-off sheet, and agree where a guest already in house will check out. Do not assume importing a reservation has transferred every operational or financial responsibility attached to it.
Will housekeeping and reception agree on room readiness?
Run a same-day departure and arrival, a room move, a maintenance hold and a cleaning task that cannot be completed on time. Ask who can change status, how reception learns about the delay and what remains visible after a shift handover. Examine the housekeeping product or connection included in the actual Mews proposal, not an unrelated demonstration module. In Sixto, show the assigned work and the context staff use to resolve it. Approve the process only when the next person can understand the exception without repeating the whole conversation.
Which country services are genuinely available to your entity?
Confirm the PMS, acquiring and settlement, terminal hardware, POS and statutory connections independently. A product’s presence in one country does not prove that every module is sold or supported there. For a Colombian property, request the exact SIRE, TRA and DIAN route and its production prerequisites. A general invoice or a list of payment currencies is not sufficient evidence. For Sixto, review the enabled local workflow, permissions and credentials. For an operation outside Colombia, do not treat Sixto as an available international rollout until country onboarding is explicitly supported.
Who resolves an integration failure at the worst moment?
Select the channel connection, door-access service, accounting export and any restaurant integration needed for your property. For each, name the contracting party, configuration owner and support contact. Simulate a delayed update or rejected transaction and ask where the failure appears and who retries it. Mews publishes a Marketplace, but the presence of a listing is only the start of a scope check. Compare the total number of handoffs in both proposals, including any work your own team must perform when two suppliers each consider the other responsible.
How do payment terms affect the real commercial decision?
Request a written proposal using the same legal entity, rooms, transaction mix and settlement assumptions. Separate software, implementation, connected modules, payment processing, hardware and any premium support. Ask about minimum commitments, renewal changes, refunds, chargebacks and exit exports. Mews describes embedded payments, so include finance in the evaluation before treating the software quote as the full cost. Do not assume that existing card credentials can move to a new provider. Require a documented arrangement for future charges and guests with payments already collected.
What is the acceptance test for choosing Sixto or Mews?
Run one ordinary stay and one deliberately difficult stay from reservation to reconciled checkout. Have reception, housekeeping and finance use their own permissions and working languages. Prefer Sixto when the Colombian shared workflow solves the important handoffs and the remaining requirements fit its demonstrated scope. Keep or choose Mews when the hotel’s billing, departmental or integration requirements make its operating model the better match. Before switching, approve balance reconciliation, inventory checks, guest communication and a named rollback decision-maker. A successful demonstration is evidence for a pilot, not a reason to skip cutover controls.
Run the same practical test
- Choose one arrival with a change of dates or companions and follow it from booking to checkout.
- Ask a second team member to take over, with their own permissions and without an extra spreadsheet.
- Try a missing prerequisite or failed integration. Check recovery, history and responsibility before deciding.
Sources and review date
- Mews Operations product scope
- Mews Payments and regional scope
- Mews Marketplace
- Serviced apartments
- Preparing a PMS go-live
- Property-specific pricing
- POS country availability