Accounts

WorkSquares Accounts is the financial ledger of record for the suite. It is a true double-entry system: every invoice, bill, payment, expense and adjustment posts through one seam to the general ledger, and every journal it writes balances — debits always equal credits.

Where to start

• Dashboard KPIs — the screen the app opens to: receivables and payables with their aging, cash and bank, income vs expense against the previous period, a 12-month trend and the overdue alerts.
• Receivables & payables — customer invoices and payments (AR), vendor bills and payments (AP), credit notes, vendor credits, retainers and refunds, with the price lists behind a sales line, the branded PDFs these documents render as, recurring invoices and transactions, and the dunning ladder that chases what is overdue.
• General ledger — the chart of accounts, manual and automatic journals, the single posting seam, fiscal-period locks, accounting dimensions and the exchange rates documents are booked at.
• Banking — bank accounts, OFX/QIF statement import with de-duplication, statement matching, automation rules and reconciliation.
• Expenses & purchase orders — record and categorize expenses, and raise purchase orders that convert into bills.
• Reports — trial balance, P&L, balance sheet, general ledger, day book, AR/AP aging, sales and expense analysis, cash flow and budget vs actual, with comparative periods and base-currency reporting. Ten of them export to CSV with ?format=csv; cash flow, the dashboard, budget vs actual, the tax and GST returns and the stock reports are screen and API only.
• Audit trail — an append-only log of who changed what, and when.
• Implementation verdict — an evidence-based comparison against QuickBooks Online and Employment Hero payroll, with the gaps it found and a release recommendation, as audited on 21 July 2026.

The rest of the app

Accounts covers more ground than the pages above:

• Finance operations — budgets on an account × period grid, fixed assets with depreciation runs, FX revaluation of open foreign-currency exposures, and revenue recognition (rules plus per-invoice-line deferral schedules and a posting run) — each with its own screen. Budget activation is routed through the approvals engine, but no budget approval process can be created today, so nothing gates it.
• Platform & settings — Common Masters (eleven typed lookup categories with parent rules, deactivate rather than delete), configurable document numbering, approval processes and workflows, custom fields, validation rules, the forms platform, roles and permissions, notification preferences and the accounting-dimension masters.
• Portal — a read-only, token-scoped view for a contact. The token names one contact and every query is scoped to it, so there is no way to ask for someone else’s documents. The same contact sees its customer side (invoices, statement, invoice PDF) and its vendor side (bills, purchase orders, payments made), and only documents that have actually been issued. There are no write routes. Do not send portal links out yet — the first query the portal runs fails, so every visitor sees an error page; the portal page has the detail.
• Projects & time — hours logged against a project, an unbilled-hours position on the project, and invoicing straight from it.
• Stock — items can carry inventory, with a valuation report that reconciles itself against the inventory accounts in the ledger and tells you when the two disagree.
• Security — how access is enforced, sign-in protection, and the outbound-request and export protections.
• Mobile — an Android app covering the day-to-day document and approval work. It is not at parity with the web app.

Capabilities summary

• One posting seam turns every document flow (AR / AP / payments / expenses / banking) into a balanced journal, all inside the document’s own transaction — a document and its ledger effect commit or roll back together.
• Fiscal periods can be closed per module (GL, AR, AP, banking, expense, fixed assets); posting into a locked period is rejected.
• Accounting dimensions — cost center, department, branch and project — ride onto ledger lines for dimension-filtered reporting.
• Multi-currency documents with exchange rates; India-aware tax (GST components, HSN, place of supply) alongside standard tax codes.
• Every journal line carries a base-currency amount as well as its face amount, so the financial statements report in one currency instead of adding two together.
• One standard list table behind the list screens — column show/hide, reorder, resize, density and an Excel download — remembered per list.
• An audit trail behind the mutating actions — with three named exceptions — and a permission gate in front of every data route.

Works with

Accounts runs in the same workspace (tenant) as the rest of the suite, and that workspace identity is what every product you are enabled for shares. Record sharing does not yet reach the books, so it is worth being plain about where the boundary sits today.

• Its masters are its own. Accounts keeps its own customer, vendor and contact list, and its own items. Pairing those to the CRM and CPQ records is planned, not built — a customer you sell to in CRM is entered again here.
• No sales document flows into this ledger by itself. A CPQ quote, order or invoice stays in CPQ; the AR invoice that reaches the general ledger is the one you raise in Accounts.
• One source of truth — how far record sharing reaches across the suite today, product by product.