Skip to content
The H6 Policy Engine

Turn finance rules into executable policy.

H6 captures how your organisation makes financial decisions and turns that knowledge into approved policies that govern every invoice—consistently, traceably and across your existing systems.

AI assists with authoring. Your team approves. H6 executes deterministically.
Explore H6 PoliciesRequest a Demo
Why policies

Finance knowledge should not live in inboxes and memory.

Approval thresholds, vendor terms, posting logic and commercial controls are often scattered across people, spreadsheets, contracts and ERP configurations. That makes the same decision difficult to apply consistently—and even harder to prove later.

01

Knowledge is fragmented

Finance rules sit across teams and systems instead of one governed source.

02

Decisions vary

The same invoice can be handled differently depending on who reviews it.

03

Control is difficult to prove

Workflows show where an invoice went, but not always why the outcome was correct.

Governed transaction lifecycle

From invoice document to governed approval.

Every policy in this flow has already been reviewed, approved, compiled and activated. H6 then applies the active versions at each stage and preserves the complete decision trace.

  1. 01

    Invoice Document

    Received by email, cloud storage, API or a connected finance system.

  2. 02

    Party Lookup & Data Capture

    Resolve the supplier and legal entity, then capture the invoice facts with their source and confidence.

    Party Lookup policyData Capture policy
  3. 03

    Match

    Compare invoice lines with purchase orders, receipts and supporting records.

    Matching policy
  4. 04

    Categorize

    Assign the correct entity, department, account, tax code and cost centre.

    Classification policy
  5. 05

    Validate

    Apply duplicate, date, price, tax, posting and required-field controls.

    Validation policy
  6. 06Governed outcome
    Policies passed

    Ready for Approval

    The governed sign-off path can continue with the full policy record attached.

    Approval policy
    Exception found

    Human Review

    The right reviewer receives the reason, context and controlling policy version.

The H6 difference

Generation and execution are deliberately separated.

AI can help structure policy logic and identify what still needs a human decision. Runtime execution uses only the approved version, producing repeatable outcomes with a clear audit trail.

01

Authoring layer

AI-assisted policy authoring

  • Structure operational knowledge
  • Identify ambiguity and missing choices
  • Prepare logic for human review
Approved artifactPolicy v4.8Immutable while active
Approved
02

Runtime layer

Deterministic execution

  • Use captured and retrieved facts
  • Execute approved conditions and actions
  • Record every input, version and outcome
Policy families

Policies for every repeat finance decision.

Each policy governs one part of the invoice journey. Together, they create a controlled path from document capture to an approved ERP outcome.

01

Data Capture

Capture invoice dates, totals, tax, currency and line-level facts.

02

Party Lookup

Resolve supplier and legal-entity identities against approved master data.

03

Classification

Assign the correct entity, department, account, tax code and cost centre.

04

Validation

Check price, dates, duplicates, tax and required fields before approval.

05

Matching

Match invoices against purchase orders, receipts and supporting records.

06

Approval

Apply thresholds, ownership and exception routing consistently.

07

Posting

Validate coding, entity and posting period before sending data to the ERP.

08Coming soon

Budget

Check committed and available spend before an invoice is approved.

09Coming soon

Vendor Reconciliation

Match statements to invoices, credits and payments with clear exceptions.

Governed execution

One invoice. One policy version. One traceable outcome.

H6 keeps captured facts, policy results and business choices distinct—so finance can see what happened, why it happened and which approved policy controlled the result.

Provable control

AI can suggest. H6 can prove.

Decision layerGeneric AP automationH6 Policy Engine
Runtime decision

Probabilistic suggestion

Approved deterministic policy

Control

Embedded in workflows and people

Versioned executable artifact

Activation

Logic can change without clear ownership

Human approval recorded before activation

Exceptions

Generic queue for manual review

Reason, context and policy version attached

  • Human-approved activation
  • Versioned policy artifacts
  • Complete decision provenance
  • Explicit exception routing
Let's get started

Ready to Turn Finance Decisions Into Governed Policies?

See how H6 fits into your finance stack and brings provable control to validation, matching, classification, approvals, posting and exceptions without replacing your existing systems.

Request a Demo