Guide to Submitting and Paying Online LBTT Returns

Submitting an online LBTT return and what happens next

An online LBTT return can only be submitted once it is complete, any validation errors have been fixed, and the required declarations have been confirmed. After submission, Revenue Scotland issues a unique transaction reference, records the chosen payment method, and shows a confirmation screen that should be saved or printed straight away.

• If the return is not ready, it can be saved as a draft. If the system shows errors, it cannot be submitted until they are corrected.
• Before submission, the filer must confirm the required declarations, including authority to act and the accuracy of the return information.
• At submission, the payment method is selected: BACS, cheque, or direct debit if the user is signed up for it.
• Once submitted, the return receives a 13-digit unique Revenue Scotland transaction reference, which must be used for payment and when contacting Revenue Scotland.
• The confirmation screen shows when payment must reach Revenue Scotland and includes links to guidance on payment, penalties and interest.
• The confirmation receipt cannot be downloaded later, so it should be saved or printed immediately. The submitted return can later be viewed, downloaded, printed, and may be amended within 12 months of the filing date.

Scroll down for the full analysis.

How to submit an online LBTT return and what happens next

This page explains the final submission stage of an online Land and Buildings Transaction Tax (LBTT) return. It covers what you must confirm before sending the return, how payment method is selected, what reference you receive after submission, and why the confirmation screen matters.

What this rule is about

The source material deals with the practical process of filing an LBTT return online with Revenue Scotland. The main issues are:

• when a return is ready to submit
• what declarations must be made on submission
• how the payment method is recorded
• what evidence of submission you receive
• what to do immediately after submission

This matters because submission is not just a technical step. It is the point at which the return is formally sent to Revenue Scotland, a transaction reference is created, and the tax payment process is tied to that return.

What the official source says

If the return is not ready, it can be saved as a draft. Once it is complete, the user submits it from the bottom of the return summary page by selecting “Submit return”.

If an error message appears at that stage, the return cannot be submitted until the relevant errors are corrected.

After submission is selected, the user is asked to choose a payment method. The available options are BACS or cheque, and direct debit will also appear if the user has signed up for it.

The source also says two declarations must be dealt with before the return can be submitted:

• a declaration about authority, confirming whether the agent has authority to deal with all matters relating to the transaction for the client or clients
• a declaration about accuracy, confirming that the buyer or buyers have said the information in the return, apart from the relevant date, is correct and complete to the best of their knowledge, and that the relevant date entered is correct to the best of the agent’s knowledge

The declaration box must be checked in order to submit the return.

Once submitted, the return is given a 13-digit unique transaction reference in the format RSXXXXXXXABCD. That reference must be quoted when making payment or contacting Revenue Scotland about the transaction.

The submission confirmation screen tells the user when payment must reach Revenue Scotland. It also links to guidance on payment, penalties and interest.

The source adds an important timing point: tax is treated as paid on time if arrangements satisfactory to Revenue Scotland are made at the same time as the LBTT return and the full payment is received no later than the return filing date.

The submission confirmation can be printed or saved locally when it appears on screen. The source says it cannot be downloaded later, so if the receipt is needed, it must be saved or printed at that time.

From the submission page, the user can also send a secure message, and the return reference will be inserted automatically. After returning to the dashboard, the user can see a summary of the return. The return can be viewed, downloaded and printed later, and may be amended within 12 months of the filing date.

What this means in practice

The submission process has three practical parts: checking the return, making the required declarations, and linking the return to payment.

First, the return must be complete enough to pass the online validation checks. If the system shows an error, submission has not happened. The user must fix the errors and try again.

Second, the declarations are not mere formalities. If an agent is submitting the return, the system requires confirmation about authority and about the basis on which the return is being certified. In practice, that means the agent should already have the client’s approval of the information in the return before submission.

Third, the transaction reference generated on submission becomes the key identifier for the case. If payment is made without the correct reference, or if Revenue Scotland is contacted without it, this may create avoidable delay or confusion.

The confirmation screen is also important evidence. Although a copy of the return itself can later be viewed or downloaded, the source says the submission confirmation receipt cannot later be downloaded. If proof of submission is likely to matter for file records, audit trail or handover to another team member, it should be saved immediately.

How to analyse it

Before pressing “Submit return”, a sensible approach is to work through the following questions:

• Is the return actually complete, or should it remain saved as a draft?
• Have all system errors been cleared?
• If an agent is filing, does the agent have authority to deal with all matters relating to the transaction?
• Has the buyer confirmed that the information in the return, other than the relevant date, is correct and complete to the best of their knowledge?
• Is the relevant date correct to the best of the filer’s knowledge?
• Which payment method will be used: BACS, cheque, or direct debit if available?
• Once the return is submitted, has the unique transaction reference been recorded accurately?
• Has the submission confirmation been printed or saved locally before leaving the page?
• Has the payment deadline shown on the confirmation screen been noted?

After submission, the next practical checks are:

• use the correct transaction reference for payment
• make sure payment reaches Revenue Scotland by the required date
• keep the confirmation receipt safely
• check the dashboard summary to confirm the return appears as submitted

Example

Illustration: a solicitor completes an online LBTT return for a purchase and reaches the summary page. The solicitor notices one validation error, corrects it, and then selects “Submit return”. They choose BACS as the payment method, confirm that they have authority to deal with the transaction, and confirm the accuracy declaration on the basis of information provided by the buyer and their own knowledge of the relevant date. After submission, the system generates a unique Revenue Scotland transaction reference. The solicitor saves the confirmation receipt immediately and uses that reference when arranging payment.

In that example, the key practical steps are not just submitting the form, but making sure the declarations can properly be made, preserving the confirmation screen, and matching the payment to the correct reference.

Why this can be difficult in practice

The source material is mainly procedural, but there are still some points where care is needed.

One difficulty is that online submission can feel mechanical, when in fact the declarations have legal significance. An agent should not treat the authority and accuracy confirmations as routine click-through statements if the client’s instructions are incomplete or uncertain.

Another issue is timing. The source says tax is treated as paid on time if satisfactory arrangements are made at the same time as the return and the full payment is received no later than the filing date. In practice, that means filing and payment should be considered together, not as separate tasks left to different stages without coordination.

A further practical risk is record keeping. Because the submission confirmation receipt cannot later be downloaded, a user who leaves the page without saving it may lose a useful piece of evidence showing that the return was submitted and what payment deadline was shown at the time.

Finally, although the source says a submitted return may be amended within 12 months of the filing date, that does not remove the need to get the original filing right. The ability to amend is not the same as a general permission to file on an uncertain basis.

Key takeaways

• An LBTT return is only submitted once system errors are cleared and the required declarations are completed.
• The unique Revenue Scotland transaction reference generated on submission should be used for payment and correspondence.
• Save or print the submission confirmation immediately, because the source says that receipt cannot later be downloaded.

This page was last updated on 24 March 2026

Useful article? You may find it helpful to read the original guidance here: Guide to Submitting and Paying Online LBTT Returns

View all LBTT Guidance Pages Here