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.
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.
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.
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.
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.
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.
Counts and open items, if included in the agreed output.
Candidate match and supporting criteria for review, if accepted in the pilot schema.
Unmatched payments are flagged for investigation; the system does not make an accounting classification decision.
An example review category; inclusion and fields depend on the agreed pilot output.
An example review category; inclusion and fields depend on the agreed pilot output.
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.
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.
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.
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.
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.
Invoice intake is not included in this pilot. Extraction, field validation and customer-format compatibility require separate testing and acceptance.
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.
Spreadsheet validation is outside the current pilot. Its rules, supported formats and results have not been accepted for customer use.
Email attachment organization is not included in the current pilot. Its classification rules and file actions need separate validation and approval.
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.
Browser automation is not included in this pilot and has not been validated for customer use.
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.
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.
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.
Every automation template is HMAC-signed by the Control Tower before the worker executes it. Unsigned or tampered packages are rejected.
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
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.


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.