GL Account Ledger
"Show me everything that hit this account" is the fundamental investigation move in accounting. REDA Financials answers it two complementary ways — the interactive drill from any statement, and a purpose-built report type for ad-hoc analysis — without you ever assembling raw data by hand.
Access you'll need. Any REDA Financials permission set can open the Financial Center tab, run statements and drill; what you see is limited to the records your role can read. Building reports on the GL Account Transactions type uses your org's normal Salesforce reporting permissions.
Route 1 — Drill from any statement (interactive)
Run a Trial Balance (or any statement) scoped how you care — entity, dates, dimension — and click the account's amount. The Transaction Detail window lists that account's ledger entries for exactly that scope, each row linking to its source document. For "what's in utilities this quarter?" this is the fastest tool in the box, and its totals reconcile to the statement by construction.
A worked pass, on Meridian's biggest account: the US entity's first-half trial balance shows Cash and Cash Equivalents with 936,950 of period debits against 61,250 of credits, closing at 875,700. Click the debit amount and the Transaction Detail window opens with the entries behind it — summary bar totals matching the 936,950 you clicked, each row dated, described, and linked to the receipt or journal that created it, 50 per page with the count in the footer. The Source Type column is the investigator's friend: a cash account should read like receipts and disbursements, and anything else in the mix explains itself in one more click.
Route 2 — The GL Account Transactions report type (analytical)
For heavier questions — a year of activity, grouped by month, filtered three ways, exported — the packaged GL Account Transactions report type puts the ledger into Salesforce's native report builder: every accounting transaction with its GL account, entity, ledger and period, ready to filter, group, summarize, chart and subscribe to. It's the "build any ledger view you can imagine" surface — as its own description puts it, for ad-hoc GL account investigation, transaction analysis, and custom financial reporting.
Three recipes that earn their keep:
| The question | The report |
|---|---|
| "Show me a year of this account, month by month" | Filter to the GL account and entity, group rows by month of the transaction date, sum debits and credits — a twelve-row activity profile no statement run gives you directly |
| "What kinds of documents hit this account?" | Group by source type — the mix (and any intruder) in one summary table, chartable for the ops meeting |
| "Ledger extract for the auditor, their format" | Filter to the accounts and period in the sample, add the columns they asked for, export — repeatable next year by saving the report |
| Statement drill-down | GL Account Transactions report | |
|---|---|---|
| Best for | Quick investigation, tying a statement figure | Recurring analyses, big extracts, charts, schedules |
| Scope | Whatever the statement was run for | Anything you can filter in a report |
| Output | On-screen list → source documents | Full Salesforce report: groupings, formulas, export, subscription |
Meridian's investigation patterns
- "That number looks wrong": statement → drill → scan Source Types for the intruder (a journal in an account that should only see invoices, say) → open the document.
- Monthly account review: a saved GL Account Transactions report per sensitive account (bank charges, intercompany), grouped by month, subscribed to the controller.
- Audit support: auditor picks samples from the trial balance; each drill hands them the source documents on the spot.
What the GL account's record page does carry
The account record itself is the account's setup home, not its transaction feed. Its related lists cover the account's configuration life: the framework Group Members it belongs to, Tax GL Mappings, Budget Lines planned against it, plus Notes & Files and field History. Transactions deliberately aren't listed there — the two routes above are built for the volumes real ledgers have, with the scoping (entity, ledger, period, dimensions) that makes a transaction list mean something.
Common mistakes to avoid
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| "Verifying" a statement figure with a report scoped differently | Different dates, ledger or entity produce a different number — and a false alarm | Match entity, ledger and period exactly; better, drill from the statement itself so the scope carries over automatically |
| Rebuilding balances by summing raw transactions in the report builder | Opening-balance rules (balance-sheet accounts from inception, P&L accounts from fiscal-year start) are easy to get wrong by hand | Take balances from the trial balance; use the report type for activity analysis |
| Investigating from the journal entries list | Journals are one source among many — invoices, receipts, disbursements and assets post to the ledger too | Start from the ledger side (drill or report type), which sees every source |
| Paging the drill window to extract a year of data | 50 rows at a time is an investigation pace, not an extraction one | Build the report-type extract and export it |
Where to go next
- Drill-Down from Any Amount — route 1 in detail.
- Standard Reports — the packaged report types, all seven.
- Accounting Transactions — the rows themselves.
Frequently asked questions
Opening and closing balances per account live on the trial balance (any date range you like); the drill lists the movements between. For a literal running-balance column over a long span, a report on GL Account Transactions grouped by date with a summary formula does it.
High-volume accounts would make that page unusable (a cash account can carry thousands of rows). The scoped tools — drill-down and the report type — are built for the volumes real ledgers have.
Both routes: set the dimension in the statement's filter panel before running, and the drill inherits it; or filter/group by the dimension in a GL Account Transactions report. Either way you get the account's story for one slice of the business.
Every REDA role can run statements and drill — the Financial Center is visible to all five roles, and what each user sees follows their data access. Building reports uses your org's normal reporting permissions.
Drill, always — you're two clicks from the answer with the scope guaranteed to match the statement. Reach for the report type when the question will be asked again next month, needs an export, or spans more data than paging suits.
Was this article helpful?