MAF CLOUD - NEW RELEASE + FIX UPDATES APR 2023

1. New Physical Trades - PS Ledger and Invoice

If modifications are made to saved data, the cells should be displayed in a prominent colour to easily indicate which changes were made. Once saved, the color display is no longer necessary.

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3688

1. Company Data - Add a new column in company data invoice tab

Tax classification name

Chinese: 税收分类名称

after INVOICE NO. text format compulsory

 IN invoice issuing

add Tax classification name in ITEMS dropdown list

add inv_group_no in ITEMS dropdown list so that they only need to choose one time and inv_group_no doesn’t need dropdown list anymore since it will be auto filled after ITEMS are chosen.

Enhancement

Company Data

https://mafint.atlassian.net/browse/MAF-3728

1. Invoice - Upload invoice in chinese version but unit remains english bug fixed

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3735

1. INVOICE -PAID:

1：SPECIFICATION column should not be compulsory

2: CCY column auto fill by CONTRACT CCY (when they choose contract no.)

3：unit should be 中文 （we can now just translate kilogram and metric ton to 千克， 吨）

4：when choose contract no, if there is only one 开票品名 and one 税收分类编码， tax rate should also auto fill， also check if the 税收分类编码 is right

 COMPANY DATA -INVOICE :

1: CHINESE TRANSLATION of INVOICE NO. 发票号 to 税收分类编码 

INVOICE ISSUE EXPORT：

 1：税收分类编码 should be text format

2：can we move all rows have been issued to another place (like assigned and unassigned in RECEIVED)

3： ISSUE TEMPLATE MODIFY: 税率（%） to 税率 ， Add a percentage sign after the exported number.

Enhancement

https://mafint.atlassian.net/browse/MAF-3725

2. add sum function for all related columns in SETTLEMENT AND UPDATED SETTLEMENT

all columns related with QTY

all columns related with AMT/AMOUNT

also，tick row to view aggregated summary

Enhancement

https://mafint.atlassian.net/browse/MAF-3727

3. Position issue of Daily statement - physical trade position and paper trade split

Enhancement

https://mafint.atlassian.net/browse/MAF-3733

4. New Physical Trades - Reduce white space in table for light theme

Enhancement

https://mafint.atlassian.net/browse/MAF-3732

5. Admin - add company name in User Management and Clean up table

Enhancement

https://mafint.atlassian.net/browse/MAF-3720

1. New Physical Trades - horizontal scroll bar disappeared issue bug fixed

2. Right click to set small, middle, large for table height, default is small

   small：15 rows middle：20 rows large：25 rows

Enhancement

https://mafint.atlassian.net/browse/MAF-3718

https://mafint.atlassian.net/browse/MAF-3719

3. Receiving invoice - upload file template change; also only highlight columns need to be upload

changes：购买方名称 map to COMPANY

货物或应税劳务名称 map to INVOICE PROD

税收分类编码 map to inv_group_no （INVOICE NO. in PAID tab, we have not added this column in RECEIVED yet）

the new template delete the TOTAL PRICE & TAX column, now when uploading, system should firstly upload AMOUNT and TAX AMT, then fill this column ( AMOUNT + TAX AMT)

new aggregate rule:

after they upload the file, system should aggregate all the rows with same “开票日，商品名称（货物或应税劳务名称 in template），规格型号，单位，税率，销方名称, 税收分类编码“ and recalculate the sum of “数量，金额，税额，价税合计（金额+税额）”

4. Upload file in RECEIVED, all the LEDGER TYPE = 开票 . It should be 收票 and save to RECEIVED

5. 不在一个GROUP的人，看不到收票信息

Enhancement

https://mafint.atlassian.net/browse/MAF-3721

https://mafint.atlassian.net/browse/MAF-3722

https://mafint.atlassian.net/browse/MAF-3723

6. Set table size (right click to set height) in dashboard

After we deploy the set the size of contract interface, the size of the table can also be set in the dashboard. However, there are some areas that need to be optimised.

1：After changing the size, the horizontal scroll bar may disappear or become unresponsive.

2：After changing the size, how can they adjust it back to the original default size of the system

Enhancement

https://mafint.atlassian.net/browse/MAF-3729

7. New trades tab

Allow pin all columns located from the left or right instead of individually select columns to pin - for trades tab first

Enhancement

https://mafint.atlassian.net/browse/MAF-3701

8. New Physical Trade - Trades table

add ACTION column

one of item in ACTION column is

AUTO CO (auto contract no. from main, please improve it if you have better idea)

1. it is enable if the row main contract no has value

2. click AUTO CO, to pop up a new window

3. in new window, FE will select all rows with the same main contract no in the table, put them into two sub table:

   1. upper table is all empty contract no rows, ordered by phy_trade_id

   2. lower table shows all existing contract no rows, ordered by contract no

4. Press Auto button, FE auto fill up all the empty contract no based on

   1. MAIN CONTRACT NO_AN

   2. AN is the next number of max AN in existing contract no rows.

   3. if no existing contract no rows, AN = 1

5. SAVE, CANCEL

   1. SAVE to update rows

   2. CANCEL to return main table without save or changes

Enhancement

https://mafint.atlassian.net/browse/MAF-3705

9. Purchase and sale contract - adjust positive and negative signs

Enhancement

https://mafint.atlassian.net/browse/MAF-3706

10. When a cell is selected, the row and column that the cell belongs to are highlighted with colours - for trades table first

Enhancement

https://mafint.atlassian.net/browse/MAF-3713

11. Daily Statement enhancements

1： remove these two columns path and group since they are too long and affect the readability of the report. With only one screen to work with, these two columns take up half of the space.

2: need group function

3：Daily changes are normal, but they become "nan" when they are included in the Daily statement.

4：If too many portfolios are selected in the Daily statement, the table cannot be opened.

5：When they changed the end date in the settings, the table failed to load.

Enhancement

https://mafint.atlassian.net/browse/MAF-3714

12. PSL & Invoice amt calculation issue

We use the quantity and price recorded in the contract to calculate the amount in the Trades tab. However, we use the data in the pricing to calculate the amount in the Invoice and PSL sections. This may cause issues, and we need to decide how to modify it.

1. when we do portfolio P/L calculation, we use phy_trade actual qty (qty) and actual_price (ested_price) in phy_pricing table, which means in settlement tables controlled by risk department

2. for contract_amt, psl, invoice, we use contract_actual_qty (qty) and contract_actual_price (provisional_price) to calculate.

   1. BE in dropdown list in psl, invoice

   2. FE un_inc_amt, un_payment_amt in psl, invoice table

   3. FE contract_amt … in phy_trade table

Enhancement

https://mafint.atlassian.net/browse/MAF-3715

13. New Physical Trades - Trade tab - Bug for PSL&invoice related columns fixed

bugs: for 102685, after I delete all QTY and PRICE data, there are still BAL AMT and UN INV AMT

for 102686, after I key the PRICE and QTY, BAL AMT and UN INV QTY UN INV AMT are null

The right logic should be: for each trade, once they key the price and qty but not yet record PSL or INVOICE for this contract, PSL AMT, INV QTY, INV AMT should be 0 and BAL AMT , UN INV QTY , UN INV AMT should not be null.

Initial BAL AMT, UN INV QTY, UN INV AMT formulas have no change

Enhancement

https://mafint.atlassian.net/browse/MAF-3711

14. ALL the columns have this filter issue, when deselect certain item, it is not filtered

Having issue on filter master row data. Need to filter out the child row value first then only can filter master row. If remove master row (with child row) might solve the issue.

Enhancement

1. Demurrage - Add validation message to prevent user from deleting main tab in calculation page

Enhancement

https://mafint.atlassian.net/wiki/spaces/MCUGX/pages/449675265

https://mafint.atlassian.net/browse/MAF-3712

2. Company Data - Add new tab in company data management

New Feature

Company Data

https://mafint.atlassian.net/browse/MAF-3632

3. New Physical Trades - PS Ledger and Invoice

• If modifications are made to saved data, the cells should be displayed in a prominent color to easily indicate which changes were made. Once saved, the color display is no longer necessary.

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3688

4. New Physical - Invoice: Add Issue Invoice tab

Pre-set two types of layouts in the invoice tab in advance, one is for Receive and the other is for Issue. Current Invoice page is for Receive

• Delete choose “assigned” and “unassigned” UI

• Delete “Recalculate” and “Split”

• steps：

  1、When users generate invoices, they first add a new row and select the contract no.

  The setting for the contract no should be similar to that for receiving invoices, with a dropdown list displaying the UN INV QTY AND UN INV AMT. Users can manually enter the Counterparty to filter the range of contracts.

  2、After selecting the contract no, the system will autofill related columns(MAIN CONTRACT NO, SPECIFICATION, UNIT, COUNTERPARTY, QTY, PRICE), as well as match the corresponding ITEMS (inv_product) in the company data with the product. The system will return a dropdown list for the user to select ITEMS.

  3、After selecting the ITEMS, If this ITEM corresponds to only one INVOICE NO, the system will automatically fill in the INVOICE NO and the corresponding tax rate.

  4、They need to export the invoicing information, and the template is attached. It should be considered whether to export directly or design a new UI if necessary.

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3692

https://mafint.atlassian.net/browse/MAF-3692

5. New Physical Trades - Updated Settlement tab

• Allow user to reallocate deals by clicking on the Setting button under Action column or tick multiple rows and click on Reallocate

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3683

6. New Physical Trade -

• when add new row, PURCHASE/SALE column shows error bug fixed

• AG Grid table will extend to 30 rows, so can view more rows in the table in 1 screen - for trades tab first

• Tick row to view aggregated summary for any quantity or amount fields, default will calculate all rows - for trades tab first

• Add Save and Undo icon button at the top of the table - for trades tab first

• Edit, undo, save bug fixed

• Add Invoice Month column in trades table

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3698

https://mafint.atlassian.net/browse/MAF-3700

https://mafint.atlassian.net/browse/MAF-3703

https://mafint.atlassian.net/browse/MAF-3702

https://mafint.atlassian.net/browse/MAF-3704

https://mafint.atlassian.net/browse/MAF-3710

7. Dashboard - Daily Statements updates

Enhancement

https://mafint.atlassian.net/browse/MAF-3641
https://mafint.atlassian.net/browse/MAF-3697

1. Daily Statement

• Parameters are similar to Group P/L app

• System will find past 14 days of data by default

• Total positions in Position Matrix and Daily Statement must be the same

• if maf product id = 0, which means no pricing, there will be no position.
  The table should only show those with maf product id and actual positions

• Only 20 portfolios will be displayed to prevent memory overload

• some update:

  1. FE map change from columns → terms

  2. order of terms should be same as Position Matrix terms columns

  3. c_date should be default 14 days ago of settlement date

  4. auto show date in Compare Date (user still can change, but default is 14 days, always 14 days if refresh)

  5. rows combines with master and non-master rows, same as FX Exposure

  BE already pushed in testing server.

• for testing scenario:

  1. try to put general_ledge expenses

  2. put buy and sell trades to check sum of size

• for DOD and WOW, only parent rows are required to show, sub row does not required; if so, for positions, only sub rows are required to show, parent row does not required.

WoW (week-over-week) 周环比 comparison means taking the profit and loss of the current day and subtracting it from that of the same day of the previous week. For example, if today is Wednesday, we subtract the profit and loss of this Wednesday from that of the previous Wednesday. If today is Thursday, we subtract the profit and loss of this Thursday from that of the previous Thursday.

DoD (day-over-day)日环比 comparison means taking the profit and loss of the current day and subtracting it from that of the previous day, without the need for a percentage change.

If there are holidays, and the holidays fall on Thursday to Sunday, then Monday to Wednesday of the new week will be compared normally, and Thursday and Friday will be compared with Wednesday. If the holiday is from last Saturday to this Wednesday, then Monday to Wednesday of the following week will be compared with Friday of the previous week.

• System will obtain data for up to 14 days by default.
  WOW will compare yesterday's data with 7 days ago's data by default, but if there is no data or weekend of PH on the 7th day ago data, system will choose the previous day's data (8th day onwards)
  DOD will compare yesterday's data with the day before's data by default, but if there is no data or weekend of PH on the 7th day ago data, system will choose the previous day's data (8th day onwards)
  For example, if End Date is 2/4/2023, WOW will be compared to 26/3/2023 (as it is either no data/weekend/PH, the actual date to compare will be 31/3/2023 and 24/3/2023); If End Date is 3/4/2023, DOD will be compared to 2/4/2023 so since it is a weekend, system will use 31/3/2023 to compare

Enhancement

https://mafint.atlassian.net/browse/MAF-3641

2. New Physical Trades - PS Ledger and Invoice

• Reminder for user to save data when change page, will apply when user switches between assigned and unassigned page as well as to all conditions when users switch to other page in system or refresh the page

Enhancement

https://mafint.atlassian.net/browse/MAF-3689

3. New Physical Trades - Trades tab:

Overdue Reminder: For the contract delivery date and contract pricing date, provide a gentle reminder in a subdued colour three days before the deadline. For those that are already overdue, use a prominent color such as red for the reminder.

• gentle reminder：yellow overdue reminder：orange

• For the contract delivery date: if un stock qty = 0(stock management), cancel the reminder. If only a portion of the goods have been received or shipped, the reminder should still be in place.

• For the contract pricing date: if the contract is split for partial price fixing, entering the price fixing time (pricing date) can cancel the reminder.

Enhancement

https://mafint.atlassian.net/browse/MAF-3685

Demurrage - Change translation message

Enhancement

https://mafint.atlassian.net/browse/MAF-3691

1. New Physical Trades -

• PS Ledger

  • add additional information for CONTRACT NO. dropdown list:

    1、UN INV AMT （未开票金额） - invoice

    2、未收/付款 - PSL

    • un_inv = CONTRACT AMT - inv_amt

un_payment = CONTRACT AMT - payment_amt

any insert or update in PSL or Invoice table, will update inv_amt or payment_amt in phy_trade table

when dropdown list in PSL or invoice table, BE do calculate un_inv_amt or un_payment_amt, if it is close to 0, we filter out. coz those contract already fully settled.

be careful purchase, sales of contract and credit, debit of payment and invoice. sign is important here

FE need to keep update un_inv_amt or un_payment_amt if any contract selected before saving.

un payment amt should = contract AMT is payment_amt is empty. coz un_payment_amt = contract_amt - payment_amt(payment_amt from db)

contract_amt should be contract qty x price, which should be calculated in BE when select.

In 5 conditions FE should change the un payment in dropdown list of contract (before save):

1: Assign contract no to PSL

2: change the contract no (from A to B )

3: Delete the contract no

4: delete row with contract no

5: change psl amt with contract no

• the dropdown list be sorted by the latest contract date（DATE in TRADES tab) at the top of the list. after entering the customer name

  • Since it returns un payment,
    autofill AMOUNT with un_payment_amt calculated by BE in contract dropdown list in PSL when they choose the contract

  • in invoice table and psl table, inv_amt and psl_amt in Database should be always positive.

    we use ledger type to control the amt should be positive or negative.

    if split in psl into negative, I suggest we update ledge type to PAID (negative), RECEIVED (positive).

  • 1、dropdown list, when users choose the “Assigned(已分配） ”，table will show all PSL or invoice with contract no.
    when users choose “Unassigned（未分配）”, table will show all PSL or invoice without contract no.

     

    2、default：Unassigned，show all PSL or invoice without contract no

Enhancement

https://mafint.atlassian.net/browse/MAF-3672 https://mafint.atlassian.net/browse/MAF-3676

https://mafint.atlassian.net/browse/MAF-3677

https://mafint.atlassian.net/browse/MAF-3679

2. New Physical Trades -

• Invoice

  • add additional information for CONTRACT NO. dropdown list:

    1、UN INV AMT （未开票金额） - invoice

    2、未收/付款 - PSL

    • un_inv = CONTRACT AMT - inv_amt

      un_payment = CONTRACT AMT - payment_amt

  • in invoice table and psl table, inv_amt and psl_amt in Database should be always positive.

  • we use ledger type to control the amt should be positive or negative.

  • if split in psl into negative, I suggest we update ledge type to PAID (negative), RECEIVED (positive).

  • Upload bug fixed

  • 1、dropdown list, when users choose the “Assigned(已分配） ”，table will show all PSL or invoice with contract no.
    when users choose “Unassigned（未分配）”, table will show all PSL or invoice without contract no.

 2、default：Unassigned，show all PSL or invoice without contract no

• In 5 conditions FE should change the un payment in dropdown list of contract (before save):

1: Assign contract no to PSL

2: change the contract no (from A to B )

3: Delete the contract no

4: delete row with contract no

5: change psl amt with contract no

Enhancement

https://mafint.atlassian.net/browse/MAF-3672https://mafint.atlassian.net/browse/MAF-3677

https://mafint.atlassian.net/browse/MAF-3678

https://mafint.atlassian.net/browse/MAF-3679

3. Demurrage Claims Table - In demurrage claims table, add a sentence to show how many rows have been updated when saved so user can tell immediately if more rows have been updated unintentionally

Enhancement

https://mafint.atlassian.net/browse/MAF-3681