AP to GL Reconciliation Webinar Recording (16-Oct-26)
Reconciling Payables to the General Ledger
Kestrel Office Interiors Inc. designs and installs office furniture for corporate clients across the United States. It buys timber, fabric and hardware from more than 300 suppliers, and its accounts payable team processes a few thousand invoices and payments every month.
Kestrel went live on Oracle Fusion Payables and General Ledger last quarter. At every month end the controller finds that the accounts payable balance in the trial balance does not agree with the supplier balances in Payables, and the team spends days matching the two by hand in spreadsheets.
The controller has asked the implementation team to set up a standard month end reconciliation between Payables and the General Ledger, to prove it with test transactions in the system, and to show the team how to find and fix the transactions behind any difference.
Key Business Requirements
Concept explain how Oracle Fusion meets it. Hands-on configure it in your practice instance.
- ConceptBoth Payables and the General Ledger are Oracle products, so the controller does not understand how their balances can ever disagree. Explain why they can, and which standard Oracle tool the team should use to find the difference.
Hint:00:13:07 to 00:15:07
- ConceptList the usual reasons the Payables balance and the General Ledger balance stop agreeing, and the one practice Kestrel should follow to keep differences to a minimum.
Hint:00:15:07 to 00:17:08, and 01:23:43 to 01:24:44 for the recap
- ConceptThe reconciliation must pick up every account Kestrel uses for supplier liabilities. Which setting on an account makes the reconciliation include it, can more than one account carry it, and what happens if no account carries it?
Hint:00:18:21 to 00:20:00, and 00:39:54 to 00:41:02
- Hands-onBefore testing, confirm in the system that the accounts payable liability account is set up so the reconciliation will include it.
Hint:00:32:38 to 00:34:23
- ConceptThe AP team has never seen the reconciliation report. Explain its three amount columns, the main rows of the summary, and why an invoice that is only saved, not validated, does not show as an invoice on it.
Hint:00:21:21 to 00:24:42, and 00:48:46 to 00:49:18, and 01:25:14 to 01:25:47 for unvalidated transactions
- Hands-onTest case 1: an AP clerk enters and validates a supplier invoice for USD 250 at month end, but nobody accounts it. Prepare the reconciliation for the period, open the report, and find the exact invoice that causes the difference.
Hint:00:41:02 to 00:43:12, and 00:43:12 to 00:46:20, and 00:46:20 to 00:51:00
- Hands-onTest case 2: the USD 250 invoice is now paid in full. The invoice is accounted but the payment is not. Run the reconciliation again and show which difference clears and which one remains.
Hint:00:53:03 to 00:56:53, and 00:56:53 to 00:57:58, and 01:02:02 to 01:03:43
- Hands-onTest case 3: someone in finance posts a manual journal of USD 120 straight to the accounts payable liability account. Run the reconciliation again and identify the journal on the report, so it can be traced back.
Hint:01:04:13 to 01:07:31, and 01:07:31 to 01:11:42
- ConceptKestrel wants the system itself to stop users posting manual journals to the accounts payable liability account. Which account setting does this, and which option should Kestrel choose?
Hint:01:15:20 to 01:16:58
- Hands-onBefore closing the period, the AP manager wants a business friendly list of every Payables transaction that is still not accounted, with what to do about each one.
Hint:01:16:58 to 01:19:38
- ConceptAn AP analyst asks: if Create Accounting already moves Payables data to the books, why run the reconciliation at all? And how often should the team run the exception report from requirement 10?
Hint:00:57:58 to 01:00:32, and 01:19:38 to 01:22:40
- ConceptWrite the month end checklist the controller asked for:
- What to do before preparing the reconciliation, and what period status to set afterwards
- What to do with unaccounted transactions that cannot be fixed before the close
- Which format to use when downloading a large report for analysis
Hint:01:26:49 to 01:27:53, and 01:03:43 to 01:04:20, and 01:25:47 to 01:26:49
Your Task
- For each Concept requirement, write a short solution: which Oracle Fusion feature meets it and how. Nothing needs to be set up in the instance for these in this session.
- For each Hands-on requirement, configure it in your practice instance. Start your setup names with your own initials, for example AB_KST01, so they do not clash with other learners in the shared instance.
Attempt the case on your own first. When you need help, show hints.
Solution hints are hidden so you can attempt the case first. Ready to check your approach? Show solution hints
Concept Answers
- Payables never posts directly to the General Ledger. Its accounting goes through Subledger Accounting: transactions are accounted, transferred to the General Ledger and posted. If any link in that chain breaks, the Payables balance and the General Ledger balance stop agreeing. Oracle provides the Payables to Ledger Reconciliation report for this, out of the box, with drill down from any difference to the transactions behind it. 00:13:07 to 00:15:07
- Common reasons Oracle lists:
- Transactions that are not accounted
- Subledger journals that are not transferred or not posted to the General Ledger
- Journals posted to the Payables accounts that did not come from Payables, such as manual journals
- Transactions whose accounts fall outside the account range of the report, for example a liability account without the Accounts Payable financial category
- Transaction amounts that do not agree with the subledger journal line amounts
- The Financial Category of the natural account value must be Accounts Payable. It is set on the Manage Values page of the value set for the natural account segment. Every liability account can carry it, and when the Account parameter is left blank the process includes all accounts with this category. If no natural account value in the chart of accounts has the category, the Prepare Payables to General Ledger Reconciliation process fails. 00:18:21 to 00:20:00 00:39:54 to 00:41:02
Oracle notes that bills payable, intercompany and tax authority liability accounts can also be given the Accounts Payable category to include them in the reconciliation.
- Columns: Payables Amount is the subledger side, Accounting Amount is the General Ledger side, and Difference should be zero. Rows: the begin balance, then the period activity (Invoices, Payments, Prepayments, Payables Variance), the end balance, and on the accounting side the non Payables lines such as Non-Payables Begin Balance, non Payables journals and Other Accounting. 00:21:21 to 00:24:42
The Payables begin and end balances include validated transactions only. Unvalidated transactions are counted in the Payables Variance amount instead. 00:48:46 to 00:49:18 01:25:14 to 01:25:47
- The Third Party Control Account attribute on the natural account value. Choose Supplier Control Account for the accounts payable liability account. General Ledger then prevents manual journals to that account, and Payables accounting must carry supplier information. 01:15:20 to 01:16:58
General Ledger prevents manual journals to every account whose Third Party Control Account is set to anything other than No.
- Create Accounting writes Payables transactions into the books. The reconciliation does not account anything: it compares the two sides and shows which transactions cause a difference, including problems Create Accounting does not show, such as manual journals posted straight to the liability account. 00:57:58 to 01:00:32
Run the exception report as often as possible during the month, for example weekly, not only at month end, so problems are fixed early. 01:19:38 to 01:22:40
- Month end checklist:
- Account all Payables activity, and transfer and post it to the General Ledger, before closing the Payables period and preparing the reconciliation. Afterwards set the Payables period to Closed or Permanently Closed so the summary and detail stay in line. 01:26:49 to 01:27:53
- Run the Payables Unaccounted Transactions and Sweep process, if Kestrel’s accounting practice allows it, to move unaccounted transactions to the next open period. 01:03:43 to 01:04:20
- Download in CSV when the data is large and will be worked on; use Excel only for reference. 01:25:47 to 01:26:49
Hands-on Steps
- Review the Financial Category on the liability account (requirement 4).
Navigation Setup and Maintenance > Manage Chart of Accounts Value Sets
00:32:38 to 00:33:18- Search for the value set of your natural account segment and click Manage Values 00:33:18 to 00:33:51
- Find the accounts payable liability account, for example 200100, and check that Financial Category shows Accounts payable 00:33:18 to 00:34:23
This is a shared instance. Review the value only, and do not change any account.
- Create and validate an invoice, but do not account it (requirement 6).
Navigation Navigator > Payables > Invoices > Tasks > Create Invoice
00:41:02 to 00:41:41- Supplier: any active supplier. Number: your initials and a test number, for example AB_KST01. Amount: 250 USD. 00:41:41 to 00:42:11
- Add one line for 250 with an expense account, keeping the same company on the liability and expense accounts so no intercompany accounting is created 00:42:11 to 00:42:41
- Make sure the accounting date is in the open period you are testing, then validate the invoice. Do not account it. 00:42:41 to 00:43:12
The accounting date must fall in an open Payables period. The trainer checks this in Navigator > General Accounting > Period Close 00:36:09 to 00:37:19. In the shared instance, do not open or close any period.
- Prepare the reconciliation data (requirements 6, 7 and 8).
Navigation Navigator > Tools > Scheduled Processes > Schedule New Process > Prepare Payables to General Ledger Reconciliation
00:43:12 to 00:43:42- Request Name: your initials and the test, for example AB_KST01_TEST1 00:43:42 to 00:44:13
- Ledger: your primary ledger. Business Unit: leave blank. Accounting Period: the period of your invoice. 00:43:42 to 00:44:13
- Review Include Intercompany Transactions and Include Bills Payable, leave Account blank, then Submit 00:44:13 to 00:45:15
- Wait for the parent process and its child processes to complete 00:45:15 to 00:46:20
Run this again with a new request name for each test case, for example AB_KST01_TEST2 and AB_KST01_TEST3.
- Open the report and drill down to the cause (requirement 6).
Navigation Navigator > Payables > Payments > Tasks > Payables to Ledger Reconciliation
00:46:20 to 00:47:43- Select your ledger and your request name, and check the parameters shown at the top 00:47:43 to 00:48:16
- Read the Invoices row: your invoice shows in Payables Amount but not in Accounting Amount 00:48:16 to 00:49:18
- Click the Difference amount to drill down. Your invoice shows a reconciling amount of 250 with no accounting created. 00:49:49 to 00:51:00
- Leave the drill down with Return, never with Done, which takes you out of the reconciliation 00:52:30 to 00:53:03 01:10:39 to 01:11:42
Other learners use the same instance, so the summary totals include their transactions too. Check your own result in the drill down, by your invoice number and amount.
- Pay the invoice and account only the invoice (requirement 7).
Navigation Navigator > Payables > Payments > Tasks > Create Payment
00:53:03 to 00:54:49- Type: Quick. Select your invoice, pay the full 250, Apply, then Save and Close. 00:54:49 to 00:55:25
- Open your invoice again and account it and post it to the ledger. Leave the payment unaccounted. 00:55:25 to 00:56:14
- Rerun the reconciliation and compare (requirement 7).
Navigation Navigator > Tools > Scheduled Processes > Schedule New Process > Prepare Payables to General Ledger Reconciliation
00:56:53 to 00:57:28- Submit with a new request name for the same period 00:57:28 to 00:57:58
- In the report, your invoice no longer appears in the Invoices difference, and your 250 payment now appears in the Payments difference 01:02:02 to 01:03:43
- Post a manual journal to the liability account (requirement 8).
Navigation Navigator > General Accounting > Journals > Tasks > Create Journal
01:04:13 to 01:04:53- Enter a journal of 120 with two lines, one of them on the accounts payable liability account, with the accounting date in your test period, and save it 01:05:28 to 01:06:29
- Post the journal and check it is posted 01:06:29 to 01:07:31
- Prepare the reconciliation again with a new request name 01:07:31 to 01:09:02
- In the report, search for your request name, then drill down on the non Payables journals line and find your 120 journal by its name 01:09:32 to 01:11:09
If the liability account is a third party control account, General Ledger rejects the manual journal. That is the control in requirement 9 working.
- Run the period close exception report (requirement 10).
Navigation Navigator > Tools > Scheduled Processes > Schedule New Process > Subledger Period Close Exceptions Report
01:16:58 to 01:17:32- Journal Source: Payables. Select your ledger and period, then Submit. 01:17:32 to 01:18:05
- Open the output: your unaccounted 250 payment is listed with the suggested action to submit Create Accounting 01:18:35 to 01:19:38
The trainer also shows the Payables Period Close Exceptions Report, which lists the same Payables exceptions. 01:20:08 to 01:22:40
0:00 – 1: Oracle ERP Guide Platform Overview ⟶
11:40 – 2: Foundational AP System Setups ⟶
15:07 – 3: Common Causes of Reconciliation Mismatches ⟶
18:22 – 4: Defining and Configuring Control Accounts ⟶
21:21 – 5: Analyzing Reconciliation Report Structure ⟶
24:55 – 6: Unaccounted Payment Scenario Demonstration ⟶
28:51 – 7: Period Close Exception Reporting ⟶
31:26 – 8: System Setup and Value Sets ⟶
41:07 – 9: Live Invoice and Payment Testing ⟶
50:00 – 10: Using Drill Down for Root Cause ⟶
1:04:32 – 11: Manual Journal Impacts on Liability Accounts ⟶
1:10:05 – 12: Trouble shooting Non Payables Journal Entries ⟶
1:17:18 – 13: Sub Ledger Period Close Exception Report ⟶
1:23:48 – 14: Summary of Common Reconciliation Differences ⟶
1:26:45 – 15: Reconciliation Best Practices ⟶
1:43:09 – 99: Live Invoice and Payment Testing ⟶
