Billing and revenue recognition are different events. Oracle Advanced Revenue Management uses nonposting arrangements to organize the revenue contract and elements representing obligations. Rules generate plans; the actual plan supplies the recognition schedule. The arrangement itself isn't a journal posting revenue.
This workspace implements a narrower route: a fulfilled service order creates a deferred invoice, and a monthly plan schedules that amount. It doesn't reproduce arrangement generation, element allocation, standalone selling prices or every recognition rule in NetSuite. Each plan starts no earlier than its source invoice and uses equal monthly slices with a rounding adjustment in the final period. Inspect the source invoice and full schedule before posting a recognition journal. A saved plan can be complete while no revenue has yet been recognized.