Skip to main content

Make Adjustments when Owner Statements are already published in VRTrust

Use these steps to make adjustments to owner statements in VRtrust in a locked (i.e. already published) state.

Updated today

Why Transactions Are Locked

When an Owner Statement is finalized, VRTrust locks all associated transactions to:

  • Preserve reporting accuracy

  • Prevent accidental changes to reconciled financials

  • Ensure consistency between the General Ledger and Owner Statements


When You Need to Make an Adjustment

You must follow this process if you need to:

  • Delete or modify an Owner Payout

  • Edit or remove an Expense

  • Update a Reservation (rates, fees, or allocations)

  • Make any change that impacts the Owner Statement totals


Step 1: Move the Owner Statement Back to Draft

  1. Navigate to Owner Statements

  2. Locate the relevant statement

  3. Open the statement

  4. Click Edit or Change Status

  5. Select Move to Draft

⚠️ Moving a statement back to Draft will unlock all associated transactions.


Step 2: Make Your Adjustments

Once the statement is in Draft, you can make the necessary changes:

Adjust a Payout

  • Go to Owner Payouts

  • Locate the payout

  • Edit or delete as needed

Edit an Expense

  • Navigate to Expenses

  • Open the expense

  • Update amount, account, or allocation

  • Save changes

Update a Reservation

  • Go to Reservations

  • Open the reservation

  • Adjust financial line items (rent, fees, taxes, etc.)

  • Save changes


Step 3: Review the Owner Statement

After making changes:

  1. Return to the Owner Statement

  2. Click Refresh (if applicable)

  3. Review:

    • Revenue totals

    • Expenses

    • Net Owner Payout


Step 4: Re-Finalize the Statement

Once confirmed:

  1. Change the status from Draft back to Published

  2. Confirm the statement is accurate and complete


Important Notes

  • Audit Trail: All changes are tracked within VRTrust for transparency

  • Closed Periods: If the period is locked, you may need to unlock it before making changes

  • Best Practice: Avoid frequent post-finalization edits—review statements carefully before approving


Did this answer your question?