Mapping defaults versus subledger suspense accounting
Blog: Oracle BPM
Subledger Accounting mapping sets provide an efficient way to derive account segment values based on a combination of input transaction values. No matter how complete the mapping logic is at implementation, exceptions may occur over time.
This post describes what happens when transaction data values do not match existing mappings and how you can approach exception handling. It applies to both Oracle subledgers and Accounting Hub implementations.
Leave a Comment
You must be logged in to post a comment.