x Want to participate? Join the group to interact
New

Thank you for adding this item to Sage City Ideas Hub.  Open for voting.

Multiple URN's on Nominal Transaction Import

I find it quite extraordinary that there seem to be very few requests to improve the NL Transaction Import by allocating 1 URN to all of the imported transaction lines!

When a Journal is created in the system, all of the lines have the same J000n reference and more importantly, the same URN.

When postings are transferred from Payroll, each line is assigned the same URN.

The core premise of accounting traceability in 200 is that all the double entry transactions associated with a posting have the same URN for consistent traceability and this is always explained to new and existing users where possible encompassing the User No, Source Module and URN logic. Much better even than S50 with Headers & Splits as should be expected!

If & when the user starts to use Import functionality within the system, there is a great deal of time wasted, particularly @ the users year end, trying to answer Auditors & Accountants queries, in justifying why all of the double entries don't have the same URN. This also has the effect of raising integrity questions from the User and/or their Accountants.

The Code exists within the system to allocate 1 consistent URN to a block of n transactions within the same Import, could this not be relatively easy to implement within NLT/a Imports please? 

Graham Michel
  • in reply to Chris Gorringe

    Chris, the URN Column has been removed from the latest Template and quite rightly so in my opinion. I have seen 2 instances recently where users  have populated the URN with a "Batch Number" which were actually a previous URN's on both occasions. As there is no integrity checking on the Import, the transactions were imported and the URN Reports & Workspace enquiries were showing the mix of the Imported transactions some 18 months apairt

  • Add the column "UniqueReferenceNumber" to the CSV or XML import file but don't think of it as the URN that you need to import but the number by which you want to group transactions by. My description of the logic may not be correct have look at. It is an undocumented field. There is also a column called NominalPeriodModule but I haven't used that yet to know what it does exactly.

*Community Hub is the new name for Sage City