Tax & Compliance / Indirect Tax is where ERP discipline either begins or breaks.
Tax Determination by Tax Point Date, Not Entry Date looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Tax is computed at the legally correct historical rate regardless of when the document is keyed; returns reconcile to the rate in force on the tax point date; no retroactive over/under-collection from data-entry lag.
The control flow a finance team actually needs.
Step 1
Tax Point Date Is A Mandatory,...
Step 2
Tax Engine Resolves Rate By...
Step 3
Back-Dated Tax Point Supported Across...
Step 4
Rate-Change Boundary Cases Produce The...
Step 5
Jurisdiction + Rate Version Recorded On...
The ERP surface involved.
Module
Tax & Compliance / Indirect Tax
Actors
AP/AR Clerk, Tax Engine, GL System
Tier
Tier 2
Finance area
Cross-Cutting Edge Cases & Failure Modes
Region lens
US and UK finance teams
Publication date
June 25, 2026
tax point date is a mandatory, separately-captured field distinct from entry date and posting date; tax engine resolves rate by effective-dated rule lookup keyed on tax point date; back-dated tax point supported across rate-change boundaries; rate-change boundary cases produce the historical rate, not the current one; jurisdiction + rate version recorded on the posted tax line; reversal/correction re-resolves at the original tax point date; audit trail cites the rate version applied.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | tax point date is a mandatory, separately-captured field distinct from entry date and posting date | Given a tax rate that changed on a known boundary date, an invoice with a tax_point_date before the boundary, and the invoice entered after the boundary |
| Control 2 | tax engine resolves rate by effective-dated rule lookup keyed on tax point date | when the invoice is posted |
| Control 3 | back-dated tax point supported across rate-change boundaries | then the system applies the historical rate in force on the tax_point_date, not the current rate, and records the jurisdiction + rate version on the tax line |
| Control 4 | rate-change boundary cases produce the historical rate, not the current one | |
| Control 5 | jurisdiction + rate version recorded on the posted tax line | Tax is computed at the legally correct historical rate regardless of when the document is keyed; returns reconcile to the rate in force on the tax point date; no retroactive over/under-collection from data-entry lag. |
| Control 6 | reversal/correction re-resolves at the original tax point date | Tax is computed at the legally correct historical rate regardless of when the document is keyed; returns reconcile to the rate in force on the tax point date; no retroactive over/under-collection from data-entry lag. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | An invoice is entered into the system on a date later than the transaction actually occurred (back-office lag, late vendor bill, period catch-up). The tax engine must apply the rate and rule in force at the **tax point date** (supply date / tax point), not the calendar date of data entry. The system reads the versioned tax configuration effective on the tax point date, computes the correct rate, and posts the tax. If an entry's tax point falls before a rate change but is keyed after it, the historical rate is used and the variance versus the current rate is explainable on audit. |
| Control rules | tax point date is a mandatory, separately-captured field distinct from entry date and posting date; tax engine resolves rate by effective-dated rule lookup keyed on tax point date; back-dated tax point supported across rate-change boundaries; rate-change boundary cases produce the historical rate, not the current one; jurisdiction + rate version recorded on the posted tax line; reversal/correction re-resolves at the original tax point date; audit trail cites the rate version applied. |
| Acceptance proof | |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`tax_line` { id: string, document_id: string, tax_point_date: date, entry_date: date, posting_date: date, jurisdiction_code: string, rate_version_id: string, rate_percent: string, tax_amount_minor: int64, currency_code: char(3), external_id: string }; references `tax_rate_version`; (reference, product may differ).API and events
`POST /v1/invoices` { ..., tax_point_date: date } -> 201 { id, tax_lines: [{ tax_amount_minor, currency_code, jurisdiction_code, rate_version_id, rate_percent }] }; `GET /v1/invoices/{id}/tax-lines`; emits `tax.computed` event with rate_version_id; idempotent via `external_id`.State transitions
`DRAFT -> POSTED`; terminal `VOID`; guard: `POSTED` blocked if tax_point_date is null; reversal re-resolves rate at original tax_point_date, not reversal date.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.