Post journal batches to update the account balances of your detail and summary accounts. You can post actual, budget, or encumbrance journal batches.
In the Enter Journals window, select a batch row and choose the Review Batch button to view, update, or create journal batches. In the Batch window, choose the Journals button to view the journal lines in the Journals window.
You can select and post journal batches from the Post Journals window. In addition, you can post a journal batch by choosing the Post button from the Enter Journals, Batch, or Journals window when you are entering or reviewing journal batches or journal entries.
Note: If you have added detail accounts to your summary accounts since your last posting operation, run the Maintain Summary Templates program before you post your journal batches. This can improve performance of the posting program. See: Running the Maintain Summary Templates Program
When you post an encumbrance batch imported from Oracle Payables or Oracle Purchasing, General Ledger automatically balances the encumbrance entries to the Reserve for Encumbrance account.
When you post to an earlier open period, actual balances roll forward through the latest open period; budget balances roll forward through the end of the latest open budget year; and encumbrance balances roll forward through the end of the latest open encumbrance year.
If you post a journal entry into a prior year, General Ledger adjusts your retained earnings balance for the effect on your revenue and expense accounts.
Suggestion: Run a Trial Balance Report whenever you post to a previous fiscal year to ensure that your Retained Earnings account is properly reconciled.
You can automate your posting process by scheduling the Automatic Posting program to periodically select and post batches.
Note: Once you post a journal batch, its contents, including descriptive flexfields, cannot be modified. Reversal information within a posted unreversed journal batch can be modified.
Note: The Oracle Workflow Business Event System, introduced in Release 2.6, allows products to seed business events and event subscriptions.
Posting is a seeded business event. See: Business Events.
If you use Reporting Currencies (Journal or Subledger Level), General Ledger automatically generates converted journals for your reporting currencies when you post the original journals in the source ledger if you have set up the appropriate journal conversion rules in Accounting Setup Manager.
Note: You must define appropriate daily rates for the currencies assigned to your reporting currencies before you post journals in your source ledger.
Suspense, rounding imbalances, and intracompany balancing lines are generated independently for each reporting currency (journal and subledger level).
If you use secondary ledgers (Journal or Subledger Level), General Ledger automatically generates converted journals for your secondary ledgers when you post the original journals in the source ledger or source reporting currency if you have setup the appropriate journal conversion rules in Accounting Setup Manager.
Note: You must define appropriate daily rates for the currencies assigned to your secondary ledgers before you post journals in your source ledger or reporting currency.
Suspense, rounding imbalances, and intracompany balancing lines are generated independently for each secondary ledger.
See: Generating Reporting Currency Journals
If you enabled the Track by Secondary Segment option for the ledger, posting to revenue and expense accounts will update the retained earnings account specific to each primary balancing segment value and secondary tracking segment value pair. This applies to the entered amount balance, as well as its corresponding converted balance in the ledger currency.
When journals are backposted to an earlier period that has an income statement impact, posting will update the detail retained earnings account affected.
For a full discussion of this feature, see: Secondary Tracking Segment.
Prerequisites
Enter or generate actual journal batches.
Enter or generate budget journal batches.
Import journal batches from subledgers.
Enter or generate encumbrance journal batches.
Navigate to the Post Journals window.
Note: You can also post a journal batch by choosing the Post button from the Enter Journals, Batch, or Journals window when you are entering or reviewing journal batches or journal entries. This will post the entire batch containing the journal you are entering or reviewing.
From the Find Journal Batches window, query the journal Batch you want to post. You can only query unposted journal batches where you have sufficient read and write access to the ledger or to all of the balancing segment values or management segment values.
From the Post Journals window, you see the Batch name and the posting Period, as well as the Balance Type indicating whether your batch affects Budget, Actual, or Encumbrance balances.
Choose the Review Batch button to review the details of your journal batch.
The Batch widow appears.
Review the Period Status and Post Status to determine if a batch is available for posting.
You can post actual batches to open periods, budget batches to periods in an open budget year, and encumbrance batches to any period up to the last period in the latest open encumbrance year.
Check the Control Total for the journal entry batch, if you entered one. If the control total does not equal Total Entered Debits and Total Entered Credits, you cannot post the batch.
Choose Post to return to the Post Journals window.
Select the journal batches you want to post by checking the box next to each batch.
Choose Post to submit a concurrent request to post the selected journal batches.
You must have read and write access to the ledger or read and write access to all of the balancing or management segment values to post the selected batches.
If you are using budgetary control and have not approved a journal batch before posting, the Posting program will attempt to reserve funds and if successful, post the batch. If the funds reservation is unsuccessful, the Posting program will mark the batch with an appropriate error.
After the concurrent process completes, review the Posting Execution Report to determine if there were any errors during posting.
Note: Posting will end in a warning if any one of the requested batches were not successfully posted.