At present we go into the distribution modules and enter transactions such as an O/E Invoice or P/O Invoice and you post it the system generates a transaction in the appropriate subledger which you must then go and post.

Firstly this is an entirely redundant process, you realistically can't do anything with this transaction in the form of modifying it as if you touch it you will invariably create an out of balance in the G/L, so you have to post it twice. Secondly it takes a whole lot of extra time for the posting processes to happen, especially if you have the option to cost during posting turned on in IC and now to create the sub ledger audit information.

When you post an O/E invoice can the system post the transaction in O/E and the relevant I/C and G/L entries and then in A/R just create all of the relevant posting journal and audit information and leave the batch side of things out of it. So after posting an Invoice in O/E clients are only interested in looking in A/R Inquiry for it, nobody sits there and trawls through the batches looking for O/E invoices anyway, on top of this all that you see in A/R in the entries to revenue / cogs / shipment clearing so you never see what was actually sold on the invoice anyway.

Same logic for PO please.

by: Kerry J. | over a year ago | Operations Management

Comments

• You can already set batches to automatically be generated and posted from OE to AR and GL, and from PO to AP and GL.

  by: Rebekah H. | over a year ago

• yes to a point where the clients security model and setup allows this, to post an oe transaction in A/R the user needs invoice posting rights in a/r which some clients don't allow, and what is the point when drilling down through the inquiry and drill down features to add another step, for example to look at an oe transaction from the G/L you need to start in G/L Transaction Inquiry, drill down to the G/L Batch, Drill down to the A/R Batch which the contents of are more or less useless as you can't see what was sold, and then drill down to o/e from there, the process is 1/3rd longer than it should be.

  by: Kerry J. | over a year ago