Business Requirement for Aging at Transaction Level and As On Date (Doc ID 2148159.1)

Last updated on JUNE 13, 2016

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.3 and later
Information in this document applies to any platform.

Goal

This article explains Oracle's stand on business requirement on aging report at transaction level and as on date.

In the scenario, in RMB 2.3 version, transactions are mapped out across dates and put expected aging balance for an invoice over different aging run date and with balance as on a particular date.

Ability for business to generate aging report based on a date. Have scenario where financial transactions are laid out with:
1. Invoice
2. Payments (On Account/Applied)
3. Adjustment (Match/On-Account)

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms