The source application’s charge services module should accomodate this.
There are a lot of things the sending and receiving systems should do that they do not. That is why we have interface engines. Certainly the first preference is for the sending system to send the charges correctly but since they may not be able to do that…
I think as long as you can document what your engine is doing and have a way to show which charges were created by the engine then there is no reason not use the full capabilities of the engine to get the job done. It would be a simple matter to write a line to a file every time you add a charge within the engine. This file could then be used as the audit log on those charges.
Not as clean as having the sending system do it for you but, IMHO, it’s better than having someone keying a charge manually.
Scott
