lakani / opencore Goto Github PK

The generation of Account number should be revisited as it should be dynamic and standard for all account types without the need to implement it by each new account type

Link Account to another Account

Totaling is a concept in modern accounting techniques that facilities grouping and more advanced setup for Accounts as it enables the accountant to hit more than one account in a single Accounting Leg

For example for the below accounting entry
CR 11110 150 USD
DR 11120 150 USD

If for the case, the parent GL for (11110) GL is (10110) and
parent GL for (11120) GL is (10120) then the above AE will translated into
CR 11110 150 USD
DR 11120 150 USD
CR 10110 150 USD
DR 10120 150 USD

However there is some constrains
1- The Parent GL should be the same type of the GL, for example if the (11110) is Income, then (10110) should be Income account also.
2- A Balanced Totaling is required also, for example a CR leg is a corresponding for DR leg, also the Sum of Total CR should equal the total DR
3- Number of affected Parent GL should be equal unless this is for Account, for example the below AE is not accepted

CR 11110 150 USD has Parent GL
DR 11120 150 USD doesn’t has Parent GL

But the below AE is accepted

After meeting with Mr Magdy, its more related to the Setup of the GL

Fixed rate account.docx

This Screen allows user to list / filter all CIF
is Part of this Epic GUI

Future Transactions

#9

(SP_AddGL) should not add the same Ledger with different Nature

fixed in Code and also in the SP

Add Hold & Release Transaction

@

TBD

• fn_String_ParseGL
• fn_OPT_GetGLFormatDigitsNum
• fn_OPT_GetGLFormatDigits
• fn_String_BuildGL
• Getnerate the new Ledger number
• #region TotallingGL

The idea of this Enhancement is to develop a mechanism to associate accounts with an object, for example the Account Class could has Asset GL to be associated with the Account, so that the new account will be defined beneath this Asset GL, an Income GL to define its Fees, another asset GL to define its Overdraft facility.

Later on, this accounting structure should act like the back bone to link any object with its associated accounts, an example of objects could be (Portfolios and Shares for Treasury and investment module, assets and fees for Wallet module, Liabilities and Assets for Loan Products module).

This structure should allow the financial administrator to link any object type with account category to be used later on while posting Accounting Entries,
for example : the following CIF number (0001) got Account of Class (001) with its accounting structure contains the following definition :
GL : 01-01-01-10000005 of Category (Liability) and sub category (Funds)

Sperate All DB related code from BL into DL

Test : BL Layer doesn't reference any Context assemblies

• #63 Separate DL from BL - CifClass in SIS.OpenCore.BL.Objects

Success when Web API only reference Model and BL (no direct Access to DAL or any Linq Code)

Web API -- > BL -- > DAL -- > Linq

EPIC for different screens Use Cases

More than CIF is using the Same CIF

For M1 Release it will be fixed as below, for later releases it will be dynamic

It should be something like this, the admin should be able to setup something like this
Nature-Zone-CompanyNo-BranchNo-SectorNo-DepNo-UnitNo-ProductNo-PostingLevel-LedgerNo
#-##-##-####-##-##-##-####-#-######

Any GL should contains the following segments

However, while creating a new GL, the (nature, Posting Level and optionally Ledger number) should be provided and in this case the other segments will defaulted by 0

Examples
(1-00-00-0000-00-00-00-0000-1-000001) is an on Balance asset GL
(2-00-00-0000-00-00-00-0000-1-000001) is an on Balance liability GL

Backdated transactions

fn_GetGLInfo does not get all accounts

we need to check the parse the GL , also the GL Generation

Channel could Pass Reference number to Post Tran so that it uses instead of generating a new One

Create CIF

CIF Types -> (Personal , Non Personal)
CIF Classes 
CIF Groups


Create Account 
	Account Type
	Account Class (Totalling GL, 
	Create Accounts 

Totalling GL
Validation on (Totalling GL, Parent GL)
Same Company, Currency , Nature , Posting Level
Database Structure
While Creating
Balance Retrieval
GL Info Retrieval
Posting
Should check if there is a corresponding Totalling GL , the Legs should balance
CR = DR of the totalling

The Size of GL ??? -> MAX is 35 Digit

Reversal

Cash Box / Cash Teller / Cash Drawler

• User Management
• IAM
• OpenID
• OAuth

https://techvisionresearch.com/wp-content/uploads/2018/01/The-Future-of-Identity-Management-2018-final.pdf

introducing webapi

This should be an option based on CIF Class, whether or not to automatic generate account while generating CIF, this option should be TRUE/FALSE and in Case of true , the user should setup the Account class to generated based on

Data Migration/import from CVS file, to mention not to list

• CIF
• CIF Accounts
• General Ledgers
• Account/Accounts transactions

user can submit a Recurring Transaction that executes every day for a number of occurs

#9

This is a categorization of the Posted AE, it’s not related to the Transaction as it doesn’t have any financial impact
This should a leaf relationship, and the AE Categories could be a tree

Channel could Pass Reference number to Post Tran so that it uses instead of generating a new One

TBD

this Feature will handle the Limit , Limit Tree, Limit Group

group of CIFs

while adding a new CIF or editing an existing CIF,
populate DEF_CIF_Company

Separate DL from BL in (CifClass) class

Needs More investigation

TBD

Milestone I

• Localization of Resources, at least English for now

• CIF Types -> (Personal , Non Personal)

• CIF

• CIF Class

• CIF Class Companies

• (SP_AddGL) should not add the same Ledger with different Nature

• Channel could Pass Reference number to Post Tran so that it uses instead of generating a new One

Totalling GL :

• Totalling GL : Validation on (Totalling GL, Parent GL)
  Same Company, Currency , Nature , Posting Level

• Totalling GL : Database Structure

• Totalling GL : While Creating

• Totalling GL : Balance Retrieval

• Totalling GL : GL Info Retrieval

• Totalling GL : Posting
  Should check if there is a corresponding Totalling GL , the Legs should balance
  CR = DR of the totalling

• GL : The Size of GL ??? -> MAX is 35 Digit

• POST TRAN :

• POST TRAN : POST TRAN

• POST TRAN : Reversal

• Cash Box / Cash Teller / Cash Drawler

• make Company, Branch integer not Smaller than that

• Procedure : SP_AddAccount.sql
• Procedure : SP_AddCIF_EXT1.sql
• Procedure : SP_AddCIF.sql
• Procedure : SP_AddCIF_Class.sql
• Procedure : SP_POST_TRAN.sql
• Functions : fn_NUM_ACT_CR_DR.sql
• Functions : fn_ACT_GL_GetLastBalance.sql
• Types : TYPE_POST_TRAN_PARAM.sql
• Functions : fn_String_BuildGL.sql
• Procedure : SP_AddEditCurrency.sql
• Procedure : SP_AddEdit_Branch.sql
• Procedure : SP_ADD_LedgerNature.sql
• Procedure : SP_ADD_LedgerPostingLevel.sql
• Functions : fn_OPT_GetBaseCurrency.sql
• Functions : fn_OPT_GetCIFFormatDigits.sql
• Functions : fn_OPT_GetCIFFormatDigitsNum.sql
• Functions : fn_OPT_GetGLFormatDigits.sql
• Functions : fn_OPT_GetGLFormatDigitsNum.sql
• Functions : fn_String_ParseGL.sql
• Functions : RANDBETWEEN.sql
• Procedure : SP_AddGL.sql
• Functions : fn_GetCurrentBusinessDate.sql
• Functions : fn_GetGLInfo.sql
• Functions : fn_GetSettings.sql
• Functions : fn_Get_MAX_TABLE_CODE.sql
• Functions : FN_GL_GetLast_LEDGERNO.sql

there must be an end of day process that marks the end of day so that Core can process effective transactions on that date

• there must be an ability to run two days in one shot

At Least (ciF_NO) should be number or empty

#22 integration of business Rules Engine