Analytics Catalog/Oracle Fusion ERP/Expenses/Credit Card Issuer Invoice Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Expenses

Credit Card Issuer Invoice Report

Expenses

Reconciles the corporate-card issuer's invoice to the card transactions recorded in Expenses — matching what the bank billed against what employees expensed — so the company pays the issuer the right amount and catches unexpensed or disputed charges.

Sample build of the Credit Card Issuer Invoice Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Credit Card Issuer Invoice Report
Sample build · illustrative
Filters
Bu
Sample
Creation Date From
2026-02-28
Creation Date To
2026-02-28
Legal Entity
Globex Holdings
Posted Date From
2026-02-28
Posted Date To
2026-02-28
$1.84M
Issuer invoice
94.1%
Expensed
$108K
Unexpensed
EmployeeCard NumberTransaction DateMerchantCharge AmountExpensedStatus
Sample10012026-04-30Sample$1,240,500.00SampleOpen
10022026-03-31$842,150.75Posted
Sample10032026-02-28Sample$96,400.00SampleValidated
10042026-01-31$1,005,233.10Open
Sample10052025-12-31Sample$58,720.40SamplePaid
Sample10012026-04-30Sample$1,240,500.00SampleOpen
AI Analyst · active
reading

The report ties EXM_CREDIT_CARD_TRXNS to EXM_EXPENSES and the card master, comparing issuer-billed charges to what employees submitted.

flag

$108K of issuer charges are not on any expense report yet, concentrated among a few cardholders — the company owes the issuer for amounts not yet matched to a business purpose.

root cause & next step

Chase the cardholders with unexpensed charges before paying the issuer; persistent gaps usually mean a card-feed mapping issue or a cardholder who has left.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.
SQL data set · genericized · parameterized · no hardcoded segments
Show / hide SQL
<![CDATA[WITH LE_TBL AS
(SELECT distinct default_Code_comb_id, PERSON_ID FROM per_all_assignments_m WHERE ASSIGNMENT_TYPE = 'E'
 AND SYSDATE 								BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE)

SELECT 
	PPNFV.FULL_NAME EMPLOYEE_NAME,
	PAPF.PERSON_NUMBER EMPLOYEE_NUMBER,
	IC.MASKED_CC_NUMBER CORPORATE_CARD_NUMBER,
	ECCT.REFERENCE_NUMBER, 
	TRUNC(ECCT.CREATION_DATE) CREATION_DATE,
	TRUNC(ECCT.POSTED_DATE) POSTED_DATE, 
    TRUNC(ECCT.BILLED_DATE) BILLED_DATE,
    TRUNC(ECCT.TRANSACTION_DATE) TRANSACTION_DATE,
	ECCT.BILLED_AMOUNT,
	HOUFTL.NAME BUSINESS_UNIT,
	--LT.name LEGAL_ENTITY,
	EE.EXPENSE_REPORT_ID,
	(SELECT gcc.segment1||' - '||gl_flexfields_pkg.get_description_sql(gcc.chart_of_accounts_id,1,gcc.segment1) FROM GL_CODE_COMBINATIONS GCC WHERE GCC.CODE_COMBINATION_ID = LT.default_Code_comb_id) LEGAL_ENTITY

FROM
	EXM_CREDIT_CARD_TRXNS ECCT,
	EXM_EXPENSES EE,
	EXM_CARDS EC,
	IBY_CREDITCARD IC,
	PER_ALL_PEOPLE_F PAPF, 
	PER_PERSON_NAMES_F_V PPNFV,
	HR_ORGANIZATION_UNITS_F_TL HOUFTL,
	LE_TBL LT
	
WHERE 1=1
	AND ECCT.CREDIT_CARD_TRXN_ID 				= EE.CREDIT_CARD_TRXN_ID
	AND ECCT.CARD_ID 							= EC.CARD_ID
	AND EC.CARD_REFERENCE_ID 					= IC.INSTRID
	AND EE.PERSON_ID 							= PAPF.PERSON_ID
	AND PAPF.PERSON_ID 							= PPNFV.PERSON_ID
	AND EE.ORG_ID 								= HOUFTL.ORGANIZATION_ID
	AND HOUFTL.LANGUAGE 						= USERENV('LANG')
	--AND ECCT.REFERENCE_NUMBER = '140110948441234'
	AND SYSDATE 								BETWEEN PPNFV.EFFECTIVE_START_DATE AND PPNFV.EFFECTIVE_END_DATE
	AND SYSDATE 								BETWEEN HOUFTL.EFFECTIVE_START_DATE AND HOUFTL.EFFECTIVE_END_DATE
	AND (-1) = (
              nvl(
                EE.ITEMIZATION_PARENT_EXPENSE_ID, -1
              )
            ) 			
	AND PAPF.PERSON_ID = LT.PERSON_ID
	AND (HOUFTL.NAME IN (:P_BU) OR 'All' IN ('All'||:P_BU))
	AND ((SELECT SEGMENT1 FROM GL_CODE_COMBINATIONS GCC WHERE GCC.CODE_COMBINATION_ID = LT.default_Code_comb_id) IN (:P_LEGAL_ENTITY) OR 'All' IN ('All'||:P_LEGAL_ENTITY))
	AND ECCT.POSTED_DATE BETWEEN :P_POSTED_DATE_FROM AND :P_POSTED_DATE_TO
	AND ECCT.CREATION_DATE BETWEEN NVL(:P_CREATION_DATE_FROM,ECCT.CREATION_DATE) AND NVL(:P_CREATION_DATE_TO,ECCT.CREATION_DATE)
	
ORDER BY
	ECCT.TRANSACTION_DATE DESC,
	PPNFV.FULL_NAME]]>
:P_BU :P_CREATION_DATE_FROM :P_CREATION_DATE_TO :P_LEGAL_ENTITY :P_POSTED_DATE_FROM :P_POSTED_DATE_TO

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per source transaction.

GL_CODE_COMBINATIONSdimensionEXM_CREDIT_CARD_TRXNSdimensionEXM_EXPENSESdimensionEXM_CARDSdimensionPER_ALL_ASSIGNMENTS_Mfact · one row per source transactionCharge Amount
●— fact → dimension join
ElementTypeDefinition
GL_CODE_COMBINATIONSdimensiondimension
EXM_CREDIT_CARD_TRXNSdimensiondimension
EXM_EXPENSESdimensiondimension
EXM_CARDSdimensiondimension
Charge Amountmeasuremeasure
Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.
How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →
See the complete model
How this report's fact and dimensions fit the full picture, via conformed keys.
Expenses data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

TableReporting columnsSubject areas
PER_ALL_ASSIGNMENTS_M12921
GL_CODE_COMBINATIONS761
EXM_CREDIT_CARD_TRXNS11
EXM_EXPENSES361
EXM_CARDSSetup / configuration table — joined for reference, not exposed for analytics
IBY_CREDITCARD101
PER_ALL_PEOPLE_F10526
PER_PERSON_NAMES_F_V124169
HR_ORGANIZATION_UNITS_F_TL13172
LE_TBLSetup / configuration table — joined for reference, not exposed for analytics
Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.