The live total of open Accounts Receivable, broken down by Business Unit. The headline working-capital figure the controller checks first thing each morning.
At a glance
AR Balance (live, by Business Unit) is the sum of every open Receivables transaction (unpaid and partially-paid invoices, debit memos and chargebacks, net of credit memos and applied receipts) as it stands right now, split out by Business Unit. It is the single number that tells a controller how much money the company is owed and is the working-capital anchor of the morning review. Because it is real-time rather than period-based, it moves as invoices post, receipts apply, and credit memos land. Sourced from Oracle Receivables across all in-scope ledgers.
| What it counts | The live open AR balance per Business Unit: the running sum of Receivables transactions less applied cash and credit memos, for every unpaid or partially-paid item in Oracle Fusion Receivables. The card surfaces the consolidated total and the per-Business-Unit split. |
| Currency | Multi-Ledger architecture: consolidated in the reporting ledger’s functional currency (typically USD or the parent legal entity’s currency), with Oracle’s GL Translation applied per ledger. Single-ledger accounts: native ledger currency, no translation. |
| Business Unit scope | This card is built around the Business Unit dimension. The consolidated headline rolls up every Business Unit the connected role can see; the breakdown shows each Business Unit individually so a controller can spot where the balance concentrates. |
| Time window | RT (real time). The balance reflects the live Receivables subledger as of the last sync window, not a fixed period. |
| Alert trigger | none. This is a monitoring headline, not a threshold alarm; pair it with the aging and DSO cards for the alerting layer. |
| Roles | owner, finance |
Calculation
Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US Fortune 500 omnichannel speciality retailer running Oracle ERP Cloud across three Business Units under two primary ledgers: US Retail Inc (US ledger, USD), UK Retail Plc (UK ledger, GBP) and EU DTC NV (EUR ledger). The reading is taken live on the morning of 22 Jun 26. The reporting ledger is the US ledger (USD), so foreign balances are shown after translation at the corporate rate.| Business Unit | Local open AR | FX rate | USD equivalent |
|---|---|---|---|
| US Retail Inc | $28,400,000 | 1.0000 | $28,400,000 |
| UK Retail Plc | £9,200,000 | 1.2780 | $11,757,600 |
| EU DTC NV | EUR 6,500,000 | 1.0820 | $7,033,000 |
| Less: intercompany AR elimination | ($2,190,600) | n/a | ($2,190,600) |
| AR Balance (this card) | $45,000,000 |
- The Business Unit split is the whole point. US Retail Inc holds 63% of the consolidated balance, but the controller can immediately see that UK Retail Plc’s £9.2M is disproportionately large relative to its revenue. That per-Business-Unit visibility is what makes this a Hero card rather than a single blended total.
- Foreign balances are translated before they roll up. UK and EU AR is converted into USD at the corporate rate so the consolidated figure is comparable. If you pivot the dashboard to a single ledger, you see that ledger’s functional-currency balance without translation.
- Intercompany AR is eliminated at the consolidated view. US Retail Inc bills UK Retail Plc for wholesale stock, creating $2.19M of intercompany AR. At the consolidated reporting ledger that nets out, because the group does not owe itself money. View a single ledger and it reappears.
- It is live, not period-based. A $1.4M receipt applied at 08:40 this morning has already reduced the balance by the 09:00 review. There is no
vsPwindow because the card is a real-time snapshot; trend lives on the aging and DSO cards instead. - This is the denominator behind several other cards. The aging percentages and DSO are all computed against this same open AR base, which is why a sudden jump here ripples into AR Aging 60+ Days and Days Sales Outstanding.
Sibling cards merchants should reference together
AR Balance is the working-capital headline. Pair it with these to understand quality, age, and the cash behind it.| Card | Why pair it with AR Balance |
|---|---|
| AR Aging 60+ Days | Tells you how much of this balance has slipped into the danger band. Balance size means little without aging quality. |
| Days Sales Outstanding | Converts the balance into days of revenue, the standard collections-efficiency yardstick. |
| Cash Collected | The flow that draws this balance down. Balance up with collections flat means cash is not arriving. |
| A/R Aging Detail | The full bucket-by-bucket breakdown behind the headline balance. |
| High-Value Overdue Invoices | Pinpoints the large invoices making up the riskiest part of the balance. |
| Invoiced Revenue | The inflow that builds this balance up, the counterpart to Cash Collected drawing it down. |
| Oracle Fusion Health Score | The composite roll-up that AR health feeds into alongside other integrity signals. |
Reconciling against Oracle ERP Cloud
Where to look in Oracle ERP Cloud: The closest native equivalents in the Oracle Fusion UI are:Navigator → Receivables → Billing → Manage Receivables Balances / Customer Balances Navigator → Receivables → Reports → Receivables to General Ledger Reconciliation Report Reports and Analytics → OTBI → Financials → Receivables Aging Real Time Subject AreaThe Receivables to General Ledger Reconciliation Report is the audit-grade tool for this card. Run it for the same as-of date and Business Unit scope and the open AR balance it reports should match the card to within rounding and any in-flight subledger postings. For the live per-Business-Unit split, most Fortune 500 teams query the OTBI Receivables Aging Real Time Subject Area, which is the same backing data the card reads. Common mistakes when comparing against Oracle’s own reports:
- GL trial-balance AR account vs subledger. The GL control account can lag the Receivables subledger by the time it takes Create Accounting to post. The reconciliation report exists precisely to bridge that gap.
- Comparing a period-end report against a live card. This card is real-time. A period-close AR snapshot is frozen at the close date and will not include today’s invoices and receipts.
- Mixing Business Unit and legal-entity scope. Oracle separates Business Unit (operational) from legal entity and ledger (financial). A report filtered by legal entity will not line up cleanly with a Business-Unit-scoped card.
| Reason | Direction | Why |
|---|---|---|
| Live card vs period-end report | Either | The card is real-time; a frozen close snapshot will not include transactions posted after the close date. Compare against a live balance inquiry, not a period report. |
| Subledger vs GL control account timing | Small | The card reads the Receivables subledger. A backlog in Create Accounting can leave the GL AR control account momentarily behind. The reconciliation report bridges this. |
| Intercompany elimination | Card lower | At the consolidated reporting ledger, intercompany AR is eliminated. A per-ledger report does not eliminate, so it shows a higher balance. |
| FX translation cadence | Small | Foreign-currency AR is translated into the reporting currency per Oracle’s GL Translation cadence. A report run in a single ledger currency differs on mixed-currency balances. |
| Unapplied and on-account receipts | Card lower | Cash received but not yet applied reduces the live net balance. A report that ignores on-account cash shows a higher gross balance. |
Known limitations / merchant FAQs
Why is this card real-time instead of period-based? Because working capital is a now question, not a month-ago question. A controller starting the day wants to know what is owed this minute so they can plan collections and cash. Period-based AR snapshots are useful for close and audit, but for the morning operating review the live balance is the right number, which is why there is novsP window on this card.
Why break it down by Business Unit rather than show one total?
A single blended total hides where risk lives. One Business Unit can be collecting cleanly while another quietly builds a balance far larger than its revenue justifies. The Business Unit split lets a controller spot that concentration in seconds, then drill into the aging detail for the unit that stands out.
Does the consolidated figure eliminate intercompany AR?
At the consolidated reporting ledger, yes. The group does not owe itself money, so intercompany Receivables between Business Units net out. If you pivot the dashboard to a single ledger, intercompany balances reappear because a single ledger does not run consolidation eliminations.
Why does the balance change minute to minute?
Because it is live. Every applied receipt lowers it, every posted invoice raises it, and every credit memo adjusts it. Two readings taken an hour apart on a busy billing or collections day can legitimately differ by millions without anything being wrong.
Is there an alert on this card?
No. AR Balance is a monitoring headline, not a threshold alarm, because a large balance is normal for a large business. The alerting layer lives on the derived cards: AR Aging 60+ Days catches quality deterioration and Days Sales Outstanding catches efficiency drift.
How does Business Unit differ from legal entity here?
In Oracle Fusion, Business Unit is the operational dimension (where the selling and billing happens) while legal entity and ledger are the financial and statutory dimensions. This card slices by Business Unit because that is the lens an operating controller thinks in. If your reconciliation is scoped by legal entity, expect the boundaries to differ.
How fresh is the data?
Vortex IQ reads the Oracle Fusion Receivables data through the Fusion REST API with a short cache, so the balance reflects the subledger as of the last sync window. For an absolutely live figure, the native Customer Balances inquiry in Receivables is always real-time.