Headline GL-booked revenue from Oracle ERP Cloud. The single number the Finance Controller checks at 9am Monday.
At a glance
Headline revenue formally booked into the Oracle ERP Cloud (Fusion ERP) General Ledger across the period. The arithmetic sum of revenue-class journal lines posted from Customer Invoices, Cash Receipts journals tagged to revenue items, AutoInvoice-imported Receivables transactions, and Subledger Accounting (SLA) revenue-recognition journals. This is the audit-grade figure that flows into the Income Statement and survives the Fortune 500 close.
| What it counts | SUM(GL_JE_LINES.entered_cr - GL_JE_LINES.entered_dr) filtered to natural-account segments mapped as Revenue in the Chart of Accounts (typically the 4xxxx natural-account range in the standard Oracle Fusion COA template), with posted_flag = 'Y', joined to the journal source (Receivables, Manual, Spreadsheet, Subledger). Includes all transaction types that hit the GL via Subledger Accounting: Standard Invoices, Credit Memos, Debit Memos, Chargebacks, and revenue-recognition entries from Revenue Management Cloud. |
| Tax treatment | Net of tax. Oracle Fusion’s E-Business Tax engine books tax to a separate liability natural account (typically 21xxx VAT Payable / Sales Tax Payable / GST Payable). This card sums revenue-class natural accounts only, so the figure is exclusive of VAT, GST, and US sales tax across every Business Unit and Ledger regardless of which local tax regime is configured. Tax-inclusive jurisdictions (UK, EU) and tax-exclusive jurisdictions (US) reconcile to the same net-of-tax figure. |
| Shipping | Configurable. If your COA maps freight income to a revenue natural account (e.g. 41900 Freight Revenue), it counts. If freight is mapped to a contra-cost expense account or a clearing account, it does not. Most Oracle Fusion implementations for distribution and retail clients post freight to revenue and so include it. |
| Discounts | Already deducted at the line level. Receivables transactions post net of trade discount, volume discount, and contract-priced terms via the Pricing module. Early-payment discounts (terms-based) hit a separate discount-taken expense account, not revenue, so they do not subtract here. |
| Credit Memos | Deducted. Credit Memos post a debit against revenue via Subledger Accounting, so a returned 0 in the same period (or the period the Credit Memo posts, whichever is later). This is the structural difference vs the commerce-platform Total Revenue, which is gross. |
| Cancelled / voided orders | Excluded. A voided Receivables transaction has complete_flag = 'N' and is reversed via SLA, leaving zero net to the GL. Sales Orders cancelled before billing never reach Receivables and so never reach this card. |
| Currency | Multi-Ledger architecture: consolidated in the reporting ledger’s currency (typically USD or the parent legal entity’s functional currency). Oracle Fusion does the FX translation via the GL Translation process at the configured cadence: daily corporate rate, period-average, or period-end (depending on the FASB-52 / IAS 21 election per ledger). Single-ledger accounts: native ledger currency, no translation. |
| Business Unit scope | Card respects the dashboard’s selected Business Unit filter. By default rolls up every Business Unit the connected role can see across all primary ledgers. Eliminations on intercompany revenue are applied automatically if the user views the consolidated reporting ledger or runs the Financial Consolidation Hub view. |
| Revenue recognition (ASC 606 / IFRS 15) | If your account uses Oracle Revenue Management Cloud (RMCS), deferred revenue is excluded from this card; only recognised revenue counts. Without RMCS, revenue is booked at AutoInvoice posting and the full amount hits the period the Invoice posts to. |
| Time window | 30D vsP (default 30D vs the prior 30D) |
| Alert trigger | drop >15% vsP, driven by sentiment_key: revenue_trend |
| Roles | owner, finance, operations |
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 30-day window covers 14 Mar 26 to 12 Apr 26. Reporting ledger is the US ledger (USD).| Business Unit | Local revenue | FX rate (period avg) | USD equivalent |
|---|---|---|---|
| US Retail Inc | $48,200,000 | 1.0000 | $48,200,000 |
| UK Retail Plc | £18,400,000 | 1.2780 | $23,515,200 |
| EU DTC NV | EUR 11,200,000 | 1.0820 | $12,118,400 |
| Less: intercompany elimination | ($1,840,000) | n/a | ($1,840,000) |
| Revenue Booked into GL (this card) | $81,993,600 |
- **Intercompany elimination removed 1.84M reappears on the US side.
- The USD equivalent uses the period-average rate, set in the GL Daily Rates table by the Treasury team. Oracle Fusion’s GL Translation process can be configured for period-average, period-end, or daily-rate translation; this card respects whichever cadence is set per ledger. If Treasury changes the cadence mid-period (rare but allowed during a rate adjustment), the card moves slightly even though the underlying transactions did not.
- **Commerce platform Total Revenue for the same window was 4.83M gap is the killer finding. A breakdown lives on the Revenue Gap vs Commerce card and the cross-connector card, but at a high level it splits as: 1.1M cancellations and Credit Memos that hit GL but not the commerce headline, 610K timing on the period boundary.
- Last period was $84,500,000. This period is down 3.0% vsP, well below the
drop >15% vsPalert threshold. The Nerve Centre stays quiet, but the trendline still appears on the card. - Revenue Management Cloud (RMCS) impact. The merchant sells extended-warranty contracts and software-bundle subscriptions on 380K hits this card; the remaining 3.82M higher and front-loaded, an audit risk that ASC 606 is specifically designed to remove.
Sibling cards merchants should reference together
Revenue Booked into GL is the canonical revenue figure but it lags real economic activity. Pair it with these to triangulate.| Card | Why pair it with Revenue Booked into GL |
|---|---|
| Revenue Gap vs Commerce | The killer finding for any commerce business running Oracle ERP Cloud. Commerce Total Revenue minus this card, broken down by reason. Tells you whether the gap is timing, mapping, or accounting policy. |
| Invoiced Revenue | The Receivables-Invoice slice of this card. Excludes manual revenue journals and Subledger Accounting adjustments. Useful when AR-driven analysis matters more than P&L roll-up. |
| Cash Collected | What you actually banked, vs what you booked. The spread between this card and Cash Collected is your DSO problem. |
| Revenue by Business Unit | The same number sliced by Business Unit. Essential on multi-Ledger accounts when one Business Unit is masking trends in another. |
| Revenue by Segment | Oracle’s flexible Chart of Accounts segments (typically Cost Centre, Product, Channel, Region) split revenue by your operating dimensions. The most actionable cut on consolidated revenue. |
| Revenue by Currency | Multi-Ledger stores: shows currency mix and FX exposure on the booked total. |
| Open Sales Order Value | Forward-looking complement. Today’s GL revenue is yesterday’s open SOs that converted; today’s open SOs are tomorrow’s GL revenue. |
| shopify.total_revenue / bigcommerce.total_revenue / adobe_commerce.total_revenue / salesforce_commerce_cloud.total_revenue | The commerce-platform headline for the same window. The gap between commerce gross and Oracle Fusion GL is the working-capital telemetry every Fortune 500 Controller wants. |
Reconciling against the vendor’s own dashboard
Where to look in Oracle ERP Cloud: The closest native equivalents in the Oracle Fusion UI are:Navigator → General Accounting → Financial Reporting Center → Income Statement (Standard Report) Navigator → Receivables → Billing → Manage Transactions (transaction-level view of revenue invoices) Reports and Analytics → OTBI (Oracle Transactional Business Intelligence) → Financials → General Ledger Real Time Subject AreaThe Income Statement summary line “Total Revenue” on the consolidated reporting ledger should match this card to within rounding when you select the same period and the same Business Unit scope. For an audit-grade match, the standard approach in Oracle Fusion is to run the Account Analysis Report filtered to the revenue natural-account range with
posted_flag = 'Y', then sum the credit column. OTBI provides the same data via the GL Real Time Subject Area, which is what most Fortune 500 finance teams actually query.
Common mistakes when comparing against Oracle’s own reports:
- Sales Order Inquiry (Order Management module) sums Sales Orders, not booked revenue. SOs in Entered, Booked, or Awaiting Shipping state contribute to that report but are not yet GL revenue. Expect SO Inquiry totals greater than this card.
- Customer Account Inquiry is AR-balance based, not revenue-based. It excludes the receipts side and shows outstanding balances, not booked revenue.
- Subledger-only Account Analysis runs against subledger balances (Receivables, Payables) rather than the GL itself. Subledger and GL are usually in lockstep but a backlog in the Create Accounting program creates short-term divergence.
| Reason | Direction | Why |
|---|---|---|
| Ledger functional currency vs reporting currency | Either | If you compare the card (consolidated reporting ledger) against an Income Statement run at a single primary ledger (functional currency), the FX translation differs. Always run Oracle reports at the same scope as the dashboard filter. |
| Period-end vs period-average FX | Small | Oracle GL Translation is configurable per ledger. The card uses transaction-date corporate rates per posted line, with a translation overlay if the ledger is in revaluation. Differences average to fractions of a percent unless the period had a major FX shock. |
| Credit Memo timing | Either | A return Invoice issued in Period 1 with a Credit Memo posting in Period 2 splits across two periods. Oracle’s Income Statement applies the same convention, but a transaction-type filter that misses the Credit Memo row understates the deduction. |
| Intercompany elimination | Card lower | When the user filters to “Consolidated Reporting Ledger”, Oracle’s eliminations apply via the Financial Consolidation Hub. Per-ledger Income Statements do not eliminate inter-co lines. |
| Revenue Management Cloud (RMCS) | Card lower | Deferred revenue is excluded from this card. The unrecognised balance lives on the Balance Sheet under Deferred Revenue, not Income Statement. |
| Subledger Accounting (SLA) rule customisation | Either | Oracle’s SLA engine lets implementers redirect specific revenue events to non-revenue accounts (e.g. shipping income to Other Income, sample give-aways to Marketing Expense). The card uses the standard revenue natural-account range; merchants with custom SLA rules should confirm their mapping in the field map. |
| AutoInvoice batch lag | Card lower | AutoInvoice is the program that imports Sales Order shipments into Receivables. If it runs on a 4-hourly schedule, orders shipped in the last 4 hours appear in commerce data but not yet in Receivables and so not yet in GL. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
| shopify.total_revenue | Commerce gross greater than Oracle GL booked | Shipped-not-AutoInvoiced orders, cancellations and Credit Memos (subtract from GL but not commerce headline), unmapped marketplace orders, period-boundary timing. |
| bigcommerce.total_revenue | Commerce gross greater than Oracle GL booked | As Shopify above. B2B BigCommerce orders are particularly prone to long Pending-AutoInvoice lag on Net-30 / Net-60 terms. |
| adobe_commerce.total_revenue | Commerce gross greater than Oracle GL booked | As above. Adobe Commerce B2B portals often have multi-step approval before SOs are submitted to AutoInvoice. |
| salesforce_commerce_cloud.total_revenue | Commerce gross greater than Oracle GL booked | Common Fortune 500 pairing. SFCC tracks the order; Oracle Fusion books the revenue once AutoInvoice runs. |
| stripe.stripe_total_revenue | Stripe at most equal to Oracle GL | Stripe sees only card / wallet payments. Wire transfers, ACH, cheque, and Net-30 invoices are missing from Stripe but present in Oracle. |
| paypal.pp_total_volume | PayPal at most equal to Oracle GL | PayPal-only subset. |
Known limitations / merchant FAQs
Why is the GL booked figure lower than my Shopify, Salesforce Commerce Cloud, or Adobe Commerce headline? Three structural reasons, in order of typical contribution:- AutoInvoice lag. Commerce orders flow into Oracle Fusion as Sales Orders via the Order Management module, then move through Booked → Awaiting Shipping → Shipped → AutoInvoice → Posted to GL. The lag is usually 1 to 3 days for DTC and 5 to 30 days for B2B Net-30 or Net-60 terms. Anything in those pre-AutoInvoice states is commerce revenue but not yet GL revenue.
- Credit Memos. A return on a $1,000 order subtracts from this card via Subledger Accounting, but the commerce platform usually shows it on the original gross headline. Over a year a 10% return rate becomes a 10% structural gap.
- Cancellations. A cancelled order may still show in the commerce platform’s lifetime totals but is voided in Oracle Fusion before it reaches Receivables, so the GL net is zero.
*.fa.us2.oraclecloud.com). Vortex IQ supports both natively. Companies migrating up-market from NetSuite to Fusion is a common pattern; we have customers running both during a 12 to 24 month transition.
How does Oracle Fusion’s Multi-Ledger model differ from NetSuite’s OneWorld?
NetSuite OneWorld has Subsidiary as the consolidation primitive and a single chart of accounts mapping. Oracle Fusion has Business Unit (operational) and Ledger (financial) as separate dimensions. A single Business Unit can post to multiple Ledgers (Primary, Reporting, Statutory) for parallel accounting. This card respects whichever Ledger the dashboard filter selects; for consolidated views it pulls the Reporting Ledger.
OTBI vs BI Publisher vs Financial Reporting Center, which feeds this card?
None directly. Vortex IQ pulls from the Oracle Fusion REST API /erpRestApi/resources/<version>/journals and /ledgers/<id>/balances endpoints, which are the same backing data store as OTBI. OTBI is the in-Oracle reporting tool; BI Publisher is the printable-document tool; Financial Reporting Center is the period-close-pack tool. All four (Vortex IQ + the three Oracle tools) reach the same GL_JE_LINES and GL_BALANCES tables.
Subledger Accounting (SLA), how does it affect this card?
SLA is Oracle’s rules engine that translates subledger transactions (Receivables Invoices, Payables Bills) into GL journals. Most Fortune 500 implementations customise SLA rules during go-live to handle their specific COA mapping, intercompany conventions, and revenue-recognition policy. The card uses GL journals (the SLA output), not the subledger directly, so it inherits whatever SLA produces. If a custom SLA rule misroutes revenue to a non-revenue natural account, the card understates; the Account Analysis Report is the audit tool to find such misroutings.
Oracle Integration Cloud (OIC) vs Vortex IQ, are we redundant?
Different layers. OIC is Oracle’s integration platform-as-a-service, used for building point-to-point and batch integrations between Fusion apps and external systems (sending Sales Orders from Salesforce CRM into Order Management, for instance). Vortex IQ is an analytics and operations layer that reads from Fusion (and 70+ other connectors) to produce cross-system findings. OIC moves data; Vortex IQ tells you what the data means once it’s in the right place. We are complementary; many of our Fortune 500 customers use OIC for inbound orchestration and Vortex IQ for cross-stack analytics.
Oracle Fusion REST API freshness, what’s the cache?
Vortex IQ uses the Fusion REST API with a 15-minute cache for this card; the underlying number reflects the GL state as of the last sync window. For real-time intraday checks, the native Oracle UI’s Account Analysis is always live. The Fusion API rate limits are documented per pod region; we honour them with adaptive back-off.
My account uses Oracle Revenue Management Cloud (RMCS), what does the card show?
Recognised revenue only. Deferred revenue (multi-period contracts, subscription billings, extended warranties, software licences with services bundles) sits on the Balance Sheet until RMCS releases it via the periodic recognition program; the released portion hits this card period by period. Pre-RMCS accounts: the full Invoice posts to revenue at AutoInvoice time, no deferral logic.
How does Oracle handle multi-currency vs SAP and NetSuite?
Oracle Fusion’s Multi-Ledger architecture lets you maintain primary, secondary, and reporting ledgers in different currencies with independent COA mappings, then consolidate via the Financial Consolidation Hub. SAP S/4HANA Universal Journal centralises subledger and GL into a single table (ACDOCA), which simplifies real-time reporting but flattens the parallel-ledger concept. NetSuite OneWorld translates at three configurable cadences inside a single GL. Oracle’s strength is Fortune 500 statutory reporting (multiple statutory books for the same legal entity); SAP wins on manufacturing-cost integration; NetSuite wins on simplicity for mid-market.
Single-Ledger vs Multi-Ledger required for consolidation on this card?
Multi-Ledger required for true multi-Business-Unit cross-currency consolidation. Single-Ledger Oracle Fusion (less common but valid for single-country operations) supports multi-currency transactions (a US ledger can take a EUR Invoice) but not parallel-ledger statutory books. The card auto-detects the ledger architecture and renders accordingly.
B2B credit-hold mechanics, does this card show held revenue?
A Sales Order on credit hold has not yet shipped, so it has not yet AutoInvoiced, so it is not in this card. Once Credit Management releases the hold, the SO ships, AutoInvoice runs, and it lands here. The lag is the killer working-capital signal; pair this card with Sales Orders Blocked on Inventory or Credit to see what is stuck.