Professional Documents
Culture Documents
Oracle ERP Cloud is designed to perform financial reporting in General Ledger, not in the Budgetary
Control module. Budgetary Control is used to control spending in the procure-to-invoice process, not
for revenue-based transactions. Organizations that need to track actual revenue against budgeted
revenue should load the revenue budget amounts into General Ledger. In addition, they should load
the expense budget amounts into General Ledger so they can perform the variance reporting for
revenues and expenses in General Ledger. If organizations desire encumbrances to be included in
the budget vs. actual reporting, they can enable Encumbrance Accounting for the ledger.
Oracle ERP Cloud is designed to control spending against revenue in Budgetary Control. To achieve
this, organizations need to track revenue in General Ledger account(s), extract the balance(s) from
General Ledger, and load them into Budgetary Control as the budget amount for expense account(s).
As expenses are incurred during the procure-to-invoice process, budgetary control checks whether
budget is available for spending.
In both scenarios, it is not necessary to load budget amounts into revenue accounts in Budgetary
Control. Budgetary Control is not an accounting system and does not recognize account types; it
processes all accounts as expenditures. General Ledger can inform users when revenue exceeds
budget or forecast via reports or analytics. Organizations should define Supplemental Rules in their
control budgets to exclude revenue accounts from Budgetary Control.
Oracle ERP Cloud performs variance reporting for revenue accounts in General Ledger, not Budgetary
Control. In fact, all financial reporting should be performed in General Ledger because it stores the
official accounting records. Budgetary Control typically captures balances for expense accounts only;
therefore not all account types are available in Budgetary Control for reporting. There can be
differences in the balances between Budgetary Control and General Ledger due to timing or
accounting differences. Budgetary Control can reserve funds for unposted journals whereas General
Ledger account balances only include posted journals. For organizations that use a contra-revenue
account in Payables invoices for revenue refunds, you should exclude the contra-revenue account
from Budgetary Control and use General Ledger for reporting on the refund or net revenue balance.
Here are the steps to achieve variance reporting for revenue accounts in General Ledger:
1. Load budget amounts for revenue accounts into General Ledger. (Also load budget amounts for
expense accounts for variance reporting on expense accounts.) Budget revenue amounts should be
loaded as negative amounts since they are credit-based accounts. For contra-revenue accounts
and expense accounts, budget amounts should be loaded as positive amounts since they are debit-
based accounts.
GL Budget Spreadsheet Figure 1. Navigator>General Accounting> Dashboard> Task: Create Budgets in Spreadsheet.
» Alternatively, for each parent value that you budget against, create a detail child value for
which to store the budget balance. Set the Allow Posting flag to “No” for this account so
actual or encumbrance journal entries cannot post to it. (You can set the Allow Budgeting flag
to any value as it is not currently used in Oracle ERP Cloud.) Reporting at the parent account
level will provide a meaningful Variance amount.
2. Enable Encumbrance Accounting for the ledger if you want budget vs. actual reporting to include
encumbrance balances. (Note: you will need to enter journals to record the initial encumbrance
balance if you have open requisitions or purchase orders at the time you enable Encumbrance
Accounting.)
Enable Encumbrance Accounting Figure 2. Navigator>Setup and Maintenance> Task: Manage Encumbrance Accounting.
» Note: if contra-revenue accounts are used in Payables invoices, you should also exclude
contra-revenue accounts from budgetary control. Reporting for these accounts are available
in General Ledger.
4. Currently, please refrain from using Account Monitor in General Ledger to report on budget vs.
actual variance for revenue accounts. The variance calculation does not reflect the desired intent for
the public sector industry. Use Smart View or Financial Reports instead.
Oracle’s best practice recommendation is to control spending against revenue in Budgetary Control.
Here are the steps to achieve this:
1. Capture revenue or net revenue in one or more General Ledger accounts. Retrieve the balance from
General Ledger using Smart View, Trial Balance, OTBI or any of the inquiry and reporting solutions
in General Ledger.
2. In Budgetary Control module, create a new control budget with Absolute control level. Upload the
revenue balance to the new control budget using the task “Enter Budget in Spreadsheet” or use the
Budgetary Control Budget Import FBDI spreadsheet. Enter the amount as the budget for the detail
or parent level expense account(s) that consume the revenue. If your organization only allows
spending a fraction of the revenue, you can calculate the appropriate amount to load as the budget
for expenditures. Upload the spreadsheet with the option “Import Amounts as Entered”.
4. Decide how frequently you need to load the revenue to Budgetary Control to control spending (i.e.
daily, weekly, etc.). Repeat steps 1-3 for the desired frequency.
Note: The control budget definition includes options to allow budget adjustment increases and
decreases. Please set these options appropriately per your organization’s policies.
blogs.oracle.com/oracle
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0518