Legal implications when making adjustments

Hi,
What are the legal implications if business needs to open FI period in OB52 to make adjustments in accounting from 3 months ago?
Is it a normal practice in FI area or can this be used as a workaround? Any clear explanation is welcome
Roger

Hi Rogerio,
                Generally the old posting will not be an issue for GAAP, since that is mainly focused on the financial year.
The big issues will be in the Tax Reporting eg VAT, EC Sales List, Intrastat. All these will (if permitted) have to be resubmitted for that month. Even where permitted there can be penalties / Interest payments for late payment that have to be paid.
It will also affect corporation tax returns where these have to be made monthly (eg Poland, provisional tax in Mexico).
If the adjustment is just reposting costs from one cost account to another then it would probalby not effect these.
All your CO reporting will also possibly be affected , since this posting will not have been included in any Distribution / Settlement.
It would therefore require manual re-posting.
The posting is not necessarily strictly illegal but the consequences and additional work required to keep the accounts clean is severe.
Kind regards

Similar Messages

  • Preference to "Create New Versions when making adjustments"

    Isnt the option in Preferences "create new version when making adjustments" seem irrelevant when Ap doesnt touch the original (master) anyway? How is this option intended to be used? Most of the imags for me would be slight tweeks so I wouldnt necessarily want every one of those showing as a 'full new version'.

    yeh, that would seem logical wouldn't it - to create a new version for each session... but that's not what happens.
    i mostly use the HUD and don't close between adjustments but i do sometimes use the side panel which i also don't hide/close between adjustments. i can't remember whether making adjustments via the side panel creates new versions for every adjustment, certainly this behaviour happens when i use the HUD and i'm fairly sure i would have tried the side panel to avoid this annoying behaviour but i can't say for sure and will have to test the side panel behaviour next week if i get time.
    even with the preference for 'create new versions' turned off, there seem to be certain images that always create a new version when i make an adjustment - whether using the HUD or side panel. I haven't figured out an exact pattern to this but it seems to be something to do with those files that have been 'sent to external editor'. subsequent adjustments within aperture always create a new version - haven't a clue why...
    just as an aside, sometimes when i make adjustments (particularly sharpening or noise reduction) i get single pixel wide horizontal lines of noise appearing across my images, which are there when i print or export too, not just screen artifacts due to a badly processed preview...hmmm...anyone else noticed this or has found a post about ways to avoid this?
    all that said, aperture is a godsend for my workflow
    MacBook 2.0 White   Mac OS X (10.4.8)  

  • Create new versions when making adjustments?

    Hi,
    What does anyone suggest this setting should be set to? It's on the Advanced Tab in Preferences.
    I think it was un checked when I installed the Trial Version.
    The help file stated the following:-
    +Create new versions when making adjustments” checkbox: Select this checkbox to have Aperture automatically create a new version when you adjust a selected image. The adjustment is applied to the original version and the new one is left untouched.+
    So when I edit an image the the software makes a copy and the original is altered? What happens if it's left un checked?
    Any help on the whole editing thing would be gratefully received.

    This is just a way to automatically create a new version when you make an adjustment. The new version is stacked with an unaltered version, allowing you to quickly see them side by side. What you have to remember is that the *original file is never altered*. This is all virtual. What is called original in this case is in fact an original version, not the actual file. The actual file is called the Master. Very important to understand the distinction.
    I personally leave this off. I never use RAW files without adjustments so there's no point in keeping an unaltered version around, plus it tends to quickly multiply versions and just creates clutter. If I want to see the original file I just hit M (this is the default command key for Show Master). Hit M again and I'm back to my version. If I've created a version and want to do a new different looking one starting from scratch, I can select New Version From Master: presto a new "original"!
    If I've worked on a picture and want to create a BW version, chances are I want to keep the work I've already done as a starting point. In that case I select Duplicate Version and do my BW on the new version. Again, I'm never actually duplicating files and I'm never actually altering pixels, original or otherwise. This is all a set of xml instructions that Aperture applies when it displays the files.
    Helping?
    Message was edited by: Jade Leary

  • "Create new versions when making adjustments" - Lion, Aperture 3.1.3

    I recently upgraded to Lion, and then shortly thereafter to Aperture 3.1.3.
    While I don't seem to share everybody else's issues with Lion nor with Aperture, I do have one of my own.
    In Preferences -> Advanced, I have a box titled "Create new versiont when making adjustment."  It is checked.
    My expectation, (and the way things have always worked under Snow Leopard) is that if I select a master image and begin to make adjustments to it from _any_ feature int he adjustments pallette, that I new version will be created, stacked next to the original, and that the changes I am making will be made to the new version.  This is _not_ what is happening.
    Instead, the changes are applied directly to the master image.  This is annoying, and will probably be fixed in an update...    I thought the work around would be to manually create the version for the time being, until Apple sorts this out.  That didn't work either.
    If I manually create a version, and then proceed to make adjustments to the version, Aperture dows what I would have expected in the first place.  It creates a new version and applies the changes to that.
    For example, I right click on a master image and select "New Version form Master"  A new version, titled "... - Version 2" is created.  When I begin to modify Version 2, a new version is created titled "... - Version 3" and my changes are applied to this version... leaving me with the master and Version 2 which are now duplicates of each other.
    Even more interesting is this:
    Images that were imported into Aperture prior to the Lion upgrade, and the 3.1.3 patch behave as expected, in that a new version is created when adjustments are applied to a master image.
    Images that were imported into Aperture _after_ the upgrade to Lion and the 3.1.3 patch act as describd above, in that no new version is created when adjustments are applied to a master image.
    So...  Here are the questions:
    1. Is anybody else experiencing this?
    2. Does anybody know how to restore the correct behavior?

    Alright,   I have solved the problem.
    Some time ago, I thought it might be neat to import pictures with the Auto Exposure adjustment in place.  What I didn't realize was that if the master image is in the library with adjustments on it, it downs't create a new version when you add additional adjustments.
    As soon as I disabled that, and imported some new imges the probelm went away.
    Also... I went back to the six or seven project that I had imported while use Auto Exposure and removed that adjustment from those images...  
    All is resolved.

  • "Create new versions when making adjustments" checkbox - do I check it??

    I have been using Aperture for many months. I'm not sure why, but I looked at my prefs the other day and the checkbox above was unchecked. Two important questions:
    1. Which way should this be set??
    2. Is Aperture still keeping the original separate from any edits I am making? PLEASE tell me that my originals have been kept separately!!! : )
    Thanks in advance,
    Erik

    1. It's a Preference. It should be set the way you prefer.
    2. Aperture never adjusts the master.
    When you look at an unadjusted image in Aperture, you are seeing +Version 1+. You can adjust Version 1, or you can create a new version and adjust that. Or you can set the preference, and when you make adjustments, a new version will be created automatically. This can cause unwanted versions to accumulate. Or maybe they are not unwanted.
    The Master is never affected, just the versions.

  • Why do I get a "no pixels selected" when making adjustments in a new layer?

    What am I doing wrong?  I want to modify or replace the color in a selection, so I make the selection, create a new layer, and try to replace the color from the Enhance menu.  I get the message " can't do it because no pixels are selected."  The selection is OK; I can see the marching ants.  The same happens when I try other color adjustments and probably other adjustments as well.  Would appreciate some help.  Many thanks.

    Sounds like you have an empty layer selected.
    Even if you have a selection established (showing the marching ants), your creation of a New Layer means that your selection is now on that new layer, which is empty, and thus there are no pixels selected to modify.
    Try skipping the New Layer step.
    Or, duplicate the layer you want to work on, then do the selection, then the adjustment.

  • Aperture Crashing when Making Adjustments

    Just that.. I have Aperture 3 installed on a 6 month old iMac 21.5" with 8gbs RAM. Never had a problem with Aperture 2 or with the 32bit config in APerture 3. Whenever I import images, it seems to be stable and happy, but after I begin to rate the images, and then to make simple adjustments like shadows/highlights, or exposure adjustments I get the spinning beach ball of death and it locks up. its especially annoying when trying to work in full screen, especially when Apple pushes this as an amazing new idea and I cannot get out of it without pulling the plug on my whole system and then restarting. I dont lose any adjustments except the one that locked it up.. but this software locking up is the most reliable feature... it doesnt work. I have rebuilt the libraries, reinstalled aperture, used the the library on multiple different machines using Aperture 3... anyone have any idea what to do here?

    Process: Aperture [64006]
    Path: /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier: com.apple.Aperture
    Version: 3.1.1 (3.1.1)
    Build Info: Aperture-1310000~1
    Code Type: X86-64 (Native)
    Parent Process: launchd [97]
    Date/Time: 2010-12-13 06:57:20.226 -0800
    OS Version: Mac OS X 10.6.5 (10H574)
    Report Version: 6
    Interval Since Last Report: 562 sec
    Crashes Since Last Report: 4
    Per-App Interval Since Last Report: 97 sec
    Per-App Crashes Since Last Report: 4
    Anonymous UUID: 18D84CE6-F6DD-4BFE-83E8-F87DA57DA7BF
    Exception Type: EXCBADACCESS (SIGSEGV)
    Exception Codes: 0x000000000000000d, 0x0000000000000000
    Crashed Thread: 40 Dispatch queue: com.apple.root.low-priority
    Thread 40 Crashed: Dispatch queue: com.apple.root.low-priority
    0 unorm16_rgba.dylib 0x0000000131d24201 _read4_2d_ff_unnormalized_linear_clamp_edge_unorm16_rgba_SSE41 + 2241
    1 libcldcpuengine.dylib 0x000000011eb6b6e8 cldexecworkitem + 540
    2 libSystem.B.dylib 0x00007fff81c3cbc8 dispatchapply2 + 44
    3 libSystem.B.dylib 0x00007fff81bd0831 dispatch_workerthread2 + 239
    4 libSystem.B.dylib 0x00007fff81bd0168 pthreadwqthread + 353
    5 libSystem.B.dylib 0x00007fff81bd0005 start_wqthread + 13
    Sometimes this happens on Thread 36
    Aperture consistently crashes every time with out fail every time I open RAW image and click on "Adjustments" If I open Adjustments first then open a RAW Image it crashes every time. I have rebuilt permissions, repaired database, rebuilt database upon opening Aperture. I have reinstalled Aperture. I have trashed and created new library on both internal and external drive. I have run Disk Utilities, Repaired the disk, repaired permissions.
    I have had this problem for a week now and I don't know how to resolve it.
    I am massively frustrated. My Macbook pro is the only machine that I am have this problem with.
    Why does Aperture 3.1 and 3.1.1 Not like my Macbook Pro I7. Help
    RJ
    Message was edited by: Nikontraveler
    PS I did try 3.1 and it does the same thing.
    One other thing. I have tried RAW images from a Nikon D80 Nikon D700 and Fuji S3. All RAW files crash when I do this task. Message was edited by: Nikontraveler
    Aperture does not crash when adjusting Jpgs.
    Message was edited by: Nikontraveler

  • When making adjustments with lens correction, the crop isnt contrained to the image

    When I first installed CC I was able to rotate, or adjust the image in lens correction and it would automatically crop to the available image dimensions.
    But I deselected the contrain to image section in crop mode, and since then it hasnt work, even though contrain to image in crop tool has since been re-selected, many times.
    Any idea whats wrong?

    Thanks!  All of my shots for this current interior shoot are panoramic.  At a halt until I can resolve this.
    Lightroom: 5.7
    camera Raw 8.7
    Photoshop CC  2014.2.2 Release / 20141204.r.310 x64
    Other notes:
    - converted arw sony raw (from a6000) into dng and still no results.

  • White screen when making adjustments

    After importing images and doing some editing, I have run into the problem of the image turning blank white while doing a simple adjustment.
    I quit the program and restarted aperture, but the problem continues. This is happening quite a bit. The files are Nef from a d700.
    Anyone have an idea of the problem and how to remedy.
    thanks

    have not noticed with my d300 images....the images i have been working on were shot with the 700.
    are you also having problems with the same nef files?

  • Image Disappears when Adding Adjustments in Aperture 3

    I am experiencing odd behavior when using the adjustment tools in Aperture 3. I tried to crop an image and instead of staying on screen for me to finish the adjustment, the image disappeared. I was able to save it by undoing. I created a version of the image and I could crop that OK. I have Add New Version when Making Adjustments checked but it does not seem to be working.

    I've had a similar "disappearing" image problem when trying to apply the retouch tool. I don't have the "create version when applying adjustments" preference checked though. Hopefully these issues are additional 3.0 bugs that will get fixed in 3.0.1. Be sure to report the issue to Apple using the "Aperture > Provide Aperture Feedback" menu item.

  • Grain/Noise disappear while making adjustments in ACR

    Can someone help me wrap my head around this? When making an adjustment using, for example, a luminance slider,(Hue Sat Lum dialog), in ACR, Noise and Grain disappear during the adjustment only to return after releasing the left click button. This makes it very difficult to get a real time feel for adjustments. More like trial and error. I haven't noticed this before. I've been running CS5 on win7 with a dedicated 500gb scratch disk. I work primarily with Raw files. The appearance during the adjustment resembles having cranked the luminance or masking, (in the sharpening/noise reduction dialog), way up. It may be that this is most prevalent when working on  an image that has been significantly cropped.
    Thank you...

    The latest update for Photoshop CS5 is Camera Raw 6.7.  You should update.  Try first by choosing Help - Updates in Photoshop.  If that doesn't work, seek out the Camera Raw 6.7 update on one of these pages:
    http://www.adobe.com/support/downloads/product.jsp?product=39&platform=Windows
    http://www.adobe.com/support/downloads/product.jsp?product=39&platform=Macintosh
    -Noel

  • Making adjustments with referenced images

    my master files are located on an external HD . when it is offline, i can't make any adjustments. when it is connected, i can make adjustments and aperture creates a version out of the master file. i also use Nik Software (such as Silver Efex Pro) to make adjustments. when i save changes, the version is saved to aperture library ?? or should i click on the version and relocate it on the external HD? If I don't relocate it after making adjustments, then is it gone after i quit using aperture ??? please advise.. 

    OkanUmit wrote:
    my master files are located on an external HD . when it is offline, i can't make any adjustments. when it is connected, i can make adjustments and aperture creates a version out of the master file.
    Yes, that's exactly how it works. You can't make adjustments unless the original file is online and available.
    i also use Nik Software (such as Silver Efex Pro) to make adjustments. when i save changes, the version is saved to aperture library ?? or should i click on the version and relocate it on the external HD? If I don't relocate it after making adjustments, then is it gone after i quit using aperture ??? please advise..
    I'm not sure what you expect to happen but Aperture will never edit the Original file. The point of Aperture is that the original is always preserved.
    Remember what you have on that external is simply file storage. If you want to acess a photo then you do so via Aperture.
    Regards
    TD

  • Aperture Crashing when making book

    Since updating to the latest release of Aperture, I've noticed it has gotten a bit freeze-prone. Working on a new book today, I've had to force quit 7 times in the last 3 hours. Thank god for Aperture saving as I go along.
    Has anyone else noticed this?
    for example (all of the below require a force quit):
    -freezing for no reason when browsing photos in my library. 
    -freezing occasionally when making minor adjustments
    -I'm currently making a book, my first since updating to 3.3 or whatever we're on now. I was incorporating a map into several pages and without fail, sometime during the process of choosing a location on each map creation, Aperture would "not respond" and freeze. I'd have to force quit.
    Any ideas? I have no clue why this is happening. I'm running the top of the line 2013 21" imac, with really no other bloating or hi-needs programs other than Aperture. I'm solely running Aperture when doing any heavy editing. I really doubt it is the Mac.

    Hopefully this will be fixed soon. You may want to send feedback to Apple to let the developers know of the problem.  Here is the feedback form:  Apple - Aperture - Feedback
    And I hope your book will turn out great, in spite of the problems.
    Unfortunately it will not help, to go offline, when entering the Places, because the connection to the server is needed. Going offline will prevent Aperture from crashing, as far as I can see, but the Place markers will not appear on the map, because there is not connection to the server.

  • Photos missing when making Calendar

    Hello everyone,
    I am in the process of making a couple of calendars. I've noticed that after making some red eye adjustments within my photo library, iPhoto removed that photo within my available photos when making my calendar. I tried "Revert to Original" in the library, thinking that the original was no longer available due to the adjustment. No luck.
    Is this an ongoing issue? I've noticed an issue with iPhoto's calendar application being able to recognize all my photos available. I know that all of my files reside in the iPhoto Library file and I handle all my importing through iPhoto. I am stumped, any help is greatly appreciated.
    Bob

    Guttermanster
    Welcome to the Apple user discussion forums
    I've noticed that after making some red eye adjustments within my photo library, iPhoto removed that photo within my available photos when making my calendar.
    Exactly what does this mean? How did you make the red eye adjustments?
    I assume that the photos no longer show up in the calender - what happens when you drag one of them back to the calendar?
    Is this an ongoing issue? I've noticed an issue with iPhoto's calendar application being able to recognize all my photos available.
    No - there is no ongoing issue with calendars in iPhoto like this. I suspect that your database is damaged but need to know more about the symptoms you are seeing - I'm not totally clear on what you are seeing - and not seeing
    LN

  • Aperture 3 freezing up after making adjustments.

    Endless(30-45 minutes)loading/processing after making adjustments to a photo. 'Quit Aperture' was not an available option so I 'Force Quit.' When I reopened the App, it was still doing the same thing. Next, I tried 'Force Quit' AND shut down my system. When I started it up again and reopened the App, still no change. That is about all I know to do; yep, sad but true.  Any advice? I sure would appreciate it! 

    I think this sounds like a problem I had with a corrupted image. Corrupted images happened to me when my iMac was turned off inadvertly when importing pics.
    You can read on my blog how I resolved my issue. Hope it helps.
    http://maximegousse.wordpress.com/2010/12/05/my-aperture-library-crash/
    Max

Maybe you are looking for