Choosing software

What should serviced apartments test in a hotel PMS for long stays?

Use a six-week booking and a two-week extension to test billing, cleaning and departure changes before choosing your software.

Quick answer

Test a complete extended stay, from the original booking through to final settlement. A serviced apartment PMS should keep dates, availability, agreed rates, billing periods, cleaning tasks and payer balances consistent when departure changes. Run six acceptance tests with sample documents and a live calendar demonstration. Record which steps are included, require an upgrade or integration, or depend on staff intervention before accepting the proposed setup.

Check that your operation fits a hospitality PMS

Focus on guest reservations, bookable apartment inventory, stayover services and departure workflows. If your core requirements are tenancy agreements, rent collection, tenant notices or landlord accounting, assess residential property software separately. A hospitality PMS demonstration does not establish suitability for residential letting, and stay length alone should not decide the software category.

For hospitality stays, write down the rules your team actually uses: billing frequency, extension approval, cleaning cadence, company payment terms and security deposits. These become the acceptance criteria for the demonstration.

Prepare one booking with a measurable extension

Illustrative example: an employee checks into apartment A12 on 5 January 2027, initially departing on 16 February: 42 nights. On 9 February, the employer approves a new departure of 2 March: 56 nights in total. The company pays accommodation every 14 nights; the guest pays personal extras. Your test policy includes a £300 refundable security deposit and weekly Tuesday servicing, starting 12 January.

Use dummy guest and company details. Agree the original and extension rates before testing; do not let the demonstration silently reprice the first six weeks. The deposit amount and billing policy are fictional operational inputs, not RoomRaccoon pricing or a VAT calculation.

Run these six acceptance tests

Ask the supplier to perform each action and show the resulting records. A feature name alone is not evidence that your complete workflow works.

Acceptance checklist: 42 nights extended to 56 nights
TestAction to demonstrateEvidence needed to pass
1. Extension and availabilityTry extending A12 to 2 March with a conflicting booking in place. Then repeat with the extra nights available.The conflict is visible before confirmation. The accepted booking contains 56 nights, preserves the agreed original rates and shows the approved extension price. Inventory matches the revised stay without duplicate reservations.
2. Periodic billingIssue the first 14-night invoice, record its payment, then extend the stay. Demonstrate the remaining billing periods and due dates.Four periods cover 5–19 January, 19 January–2 February, 2–16 February and 16 February–2 March. No night is omitted or billed twice. The issued invoice and its payment remain traceable. Identify separately how invoices are created, sent and paid.
3. Recurring housekeepingGenerate Tuesday services, extend departure, then mark one visit skipped and arrange a replacement.Seven planned stayover visits run from 12 January through 23 February. The 16 February departure clean becomes a stayover service; the final clean moves to 2 March. Staff can see the skipped visit, replacement task and completion status.
4. Company and guest balancesKeep accommodation with the employer, add a personal extra for the guest and approve the extension against the company booking reference.The correct recipient, purchase order reference and due date appear on each relevant document. The guest's extra stays separate. A company payment reduces the correct balance, with no duplicate charge after extension.
5. Security depositRecord the illustrative £300 security deposit separately from accommodation payments. Extend the stay and demonstrate final settlement.Staff can distinguish collected money from any card authorisation. The deposit status, refund or release action, responsible person and history are clear. If using an authorisation, obtain provider confirmation of its validity and the process needed for this stay length.
6. Departure and reconciliationInspect scheduled departure messages, the departure list and your accounting export after the date change. Complete the revised checkout.No obsolete 16 February departure instruction remains queued. The stay ends on 2 March; 56 occupied nights, invoices and payments reconcile without duplicate entries. Demonstrate any connected access-expiry update separately, including a manual fallback.

Billing ranges include the first date and exclude the last. Cleaning dates follow this example's service policy, not a default software setting.

Have your accountant confirm the applicable tax treatment before configuring the example in production. Consult HMRC's accommodation guidance, including its long-stay section; this checklist does not prescribe a VAT rate.

Turn the demonstration into a buying decision

  • Record the delivery method: included functionality, paid upgrade, partner integration or manual procedure, with the exact package and any extra cost.
  • Keep evidence: sample invoices, the revised calendar, task list and reconciliation output. Record who owns any manual exception.
  • Set your acceptance threshold: reject unresolved billing duplication or inventory conflicts. Accept manual steps only when your team can reliably handle their frequency and workload.

Separate recurring invoicing from automatic payment collection. Generating a document every fortnight does not demonstrate that funds will be collected on its due date. Repeat the test using your actual company payment terms and payment provider.

What to demonstrate with RoomRaccoon

RoomRaccoon's hotel property management system describes reservation management, invoice editing and splitting, corporate activity statements and automated guest emails. Use those capabilities as the starting point for the six tests; they do not establish automatic periodic invoicing for every long-stay arrangement.

Its hotel housekeeping software, RaccoonHousekeeping, is presented as an upgrade with stayover scheduling, recurring jobs, task assignment and mobile status updates. Ask how your weekly cadence behaves after an extension. Confirm package inclusion and any payment, accounting or access integration required for the complete workflow.

Bring your own extended-stay scenario. Include original and revised dates, billing periods, cleaning rules and who pays. Ask RoomRaccoon to demonstrate the six tests and identify any configuration or manual steps.

Discuss your serviced apartment setup

Questions before your demo

What if we invoice by calendar month?

Replace the fortnightly periods with your actual month boundaries. Test the partial first and final months, agreed pricing and due dates. Do not assume monthly invoicing means four-week billing.

What if the guest must change apartments?

Repeat the extension test with a move from A12 to another unit. Check availability, service tasks and guest instructions for both units, while ensuring the agreed stay and payment history remain traceable.

Can a manual billing step still be acceptable?

Yes, if its workload is manageable and someone owns the deadline and reconciliation. Ask staff to repeat it themselves. A workaround that depends on remembering an undocumented action is a weak basis for purchase.

Sources and product checks

Checked on 10 November 2026. The checklist is an illustrative evaluation framework; confirm the proposed package and workflows in your demo.