MAF CLOUD - NEW RELEASE + FIX UPDATES JUL 2023

data migration excel upload

1. invoice receive, they already has their own excel template, so in this case, we just add a header name and key for contract no which our BE is able to grab. and then just tell user what is the header to follow

2. invoice issue and stock mgmt: we do not have file upload now. so please make a template as normal. and then ask them to follow our template.

file upload:

1. need to add a column for invoice receive.

2. add file upload for invoice issue table

3. add file upload for stock management table

1. 合同号: contract no

   1. highlight that contract no in the upload file is contract no, not phy_trade_id

   2. stock details only

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

physical trade - contract delivery date should not be highlighted once conditions are fulfilled, so it is caused by decimal point bug fixed 库存明细数据带入合同页小数点问题

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

issue invoice table - change position of the save and undo button to the red area

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

Make columns no editable in PSL & Invoice

update restriction (it means those rows have psl_id)

In PSL, RECEIVE and ISSUE, both assigned and unassigned (only tables, not include allocate window), set all columns no editable except CONTRACT NO.

for insert new one, still allow user to edit before saving.

Enhancement

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

1) in new phy trade, if the trade mode is import/export, contract ccy is USD but the received invoice is in CNY, because the value added tax invoice is issued by the customs and not the counterparty, so there will be 2 issues

1. contract ccy and invoice (receive) ccy will be different

2. contract counterparty and invoice (received) counterparty will be different (they can input manually as usually the file they upload does not include invoice (received) counterparty, can refer to the attachment),

so in these situations, how they assign the contract no? the issue is:

1. both contract and invoice (received) have different currencies so they cannot assign the contract no

2. contract and invoice (received) have the same quantity but invoice (received) amount and tax amount do not match those in the contract, because contract is USD amount, but invoice (received) amount is converted from USD into CNY based on customs' own exchange rate to calculate tax amount (same qty is referring to total qty, because each import contract may involved multiple custom declarations. So each import contract may have several invoices but the final invoice total quantity will be exactly the same as the actual contract quantity)

 2) domestic purchase contract, export sale contract (similar to import purchase contract)

for domestic purchase contract they will receive value added tax invoice from counterparty. for domestic sale contract they will issue a value added tax invoice, so the input tax can be offset against the output tax

however, for domestic purchase contract that correspond to export sale contract, the export sale contract is usually denominated in USD. In this case, they will need to deduct the quantity and amount corresponding to the purchase contract from the invoice reserve. This means they have to virtually issue an invoice with a quantity matching the contract qty and an amount matching the corresponding purchase contract's amount.

The problem arises when the sales contract is in USD, but the invoicing currency is CNY. In this situation, the invoice and the contract will have the same quantities, but the invoice amount should correspond to the amount in the purchase contract, not the USD amount in the export sales contract. As a result, the invoice amount will not match the contract amount. How should we handle this situation?

1. ADD column to display trade mode (IMPORT/EXPORT e.g., from contract no) in both unassigned and assigned table; only assigned will have trade mode from contract no

2. if contract no is IMPORT/EXPORT

   1. FE allow user to change CCY and counterparty

3. allow to change in the table only

Enhancement

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

Copy paste the value, the value is parsed as 29 instead and does not consist any comma on it

• basically affect all physical trade and paper trade number values as they do not support comma

1. check file upload in bulk update settlement

2. copy paste in old execution table, settlement and update settlement tables

3. key in old execution table, settlement and update settlement tables

4. also check other columns with numbers format

dashboard some apps cannot open

Enhancement

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

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

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

estimated price and settlement price in updated settlement table

• Pricing Mode for Fix cant change Ested Price. - so disable edit

• Unable to set settlement price empty for Pricing Mode Fix - so set as red highlight if empty

Enhancement

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

BE: KGI 2 yrs note pricing issue.

Enhancement

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

enter any trade execution and click on save got this error

Enhancement

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

stock mgmt table

• search button doesnt work

stock mgmt table - back to back page:

• according to previous logic qty variation should not be editable when add new row

• according to previous logic counterparty (in) and counterparty (out) should not be editable when add new row

Enhancement

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

phy trade settlement issue trade qty different from settlement actual qty

this issue is because update phy trade access level is group, which makes user can not update phy_pricing, trade and portfolio calculation accordingly.

How test:

1. user A and user B, and they are in different groups with the same company

   1. user A phy_trade update in group level

2. A create a phy trade

3. B insert settlement price (with a new deal no), without actual qty

4. then A change phy trade Qty

5. then check portfolio trades and p/l correct or not.

if it is correct, then this ticket fixed.

Enhancement

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

stock management pair details update

stock in/out page branch out into 2 pages - stock in/out and back to back

if btb, user will input in btb page directly

1. in BTB page, if edit either one, the other one will be auto updated

• stock date on the right side is equal to stock date on the left side

• stock type on the left = stock type on the right

• contract qty (in) = qty (in)

2. in BTB page

• when add new row, qty (out) will autofill qty (in)

• after save, when edit qty (out), it will not auto change qty (in)

• if qty (in) is different from qty (out), highlight in green

so new logic for stock in/out - user will not add new row in stock in/out page to input. user will only input stock in and out details and then pair them directly via the pair button in stock details page, and all paired items will appear in the stock in/out page.

1. clash with the current logic of selecting contract no will autofill qty.

so in BTB page, when select contract no., same current logic remains but dont need to auto fill these qty cus they will usually manually input qty

• contract qty (out) 提货数量（出库)

• qty (out) 磅单（出库）

• contract qty (in) 提货数量（入库)

• qty (in) 卸货磅单（入库）

so above written logic is correct, they will only need to input qty (out), so qty (in) and contract qty (in) will be autofilled with qty (out)

qty variation column formula in BTB table = qty (in) - qty (out)

so this should match with bal qty in stock details page

Enhancement

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

table auto size issue fixed

Enhancement

https://mafint.atlassian.net/browse/MAF-4048 x

in new phy trade table, the stock qty column should use contract qty in stock management page, if dont have then use qty in stock management page,

unstock qty calculation is the same logic = UNSTOCK QTY = CONTRACT ACTUAL QTY/QTY(physical trade table) - STOCK QTY (physical trade table) [for reference stock qty is also CONTRACT QTY(stock details)]

Enhancement

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

in settlement table, the summary calculation at the bottom is wrong

Enhancement

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

stock management add columns qty variation calculation update

Enhancement

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

Minimise column should not auto go back to default when input data or copy and paste data, or switch page

Enhancement

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

Ps ledger/invoice (receive and issue) - can view assigned table even though is group level bug fixed

Enhancement

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

1. 合同编号下拉框里加上“合同单价“（有终价用终价，无终价用临时价格 [有合同实际价格用合同实际价格，没有合同实际价格用临时价格]）contract no drop down list add Contract Actual Price and the formula is if have contract actual price, use contract actual price, if dont have then use provisional price

2. 在库存明细加一列：合同单价（有终价用终价，无终价用临时价格）in stock details page, add Contract Actual Price column ( if have contract actual price, use contract actual price, if dont have then use provisional price)

   1. not editable

3. 在库存明细加一列：磅盈/磅亏：实际出入库数量-理论出入库数量 in stock details page, add 磅盈/磅亏 column and the formula is Qty - Contract Qty (in stock details page)

   1. QTY variation

   2. FE handle it, no need store in BE

4. 库存类型：添加“在途”， “海运提单” stock type add “在途” and “海运提单”

   1. 海运提单 - BL

   2. 在途 - IT (In Transit)

Enhancement

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

add pricing price, contract premium and contract tax rate columns (from trades table) into settlement table

when input contract tax rate in trades table, it should auto fill both contract tax rate and settlement tax rate in settlement table

settlement tax rate should be editable, same logic as settlement qty and settlement price

if settlement tax rate is empty, auto fill it based on contract tax rate. (if empty only)

Enhancement

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

settlement tab match product and category

product is input in trades table, will be auto filled in settlement tab

user can input category in settlement table, and category will be linked to the product

so when the same product is shown in settlement table, the category will be auto filled. but category is also editable in settlement and updated settlement table

if edit category in settlement or updated settlement table, the category will be updated for the product in settlement table

but existing row with old category in updated settlement will not change

Enhancement

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

add date to psl combination logic

current psl logic: only PSL with same THIRD PARTY, LEDGER TYPE, CCY and COMPANY are allowed to combine, will sum up all AMOUNT

new logic: please add DATE too, so only psl with the same DATE, THIRD PARTY, LEDGER TYPE, CCY and COMPANY are allowed to combine

Enhancement

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

add contract amt column in settlement table

Enhancement

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

settlement table and updated settlement table: positive/negative signs for all qty and amount columns to follow trade table’s logic: purchase will be positive, sale will be negative

Enhancement