A Guide to Revela System Errors and What to Do Next

When something goes wrong in Revela, the system communicates the issue through error messages. This guide explains what those messages mean, how to tell whether the issue is something you can fix yourself, and when it makes sense to reach out to support for help.

How Errors Appear in Revela

Revela uses several different types of notifications to let you know when something needs your attention. Understanding where and how errors appear makes it easier to respond to them quickly.

Banner messages appear at the top of the page after you perform an action. A red banner indicates an error, while a green banner confirms success. These messages typically appear after submitting a form, saving a record, or completing a workflow. They remain visible until you navigate away from the page.
Toast notifications are smaller messages that appear briefly in the corner of your screen. These are used for quick confirmations or warnings, such as when a record is successfully updated or when a background process encounters a problem. Toast notifications disappear on their own after a few seconds.
Inline form errors appear directly on the form you are filling out, usually highlighted in red near the field that needs your attention. These errors prevent the form from being submitted until the issue is corrected. They are the most common type of error you will encounter during day-to-day data entry.
Full-page error screens appear when Revela is unable to load a page at all. These screens display a clear message describing the problem, such as “Page Not Found” or “Something Went Wrong,” along with a link to go back or contact support.

Common Error Categories

Most errors in Revela fall into a few broad categories. Recognizing which category an error belongs to helps you understand what happened and what to do next.

Validation errors occur when the information you entered does not meet the requirements for that field or form. These are the most common errors and are almost always something you can resolve by correcting the data and resubmitting.
Permission errors appear when your user role does not have access to a particular feature or action. These are not mistakes on your part, they simply mean your account is not configured for that function.
Accounting restriction errors are specific to the accounting module and occur when an action conflicts with a closed period, a locked journal, or a linked document. These errors protect the integrity of your financial records.
System errors are rare and indicate that something unexpected happened on Revela’s side. These typically appear as a full-page error screen and are automatically reported to the Revela support team.

Accounting and Journal Errors

The accounting module in Revela has safeguards in place to protect your financial data. Because of this, certain actions are intentionally restricted, and you may encounter specific error messages when working with journals, invoices, and payments.

Closed and Locked Period Restrictions If you see the message “Period is already locked”, it means the accounting period you are trying to post to has been closed. Once a period is locked, no new transactions can be posted before that lock date. This protects your financial statements and owner reports from being changed after they have been finalized.

To resolve this, check the lock date on the journal by navigating to the entity and reviewing the journal settings under Actions > Management Contract. If the transaction truly needs to be posted in the locked period, an administrator will need to unlock the period first.

Journal Entry Editing Restrictions

When you try to edit or delete a journal entry and see the message “Please modify the associated invoice instead of this entry” or “Please modify the associated payment instead of this entry”, it means the entry was created automatically by an invoice or payment. Revela prevents direct edits to these entries to keep your books in sync. Instead, navigate to the original invoice or payment record and make your changes there.

Invoice Validation Messages When creating or editing an invoice, Revela checks that all required information is present and valid. Common messages include:
- “Invoice must contain at least one line item” means you need to add at least one charge or credit line before saving the invoice. Every invoice requires at least one line item with an account, description, and amount.
- “Due date cannot be before invoice date” appears when the due date is set earlier than the invoice date. Adjust the due date so it falls on or after the invoice date.
- “Buyer must be different than seller” indicates that the same entity has been selected as both the buyer and the seller. Review your selections and correct the appropriate field.
- “This invoice cannot be deleted because it is linked to a payment” means a payment has already been applied to this invoice. To remove the invoice, you will first need to void or unapply the associated payment.

Payment and Batch Errors

“Batch Already Closed” appears when you attempt to process a payables batch that has already been finalized. Once a batch is closed, it cannot be modified. If additional payments are needed, create a new batch under Accounting > Payables > Batches.
“Not all invoices are approved” means one or more invoices in the payment have not yet been approved. Navigate to the invoices in question and approve them before proceeding with the payment.
“This payment cannot be voided” indicates that the payment’s current status does not allow voiding. Payments can typically only be voided while they are still processing. If the payment has already been settled, a reversal or refund may be required instead.
“Please select a withdrawal account” appears when no bank account has been chosen for the payment. Select the appropriate bank account before submitting.
“Overdraft acknowledgement cannot be blank” means the payment would cause the withdrawal account balance to go negative. Revela requires you to acknowledge this before proceeding. Review the payment amount and confirm whether you want to continue.

Reporting Errors

Revela’s reporting module is designed to handle large volumes of data, but certain conditions can cause issues when generating or exporting reports.

“Unable to Load Report” appears when a report encounters a problem during generation. This can happen if the report includes a very large date range or an unusually high volume of data. Try narrowing the date range or reducing the number of properties included, and then regenerate the report.
“Timed-out while preparing documents. Please try again.” means the system took too long to compile the requested documents. This most often occurs with large document packages or bulk exports. Try generating the documents for a smaller set of records, or wait a few minutes and try again.
“Download Failed” appears as a toast notification when a background export does not complete successfully. This can happen with large data exports. If the issue persists after a second attempt, contact support and let them know what you were trying to export.

Note: When exporting data to spreadsheets, keep in mind that very large exports may be automatically trimmed. If your export seems to be missing records, try applying filters to reduce the dataset and export in smaller batches.

Permission and Access Errors

Revela uses role-based access to control what each user can see and do within the system. When you encounter a permission error, it means your user role does not include the access needed for that specific action.

“You do not have permission to perform this action” is the most common permission error. It appears when you try to do something, like approving an invoice, modifying a setting, or accessing a restricted page, that is outside the scope of your assigned role.
“You Don’t Have Access” appears as a full-page message when you navigate to a section of Revela that your role cannot view. The page will include a message saying “If you believe this is an error, contact your administrator” along with a link to go back.
“You are not authorized to access this resource” is a similar message that can appear when attempting to view or modify a specific record, like a bank account detail or a configuration setting.

These errors are not caused by anything you did wrong. They reflect how your account has been configured by your organization’s administrator. If you believe you should have access to a feature, reach out to your administrator or manager to request a role update. Administrators can manage user roles under Setup > User Roles.

Data Entry and Validation Errors

Validation errors appear inline on forms when the information entered does not meet the requirements for a particular field. These are straightforward to resolve once you know what the system is looking for.

Required Fields The most common validation error is a blank required field. Messages like "Description can’t be blank”, “Post date can’t be blank”, or “Amount can’t be blank” indicate that a mandatory field was left empty. Required fields are typically marked on the form, and the error message will name the specific field that needs attention.
Date and Amount Formatting Revela validates that dates and amounts are entered correctly. If you see a message like “Amount must be greater than 0”, check that you have entered a positive number. For date fields, ensure the date is realistic, for example, lease start dates must be after 1969, and end dates must be before 2100.
“Post date cannot be within a closed period” means the date you selected falls within a locked accounting period. Choose a date that falls after the period lock date.
Duplicate and Conflict Checks Some records must be unique. “Email has already been taken” means another contact in the system already uses that email address. Similarly, “Primary contact already exists for the company” indicates that only one primary contact is allowed per company record.
Import File Errors When importing data via spreadsheet, Revela validates the file before processing it. “Unable to parse file. Please ensure it is a valid CSV file” means the file format is not recognized. Make sure you are uploading the correct file type.
“Unable to find required column(s)” followed by column names means the spreadsheet is missing one or more columns that the import expects. Check the import template and ensure all required columns are present with the correct headers.
“Row count exceeds the maximum limit” means the file has too many rows. Split the file into smaller batches and import each one separately.

Note: Individual row errors, like a missing required value in a specific row, will be listed with the row number so you can locate and fix the issue in your spreadsheet before re-importing.

Session and Login Errors

Occasionally, you may encounter errors related to logging in or staying logged in. These are typically quick to resolve.

“Invalid email or password” means the credentials you entered do not match an active account. Double-check your email address and password. If you have forgotten your password, use the Forgot your password? link on the login page to receive a reset email. Password reset links expire after six hours.
“Your session expired. Please log in again to continue.” appears when your session times out due to inactivity. For security, Revela automatically ends sessions after a period of inactivity. Simply log in again to continue where you left off. Before your session expires, you will see a warning notification with the option to continue your session or log out.
“Your account is locked” means too many unsuccessful login attempts have been made. Wait a short period and try again, or contact your administrator to unlock your account.
“Your account has been archived” indicates that your user account has been deactivated. Reach out to your organization’s administrator if you believe this was done in error.

Determining the Type of Issue

When you encounter an error, the first step is understanding whether the issue is something you can fix, something your administrator needs to address, or something that requires support from Revela.

It is likely a data entry issue if the error message names a specific field, mentions a blank or invalid value, or appears inline on a form. These errors are resolved by correcting the information and resubmiting. Examples include missing required fields, invalid dates, or duplicate records.

It is likely a permissions issue if you see messages about not having permission, not being authorized, or not having access. You will not be able to resolve these on your own, they require an administrator to update your user role or grant access to the relevant feature.

It is likely an accounting restriction if the error references a locked period, a linked document, or a batch that is already closed. These restrictions are intentional safeguards. Determine whether the restriction is correct (and you should use a different date or approach) or whether an administrator needs to temporarily unlock the period.

It is likely a system issue if you see a full-page error screen that says “Something Went Wrong,” or if the error does not reference a specific field or action you took. System errors are automatically reported to the Revela team. If they persist, contact support.

When and How to Escalate to Support

Most errors in Revela can be resolved by correcting data, adjusting dates, or working with your administrator on permissions. However, there are situations where contacting Revela support is the right next step.

Reach out to support when:

You see a “Something Went Wrong” error that persists after refreshing the page
When an export or report repeatedly fails despite using a smaller dataset
When a payment or transaction is stuck in an unexpected status
When an error message does not clearly explain what went wrong

To contact support, click your name or profile icon in the upper-right corner of Revela and select Contact Support. The support form asks you to categorize your issue, identify the area of the platform where it occurred, provide a description, and set the priority level.

When describing the issue, include what you were trying to do, the exact error message you saw, and any specific records involved (e.g., a property name, invoice number, or tenant name). The more detail you provide, the faster the support team can investigate. If the error appeared on a full-page error screen, you may also see a feedback form directly on that page where you can describe the problem.

Best Practices

Pay attention to the exact wording of error messages. Revela’s messages are designed to tell you precisely what went wrong and often point directly to the field or record that needs attention. Reading the message carefully before taking action can save you time.

Before posting transactions, confirm that the date falls within an open accounting period. This is one of the most common sources of accounting errors and is easy to avoid by checking the journal’s lock date ahead of time.

If you frequently encounter permission errors for actions you need to perform, have a conversation with your administrator about adjusting your user role. It is more efficient to update role permissions than to work around access restrictions.

When importing data, always start with the provided import template. Templates ensure your columns match what Revela expects and reduce the chance of parsing errors. For large imports, consider splitting the file into smaller batches to avoid row count limits and make it easier to identify any row-level issues.

Keep your browser up to date and clear your cache periodically. Occasionally, display issues or unexpected behavior can be resolved simply by refreshing the page or clearing stored browser data.