Meet @ledgerq: Your ERP, Now Inside Slack

Someone drops a question in your #finance channel: "how much is Acme still sitting on past 90 days?" Normally that kicks off the ritual — someone alt-tabs to the ERP, filters an aging report, screenshots it, pastes it back. Twenty minutes and three context-switches later, everyone's moved on.

LedgerQ's Slack integration collapses that to one line. Type @ledgerq in any channel or DM, ask in plain English, and the answer comes back in the thread — pulled live from your books by the same Sebee AI CFO that powers the in-app assistant. No login, no export, no leaving the conversation.

Ask @ledgerq in any channel — answers land in the thread, live from your ledger, where the whole team can see them.

What it actually is

The integration wires a Slack app to your LedgerQ tenant. When someone mentions the bot, Slack posts the event to LedgerQ, which:

1. Verifies it's really Slack — every event is HMAC-checked against your signing secret with a 5-minute replay window.
2. Maps the workspace to your company — the Slack team_id resolves to exactly one LedgerQ tenant, so a mention can only ever touch your books.
3. Maps the person to a LedgerQ user — a Slack user has to be a known user in your tenant (by mapping or verified email). Random workspace members get a polite "you're not linked" — never data.
4. Asks Sebee — the question runs through the identical brain the app uses, then the answer is posted straight back into the channel or thread.

The important word is live. @ledgerq isn't reading a nightly export or a cached summary — it queries your current ledger the moment you ask, honouring closed periods and your chart of accounts.

Why finance belongs in the channel

Your team already lives in Slack. Sales asks about a customer's balance; ops asks what's low on stock; the founder asks "are we okay on cash this month." Every one of those is a finance question that today becomes a Slack DM to whoever owns the numbers. @ledgerq turns that person-shaped bottleneck into a bot that never sleeps, answers in seconds, and does it where everyone can see the answer — so the whole team gets smarter, not just the one person who ran the report.

And because it's the same engine as the app, it inherits every guardrail: per-tenant isolation, a read-only database role, and your role-based permissions. More on that below — first, the fun part.

Ten questions, ten modules

Here's what a day of @ledgerq looks like across the suite — tap any question below to watch it answered in the thread, straight from the live ledger. (Figures are illustrative; yours come from your books.)

…and a rapid-fire round

Because it's the whole ledger, the long tail is just as answerable:

@ledgerq top 5 customers by revenue this quarter — ranked list with amounts. @ledgerq flag any unusual transactions this week — surfaces >2σ / >25% deviations for review. @ledgerq total T&E expense reports pending reimbursement — batch total + count. @ledgerq compare Q1 vs Q2 revenue and operating expenses — side-by-side with deltas. @ledgerq what's the per-diem cap in our travel policy? — reads it straight out of your uploaded SOPs.

That's AR, AP, treasury, GL, financial reporting, KPIs, inventory, fixed assets, FP&A, consolidation, expenses, and policy search — all from a text box you already have open.

Reports, not just answers

Ask for a report and @ledgerq returns the actual numbers, not a link. AR aging, AP aging, trial balance, balance sheet, income statement, cash-flow (direct or indirect), financial ratios, top customers/vendors, period comparisons — each is a purpose-built report tool, so the figures are consistent with what the app's statements show and respect period locks.

In Slack you get the report as clean, readable text right in the thread — perfect for a quick answer the whole channel can see. When you want it to stick, ask Sebee in the app to pin it to your executive dashboard as a live chart — the underlying query is saved and re-runs on refresh, so the pinned view stays current without anyone rebuilding it. Think of Slack as the fast lane for "what's the number right now," and the dashboard as the home for "watch this number over time."

What stays in the app — on purpose

@ledgerq in Slack is built for asking and reporting, and it's deliberately scoped there:

• Anything that moves money is confirmed in the app. Sebee can propose a journal entry, a collection reminder, a purchase order — but those become approval cards behind your segregation-of-duties workflow. Slack is text-only and has no approval surface, so it can't post to your ledger. That's a feature: the channel is a great place to ask, not a place where a stray message could touch your books.
• Hands-on workflows live where they belong. Bank reconciliation, marketplace/Shopee settlement matching, BIR forms and e-filing, and period-close all have dedicated, controlled screens in LedgerQ. @ledgerq will happily tell you the numbers behind them — your cash-clearing balance, your VAT Payable, revenue by channel — but the close itself is a deliberate, reviewable app action, not a one-liner in a channel.
• No employee PII, ever. Payroll is answerable only at batch-total level; salaries, payslips, tax IDs and bank details are simply not reachable by the assistant, in Slack or the app.

Isolation you can actually trust

Putting your ledger one @-mention away only works if the walls are real. They are:

• DB-enforced tenant isolation. @ledgerq's queries run under a dedicated read-only Postgres role with row-level security — every tenant-scoped table is filtered to your company_id at the database, so even a cleverly-worded question can't reach another company's rows.
• One workspace, one tenant. A Slack team_id is unique and can't be claimed by two companies; registering a workspace already linked elsewhere is rejected.
• People are mapped, not assumed. A Slack user must resolve to a real user in your tenant (explicit mapping, or a verified email match to a designated user). Unmapped members get a friendly refusal — not a data leak.
• Every event is signature-verified with a replay window, so spoofed webhooks don't get in.

Setup: five steps, one screen

From Administration → Slack Integration → Connect Workspace:

1. Create a Slack app at api.slack.com/apps.
2. Under Event Subscriptions, set the Request URL to https://erp.ledgerq.cloud/api/v1/slack/events/.
3. Subscribe to the bot events app_mention and message.im.
4. Add the OAuth scopes app_mentions:read, chat:write, im:history, im:write, users:read.
5. Install the app, then paste your bot token, signing secret, team ID, and a default user ID into LedgerQ.

Secrets are encrypted at rest, and you can connect more than one workspace. Once it's live, @ledgerq hello in any channel is your smoke test.

The bigger idea

The best finance tooling isn't the one with the most dashboards — it's the one that answers the question at the moment someone asks it, in the place they asked. Your team doesn't want to "go run a report." They want to type a sentence and get the number. @ledgerq puts a BIR-aware, multi-entity, real-time ledger behind that sentence — and keeps every guardrail that makes it safe to do so.

Ask your books anything. They're in the channel now.