Every GL export looks different. GL Down Driller doesn't care.

Who this is for

• Accountants who spend the first ten minutes of every GL review just figuring out which columns are which in a new or unfamiliar export.
• Controllers overseeing multiple entities or properties who need to drill into GL detail without opening a different tool or template for each system's export format.
• Junior FP&A analysts learning to navigate GL detail who need a tool that adapts to the data instead of forcing the data into a rigid template.
• Anyone handling sensitive financial data who wants GL analysis without uploading a general ledger export to a third-party server.

What it solves

Drilling into GL detail sounds simple until you're staring at an export from a system you don't normally work in, with column headers that don't match what you expected, and no clean way to get to the transaction-level detail behind a summary number. Every accounting system exports GL data a little differently — different column orders, different naming conventions, different ways of handling multi-entity data. That inconsistency turns a five-minute drill-down into a twenty-minute exercise in reverse-engineering the file.

There's also a data-handling problem most tools ignore: GL exports contain real financial detail, and uploading that to a third-party server to get it analyzed is a legitimate concern for anyone handling client, tenant, or owner financials.

GL Down Driller addresses both. It auto-detects the format of whatever GL export you bring — using a two-pass column-matching process to correctly identify what each column represents, even across formats it hasn't seen structured exactly that way before. And because all processing happens in your browser, the file never leaves your device. There's no upload, no server-side storage, no third party ever touching your GL data.

Features

• Automatic GL format detection. No manual column mapping required for standard exports — the tool identifies the structure of the file you bring.
• Two-pass column matching. A first pass identifies likely column matches; a second pass verifies and corrects them, which is what makes the auto-detection reliable across inconsistent export formats instead of just guessing once and hoping.
• Multi-entity support. Drill into GL detail across multiple entities or properties in the same session without re-uploading or reconfiguring for each one.
• In-browser processing — no data leaves your device. There's no server-side upload. Your GL data is processed locally, which matters when the file in front of you includes real financial detail you're responsible for protecting.
• Built and hardened through real QA cycles. Currently at v1.1.0 with all 21 identified QA defects resolved and 28 regression checks passing — this has been through actual bug-fixing rounds, not shipped once and left alone.

How it works

1. Bring your GL export. Drop in a GL export from whatever system you're working with — Yardi, MRI, RealPage, or a custom export. No pre-formatting required.
2. GL Down Driller auto-detects the format and matches columns. The two-pass matching process identifies which columns represent account, date, amount, entity, description, and so on — even if the export's structure doesn't match a format the tool has seen labeled that way before.
3. Drill into the detail. Once the format is matched, drill down into GL detail by account, entity, date range, or transaction — all inside your browser, with nothing sent anywhere.

Typical input: a raw GL export file (CSV or similar) from any standard property accounting system. Typical output: a drillable, correctly-mapped view of that GL data, ready for line-item analysis.

Real use-case example

Input (anonymized GL export excerpt, unfamiliar column order):

What GL Down Driller does with it:

The two-pass column matcher identifies GLDate as the transaction date, Acct#/AcctDesc as the account identifier and name, Ent as the entity/property code, Amt as the transaction amount, and RefNo as the reference number — despite none of those headers being the "expected" labels. From there, you can drill into every transaction under Account 6410 across PROP-04, or pull every R&M transaction across all entities in the export, without manually remapping a single column.

FAQ

Does my GL data get uploaded anywhere?

No. All processing happens in your browser. There's no server-side upload and no third party sees your GL data.

What GL export formats does it handle?

It's built to auto-detect standard property-accounting GL exports (Yardi, MRI, RealPage, and similar), and the two-pass matching is designed to adapt to export formats it hasn't seen in that exact structure before. If a file genuinely can't be parsed, that's useful feedback — flag it.

What does "multi-entity support" actually mean here?

You can drill into GL data across more than one entity or property within the same session, rather than needing a separate upload or reset for each one.

How stable is this tool?

Currently at v1.1.0. All 21 QA defects identified during testing have been resolved, and it's passing 28 regression checks. It's had real bug-fixing cycles behind it, not a single release with no follow-up.

Is the code available to review?

Yes — GL Down Driller is open source. See the GitHub repo for the code itself.

Why should I trust what it pulls back?

Because you can check every step. Format detection and column matching are deterministic — the same export always resolves the same way — and the drilled-down detail is your own GL rows, not a summary or an inference. Nothing leaves your browser, and the source is public if you want to read exactly how the parsing works.