AAIA is being evaluated for local bank-to-invoice matching with human review. Browser, desktop, legacy and other document workflows are assessment areas only—not customer-accepted capabilities or part of the current pilot.
The Worker processes agreed files on a designated computer. The AAIA Control Tower (Hub) dispatches signed jobs and records pilot-scoped run metadata; it is not the Worker or the customer's ERP. No ERP integration is included in the current pilot candidate.
Other document types are assessed separately; the current pilot candidate uses an agreed bank export and invoice list.
Matching fields and review rules are defined and tested against the agreed pilot sample.
No ERP posting, browser automation or desktop-system update is included in the current pilot.
Not generic IT promises. Each area starts with a fixed-scope assessment.
Invoice extraction and other document types are outside the current pilot and have not been accepted in customer formats.
Desktop automation is a future assessment area, not a current pilot capability. Any use requires separate compatibility, safety and acceptance testing.
We assess old software and terminal screens when an API or file-based connection is unavailable.
Language and format compatibility are confirmed from the agreed sample; no customer-format acceptance is recorded.
The current candidate is bank-to-invoice matching. Scope, sample, environment, data boundary, acceptance criteria and commercial terms must be agreed before any customer run.
The standard pilot processes full source files locally and does not upload them to the Hub. The Hub receives run metadata and any other fields only as defined in the agreed data scope. Human review is required before downstream action.
Describe one repeated task. Do not email sensitive or identifiable files. If a sample is needed, agree its contents and a safe transfer method first; a written scope and quote follow assessment.