Oracle FCC: Reviewing Intercompany Balances Using AR/AP and Matching Reports

Rithik

4 min read

·

Oct 21, 2026

--

1

Listen

Share

Introduction

Intercompany transactions are a regular part of financial consolidation. When multiple entities within the same organization transact with each other, their receivable and payable balances need to be reviewed to ensure that the intercompany positions are consistent.

In Oracle Financial Consolidation and Close (FCC), reviewing intercompany data is an important part of the financial close process. Differences between the balances recorded by two entities may require further investigation before the close is completed.

In this blog, I’ll look at Two reports that can help with this review: the Accounts Receivable (AR) and the Accounts Payable (AP) report, and the Intercompany Matching Report.

Each report provides a different perspective on intercompany data and can help users identify balances that need attention.

Understanding Intercompany Reporting

Consider a simple example in which Entity A provides a service to Entity B.

Entity A records an intercompany receivable, while Entity B records the corresponding intercompany payable.

Ideally, the amounts recorded by both entities should agree, subject to the applicable accounting treatment, timing, currency, and other adjustments.

However, differences can arise for several reasons, including:

• Transactions recorded in different periods.
• Differences in the amounts recorded by the two entities.
• Incorrect or missing intercompany partner selections.
• Currency or exchange-rate differences.
• Transactions recorded by one entity but not yet recorded by the other.

Reviewing intercompany reports helps finance teams understand the balances recorded in the application and investigate potential differences.

Reviewing the AR/AP Report

The AR/AP report provides a combined view for reviewing intercompany accounts receivable and accounts payable balances.

This report helps users examine the intercompany balances recorded by entities and review the relevant details, such as the entity, intercompany partner, account, period, and amount, depending on the report configuration.

For example, when Entity A records a receivable from Entity B, the corresponding payable recorded by Entity B can be reviewed as part of the intercompany balance review.

Using the report, users can examine the available AR/AP information and identify balances that may require further investigation. If differences are identified, the relevant entities, intercompany partners, accounts, and periods should be checked to understand the reason.

Using the Intercompany Matching Report

While the AR and AP reports help users review receivable and payable positions, the Intercompany Matching Report provides another view for examining intercompany balances and identifying differences.

The report can help users investigate whether the relevant intercompany balances agree, based on the report’s configuration and the data available.

For example, when reviewing a transaction between Entity A and Entity B, the reviewer can compare the receivable recorded by one entity with the corresponding payable recorded by the other.

If the report identifies a difference or unmatched balance, the next step is to investigate the underlying data.

Some useful checks include:

• Confirming that the correct intercompany partners have been assigned.
• Checking whether both entities have recorded the relevant transaction.
• Reviewing the accounts and periods included in the comparison.
• Checking currency and exchange-rate considerations where applicable.
• Investigating timing differences or other accounting adjustments.

The report helps direct attention to potential discrepancies, but the underlying cause must still be identified and resolved through the appropriate process.

Bringing the Reports Together

The two reports can be used as part of a practical intercompany review process.

A typical review could follow this sequence:

1. Review the AR/AP report. Identify the receivable balances recorded by the relevant entities and examine the corresponding payable balances.
2. Use the Intercompany Matching Report. Review the matching results or differences available in the report.
3. Investigate discrepancies. Check the relevant entity, partner, account, period, and transaction details.
4. Validate corrections. After any necessary adjustments are made, review the relevant data again to confirm the expected result.

This approach helps users move from reviewing individual balances to investigating the intercompany position between counterparties.

The exact review process will depend on the reports configured in the application and the organization’s intercompany reconciliation procedures.

Why These Reports Are Useful

Using these reports together can make intercompany review more structured.

Visibility into receivables and payables: AR and AP report help users examine the balances recorded by individual entities.

Easier investigation: Reviewing both sides of an intercompany relationship helps users identify where further investigation may be required.

Identification of potential differences: The Intercompany Matching Report provides an additional view for reviewing matching results and discrepancies.

Support for the financial close: A structured review process helps teams identify and investigate intercompany issues as part of close activities.

It is important to remember that the reports support the review process; they do not automatically resolve every discrepancy. The underlying data and accounting treatment must still be examined.

Conclusion

Intercompany reporting is an important part of reviewing financial data before completing the consolidation process.

In Oracle FCC, the AR/AP report, and Intercompany Matching Report provide complementary views of intercompany balances. AR and AP report help users review the receivable and payable positions, while the matching report helps them examine matching results and potential differences.

Using these reports together provides a practical starting point for investigating discrepancies and validating intercompany data during the financial close.

Understanding what each report shows, and knowing how to follow up on differences, can make the intercompany review process more consistent and effective.