Thomas Tian SUPPORT ENG

currently, if user select multiple projects in project list, the button to change the project stage is disabled.

so, no mothed for customer to change bundle projects once a time.

Could we please develop a new feature allow user change multiple projects once a time?

1: customer start the asset leasing at 2021/1/1.

2: And assign index rate to the asset leasing.

3: finished the payment for year 2021.

4: Customer forget to do the index rate revaluation at the begin of 2022.

  They continue to do the payment for 2022/1 and 2022/2.

5: Then the customer do the index rate revaluation.

The payment schedules are updated according to the index rate as well as the 2022/1 and 2022/2

6: The customer can continue create new journal for payment journal for the 2022/1 and 2022/2.

This will result in double payment.

Looks like some validation need here. But not sure where is the best place to has the validation.

For the previous payment journal for 2022/1 and 2011/2 with the load rate, they could be reversal manually,

But customer has thousands of transaction create in the new year before the index rate revaluation.

Do you have some other workaround can help customer mitigate the issue. And could we have a fix the prevent the issue happen again.

steps in 365FO.

1： purchased order and receipt. total amount = 1000+ 50 = 1050, withholding tax rate 28%

2:   invoice register with include tax.(credit 1050)

3:   Invoice approval through purchase order in the invoice approval form.

4:   payment against the invoice. And find the tax calculated wrong. the total amount is 1000, base amount is 950.

this is not correct.

expected result.

The invoice amount should be: 1050

The invoice amount excl tax in invoice currency should be: 1000

Based for withholding tax calculation in invoice currency should be 1000

Updated for withholding tax calculation in invoice currency should be 1000

Withholding tax in invoice should be 280.

Please fix it.

1: create an invoice register with tax included.

2: post the invoice register.

3: create an invoice approval. retrieve the tax register in step 1.

4: if customer identity the tax information again in the invoice approval.

system pop not balance issue. in fact, if the invoice set with tax excluded. there is no issue if customer identity the tax information again in the invoice approval.

The new idea here: system should follow the behavior as excluded tax. user can identify the tax information in the invoice approval if the invoice register with tax included.

this is for AU localization.

1: Create a normal fixed asset

2: Do the depreciation

3: Transfer it to the low-value pool

4: The original fixed asset account was not cleared. And don’t have a chance to disposal it.

the acquisition account and depreciation account need to be cleared when the original fixed asset transferred to the lower-value pool

1: Enable master data sharing.

2: Set USMF as parent company, T001 as Child company.

3: Share CustTable

4: posting a customer transaction in T001.

5: Create customer ageing snapshot in T001

6: No record could view in report customer ageing report.

Repro steps

Step1: Enable the SRS feature.

Enable the srs feature by following steps.

Steps to enable SRS feature on local Dev environments - Overview (visualstudio.com)

Step2: Create new Legal entity.

(Organization Administrator -> Organizations -> Legal entities -> New)

Click create

Step3: Legal on to T001

Step4: Set the ledger

(General ledger -> Ledger setup -> Ledger)

Set as following

Step5: Generate number sequence.

(Organization administration -> Number sequences -> number sequences )

Number sequences -> new -> Generate

Follow the steps to generate the number sequences.

Step6: Create customer posting profiles.

(Accounts receivable -> setup -> customer posting profiles.)

Step6: Set default posting profile for AR parameters.

(Accounts receivable -> set up -> Accounts receivable parameters)

Step7: Log on to USMF

Step8: Set SRS between USMF and T001.

(System administrator -> setup -> Configure cross-company data sharing)

Create a new SRS sharing and add the table customers.

All fields set as default.

Add the chiled companies T001

Enable it.

Create a new SRS sharing and add the table StatRepInterval and StatRepInterval line.

All fields set as default.

Add the chiled companies T001

Enable it.

Step9: Log on to T001

Create a free text invoice under the shared customer.

(Accounts receivable -> Customers -> All customers)

Select US-001.

Invoice -> new -> Free text invoice.

Post it.

Check customer transaction.

Step10: Create the Age customer balances.

(Credit and collections -> Periods tasks -> Age customer balance)

Click ok

Step11: Check the result.

(Credit and collections -> Collections -> Aged balanced.)

No record showed.

*** [ACTUAL RESULT] ***

Customer ageing balance not show in child company for child company transactions under SRS model

*** [EXPECTED RESULT] ***

Customer ageing balance should also show in child company for child company transactions under SRS model

this is a button on inventory ageing report storage to view the result. Please add the same funtion on customer ageing data storage

in Australia National Australia bank, we need to generate direct debit bank file from customer payment journal.

we need to force a sales order to the credit hold management even if it be partial invoiced or partial packing slip.

below is the example explained the requirement.

*********************************************

Let’s assume we purchase 12-month system support and maintenance (1st Oct 2024 to 30th Sep 2025) for $12,000 on 1st Oct 2024. In this case, we prepaid the whole year’s system support and maintenance expense and reflect it in P/L on Oct-2024. The term of the system support and maintenance is only 12 months; therefore, we will not recognize any long-term prepaid asset.

To recognize the expense of the system support and maintenance evenly over the 12 months, divide the total amount of $12,000 by 12 for a monthly system support and maintenance premium expense of $1,000.

Remarks:

1. The vendor will bill us in Oct-2024 for the whole year’s (12 months) system maintenance and amortize it each month.
2. The procurement team will raise two PRs for budgets 2024 and 2025 because D365 cannot handle multiple budget years within the same PO.

************************************

to satisfy the requirement. I suggested customer the following

&&&&&&&&&&&&&&

Let’s assume we purchase 12-month system support and maintenance (1st Oct 2024 to 30th Sep 2025) for $12,000 on 1st Oct 2024. In this case, we prepaid the whole year’s system support and maintenance expense and reflect it in P/L on Oct-2024. The term of the system support and maintenance is only 12 months; therefore, we will not recognize any long-term prepaid asset.

To recognize the expense of the system support and maintenance evenly over the 12 months, divide the total amount of $12,000 by 12 for a monthly system support and maintenance premium expense of $1,000.

Remarks:

1. The vendor will bill us in Oct-2024 for the whole year’s (12 months) system maintenance and amortize it each month.
2. The procurement team will raise two PRs for budgets 2024 and 2025 because D365 cannot handle multiple budget years within the same PO.

&&&&&&&&&&&&&&&&&&

but it is not the perfect one as customer need to do manually GL,

1:it is could not acceptable as the huge GL need to be created.

2: the budget could not be cost at the PO stage and invoice stage