Flow 44 — Statutory tax and localisation controls
Version one legal entity and jurisdiction's registration, fiscal/localisation policy, effective tax rules and statutory document-series constraints, then activate them through independent Finance approval.
Overview
Flow 44 is configuration authority only. It creates no invoice, credit/debit note, document number, tax calculation, journal, return, filing, payment, exchange rate, inventory valuation, demand, receipt, custody, current-stock or stock-ledger fact.
Tax Accountant author/submitter → different Finance Controller approver or retire authority → Compliance Manager / Project / Accountable Executive / Auditor read-only reconciliation
Process
- 1Pin legal and site identity
Bind one legal entity, country, jurisdiction, registration and classification to an assigned accountable site.
Identity only · no transaction - 2Freeze localisation policy
Record base currency, locale, timezone, fiscal start, tax point and exact rounding controls.
Immutable DRAFT - 3Compose effective tax rules
Reconcile each total percentage to named components and exact authority references inside the profile period.
No tax calculated - 4Define series constraints
Retain document type, series shape, reset and length policy without allocating or issuing a number.
No document issued - 5Approve independently
A different Finance Controller approves or rejects the exact submitted checksum and CLEAN evidence.
ACTIVE configuration only - 6Read and retire safelyREAD ONLY
Scoped readers reconcile full history; an independent controller may retire the active definition without deleting it.
Zero posting authority
Role handoff
Tax Accountant author/submitter → different Finance Controller approver or retire authority → Compliance Manager / Project / Accountable Executive / Auditor read-only reconciliation
Detailed reference chapters
Detailed steps
- 1
Open Finance → Statutory tax & localisation with finance_localisation:write. Select an assigned site and enter the legal entity, country/jurisdiction, registration and authority reference from current official evidence.
- 2
Set the company-approved base/functional currency and locale plus timezone, fiscal-year start, tax-point basis, price-inclusion, rounding level/rule/precision, place-of-supply and reverse-charge policy. For India GST, verify Asia/Kolkata, 1 April and the GSTIN's two-digit state prefix; INR is an editable default, not an inferred functional-currency conclusion.
- 3
Add effective tax rules. Ensure each named component equals the total and zero-rated, exempt or out-of-scope rules total zero; keep every rule date inside the profile period.
- 4
Add unique document-series policies. For India GST tax invoices, credit notes and debit notes, use financial-year reset and ensure the composed prefix/separator/digits fit the 16-character maximum. This does not allocate a sequence number.
- 5
Attach same-site CLEAN evidence, save and submit the immutable version as its Tax Accountant author. As a different Finance Controller, compare the checksum and approve or reject with decision evidence; approval requires today's date inside the version effectivity.
- 6
As Auditor, reconcile rejected, approved, superseded or retired versions and their named actors. Prove outside-site denial and compare stock, ledger, Programme, Supply, receipt, notification and Finance-transaction witnesses; only expected audit/outbox configuration facts may change.
Field-by-field practice data
Reject version 1, approve corrected version 2 and reconcile one India GST statutory/localisation profile without creating any Finance transaction. The page shows sample set A; the workbook includes independent A, B and C values.
Field names match the current application labels. Select existing approved records where shown, leave optional values blank unless they genuinely apply, and never copy fictitious TRAIN values into live work.
Create the statutory draft
Select the assigned training site and enter the verified legal, registration, fiscal/localisation and authority data. Save immutable version 1 with CLEAN evidence.
| Exact field name | Requirement | Sample value A | How to use it |
|---|---|---|---|
| Legal entity code | Required | TRAIN-A-INDIA-OPS | Use a fictitious stable training identity. |
| Country code | Required | IN | Use the ISO country code. |
| Tax jurisdiction code | Required | 29 | For India GST, the two-digit jurisdiction must agree with the verified GSTIN prefix. |
| Registration type | Required | GSTIN | Use the authority's exact registration type. |
| Registration number | Select existing | Use authorised training GSTIN | Never place a real or invented production registration in generic practice data. |
| Base currency | Required | INR | Use the bounded India profile currency. |
| Locale | Required | en-IN | Use the intended BCP 47 presentation locale. |
| IANA timezone | Required | Asia/Kolkata | Use the bounded India profile timezone. |
| Fiscal start month | Required | 4 | Retain the legal fiscal boundary. |
| Fiscal start day | Required | 1 | Retain the legal fiscal boundary. |
| Profile authority reference | Required | TRAIN-A-GST-AUTH-001 | Identify the exact controlled authority source. |
Expected result: One DRAFT profile version has a stable checksum; no tax calculation, invoice, document number, journal, return, filing, payment or exchange rate exists.
Add tax and series policy
Add one local standard-rate rule with reconciling components and one financial-year invoice-series policy.
| Exact field name | Requirement | Sample value A | How to use it |
|---|---|---|---|
| Rule code | Required | GST-LOCAL-18 | Use a stable company rule code. |
| Total rate % | Required | 18.000000 | The named components must sum exactly to this total. |
| Component code | Required | CGST | Retain the independently stated component code. |
| Component name | Required | Central GST | Use the recognised component name. |
| Rate % | Required | 9.000000 | Add the SGST component separately so both components total 18. |
| Supply type | Required | GOODS | Configuration describes an eligible supply family; Flow 45 still requires explicit transaction selection. |
| Collection | Required | NORMAL | Only explicit NORMAL supplier purchase rules are consumed by Flow 45; reverse charge and withholding remain separate. |
| Document type | Required | TAX_INVOICE | Describe issuance constraints only; do not issue a document. |
| Series code | Required | INV | Use a unique code for the document type. |
| Prefix | Required | INV | Keep the composed maximum length within the configured limit. |
| Minimum digits | Required | 6 | Reserve sufficient sequence width without allocating a number. |
| Reset period | Required | FINANCIAL_YEAR | Use the bounded India GST reset rule. |
| Maximum length | Required | 16 | The composed series policy must fit this maximum. |
Expected result: The rule and series become version-owned immutable configuration; no transaction consumes them.
Submit and reject version 1
Submit the exact checksum, then reject it with controlled decision evidence to exercise the retained correction path.
| Exact field name | Requirement | Sample value A | How to use it |
|---|---|---|---|
| Submission note | Required | Training A version 1 submitted for independent statutory review. | The author submits their own version. |
| Decision | Required | REJECT | Use a different named Finance Controller. |
| Decision note | Required | Training A authority reference needs correction before activation. | Explain the evidence-based rejection. |
Expected result: Version 1 is REJECTED and immutable; no active version or transactional side effect exists.
Replace and approve version 2
Create corrected version 2, submit it and approve it while its effective period includes today.
| Exact field name | Requirement | Sample value A | How to use it |
|---|---|---|---|
| Current draft | Read only | v2 · Draft | A correction is a new immutable version. |
| Effective from | Required | Current financial-year start | Approval activates immediately; future scheduling is outside this flow. |
| Effective to | Optional | Current financial-year end | Keep the rule/profile effective today for immediate approval. |
| Decision | Required | APPROVE | The controller must differ from the author/submitter. |
| Decision note | Required | Training A registration, rule components, series policy and evidence verified. | Record the exact controller basis. |
Expected result: Version 2 is the sole ACTIVE definition and version 1 remains retained.
Reconcile authority isolation
Review both versions, checksums, evidence and named actors; retry outside the assigned site and compare operational witnesses.
| Exact field name | Requirement | Sample value A | How to use it |
|---|---|---|---|
| Active version | Read only | 2 · APPROVED | Confirm one exact active pointer. |
| Current draft | Read only | v1 · Rejected retained in history | Confirm rejected evidence was not edited or deleted. |
| Attributable note | Read only | Training A zero-authority witness reconciled outside this read-only register. | Compare stock, ledger, demand, procurement, receipts, invoices and journals in the disposable fixture. |
Expected result: Outside-site access fails and only expected audit/outbox configuration facts increase; all operational and Finance-transaction witnesses remain zero.
End state
One site-bound legal/jurisdiction profile becomes an exact, evidence-backed active configuration through maker-checker control while every tax transaction, statutory issuance, filing and accounting authority remains absent.