Vajra

Every document.
Every decision.
A clear path to posting.

Connect document intake, validation, human review and your finance-system outcome. Keep the source, decision and downstream status together, in your customer-controlled AWS deployment.

The work behind a posted invoice
01
CaptureInvoice and line-item data
02
CheckSupplier, coding and business rules
03
ReviewExceptions and human approval
PostConfirmed downstream result

When manual finance stops scaling

Less chasing.
More financial clarity.

Growing invoice volumes, multiple entities and more approval paths put pressure on the same finance team. Vajra connects the work around each document so people can focus on the exceptions that need judgement.

Repeated data entry

Capture invoice details once, then carry the record through checks, approval and posting.

Approval bottlenecks

Give reviewers a defined task, the supporting document and a visible workflow state.

Fragmented visibility

Keep entity context, decisions and downstream results together for review and audit.

Growing operating cost

Expand the workflow around volume and complexity, with usage and cloud costs made explicit.

Illustrative finance dashboard with invoice totals, invoice count and sales charts
Finance reporting concept · Illustrative figures, not customer results

Follow the document

The invoice is
only the beginning.

Is the supplier right? Do the lines reconcile? Was the order received? See how the workspace connects those checks to the posting outcome.

Inside Vajra

An inbox that shows what needs attention.

Bring invoices into one queue. See supplier, reference, amount and workflow state before opening the supporting record.

01 / 04
Vajra · product snapshot
Document intake and operational status, together.
Vajra / Capture

Document intake and operational status, together.

Vajra · Invoice review
Vajra invoice review showing the workflow timeline, supplier mapping and verification controls
Keep decisions with the document.

Supplier verification, approval controls and the workflow timeline in the current Vajra workspace.

The workflow in detail

Six steps.
One connected record.

Configure the route to match your entities, documents, approval rules and accounting system.

01Ingest the document

Receive documents through upload or a configured intake channel. Store the source in the customer deployment and create a workflow record.

02Identify and extract

Use Claude through Amazon Bedrock to classify the document and extract the header and line items for the relevant finance workflow.

03Structure the transaction

Prepare the supplier, entity, amounts, tax and line coding needed by the connected accounting system.

04Validate and resolve exceptions

Check required fields and business rules. Bring uncertain mappings and discrepancies to a person for review.

05Route for approval

Apply the agreed approvers and routing rules. Keep the decision, supporting information and timeline together.

06Post and retain the outcome

Send the approved transaction to the authorised finance connection and record the result, including failures or an existing-record match.

One finance workspace

Different documents.
Connected responsibilities.

01

Accounts payable

Capture invoices, resolve exceptions, obtain approval and retain the posting response.

02

Purchase orders & receipts

Connect what was ordered to what arrived, with the source document and timeline.

03

Accounts receivable

Bring customer invoices, approval, posting and payment visibility into the workspace.

04

Employee expenses

Support receipt verification, approval and reimbursement processing.

Who it is for

For finance teams
outgrowing manual work.

Mid-market businesses with increasing document volume, multi-entity responsibilities and a need to keep control of their finance data.

A typical starting point

3–10Business entities
1,000+Invoices per month
5–10Finance team members

Indicative fit from our mid-market focus, including businesses around US$5M–50M in annual revenue. These are conversation starters, not eligibility requirements.

Signals that it is time to look closer

  • Approval chasing and rekeying consume too much of the month.
  • Several entities need consistent workflows and separate accountability.
  • An existing ERP is difficult to adapt, or the team is moving beyond manual processes.
  • Leadership wants control over cloud access, data and integration boundaries.

Your accounting stack

Build around
the systems you use.

Vajra supports connections to Xero, QuickBooks, NetSuite and SAP. Connect your existing accounting environment, or use Vajra as your finance workspace and ledger.

XeroQuickBooksNetSuiteSAPVajra ledger
Choose your starting point
Do we need an existing accounting system?

No. Vajra can serve as your finance workspace and ledger, or connect to the accounting platform you already use. Choose the model that fits your business.

Where does Vajra run?

The deployment is scoped for your AWS environment, including application access, workflow services, document storage and authorised finance-system connections.

How do we start?

Choose a workflow and owner. Bring sample documents, expected volume, approval rules and connected systems so we can define a testable pilot.

How is pricing scoped?

The proposal separates successful workflow usage, AWS cloud cost, deployment, annual maintenance and any custom integrations. We confirm completion rules and service terms with you.

Deployment & security

Your cloud.
Your operating controls.

A customer-deployed architecture on AWS, with access, encryption and connected systems considered as part of the implementation.

Your AWS environment

Application services, document storage and workflow records are deployed into your AWS environment, with authorised connections to your finance systems.

Encryption and access

AWS KMS, IAM and application roles provide the basis for encryption and access controls. Key ownership and permissions are agreed in the deployment design.

Identity and governance

Authentication uses Amazon Cognito. MFA, SSO requirements, finance roles and approval responsibilities are addressed during onboarding.

Operational readiness

Vajra has passed the AWS Foundational Technical Review. Deployment planning also covers monitoring, recovery, maintenance and support responsibilities.

Commercial approach

Pricing that follows the work.

Scope the invoices, entities and approval paths you need. Your proposal separates successful workflow usage, AWS cloud costs, deployment, annual maintenance and custom integration work, so the operating model is clear before you start.

Discuss volume and deployment

Frequently asked questions

A closer look at Vajra.

What is Vajra?

Vajra is an AI-powered finance platform that connects documents, approvals, reconciliation and accounting records. It brings accounts payable, accounts receivable and related finance workflows into one place, reducing manual handoffs and giving teams a clear view of their financial operations.

Do we need an existing accounting system?

No. Vajra can serve as your finance workspace and ledger if you are starting without an accounting platform. If you already have a system in place, Vajra can connect to it and automate the work around it. Choose the approach that fits your business.

Does Vajra support Xero, QuickBooks, NetSuite and SAP?

Yes. Vajra supports connectors to Xero, QuickBooks, NetSuite and SAP, bringing document processing, approvals and accounting workflows together across your finance environment. Your deployment aligns the connections, field mappings and permissions with the way your organisation operates.

Can Vajra support multiple business entities?

Yes. Vajra brings finance workflows across your entities into a shared operating workspace while preserving entity context and responsibility. Configure the approval paths and accounting connections around each business, with visibility for the teams overseeing the group.

How does Vajra handle approvals and exceptions?

Vajra brings the source document, extracted information and validation results together for review. Route work to the right approvers, resolve discrepancies and keep a record of the decision, so people can focus on the transactions that need their judgement.

How do we track a transaction through to completion?

Follow the transaction from intake through validation, approval and its accounting outcome. The workflow history keeps decisions and processing results together, making it easier to review what happened, investigate an exception and complete outstanding work.

Where does Vajra run, and who controls our data?

Vajra runs in your AWS environment, giving your organisation control over data, access and connected systems. Encryption, identity, application roles and operational support form part of the deployment design, aligned with your governance requirements.

How do we get started, and how is pricing structured?

Start with the finance workflow that will make the greatest difference to your team. We work through your documents, volumes, entities and approval needs, whether you are connecting an existing system or adopting Vajra as your ledger. Pricing separates workflow usage, AWS cloud costs, deployment, maintenance and any custom integration work.

Have a question about your setup? Talk to our team.

Behind the name

Why Vajra?

Vajra is the Sanskrit counterpart of the Tibetan word Dorje, associated with the diamond and thunderbolt. For us, it expresses a practical ambition: dependable operations, clear decisions and a durable record of how work gets done.

Make the next step concrete

Bring one workflow.
Test the real exceptions.

We’ll agree the evidence your pilot needs to demonstrate before a wider rollout.