REDA One Help Center
EN
Language
English EN Español ES Português PT Italiano coming soon Français FR Deutsch coming soon العربية coming soon
reda.one ↗
Home / REDA Financials AI / Financial Reports / Financial Statements / Drill-Down from Any Amount

Drill-Down from Any Amount

A financial statement that can't answer "what's in that number?" invites arguments. In the Financial Center, every detail-line amount is a link: click it and the Transaction Detail window opens with the exact ledger entries behind that figure — scoped to that account, that entity, that period, and whatever dimension filters you had on. Two clicks from statement to source document.

Getting there. Open the App Launcher (the grid icon at the top-left of any page) → REDA Financials AI → the Financial Center tab, run any statement, then click a detail-line amount to open the Transaction Detail window.
Access you'll need. Any REDA Financials permission set can open the Financial Center tab, run a statement and drill into its amounts; what you see is limited to the records your role can read.

The drill chain

Click an amount on a report line

Account-level amounts are drillable (blue); group subtotal rows are the sum of their children — drill the children.

Read the Transaction Detail window

A summary bar (entity, date range, total debit/credit, record count) over a paged list — 50 per page — with columns Transaction #, Date, Source Type, Source Document, Description, Debit, Credit. The list's totals reconcile to the number you clicked, by construction.

Jump to the source document

The Source Document column links to the actual invoice, receipt, payment, journal or asset behind each entry. Statement → ledger → paper: the full audit chain, no report-building required.

The window, piece by piece

The Transaction Detail window has three parts. The summary bar states the scope and the proof: the entity, the date range, Total Debit and Total Credit across everything in scope, and the record count. The list pages through the entries 50 at a time (Previous / Next, with a "Showing 1 - 50 of 212" footer). Each row carries:

ColumnWhat it holds
Transaction #The ledger entry's own number — the atomic unit of your books.
DateThe posting date that placed it inside the period you clicked.
Source TypeWhat kind of document created it — the fastest mis-posting detector there is (a journal in an invoice-only account stands out immediately).
Source DocumentA link to the actual record. The window resolves it in a sensible order — sales invoice, purchase invoice, cash receipt, cash disbursement, journal entry, fixed asset, or the posting's source record — and one click opens it.
DescriptionThe posting's own narrative.
Debit / CreditThe entry's amounts, in the report's currency mode. They sum to the summary bar's totals — which reconcile to the number you clicked.

What's drillable, statement by statement

  • Trial Balance — the Period Debit and Period Credit amounts on account lines. Opening and closing balances aren't links (they summarize history outside the period); group subtotal rows aren't either.
  • Income Statement, Balance Sheet, Cash Flow — the account-level line amounts.
  • Everywhere — group totals are arithmetic over their members, so the drillable detail always sits one level down.
The dispute killer. "Why is repairs so high this quarter?" used to be an afternoon. Now: open the income statement, click Repairs & Maintenance, read the invoices, forward the two big ones. The same trick verifies auditor samples, hunts mispostings (drill the account that looks wrong and scan Source Types), and settles month-end reviews in the meeting itself.
Meeting-room habit: drill live. Month-end reviews go faster when the statement is on the screen and every "what's that?" gets drilled on the spot — the summary bar proves the total, the Source Document link shows the paper, and the action item leaves the room already specific.

What the drill respects

  • Your whole filter state — entity, ledger, the clicked period's dates, dimension filters, currency mode. The detail is always the same scope as the statement.
  • Your permissions — the drill shows what your access allows, like everything in reporting.

Common mistakes to avoid

MistakeWhy it hurtsDo this instead
Paging through hundreds of records to build an extractThe window is an investigation tool, 50 rows at a time — extraction by paging is an afternoon lostReproduce the scope in a report on the GL Account Transactions report type and export that (see GL Account Ledger)
Forgetting a dimension filter is activeThe drill inherits the statement's whole filter state — the "missing transaction" is simply outside the sliceCheck the Dimensions section of the filter panel when a drill looks thin
Drilling to answer "what's the opening balance made of?"The drill covers the clicked period's activity; an opening balance is history before itRe-run the statement with an earlier date range covering that history and drill there
Judging an account by its first pageThe interesting entry is rarely in the first 50 of 400Read the summary bar first — Total Debit, Total Credit, record count — then hunt with the totals in mind
If the window closes on you. A drill that can't fetch its data closes with an error toast ("Drill-down failed: …") rather than showing half an answer. Re-run the statement and drill again; a persistent failure is one for your administrator, with the toast's detail text in hand.

Where to go next

  1. GL Account Ledger — deeper per-account investigation patterns.
  2. Trial Balance — the classic drill starting point.
  3. Accounting Transactions — what those ledger rows are.

Frequently asked questions

A group is arithmetic over its member accounts — the transactions belong to the accounts. Drill the account lines; the group is their sum.

Usually you're hunting the outliers — sort by scanning the amounts per page. For bulk analysis, that's the moment for a Salesforce report on the GL Account Transactions report type (see GL Account Ledger) with the same scope.

The modal is for investigation; for a shareable extract, reproduce the scope in a report on the GL Account Transactions report type and export that.

Yes, by construction — the summary bar's Total Debit / Total Credit aggregate exactly the entries in scope, which are exactly what the statement summed. If you clicked a debit amount, compare it to Total Debit; a credit amount, to Total Credit.

The same as the statement you drilled from — entity functional or corporate, per the run's currency mode. The scope carries over whole; nothing is re-translated on the way into the window.

Straight to the record that created the posting — the sales or purchase invoice, cash receipt or disbursement, journal entry, or fixed asset. That's the end of the audit chain: statement line → ledger entry → the paper itself.

Was this article helpful?