Financial Verification & QA Checklists

To maintain high financial audit standards, Business M features structured Sanity and Smoke Verification Checklists. These checklists serve as operational QA scripts for business administrators, testers, and compliance officers validating accounting transactions in the Desk UI workspace.

---

1. Payment Entry Workspace Verification

Scope: Validating the payment entry engine, statutory tax deductions (TDS), and ledger settlements.

1.1 Preconditions

• The Business M backend is active with a production-ready PostgreSQL connection.
• The active user has Accounting Manager permissions.
• Voucher Types and active Cost Centers are pre-configured.

1.2 Step-by-Step QA Checklist

• [ ] Workspace Navigation & Load
  • Navigate to /finance/workspace/payment-entry.
  • Verify that the workspace shell renders instantly with zero console or network errors.
• [ ] Header Context & Adapter Strip
  • Confirm the Payment Entry title, audit breadcrumbs, and active adapter status strips are visible.
  • Verify the status text dynamically reacts to settlement references and tax deduction (TDS) variables.
• [ ] Form Field Grouping & Sequencing
  • Confirm form fields are organized into logical sections: Settlement Party, Settlement Details, Statutory Deductions, and Disbursement Summary.
• [ ] Outstanding Grid Skeletal Integrity
  • Open the settlement allocation grid.
  • Confirm the following columns render correctly: Outstanding Amount, Current Settlement, Net Disbursed, and Deduction Amount.
• [ ] Summary Panel Recomputation
  • Input test settlement figures.
  • Verify that Outstanding, Settlement, Net Disbursed, and Tax indicator summaries recalculate instantly.
• [ ] Action Bar Verification
  • Verify that context-action buttons render and react dynamically: Match Open Items, Validate Tax Deductions, and Recompute Net Disbursed.
• [ ] Framework Form Save & Submit Flow
  • Click Save and verify that the transaction commits to the PostgreSQL backend database with a secure, framework-generated hash.

---

2. Purchase Invoice (Accounts Payable) Verification

Scope: Validating vendor billing, expense distribution, and multi-cost center tax ledgering.

2.1 Preconditions

• Suppliers and active Items are pre-registered in the WMS catalog.
• Tax rates (GST/Local Tax) are configured in the tax masters.

2.2 Step-by-Step QA Checklist

• [ ] Purchase Invoice Workspace Load
  • Open /finance/workspace/purchase-invoice.
  • Verify the grid listing displays existing unpaid vendor bills.
• [ ] Form Hierarchy Validation
  • Click New Purchase Invoice.
  • Confirm the fields display in correct group zones: Vendor Details, Item Grid, Tax Allocations, Expense Cost Centers, and Total Payable Summary.
• [ ] Multi-Item Calculations
  • Add 3 items with distinct tax rates.
  • Confirm that row-level and total-level tax totals (CGST, SGST, IGST) auto-calculate accurately.
• [ ] Cost Center Expense Splitting
  • Confirm that expenses can be partitioned across different cost center tags.
  • Verify that the system registers corresponding split debits on the Expense ledger.
• [ ] Workflow Submission Lock
  • Click Submit.
  • Confirm that once submitted, the invoice enters a read-only lock state, preventing subsequent modifications to preserve audit integrity.

---

3. Sales Invoice (Accounts Receivable) Verification

Scope: Validating customer invoicing, credit limits, and immediate ledger projections.

3.1 Preconditions

• Customers and active Price Lists are pre-registered.
• Row-Level Security (RLS) policies are active for the user’s division.

3.2 Step-by-Step QA Checklist

• [ ] Sales Invoice Workspace Load
  • Navigate to /finance/workspace/sales-invoice.
  • Confirm existing invoice collections and outstanding balances render.
• [ ] Customer Profile Auto-Fill
  • Select a customer from the search drop-down.
  • Verify that customer billing addresses, payment terms, and outstanding credit limits load automatically.
• [ ] Dynamic Pricing Verification
  • Select an Item in the sales grid.
  • Verify the item price matches the active customer price list.
• [ ] Credit Threshold Warnings
  • Attempt to create an invoice that exceeds the customer’s maximum credit limit.
  • Confirm that the Desk UI issues a hard block or a manager authorization requirement.
• [ ] Immediate General Ledger Posting
  • Submit the sales invoice.
  • Open the General Ledger report for the customer.
  • Confirm that Accounts Receivable has debited and Sales Revenue has credited by the exact invoice amount within the same calendar second.