Party? Party? You're lucky. It's 1:30am and I've just finished this memo:
Alex, as discussed, please use this revised Management Reporting database which is already populated with the 2005 Budget and reprogrammed to take into account the underlying currency. Instructions are below.
Dear All,
Regarding currencies, I’ve been doing some thinking. Please note the following:
Management Reports Budget
Because we are forced by International Accounting Standards 21 to translate the P/L at an average rate rather than the forward rate as we had planned, so are the Budget numbers in this version. As a result, the budget is floating and subject to the vagaries of exchange rate movements during the year. (IAS 21 has got it wrong in my opinion – badly wrong).
However, because we have forward rates in place to pretty much fix the budget, there needs to be more sophistication in the budget programming here. It needs to take the difference between the forward rates and the average rate, and post the difference to FX gain/loss in the P/L (602300). Thus the bottom line is fixed, but the individual line items may be different. This will take some serious reprogramming which I will not be able to do this month – especially since Alex needs to send out cubes tomorrow, but I’m not sure whether for Month 1 it will be significant anyway.
The idea about posting the difference to FX gain/loss should approximate what happens in real life in the companies. Take the prime case of Euro costs in CEPH (a dollar denominated company) in January. They posted EUR 500k of salaries in mid-Jan into the P/L not at any forward rate, but at the rate Coda had at the time – the December rate. After the month end when all the income and costs had been calculated, they made the calculation for Dutch tax. That was entered in their books in the P/L at, again, the rate Coda had at the time – in this case since the booking was made a few days into February, it used the January month end rate.
This method will be repeated in February – salaries posted at January rates, the tax (and any other post month end bookings for Euros) at February’s rate, etc etc.
To summarize, the actual bookings made into the P/L on a line by line basis are a mish-mash of the prior month end rate or the current month end rate. This is true of all such companies.
When they then come to revalue the balance sheet, that is where the P/L gets a credit or debit (in FX gain / loss) because of the forward rates used to source the foreign currency in the first place.
Therefore, my plan to fix the budget in the management report by having floating individual line numbers (with the FX gain / loss being the balancing number) closely follows what actually happens in the companies.
Local Budgets
Having seen in detail what a company does in real life, it begs the question whether we have populated Coda correctly using the forward rates for the line items.
I don’t think we have (although the bottom line should be correct). I think every month end we need to populate the Coda the same way as I have suggested above – use the previous month end rate for the line items, the current month end for tax, and the net difference to FX gain / loss.
Thus when Peter K reviews actual vs budget, if his Euro expenses are in line with budget, he should see no variance in his local TB.
Alex,
1 Back up your current Management Reporting.mdb to another name
2 Unzip this file.
3 Repopulate the following tables with whatever you have from the old file:
Financial Adjustments
Geneva Download
History
Management Adjustments
4 Run the Cube
Now, where's the friggin' alcohol?