Analytics Catalog/Oracle Fusion ERP/Receivables/AR Applied and Unapplied Receipts Register Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Receivables

AR Applied and Unapplied Receipts Register Report

Receivables

The receipts register — every receipt in a period showing what was applied to invoices and what remains unapplied or on account, by customer and method, so cash application can reconcile cash received to cash applied.

Related  Pairs with the Receipt History Report — this is the period register; that traces each receipt's full life.

Sample build of the AR Applied and Unapplied Receipts Register Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

AR Applied and Unapplied Receipts Register Report
Sample build · illustrative
Filters
P Company
Sample
P From Date
2026-02-28
P Organization Id
1003
P To Date
2026-02-28
2,310
Receipts
$17.90M
Cash received
$420K
Unapplied
ReceiptCustomerReceipt DateAmountAppliedUnappliedMethod
SampleAcme Industrial2026-04-30$1,240,500.00SampleSampleStandard
Northwind Trading2026-03-31$842,150.75Corporate
SampleGlobex Holdings2026-02-28$96,400.00SampleSampleStandard
Initech LLC2026-01-31$1,005,233.10Default
SampleUmbrella Corp2025-12-31$58,720.40SampleSampleStandard
SampleAcme Industrial2026-04-30$1,240,500.00SampleSampleStandard
AI Analyst · active
reading

The report reads AR_CASH_RECEIPTS_ALL with each receipt's applications, splitting applied from unapplied.

flag

$420K is unapplied across 140 receipts — cash held but not matched to an invoice, which overstates open AR.

root cause & next step

Work the unapplied queue; persistent unapplied cash usually means remittance detail isn't arriving with the payment.

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
Select 
	  hra.Name Business_Unit
	, ccid.segment1 Company 
	, com_d.Description Company_Name	
	, hca.account_number Customer_No , hp.Party_Name Customer_Name
	, rec.Receipt_Number Receipt_No	
	, to_char(his.GL_Date,'MM/DD/YYYY') GL_Date
    , to_char(rec.Deposit_Date,'MM/DD/YYYY') Deposit_Date
    , to_char(rec.Receipt_Date,'MM/DD/YYYY') Receipt_Date
    , Case when his.Status = 'REVERSED' 	
	            then Round((his.Amount *(-1)), 2)	
	            else Round((his.Amount *(1)), 2) end Receipt_Amount
    , rec.Currency_Code Receipt_Currency
	, Case when his.Status = 'REVERSED' 	
	            then Round(((his.Amount *(-1)) * (Case when his.Exchange_Rate is null then 1 else his.Exchange_Rate end)), 2)	
	            else Round(((his.Amount *(1)) * (Case when his.Exchange_Rate is null then 1 else his.Exchange_Rate end)), 2) end Accounted_Receipt_Amount
    , sob.Currency_Code SoB_Currency	
    , nvl(abs(nvl(ar.amount_applied,0)+ar.amount_other_account),0) applied_amount
    , nvl(abs(ar.amount_on_account),0) on_account_amount
	, Case when his.Status = 'REVERSED' 
		        then 0
                  else nvl(round(his.Amount+nvl(ar.amount_applied,0)+ar.amount_other_account+ar.amount_on_account,2)*1,0) end un_app_amount	
--                                3000+				  
	, ar.Status AR_Schedule_Status 
	, his.Status History_Status
	, meth.Name Receipt_Method
	, rec.Type Receipt_Type	
	, rec.Status Receipt_Status
	, aba.name Batch_Number
	, fvvb.Attribute5 HRC_ORG_ID     	
	, ar.payment_schedule_id 
	, his.Cash_Receipt_History_ID
	, rec.Cash_Receipt_ID
	, his.Org_ID	
	, sob.CHART_OF_ACCOUNTS_ID
	, info.org_Information3
		
		
	From AR_Cash_Receipts_All rec
		
	     inner join HR_All_Organization_Units hra
	     on rec.Org_ID = hra.Organization_ID
		
	     left outer join AR_Cash_Receipt_History_All his
	     on his.Cash_Receipt_ID = rec.Cash_Receipt_ID
	     and his.Cash_Receipt_History_ID in (Select his_R.Cash_Receipt_History_ID	
	                                         from AR_Cash_Receipt_History_All his_R 	
	                                         where 1=1	
	                                           and his_R.Status = 'REVERSED'	
											  and his_R.GL_Date >=:p_from_date
											  and his_R.GL_Date <=:p_to_date
											  
	                                          and his_R.Cash_Receipt_ID = rec.Cash_Receipt_ID
		
	                                         Union All	
		
	                                         Select his_O.Cash_Receipt_History_ID	
	                                         from AR_Cash_Receipt_History_All his_O 	
	                                         where 1=1	
	                                         and (Select GL_Date 	
	                                              from AR_Cash_Receipt_History_All his_F 	
	                                              where 1=1 	
	                                                and First_Posted_Record_Flag = 'Y'	
	                                                and his_F.Cash_Receipt_ID = rec.Cash_Receipt_ID
                                              ) between	:p_from_date and :p_to_date 										 
	                                         and his_O.Cash_Receipt_History_ID = (Select Max(his_max.Cash_Receipt_History_ID)	
	                                                                              from AR_Cash_Receipt_History_All his_max 	
	                                                                              where 1=1	
	                                                                                and his_max.Status <> 'REVERSED'	
	                                                                                and his_max.GL_Date >=:p_from_date
                                                                                      and his_max.GL_Date <=:p_to_date																					  
	                                                                                and his_max.Cash_Receipt_ID = rec.Cash_Receipt_ID
	                                                                             )	
	                                          ) 	
	     	
	     left outer join AR_Payment_Schedules_All ar	
	     on rec.Cash_Receipt_ID = ar.Cash_Receipt_ID
		 and ar.org_id =rec.org_id
	     	
	     left outer join HZ_Cust_Accounts hca	
		   on ar.Customer_ID = hca.Cust_Account_ID
	     	
	     left outer join HZ_Parties hp	
	  	 on hp.Party_ID = hca.Party_ID
	     	
	     left outer join GL_Code_Combinations ccid	
	     on his.Account_Code_Combination_ID = ccid.Code_Combination_ID	
	     	
	    /* left outer join fnd_flex_values_vl com_d	
	     on com_d.Flex_Value_Set_ID = 1005441	
	     and ccid.segment1 = com_d.Flex_Value	*/
	     	
	     left outer join HR_Organization_Information info	
		   on info.organization_id = rec.Org_id
	     and info.Org_information_Context = 'FUN_BUSINESS_UNIT' --'Operating Unit Information' 	
		
	     left outer join GL_Sets_of_Books sob	
		   on sob.Set_of_Books_ID = info.org_Information3
	     	
	     left outer join AR_Receipt_Methods meth	
		   on meth.Receipt_Method_ID = rec.Receipt_Method_ID 
		
		left outer join  fnd_id_flex_segments_vl ffs
		on sob.CHART_OF_ACCOUNTS_ID= ffs.ID_FLEX_NUM and ffs.segment_name ='Entity' and ffs.enabled_flag='Y'
		
		 left outer join fnd_flex_values_vl com_d	  
	     on com_d.flex_value_set_id = ffs.flex_value_set_id	 and com_d.enabled_flag ='Y'	
	     and ccid.segment1 = com_d.Flex_Value

         left outer join ar_batches_all aba
         on aba.batch_id = rec.receipt_batch_id
         and aba.org_id	= rec.org_id
		 
		 left outer join hz_cust_site_uses_all hcsua
		 on hcsua.site_use_id = rec.CUSTOMER_SITE_USE_ID
		 
		 left outer join hz_cust_acct_sites_all   hcasa
		 on hcasa.CUST_ACCT_SITE_ID= hcsua.CUST_ACCT_SITE_ID
         
         left outer join FND_VS_VALUES_B fvvb
         on fvvb.VALUE = hcasa.ATTRIBUTE3				 
		 and value_set_id = ( select value_set_id from FND_VS_VALUE_SETS where VALUE_SET_CODE ='XXC_OMS_COMPANY_CODE_MAPPING')
		 	
		
	Where 1=1	
	and his.GL_Date >=:p_from_date
	and his.GL_Date <=:p_to_date
	and (rec.org_id IN (:p_organization_id)OR  1 IN (:p_organization_id||'1'))
	and (ccid.segment1  in ( :p_company ) or 'All' in ( :p_company||'All') )
	and rec.Org_ID in (
							SELECT distinct bu.bu_id
						FROM fusion.fun_all_business_units_v bu
						,fusion.fun_user_role_data_asgnmnts role
						,fusion.per_users pu
						,fusion.per_roles_dn_vl pr
						,fusion.per_roles_dn_tl prtl
						WHERE role.org_id = bu.bu_id
						AND pu.user_guid = role.user_guid
						AND pr.role_common_name = role.ROLE_NAME
						and role.active_flag ='Y' 
						and pu.username = fnd_global.user_name
						and pr.role_id=prtl.role_id
						and prtl.LANGUAGE='US'
						and prtl.ROLE_NAME  in  ('XXC Accounts Receivable Analyst'
												,'XXC Accounts Receivable Manager'
												,'XXC Receivables Inquiry'
												,'XXC Billing Manager'
												,'XXC Billing Analyst'
												)
						and (bu.bu_id IN (:p_organization_id)OR  '1' IN (:p_organization_id||'1'))
	)
	--and rec.Receipt_Number in ('503368588','US01','61387648')
	Order by hra.Name, ccid.segment1, com_d.Description , hca.account_number, hp.Party_Name, rec.Receipt_Number
:p_company :p_from_date :p_organization_id :p_to_date

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.

AR_CASH_RECEIPT_HISTORY_…dimensionAR_PAYMENT_SCHEDULES_ALLdimensionHZ_CUST_ACCOUNTSdimensionAR_RECEIPT_METHODSdimensionAR_CASH_RECEIPTS_ALLfact · one row per source transactionAmount
●— fact → dimension join
ElementTypeDefinition
AR_CASH_RECEIPT_HISTORY_ALLdimensiondimension
AR_PAYMENT_SCHEDULES_ALLdimensiondimension
HZ_CUST_ACCOUNTSdimensiondimension
AR_RECEIPT_METHODSdimensiondimension
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.
Receivables 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
AR_CASH_RECEIPTS_ALL259
AR_CASH_RECEIPT_HISTORY_ALL172
AR_PAYMENT_SCHEDULES_ALL326
HZ_CUST_ACCOUNTS1443
AR_RECEIPT_METHODS15
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.