Skip to main content
Operate Journal → General Ledger → Financial statements (CF/PL/BS) on Sanka’s accounting stack, giving teams real-time access across entities and departments.

​
Value highlights

  • All accounts, journals, closing in one place: Every journal posts in real time, consolidating subsidiaries and departments.
  • Cash flow visibility and simulation: Combine inflows/outflows with bank balances to see cash positions and forecast liquidity.
  • Balance sheet management: Link sales, inventory, and procurement data so frontline teams can act on balance sheet KPIs.

​
Sanka setup essentials

  • Standardize on Journal Entry plus a chart of accounts with sub-accounts, department, and project dimensions.
  • Align transaction objects (Sales/Procurement/Expense/Payment) to the same accounting properties for CSV/API export.
  • Manage closing with period statuses and lock dates to prevent post-close edits.

​
Operating steps

  1. Master design: Define accounts, sub-accounts, departments, and projects; apply them to transaction objects.
  2. Journal creation: Auto-generate entries from orders/invoices/payments/procurement/expenses; handle fees or differences with adjustment lines.
  3. GL & trial balance: Aggregate journals into the ledger and review balances by period/department/project.
  4. Financial statements: Template PL/BS/CF and keep them live; lock periods at close.
  5. Cash planning: Merge expected inflow/outflow with bank balances to monitor weekly/monthly cash positions.

​
Automation ideas

  • Workflow actions: When closing starts, lock edits on related objects except for approved exceptions.
  • Record actions: Alert on abnormal balances (for example, negative inventory or unmatched postings).
  • Object actions: On bank import, generate journal candidates and queue them for review.

​
Reporting and oversight

  • Dashboards for department PL, cash flow statements, and balance sheets.
  • Year-over-year and month-over-month variance widgets for leadership reviews.