Handle prepayments posted to the wrong period
This guidance is only for IRIS Financials if using an earlier version than Version 7.0.2103. If using version 7.0.2103 or later, go to Prepayments posted to the wrong period.
You can have issues with prepayments if the relevant accounting periods do not exist or have a security role of PERIOD.9 or NO_ACCESS. You can only make prepayments to an accounting period with a security role of PERIOD.8 or less.
If an accounting period within a prepayment range has a security role of PERIOD.9 or NO_ACCESS, the prepayment is ignored for that period and allocated to the next future accounting period with a security role of PERIOD.8 or less. If no future periods exist with a security role of PERIOD.8 or less, the system posts the remainder of the prepayment into the Register period (REG.REG).
Prepayments with correct accounting periods
The prepayment example used in this topic is for a purchase invoice for a 12 month insurance policy. The invoice is for £12,000 and you prepay it across the financial year, as this table shows. If all the accounting periods exist and have a security role of PERIOD.8 or less assigned, the prepayment postings would appear as follows.
| Period | Example | Access Level |
Prepayment Posting |
| Period 1 (Current) | 2020/21.01 | 3 | £1,000 |
| Period 2 | 2020/21.02 | 8 | £1,000 |
| Period 3 | 2020/21.03 | 8 | £1,000 |
| Period 4 | 2020/21.04 | 8 | £1,000 |
| Period 5 | 2020/21.05 | 8 | £1,000 |
| Period 6 | 2020/21.06 | 8 | £1,000 |
| Period 7 | 2020/21.07 | 8 | £1,000 |
| Period 8 | 2020/21.08 | 8 | £1,000 |
| Period 9 | 2020/21.09 | 8 | £1,000 |
| Period 10 | 2020/21.10 | 8 | £1,000 |
| Period 11 | 2020/21.11 | 8 | £1,000 |
| Period 12 | 2020/21.12 | 8 | £1,000 |
| TOTAL | £12,000 |
Prepayments where accounting periods have a PERIOD.9 or NO_ACCESS security role, but future periods exist
If one or more accounting periods have a security role of PERIOD.9, the system posts the prepayment portion that it cannot post (in this example, £2000) to the next future period with a security role of PERIOD.8 or less. In this example, you cannot access periods 11 and 12, so the system posts the prepayment amount of £2000 into period 1 of the new financial year.
| Period | Example | Access Level |
Prepayment Posting |
| Period 1 (Current) | 2020/21.01 | 3 | £1,000 |
| Period 2 | 2020/21.02 | 8 | £1,000 |
| Period 3 | 2020/21.03 | 8 | £1,000 |
| Period 4 | 2020/21.04 | 8 | £1,000 |
| Period 5 | 2020/21.05 | 9 | £1,000 |
| Period 6 | 2020/21.06 | 8 | £1,000 |
| Period 7 | 2020/21.07 | 8 | £1,000 |
| Period 8 | 2020/21.08 | 8 | £1,000 |
| Period 9 | 2020/21.09 | 8 | £1,000 |
| Period 10 | 2020/21.10 | 8 | £1,000 |
| Period 11 | 2020/21.11 | 9 | £0 |
| Period 12 | 2020/21.12 | 9 | £0 |
| Period 1 Next FY | 2021/22.01 | 8 | £2,000 |
| Period 2 Next FY | 2021/22.02 | 8 | £0 |
| TOTAL | £12,000 |
If this occurs, you need to edit the document into the closed accounting periods as a CUSTADMIN user (in the earlier example, Period 11 and Period 12). Alternatively, change the security roles on the two accounting periods to a maximum of PERIOD.8 then edit the document as the current user, assuming their access level matches that of the accounting periods. For more information, refer to Opening/Closing Accounting Periods.
Scenario example:
A non-order invoice has been posted for 12 months annual insurance. The invoice should have been prepaid to cover the full 12 months the insurance is active for. Periods 11 and 12 had a security role of PERIOD.9 at the time of posting. As a result, the prepayment that you should have posted in periods 11 and 12 posted into the following financial year because the period has a security role of PERIOD.8.
The non-order invoice needs to be edited to post the prepayment into the correct periods.
Before correcting the documents, speak to your CUSTADMIN user and request they change the security role on the applicable periods to PERIOD.8. This opens the periods and allows you to move the prepayments into them.
Alternatively, log in as the CUSTADMIN user to edit the documents without reducing the security role on the applicable periods.
- Right-click the applicable prepayment document you need to edit, then select Edit.
- The PSFJournal document input form opens. Replace the existing Year code and Period in Period with the required period year and number. In our example we are changing the Year code from 2021/22 to 2020/21 and the Period from 01 to 11.
- Press F5 to post the document with the changes and repeat for any other required documents.
Prepayments where accounting periods have have a PERIOD.9 or NO_ACCESS security role, but no future periods exist
If there are no future periods with a security role of PERIOD.8 or less, the system posts the portion that it cannot post into a future accounting period to the Register period (REG.REG). It posts one document for each period that it could not post. In this example, the system posts two PM – Prepayment Movement documents to the REG.REG period, each for £1000.
| Period | Example | Access Level |
Prepayment Posting |
| Period 1 (Current) | 2020/21.01 | 3 | £1,000 |
| Period 2 | 2020/21.02 | 8 | £1,000 |
| Period 3 | 2020/21.03 | 8 | £1,000 |
| Period 4 | 2020/21.04 | 8 | £1,000 |
| Period 5 | 2020/21.05 | 8 | £1,000 |
| Period 6 | 2020/21.06 | 8 | £1,000 |
| Period 7 | 2020/21.07 | 8 | £1,000 |
| Period 8 | 2020/21.08 | 8 | £1,000 |
| Period 9 | 2020/21.09 | 8 | £1,000 |
| Period 10 | 2020/21.10 | 8 | £1,000 |
| Period 11 | 2020/21.11 | 9 | £0 |
| Period 12 | 2020/21.12 | 9 | £0 |
| REG.REG | £2,000 | ||
| TOTAL | £12,000 |
If this occurs, you need to change the security role on the two accounting periods to a maximum of PERIOD.8, then edit the documents as the current user, assuming their access level matches that of the accounting periods.
Scenario example:
A non-order invoice has been posted for 12 months annual insurance. The invoice should have been prepaid to cover the full 12 months the insurance is to be active for. Periods 11 and 12 had a security role of PERIOD.9 at the time of posting. As a result, the prepayment that you should have posted in periods 11 and 12 posted to the Register period because no future open periods exist.
The non-order invoice needs to be edited to post the prepayment into the correct periods.
Before correcting the documents, speak to your CUSTADMIN user and request they change the security role on the applicable periods to PERIOD.8. This opens the periods and allows you to move the prepayments into them.
Alternatively, log in as the CUSTADMIN user to edit the documents without reducing the security role on the applicable periods. For more information, refer to Opening/Closing Accounting Periods.
- Right-click the applicable prepayment document you need to edit, then select Move to the Books.
- The Move documents out of the Register window opens. Select the applicable documents, then select MOVE.
- A confirmation message appears. Select OK to return to the window.