Supply WeaveDocumentation
Product guidesAccounting
Supply Weave
DocsAccountingAccounting Readiness

Accounting Readiness

Purpose

Accounting Setup -> Readiness (/accounting) helps an ADMIN find accounting configuration, classification, calendar, and posted-ledger integrity issues. The dashboard computes its result from current data each time it is loaded or refreshed; Readiness is not a saved approval record.

Readiness tells you where to investigate. It does not determine whether source documents are complete, replace report reconciliation, or certify the accounts.

Status Meanings

Status Meaning Operator response
PASS The specific automated check found no issue in the data it evaluates. Verify supporting reports and evidence; do not treat it as professional approval.
WARNING Setup may be incomplete or reports may be incomplete, but the condition is not treated as a blocker by that check. Investigate, document the reason, and correct it when applicable.
BLOCKER The check found a material setup or integrity condition requiring correction. Open Review details, investigate affected records, and resolve the applicable issue.

The overall status is the highest severity present: any BLOCKER produces overall BLOCKER; otherwise any WARNING produces overall WARNING; otherwise the result is PASS. The page also shows passing, warning, and blocker counts, an as-of date, and the generated time.

The normal opening-balance check is a WARNING when no authoritative import has been posted. A duplicated or invalidly linked active opening import is a BLOCKER.

Global Diagnostic Versus Contextual Blocking

This distinction is important:

  • The Readiness page is a global diagnostic of current accounting setup and ledger integrity.
  • Its overall BLOCKER status does not automatically disable every accounting or operational action.
  • Ordinary operational posting still applies its own validation and posting-date period lock.
  • Ordinary monthly period close is not automatically blocked by the global Readiness status.
  • Opening-balance posting recalculates the blocker set relevant to that proposed import inside the same transaction as the posting attempt.
  • Fiscal-year close recalculates its own relevant blocker set and year-specific accounting controls inside the close transaction.
  • A contextual action can therefore reject for applicable blockers without using every global finding, and a global finding must not be dismissed merely because a different action remains available.

Readiness is advisory for review and selectively reusable by controlled workflows; it is not a single master on/off switch.

The 16 Checks

The dashboard returns these checks in a stable order:

  1. Accounting settings configured: confirms that the application’s Accounting Settings record exists with valid BDT reporting defaults.
  2. Financial year exists: confirms that at least one fiscal year is configured.
  3. Current period exists and is open: evaluates the period containing the current UTC date. This does not mean another posting date is invalid; each posting is checked against its own period.
  4. Fiscal calendar has no gaps or overlaps: checks complete, contiguous fiscal years and their 12 periods.
  5. Retained-earnings account configured: requires an active EQUITY leaf with effective Equity balance-sheet classification.
  6. Required system accounts exist: checks all required seeded account codes.
  7. Required system accounts are active leaves: also checks each account’s expected type.
  8. Active Revenue and Expense accounts have P&L sections: checks accounts that have ever had posting activity and accepts a section set directly or inherited from a parent.
  9. Balance-sheet accounts with balances are classified: checks Asset, Liability, and Equity balances through the current UTC date for a section set directly or inherited from a parent.
  10. Cash and bank accounts are classified: requires Petty Cash and every liquidity-facing transaction account to be an active ASSET leaf classified as CASH or BANK and effectively classified as Current Asset.
  11. No postings exist directly on parent accounts: all postings should use leaf accounts.
  12. Opening balances posted: expects exactly one healthy active opening import linked to its opening journal; no posted import is normally a warning.
  13. System journals balance: checks every system journal for at least two lines, nonzero content, and exact equal debits and credits.
  14. Manual journals balance: checks every manual journal in source currency for at least two lines, nonzero content, and exact equal debits and credits.
  15. Combined Trial Balance balances: checks the combined BDT ledger used by reports, including system and manual postings, without rounding through normal spreadsheet-style arithmetic.
  16. No postings exist outside configured periods: confirms every posting date belongs to the accounting period stored on that posting.

Original reversed entries and their compensating entries both remain in the canonical posting stream. Readiness does not hide the original merely because it has been reversed.

How To Review A Finding

  1. Refresh Readiness after relevant setup or posting changes.
  2. Read the check title and full explanation.
  3. Record the status, affected count, and any listed account codes.
  4. Use Review details to open Accounting Settings, Fiscal Periods, Chart of Accounts, Opening Balances, system journals, or manual journals.
  5. Confirm the accounting correction with the finance owner or CA when it involves classification, balances, or journal treatment.
  6. Make the approved correction in the source configuration or through the proper accounting workflow. Do not edit exported reports as a substitute.
  7. Refresh Readiness and rerun the affected reports.
  8. Retain before-and-after evidence for material corrections.

Printable Readiness Checklist

  • The dashboard was refreshed after the latest setup and posting changes.
  • The generated time and UTC as-of date were recorded.
  • The overall status and PASS/WARNING/BLOCKER counts were recorded.
  • Every non-passing check was read individually.
  • Affected account codes and correction targets were reviewed.
  • Account hierarchy, P&L sections, balance-sheet sections, and CASH/BANK rules were checked against Chart of Accounts.
  • The configured start month, retained earnings, and reporting defaults were checked against Accounting Settings.
  • Fiscal-year and period findings were checked against Fiscal Years and Periods.
  • Opening-balance findings were checked against Opening Balances and the Opening-Balance Import Guide.
  • Journal or Trial Balance integrity findings were escalated rather than bypassed.
  • Relevant financial reports and ledgers were rerun after corrections.
  • Global diagnostic findings were not confused with a workflow’s contextual blocker calculation.
  • The finance owner or CA reviewed unresolved accounting judgments.

Verification

A setup review is complete only when:

  1. Readiness reflects the expected status after refresh.
  2. Each non-passing item has an owner, explanation, and resolution or approved follow-up.
  3. The Trial Balance independently reconciles and unresolved accounts are investigated.
  4. Profit & Loss, Statement of Financial Position, Receipt & Payment, and relevant General Ledgers are reviewed for completeness and classification.
  5. Opening-balance and fiscal-year-close actions, when applicable, pass their own contextual checks at transaction time.
  6. Supporting source documents, mappings, reconciliations, approvals, and CA workpapers are retained outside the Readiness dashboard.

Common Mistakes

  • Looking only at the overall badge and ignoring individual checks.
  • Treating PASS as proof that all source documents and adjustments are complete.
  • Treating any global BLOCKER as a universal system lock.
  • Ignoring a global blocker because ordinary posting or monthly close remains available.
  • Assuming Current period exists and is open decides every posting date. Historical and future dates are checked against their own periods.
  • Creating a journal only to force a check to pass without approved accounting support.
  • Deleting, repurposing, or deactivating historical accounts to hide findings.
  • Classifying receivables or other current assets as CASH or BANK merely to remove a liquidity blocker.
  • Assuming a reversed journal disappears from accounting history.
  • Editing a CSV or PDF report and treating the edit as a ledger correction.

Responsibility Boundaries

Supply Weave checks system configuration, classifications, calendars, required accounts, posting attribution, and posted-ledger integrity. The business and its CA remain responsible for source-document completeness, tax and VAT, depreciation, accruals and provisions, audit procedures, statutory disclosures, filing, and the professional interpretation of balances. CA-approved adjustments must be posted through journals before they appear in reports.

Return to the Accounting User Guides index.

Reviewed against the application on: 2026-08-21