AAIA: a clearer view of bank movements and invoices

Evaluate bank-to-invoice matching.
Local processing, human review.

We are testing a supervised way to compare an agreed bank file with an invoice list and highlight suggestions for your review. The evidence so far uses synthetic data; customer formats have not yet been accepted. Processing takes place on a designated computer, and any information sent to the Hub is agreed before a pilot.

A scoped pilot candidate for bank-to-invoice matching

The pilot will test whether agreed bank and invoice files can be matched reliably enough to reduce manual review. No customer-format result or time saving has been measured yet.

1

Today: line by line

Download the bank CSV, open the invoice file in Excel and compare amounts and names one payment at a time. Mistakes show up late, at closing.

2

With AAIA: candidate matches for your review

The candidate matching rules and supported file formats are agreed from a suitable sample. Ambiguous cases must be flagged for human review; customer-format behaviour has not yet been accepted.

3

You: approve the exceptions

The pilot defines a reviewable output and acceptance criteria before a customer run. No ERP posting or AADE submission is included in the current scope.

Illustrative review output

The output format and categories will be defined and tested against the agreed sample; the items below are possible review categories, not a customer-accepted deliverable.

📊

Summary

Counts and open items, if included in the agreed output.

✅

Matched

Candidate match and supporting criteria for review, if accepted in the pilot schema.

🔎

Payments without invoice

Unmatched payments are flagged for investigation; the system does not make an accounting classification decision.

💶

Receipts without invoice

An example review category; inclusion and fields depend on the agreed pilot output.

📌

Invoices without payment

An example review category; inclusion and fields depend on the agreed pilot output.

From agreed files to a result you review

First we agree the files, the scope and the information needed for supervision. The local worker processes the files on the designated computer; the Control Tower coordinates the authorised run. You review the result before using it.

1

1. Agree and start

An authorized user dispatches a signed job from the AAIA Control Tower (Hub). Pilot requests from this website are sent by email; they are not automatically recorded as Hub leads or tasks.

2

2. Process locally

The local worker downloads the signed job package and processes the agreed input files on the designated computer. Source files are not uploaded to the Hub in the standard pilot flow.

3

3. Review the result

The operator reviews the local result. The Hub receives only the run metadata defined for the pilot; selected result fields are sent only if expressly agreed. Nothing is posted to an ERP or submitted to AADE automatically.

Workflows and current pilot scope

The current pilot candidate is bank-to-invoice reconciliation. The other cards are separate workflow ideas, not included in this pilot and not evidence of customer-accepted availability.

📋
Pilot candidate

Greek Invoice Intake

Invoice intake is not included in this pilot. Extraction, field validation and customer-format compatibility require separate testing and acceptance.

Formats and languages to be confirmed from a sample
🏦
Pilot candidate

Bank Statement Reconciliation

Pilot candidate: match a supported bank CSV with an agreed invoice list and flag uncertain cases for review. Current evaluation is synthetic only; no real customer sample, named tester or customer acceptance is recorded. Full transaction rows stay on the worker machine in the standard flow.

File format and matching criteria confirmed before a run
📊
Outside current pilot

Spreadsheet Validation

Spreadsheet validation is outside the current pilot. Its rules, supported formats and results have not been accepted for customer use.

Not validated for this pilot
📂
Outside current pilot

Email Attachment Organizer

Email attachment organization is not included in the current pilot. Its classification rules and file actions need separate validation and approval.

Not validated for this pilot
📱
Outside current pilot

myDATA XML preview — outside current pilot

This is not part of the current pilot. XML preview is not a production submission capability; AAIA does not issue or submit invoices to AADE.

Preview only — no AADE submission
🌎
Outside current pilot

Browser Automation

Browser automation is not included in this pilot and has not been validated for customer use.

Not validated for this pilot

Local processing with an agreed data boundary

The local Worker processes the agreed files. The AAIA Control Tower (Hub) dispatches signed jobs and records the run status and other metadata defined for the pilot. Any result fields sent to the Hub are agreed explicitly. Website enquiries go by email; they do not automatically create Hub leads or tasks.

🔒

Data boundary agreed for each pilot

The current bank-to-invoice pilot candidate processes source files on the Worker machine; the standard flow does not upload full source files to the Hub. The exact run metadata and any reviewed result fields are agreed before a pilot. Optional cloud-model use is disabled by default and requires separate scope and approval.

✅

Human approval required

The pilot includes human review of results. No automatic posting to an ERP or submission to AADE is included; any downstream action and approval point must be agreed in the written scope.

📜

Signed templates only

Every automation template is HMAC-signed by the Control Tower before the worker executes it. Unsigned or tampered packages are rejected.

💻

Designated execution environment

The Worker runs on a designated computer and connects to the hosted Control Tower. Supported operating systems, versions and access requirements are confirmed for each scoped pilot.

Data boundary

Invoice PDFsProcessed on the Worker; full source files are not uploaded to the Hub in the standard flow
Local processing
Extracted text & fieldsProcessed on the Worker; any Hub metadata is pilot-scoped
Local processing
Bank statement CSVFull transaction rows stay on the Worker in the standard flow
Local processing
Job status & countsRun status and agreed aggregate match counts
Synced as defined for the pilot
Approved field valuesOnly if included in the agreed pilot data scope
Only if expressly agreed
Document contentRaw OCR text and full transaction rows
Not part of the standard Hub sync

Two screens. One workflow.

AAIA has two distinct parts: the local Worker processes agreed files; the hosted Control Tower (Hub) dispatches signed jobs and records pilot-scoped run data. The Hub is not the Worker, your ERP or the public website.

Control Tower — dispatch and review agreed jobs
AAIA Control Tower automation builder — illustrative interface
Local Worker — process agreed files on the designated computer
AAIA Local Worker suggestions interface — not customer acceptance evidence

Discuss a scoped bank-to-invoice pilot

Bank-to-invoice matching is a pilot candidate, not a customer-accepted service. We first agree the sample, data boundary, test criteria, environment, support, timing and commercial terms in writing.

No customer data is needed for an initial enquiry. Do not email sensitive or identifiable files; any sample exchange uses a separately agreed safe channel.