Hello I have a problem with Exchange rates in Dynamics AX 2009.
In TaxTrans table is different exchange rate than in LedgerTrans table.
In PurchParameters table Exchange Date Rate is set to DocumentDate but in TaxTrans is get exchange rate from TransDate.
What's wrong with that? Sounds like normal accounting behavior. You have provided an incomplete question with little to go on, so this answer could be wrong if you add more info.
Let's say your company operates in USD and today is June 10.
If you receive an invoice dated June 1 in CAD, your document date would be June 1, and your exchange rate would be the rate as of June 1. This depends on your accounting, but normally you want to know your cost on the date you accrued it...not the date you happened to transact it. This can give you more accurate costing.
Then when you pay a bill or whatever, the tax will be on the date of the transaction, so you will want the exchange rate on that transaction date.
Related
If someone could please advise on how to achieve the following function on my site: I have a business where I ship live animals to customers. The challenge is communicating the weather forecast with the customer, along with the safest day/s to ship for the animals’ wellbeing. This planning is especially key during the peak summer and winter months when temperatures are very extreme. I am looking to automate these functions during the customers checkout process, giving them control of the shipping date. I am looking to implement something like this on my site.
I found another website where I recently placed an order that provided this relevant information for the customer to review before deciding on what day they would like to have the animal shipment shipped out. The table provided a 5 day forecast, which included temperatures for morning and evening at the point of origin, in transit, as well as the customers’ destination address. Any day/s where the temperature is too hot or too cold was marked as unavailable (red) for shipping. Possible shipping dates consisted of two consecutive days where temps are in the safe range and labeled as available (green) Excluding Friday, Saturday, and Sunday. It is also important for the customer to plan ahead and pick a shipping day based on their availability to be home to receive the package the following morning.
I am a retailer trying to forecast sales for each product.
The events that have the most impact on the retailer are neighborhood events and having a sale in store.
Amazon forcast's Related Time Series Dataset allows us to use promotions per product, such as item_id, timestamp, promotion_applied, but it is difficult to send information for all products in this format.
Amazon forcast has built-in holiday data, but can we use our own store-wide or regional event information in addition to this data?
For example, information such as
2021-8-14, have a summer sale [begin]
2021-8-15, have a summer sale
2021-8-16, have a summer sale
2021-8-16, local festival
2021-8-17, have a summer sale [end]
2021-9-4, local festival
2021-9-24, before school holiday
2021-9-25, school holiday
*Aug-16 has two events on the same day.
If I can have this kind of setup, is it better to specify the beginning and end of the sale? like [begin] or [end].
Generally, sales tend to be larger on the start and end dates of a sale.
Also, if sales are slightly higher on the day before a school holiday, would it be better to include information such as before school holiday?
I am using Quantlib swig implementatin in python. I am trying to model some loan agreements with fixed interest rate which is calculated monthly on simple basis and compounded quarterly basis.
Example
Issue Date March 18, 2011
First stub April 1, 2011
Second interest date july 1, 2011
Next interest payment dates every quarter after that October 1 and so on.
Coupon 8.45% calculated on simple basis and compounded every quarter.
I am unable to strcuture the flows using FixedRateLeg or FixedRateBond functions.
I notice that in C++ code there is an option to use FixedRateLeg with couponRates. I can provide Interest rate class with compounding of SimpleThenCompounded. But I think this function override is not available in Python swig version.
Any solutions as to how I can solve this ?
For the dates, genereting what you want it pretty easy since if nothing is defined, the stub will be at the beggining:
issueDate = ql.Date(18,3,2011)
maturityDate = ql.Date(1, 10, 2021)
schedule = ql.MakeSchedule(issueDate, maturityDate, ql.Period('3M'))
for date in [*schedule][:5]:
print(date.ISO())
2011-03-18
2011-04-01
2011-07-01
2011-10-01
2012-01-01
As for the rate, I'm not sure you mean by compounding quarterly if payments are quarterly. The ql.SimpleThenCompounded convention is used for example for TBills that might have more that one year, where the rate convention will be simple until one year and compounded for over a year.
Are you sure this won't give you what you want?
dayCount = ql.Actual360()
leg = ql.FixedRateLeg(schedule, dayCount, [100.], [0.0845])
for cf in leg:
print(cf.date().ISO(), cf.amount())
I got two currencies. € (geozone germany) and CHF (geozone switzerland). Both currencies should have weight base shipping applied.
Important is, that both currencies should have FIXED shipping costs. E.G.
Shipping costs for € - 5.00 €
Shipping costs for CHF – 8.00 CHF
The exchange rate of CHF to € is changing every day. Because it is only possible to add the shipping rates in the default currency (€), the shipping costs of CHF changes every day.
That is bad. Anyone knows how to come around this?
If you don't want currencies to fluctuate you can go to Admin > System > Settings > Edit and under the Local tab set Auto Update Currency to No. Now set your exchange rate and shipping rates accordingly and they will not change.
If you need currencies to stay up to date but only want your shipping to be an exception, you'll need to modify the shipping model file to adjust the cost relative to the selected currency's current exchange rate.
http://msdn.microsoft.com/en-us/library/windows/apps/hh694058.aspx
"Microsoft will pay you an amount equal to the Net Receipts for your
app, minus the Store Fee (the “App Proceeds”) as full compensation for
your app as made available to customers from the Windows Store, on a
monthly basis"
Please specify what the current practical behavior of "on a monthly basis" means. Eg, what is the current implemented payment schedule.
In the instance that Microsoft employees read this, please consider amending the public agreement to specify the expected behavior, eg similar to the Facebook agreement:
Microsoft will make payment of your Developer Balance approximately X number of days following the end of the Timespan period in which the transaction occurred, except as otherwise set forth herein.
Where X is the expected number of days after the particlar Timespan that transactions are grouped into. Eg, X is 2, and Timespan is monthly.
First of all, Microsoft will not pay anything less than a $200(USD) check, so you must clear that hurdle first. Once you trigger over $200 a month steadily, you will get paid regularly on a monthly basis.
Also note that your cut is only 70% of the first $25,000 USD and then 80% on anything after.
As a developer, I do not make the $200 in a month, but it is generally only a day or two after I notice that I have hit the $200 threshold until my bank account gets creditted with the balance.