Account - Parameter: Posting Restrictions
Account - Parameter: Posting Restrictions
Account - Parameter: Posting Restrictions
PARAMETER
The ACCOUNT.PARAMETER record contains high-level specifications for the ACCOUNT application. For example:
l Number of days forward for cash-flow processing.
l Whether accounting is performed on a value date or booking date basis.
l Whether accounts can be referenced by an alternative ID or not.
l Whether the customer number must form part of the account number.
l Whether payments can be netted.
l How settlement defaulting is to take place.
l Whether to update ENT.TODAY files or not based on the ENT.TODAY. UPDATE field value. The value of NULL will be
defaulted,
which will allow updates to ENT.TODAY files
l Whether to use the future BOOKING.DATE option through OFS.CLEARING or not, is based on the RAISE.VD.ENTRIES field
value.
The value of NULL will be defaulted, which can be set as YES to allow the use of future BOOKING.DATE in OFS.CLEARING.
Once set
to YES, this becomes a ‘no change field.’
There is only one record, with an ID of SYSTEM.
Posting Restrictions
The field POSTING.RESTRICT in the ACCOUNT.PARAMETER defines the behaviour of the POSTING.RESTRICT field set at
underlying
ACCOUNT level at the time of ACCOUNT.CLOSURE.
This field will accept the following options:
l Single - Upon input of the ACCOUNT.CLOSURE, any existing value/multivalue is removed and the field POSTING.RESTRICT
of the
Account is populated with the value of 90.
l Multiple/None - The POSTING.RESTRICT value for ACCOUNT.CLOSURE is appended along with the existing values in the
underlying account record.
Refer to the following section of the user guide for an example - Client Account
The existing functionality of ACCOUNT.PARAMETER table is modified and new fields are added to allow the set up for
ACCT.ACTIVITY to be
updated using the Exposure date of a credit movement. It is also possible to switch from one Accounting system to another
accounting. Only
the new transactions are applied at a System level or at a Category range. Else, the existing functionality would be continued.
The statement
entries, which are raised after the Exposure Date setup is turned on, will have the value, EXPOSURE.DATE in the field
TDGL.DETAILS for calculation of interest, only for credit transactions. If the setup is turned off, then the field has the value
VALUE.DATE
l It is required to set the values in ACCOUNT.PARAMETER to allow the setup for ACCT.ACTIVITY to be updated using the
Exposure
date of a credit movement.
Based on the above set up, the system first checks the Category from the Entry fits in the Category Range, and then
checks if there is
anything set-up in EXP.UPD.ACCT.ACTIV.CAT
If not defined at the Category Range, then it checks at the system level under EXP.UPD.ACCT.ACTIV and restricts
only to the mentioned category.
If the above setup is not defined, the set-up is a ‘VALUE.DATE’ by default.