Alongside the core financial statements (Profit & Loss, Balance Sheet, Cash Flow, Trial Balance, General Ledger, Tax), AccountDesq has eleven more focused reports. Each one answers one real question - who to chase for collections, what’s actually being bought, which customers are worth the most. Two things are worth knowing before you read any of them: what population of records they include, and where a score or grade on the page actually comes from.
The core financial statements
Six reports form the audited backbone every accountant expects, all sharing one export engine (PDF/Excel/CSV, with your workspace letterhead) so the numbers you print always match what the screen shows.
Balance Sheet
What the business owns, owes, and is worth, as of a specific date - laid out as a single formal statement. Every account-level line drills straight into that account’s own register, so "why is this number what it is" is always one click away, not a separate report.
Cash Flow (indirect method)
Built the standard indirect way - starting from net income and adjusting for non-cash items and working-capital changes - and it provably reconciles against the actual change in cash for the period, not an approximation. If it doesn’t reconcile, that’s treated as a real double-entry problem worth investigating, not rounding noise.
Trial Balance
Every account with its debit or credit balance, side by side. Total debits equal total credits by double-entry construction - if they ever didn’t, that would mean a posting bug, not a business event, since AccountDesq’s ledger simply cannot post an unbalanced entry.
General Ledger
A directory over every account, grouped by type, showing which ones actually have activity - purely a jumping-off point. Opening an account takes you to its full register (the same drill-down every other statement links into), where the real transaction-level detail lives.
Tax
Four tabs - Summary, Register, Liability, Reconciliation - deliberately country-agnostic rather than a clone of any one regime’s return form, since the underlying Tax Engine itself is built to work across tax systems. For India specifically, the export menu also offers GSTR-1 and GSTR-3B shaped exports without the on-screen report itself being GST-specific.
Journal Report - everything, traced back to source
Every journal entry the system has ever posted, both sides together, with no status filter - this is the raw ledger, not a business-status view of it. Filter by date, source document type, or entry kind, search by entry number or account, and every entry links back to the document that caused it. If a number anywhere else in AccountDesq looks wrong, this is where you go to see exactly what actually posted.
Sales Register
Every invoice you’ve ever created, regardless of status, annotated with the same customer health, priority, and next-best-action signals Receivables Intelligence shows - deliberately kept in sync rather than risk disagreeing with it. Margin is estimated using today’s item cost and computed only for the rows on the current page, so it stays fast no matter how large your catalog is. There’s no salesperson or branch column - AccountDesq doesn’t model a sales-rep field, so "Owner" shows who actually created the invoice instead of inventing one.
Procurement Register
The purchasing equivalent of Sales Register, but built on Bills rather than Purchase Orders - a PO is a commitment, not yet a financial event, so it’s intentionally excluded. Every bill regardless of status is included, with the same vendor health grading Payables Intelligence uses. There’s no branch or cost-center breakdown in this schema; "Created By" shows the real person who entered it instead.
Collections
A working queue for whoever chases payment, not a static report - built directly on Receivables Intelligence’s own numbers so it can’t disagree with them. Shows who to contact today, why, and the expected recovery, plus how effective recent collection efforts have been. It’s honest about what it can’t show: there’s no payment-gateway integration, so "failed payments" doesn’t exist as a real concept here, and there’s no collector-assignment feature, so it isn’t pretended into existence.
Cash Outflow
A treasury view of vendor payments - what’s gone out, what’s pending, what’s coming. Its KPIs and forecast are pulled directly from Payables Intelligence rather than recalculated, so the two can never quietly drift apart.
Customer Financial Profile
Pick a customer from the ranked landing list (the same ranking Receivables already produces) to open their full relationship: health score and grade, payment-speed trend, credit wallet, open invoices with a journal drill-down on each, and one prioritized recommended next action - all computed by wrapping Receivables Intelligence’s own per-customer detail rather than a second calculation.
Customer Profitability
Ranks customers by more than revenue - margin, lifetime value, growth, payment speed, and risk together, with filters like "top margin," "highest risk," or "dormant." Revenue is trailing-12-month billed invoices; margin is an estimate using each item’s current buy price, since AccountDesq doesn’t keep a historical cost snapshot per invoice line - a customer’s margin can shift slightly if item costs change, even with no new sales.
Item Performance
Sales by item - quantity, revenue, estimated margin, estimated returns, and growth - built only from issued invoices (drafts and voids excluded). "Estimated returns" is a genuine estimate: a credit note only references the invoice it corrects, not a specific line, so its value is split proportionally across that invoice’s lines and summed by item.
Item Purchasing
The purchasing mirror of Item Performance - what you’re buying, from how many vendors, and at what average cost, built from non-draft, non-void bills. Deliberately has no price-trend column: knowing whether a cost is rising over time needs multi-period history this report doesn’t track, so it shows a same-book snapshot rather than a guess.
Vendor Performance
Who you buy from, how much, and how reliably - spend, bill count, outstanding balance, average payment days, and health grade per vendor. It reuses the exact same per-bill data Procurement Register already assembled rather than querying again, so the two views can never disagree.
Vendor Profile
The vendor-side counterpart to Customer Financial Profile - pick a vendor from the Payables-ranked list to see lifetime spend, outstanding balance, credit wallet, open bills with journal drill-down, and relationship health, wrapping Payables Intelligence’s own detail rather than recalculating it. It shows Credit Activity rather than a fabricated "Debit Notes" section, and a credit wallet balance rather than a "credit limit," since Vendors have no such field to begin with.
Why do two reports sometimes show different totals for what looks like the same thing?
Usually by design, not by error - some reports (like Sales Register or Procurement Register) include every invoice or bill regardless of status, while others quietly exclude drafts and voids. Before assuming a discrepancy is a bug, check whether the two reports actually share the same inclusion rules.
Where do margin figures in reports actually come from?
Margin figures across every report use today’s current cost, not a historical snapshot from when the sale actually happened - they’re a live estimate, not a point-in-time record. Keep that in mind when comparing margin on an old sale to its original economics.
Which report is the single source of truth if numbers ever look wrong?
The Journal Report - every other report’s numbers trace back to it, since it’s the one true record of every posting in the system. If a number elsewhere looks off, the Journal Report is where to verify what actually posted.
Resources
Was this guide helpful?