This example represents the control path for determining and reporting VAT on a cross-border supply. It connects the commercial facts—supplier and customer status, goods or services, establishments, movement, consideration, and invoice jurisdiction—to the resulting place-of-supply analysis, rate or relief, invoicing, ledger posting, return disclosure, and input-tax recovery position.

The workflow starts with transaction intake because VAT treatment cannot be selected reliably from an invoice label alone. The relevant parties, movement or performance facts, jurisdictions, and period are captured before the supply is classified. Classification distinguishes goods from services, considers customer status and establishment, and handles composite supplies, chains, and intermediaries. Incorrect or incomplete facts return to intake. The tax-treatment review then applies the controlling jurisdictional rules to decide whether the supply is taxable, exempt, zero-rated, or subject to reverse charge, and verifies identifiers and transport or other supporting evidence.

An approved treatment moves to invoicing and the ledger, where mandated statements and tax fields are produced, output and recoverable input VAT are posted, and evidence is linked to the entry. Reporting assigns the transaction to the correct jurisdictional return fields and supplementary reports and reconciles invoice, ledger, and transport records. Conflicts in either posting or reporting open a treatment exception. A repair may correct the invoice or posting and return to that stage, or may require a fresh treatment analysis. Closure records the submitted treatment and recoverability outcome only after reporting is complete.

These controls matter because the same commercial supply can produce different VAT consequences when customer status, establishment, movement, evidence, or the rule period changes. A missing identifier or transport document may defeat a relief even when the commercial facts otherwise support it. Connecting the rule path to invoice, ledger, return, and evidence reduces inconsistent treatments, blocked recovery, duplicate taxation, and amendments that cannot be explained to auditors or authorities.

This example represents preparation of a research-credit claim in which qualification, cost capture, calculation, and substantiation remain tied together. It is organized around projects, activities, entities, and tax periods because a general statement that a company performs innovative work is not enough. The claim must show which work was evaluated, which qualifying conditions were met, which expenditures relate to that work, and what evidence supports those conclusions.

The cycle starts with a project inventory. Candidate projects are associated with technical objectives and responsible substantiation owners. Activity qualification then maps the actual work to each applicable condition, separates routine or excluded activity, and records the technological uncertainty and process of experimentation. An incomplete inventory loops back for correction before costs are classified, preventing payroll or contractor amounts from driving qualification after the fact.

Cost classification associates wages, supplies, and contracted research with qualified activities, applies allocation and related-party rules, and removes amounts outside the qualifying period. The claim calculation aggregates those costs using the selected method and applicable limitations, then reconciles the result to return workpapers. Substantiation review samples costs back to project evidence, checks that the correct rule and period assumptions were used, and resolves unsupported amounts. A finding opens a claim exception with a named owner and explicit treatment. Depending on the gap, remediation returns to activity qualification or cost classification; changed amounts are recalculated before approval. Finalization occurs only when the supported amount and disclosures are approved and the evidence trail is archived.

The controls matter because research-credit exposure usually arises at the seams: a technically credible project with weak contemporaneous evidence, an eligible activity with an unsupported allocation, or a correct calculation built from an overstated cost pool. Keeping every amount connected to qualification and evidence supports review, reduces inconsistent treatment across business units, and makes exclusions and revisions as traceable as the claimed benefit.

This example represents the operating cycle a tax department uses to decide where a business has a sales-tax obligation and then carry that decision through registration, collection, return preparation, and period close. It is deliberately jurisdiction- and period-aware: a threshold, exclusion, marketplace-facilitator provision, or product treatment may be correct in one state and filing period but wrong in another.

The workflow begins with activity monitoring. Direct and marketplace sales, transaction counts, and physical-presence events are accumulated by jurisdiction and effective period. A nexus review applies the relevant definition and threshold rather than treating a national sales total as the deciding fact. Activity below the applicable threshold returns to monitoring; established nexus moves into registration. Registration status and effective dates then govern when collection can be activated. Once collection is active, the tax engine’s rates and product mappings, exemption certificates, and collected-tax totals must stay aligned with the approved posture.

At filing time, transaction sources and collected tax are reconciled, adjustments and exemptions are assigned to the correct return lines, and the return and remittance are prepared. Missing transaction data, a rejected return, or a payment variance opens a filing exception instead of being hidden in the close process. A repair may return the case to filing preparation, while evidence that the underlying activity was classified incorrectly sends it back to activity monitoring and nexus analysis. The period closes only after acceptance and remittance reconciliation, with the jurisdictional posture carried into the next monitoring period.

These controls matter because nexus and collection failures can create uncollected liabilities, customer overcharges, late registrations, penalties, and inconsistent positions across jurisdictions. The model keeps the rule version, activity facts, exemption support, return treatment, and remediation path connected so reviewers can reproduce why the business registered, collected, filed, amended, or remained below threshold.