Local by default, with a clear data boundary

AAIA separates the local Worker, which processes agreed files, from the hosted AAIA Control Tower (Hub), which dispatches signed jobs and records pilot-scoped run data. The Hub is not the Worker or your accounting system. The standard bank-to-invoice flow keeps full source files on the designated computer; exact metadata and any result fields are agreed before a pilot.

Agree the scope. Run locally. Review the result.

This describes the bank-to-invoice pilot candidate, not a claim that every AAIA workflow is available or customer-accepted.

1

Drop file into inbox

Before a run, the parties agree a suitable bank export and invoice list, designated computer and safe sample-transfer method. Do not email sensitive files.

2

Worker processes locally

The Worker processes the agreed files locally using the matching rules defined for the pilot. Current evaluation is synthetic; customer-format compatibility and acceptance remain open.

3

You review and approve

A person reviews the agreed output and acceptance criteria. No automatic ERP posting or AADE submission is included; downstream actions must be separately scoped.

Clear separation between local and cloud

🔒

Document content is local by default

For the current bank-to-invoice pilot candidate, agreed source files are processed on the designated Worker computer. Full source files are not uploaded to the Hub in the standard flow.

💻

AI processing is local

File processing for the candidate pilot is local. Cloud-model assistance is disabled by default; it is outside the current pilot and cannot be used without separate data scope, purpose, consent and approval.

📡

Job status syncs to hub

The Control Tower records the run status and metadata defined for the pilot. Full document text and transaction rows are not part of the standard Hub sync; any other fields must be explicitly scoped.

✅

You control what gets approved

The pilot agreement identifies any result fields that may be stored in the Hub. Human review is a separate control; it does not by itself define the data boundary.

What crosses the line — and what never does

Your computer

Documents

PDF invoices, bank CSVs, spreadsheets

AI Worker

OCR, extraction, matching — on your machine

Your Dashboard

You review and approve

AuxinVas Cloud

Job Status Only

Run status and only the additional fields agreed for the pilot

Ready to see it in action?

Ask about a scoped walkthrough using synthetic or otherwise approved non-sensitive data. No customer-format run or performance benchmark has been accepted.