Funds Capture Authorization And Settlement Formats

Payments

The funds-capture formats configured for inbound payments — the authorization and settlement file formats used to process customer card and bank receipts through each payment processor.

Sample build of the Funds Capture Authorization And Settlement Formats — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Trxn Document Id

1003

Formats

Processors

Incomplete pair

Format	Type	Processor	Status
Sample	Standard	Sample	Open
—	Corporate	—	Posted
Sample	Standard	Sample	Validated
—	Default	—	Open
Sample	Standard	Sample	Paid
Sample	Standard	Sample	Open

AI Analyst · active

reading

The report reads the funds-capture authorization and settlement formats by processor.

flag

One processor has an authorization format but no settlement format — captured funds authorize but never settle, leaving receipts in limbo.

root cause & next step

Assign the matching settlement format for that processor; an authorize-without-settle pair strands customer payments.

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

IBY_TRXN_DOCUMENTS
IBY_FORMATS_VL

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 XMLTYPE(DOCUMENT, NLS_CHARSET_ID('UTF8'))
FROM IBY_TRXN_DOCUMENTS WHERE TRXN_DOCUMENT_ID =:TRXN_DOCUMENT_ID

:TRXN_DOCUMENT_ID

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.

●— fact → dimension join

Element	Type	Definition
IBY_FORMATS_VL	dimension	dimension
Amount	measure	measure

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.

Payments 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.

Table	Reporting columns	Subject areas
IBY_TRXN_DOCUMENTS	Setup / configuration table — joined for reference, not exposed for analytics
IBY_FORMATS_VL	Setup / 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.