This article aims to guide you through the rules for sub ledgers when using Multi Entity on a purchase order credit note.
If you are interested in creating a purchase order credit note without using multi entity, please refer to our Enter a purchase order credit note article.
This article will highlight the rules for you when using Multi Entity and will also provide you information about the purchase order credit note screen in general.
Access credit note from the Navigator
Click Purchasing then Transactions and then click Purchase Credit Note.
The Credit Note screen opens for you to enter your supplier and values.
Important rules when using sub ledgers and or Multi Entity
When you use Sub Ledgers or Multi Entity and visit the Purchase Credit Note screen for the first time, the Sub Ledger field is going to default to empty regardless of you having a sub ledger set up for the Purchase Ledger or if the user you are logged into Financials with is assigned a default purchase sub ledger in their security profile.
Once you have saved an order with a particular sub ledger, this sub ledger will be saved against your user as the user preference, so when you open the Purchase Credit Note screen again, the sub ledger field will be prefilled for you with the previously used sub ledger record.
You can change the sub ledger manually and if you have selected a different sub ledger than on the previous order, then this newly selected sub ledger will be saved against your user preference.
Your selected sub ledger drives the defaults on the Purchase Credit Note screen and the Categories will be prefiltered based on the sub leger you are working with.
When you use a supplier where you have assigned an analysis record that is assigned to a sub ledger but that sub ledger is different to the one you have last used on the credit note, you must change the sub ledger to match the same sub ledger on the analysis record to avoid a validation error.
When you manually type over the default categories tied to the same sub ledger selected on the header, upon clicking Save on the transaction, you will encounter a validation error alerting you that the categories must align with those belonging to the same sub ledger specified on the header.
When a sub ledger is not set up as an Accruals sub ledger, the fields on the Details section related to Accruals are going to be disabled.
The Accruals fields are only enabled when you select a sub ledger that has been set up with accruals on the company level. Please refer to our Set up Accruals with Multi Entity article.
The project and cost centre that you selected on the Details section for an order are filtered based on the sub ledger you have used on the Header section of a credit note making it easier for you to select a record.
To make your transactions easy and consistent, our purchase order transaction entry window follows the same logic as our other transaction entry screens.
Below is an explanation of how to enter your details on the header and details sections of a purchase order credit note:
Tabs | Description |
Header |
|
Summary |
|
Addresses |
|
Notes |
|
Customer |
|
Terms |
|
Discount |
|
EU |
|
Custom |
|
Detail
Details | Description |
Details section |
Note: If your database currency isn't GBP then the relevant currency code displays.
|
Transaction User Keys
If you're using transaction user keys, these display on the detail line of a credit note.
For more information on setting up transaction user keys, follow our article on transaction user keys.
For information on attaching a transaction user key to a transaction, follow our article on attaching transaction user keys.
