Data Alchemy — Software IDP con AI
Accounts Payable

AI Accounts Payable (AP) Automation Software

Data Alchemy matches purchase orders, delivery notes (DDT) and supplier invoices line by line and posts the entries into SAP, Zucchetti or TeamSystem with no re-keying: your finance team only reviews the exceptions.

What it is

What accounts payable automation is

The accounts payable cycle runs from purchase order to supplier payment: order, goods receipt with delivery note (DDT), invoice receipt, control, posting and payment. It is the most document-heavy process in finance and the one that absorbs the most data-entry hours. Accounts payable automation — often called AP automation — removes the manual entry: Data Alchemy assigns a single AI engine to each document model — Claude by Anthropic (the engine we recommend by default), GPT by OpenAI, Data Alchemy AI (Data Alchemy's proprietary model, running on its own servers and GPUs in Italy) or another compatible large language model (LLM) through the European inference providers Scaleway and Seeweb Regolo.ai, on the customer's own subscription — reads orders, DDTs and invoices, aligns line items by SKU, quantity and price, validates the data against ERP master data and posts entries automatically. The finance team stops re-keying documents and reviews only genuine exceptions.

Comparison

Accounts payable software vs a traditional ERP

An ERP records invoices, but the data entry stays manual: someone has to read the order, DDT and invoice and key them in line by line. An accounts payable automation software like Data Alchemy works alongside SAP, Zucchetti or TeamSystem and does the upstream work — it reads the documents, runs the three-way matching and writes the already-reconciled entries into the ERP through the AI agent or the REST API. Unlike generic invoice processing software, Data Alchemy runs the full three-way match against your ERP master data before anything is posted. You don't replace your ERP: you eliminate the hours of entry that precede it.

The flow

The automated payable cycle, from order to payment

Data Alchemy maps every stage of the accounts payable cycle and automates it end-to-end, linking order, DDT and invoice into a single reconciled entry ready for accounts payable.

1. Purchase order

The order issued to the supplier is captured and digitised: the AI extracts line items, quantities, prices and terms that become the reference for downstream controls.

2. Inbound delivery note

On goods receipt, the delivery note is read by the AI and aligned with the open order: received quantities and items are compared line by line.

3. Supplier invoice

The invoice — PDF, XML or FatturaPA — is captured from email, scanner or upload, classified and read line by line with no templates.

4. Three-way matching

Order, DDT and invoice are compared by SKU, quantity and price: price mismatches, missing goods and duplicates surface before posting.

5. Master-data validation

Suppliers, items, price lists and payment terms are checked in real time against SAP, Zucchetti or TeamSystem. Clean matches flow straight through.

6. Posting and payment

The reconciled entry is posted into the ERP through the AI agent or the REST API and enters the payment cycle, ready for approval.

Exceptions

What happens when invoice, order and delivery note disagree

No payable cycle matches 100% of the time: renegotiated prices, partial deliveries, ancillary charges and off-catalogue items are the norm. Automating accounts payable does not mean posting everything blindly — it means deciding in advance what can pass on its own and what deserves a human check. Validation rules are configured with you during onboarding and stay editable over time, as suppliers and purchasing terms change.

Clean matches

When the three lines agree within the rules you defined, the entry is posted to the ERP with no intervention. This is the share of documents the finance team stops seeing altogether.

Routed exceptions

Lines that fail the check are queued to the responsible reviewer — buyer, warehouse or finance — with the order, delivery note and invoice side by side: the exception is resolved by reading, not by rebuilding the case from scratch.

Blocks before payment

Duplicates, double submissions, tampered totals and suppliers missing from master data are stopped before the entry reaches the payment cycle, where fixing them costs far more.

ERP integrations

Native ERP integrations for accounts payable

Data Alchemy posts reconciled AP entries directly into SAP, Zucchetti, TeamSystem, Microsoft Dynamics and Oracle NetSuite through the AI agent installed at your premises (a database, CSV/JSON/TXT files or APIs) or with an integration built on Data Alchemy's REST API and webhooks. Master data — suppliers, items, price lists and payment terms — is read back from the ERP in real time, so every invoice is validated against the system of record before posting.

Core capabilities

Everything you need to automate accounts payable

Template-free AI extraction

A dedicated LLM reads orders, DDTs and invoices from any supplier and extracts line items (item, quantity, unit of measure, price) with no template configuration, at 99.8% accuracy (measured with Claude).

Automatic three-way matching

Each invoice line is aligned with the matching purchase-order line and delivery-note line. Payable-cycle discrepancies surface before the entry reaches finance.

ERP master-data validation

The AI validates every document against SAP, Zucchetti or TeamSystem master data in real time: suppliers, items, price lists and payment terms always consistent.

Duplicate and anomaly detection

Every incoming invoice is compared with the posted history: duplicates, double submissions and tampered totals are blocked before payment.

Email-first acquisition

The Mail service, installed at your premises, manages multiple business mailboxes and sends the platform the orders, DDTs and invoices matching a model, queuing only payable-cycle documents. Emails and credentials stay within your perimeter.

Licence and pay-as-you-go credits

A Basic, Business or Enterprise licence chosen to fit your needs, plus pay-as-you-go credits for the documents processed. Quote on request.

Getting started

How to automate accounts payable: from test to go-live

Automating accounts payable requires neither an ERP replacement nor a pause in the finance team's work. With the AI agent, ERP integration takes 2–5 working days without custom integrations, and onboarding runs alongside the payable cycle already in production.

1. Document and volume analysis

We start from a real sample of purchase orders, delivery notes and supplier invoices, plus the annual volume handled by finance: these two figures drive both the configuration and the sizing of the licence and pay-as-you-go credits. Nothing needs normalising upstream — layouts differing from supplier to supplier are the normal case, not the exception.

2. ERP connection

The integration with SAP, Zucchetti, TeamSystem, Microsoft Dynamics or Oracle NetSuite is activated through the AI agent installed at your premises (a database, CSV/JSON/TXT files or APIs) or the REST API and webhooks. From that point master data — suppliers, items, price lists and payment terms — is readable in real time and becomes the reference for every validation.

3. Validation rule configuration

You define the rules by which three-way matching decides what passes automatically and what stops: which deviations are acceptable, which documents require approval and who each payable-cycle exception is routed to.

4. Acquisition and go-live

The mailbox or monitored folder receiving supplier documents is connected and the flow goes live. Operator training is included in the onboarding: from then on the payable cycle runs automatically on real documents.

ROI

The ROI of AP automation

Automating the payable cycle frees the finance team from data entry and shortens close times. Here are Data Alchemy's reference figures, the same as on the home page.

99.8%

data extraction accuracy with Claude, versus the errors of manual data entry

~12 s

Per 1-page document (Claude Sonnet)

-60%

operational time (Data Alchemy average)

0

templates to configure: the AI reads any supplier with no setup

FAQ

Frequently asked questions about accounts payable automation

What is accounts payable automation?

Accounts payable automation uses artificial intelligence to handle the entire flow from purchase order to supplier payment: capturing orders, DDTs and invoices, extracting line-level data, three-way matching, validating against ERP master data and posting entries automatically. Data Alchemy assigns a dedicated LLM to each document model — Claude by Anthropic, GPT by OpenAI, Data Alchemy AI (Data Alchemy's proprietary model) or a compatible model through the European providers Scaleway and Regolo.ai — and, with Claude, reaches 99.8% accuracy (no accuracy figure is published for the other engines) and 3-second processing per document, with no templates and no manual re-keying.

Which payable-cycle documents does the platform handle?

Data Alchemy processes every payable-cycle document: purchase orders, delivery notes (DDT), supplier invoices in PDF, XML and FatturaPA, price lists and supply terms. It ingests documents from email (business mailboxes, via the on-premise Mail service), scanners or upload, classifies them automatically and links them to build a reconciled entry ready for accounts payable.

How does it integrate with the ERP (SAP, Zucchetti, TeamSystem)?

Payable-cycle entries flow directly into SAP, Zucchetti, TeamSystem and other ERPs through the AI agent installed at your premises (a database, CSV/JSON/TXT files or APIs) or with an integration built on Data Alchemy's REST API and webhooks. Master data (suppliers, items, price lists, payment terms) is read from the ERP in real time, so the AI validates every document against the system of record before posting.

What is the ROI of accounts payable automation?

By automating the payable cycle, the finance team cuts operational time by 60% (Data Alchemy's average), at 99.8% accuracy (measured with Claude) and, with Claude Sonnet or higher, around 12 seconds of reading for a one-page document and around 18 for two pages (average times). Data-entry errors are eliminated and close times shorten. Use the ROI calculator to estimate the savings on your real document volumes.

How is it different from traditional OCR automation?

Traditional OCR converts pixels into text but cannot decide whether an invoice line belongs to a specific order or whether quantities match the delivery note. An LLM-powered engine understands the semantics of payable-cycle documents: it identifies suppliers, items, units of measure and prices, performs three-way matching against ERP master data and produces a structured, validated entry ready to post — with no manual re-keying.

How much does AI accounts payable automation cost?

The cost of Data Alchemy is made up of a licence — Basic, Business or Enterprise, chosen to fit your needs — plus pay-as-you-go credits for the documents processed. From the Business licence up, external fields (the document checked against the ERP data it refers to, such as the purchase order) and remote validation (individual values, such as the supplier or item code, checked against your master data) extend the check to your ERP: when reading a delivery note that carries the purchase order reference, Data Alchemy queries the ERP via API, retrieves the order and checks item code and quantity line by line. Quotes are on request and the licences are compared on the pricing page.

How long does it take to automate accounts payable?

With the AI agent, the ERP connection takes 2–5 working days without custom integrations; onboarding also covers the configuration of three-way matching validation rules and operator training. The existing payable cycle keeps running: AI extraction can run in parallel on real documents until you are satisfied with the results.

Do I have to change ERP to automate the payable cycle?

No. Data Alchemy does not replace your ERP: it works alongside SAP, Zucchetti, TeamSystem, Microsoft Dynamics or Oracle NetSuite and feeds it already-reconciled entries through the AI agent or Data Alchemy's REST API and webhooks. Master data stays in your ERP, which remains the system of record for suppliers, items, price lists and payment terms: the only thing that changes is who keys the data in.

How are non-PO invoices handled?

Invoices with no purchase order behind them — utilities, services, consulting, general expenses — cannot be three-way matched, but they can still be automated: the AI extracts supplier, VAT number, taxable amount, VAT rates and line items, validates the data against the supplier master data in your ERP and runs the duplicate and abnormal-amount checks. What changes is the approval criterion: instead of matching against order and delivery note, the cost centre owner authorises the invoice, and only then is it posted.

Is human review still needed in the payable cycle?

Yes, but by exception. The goal is not to take control away from the finance team: it is to take away the typing. Documents that pass extraction and master-data validation go through untouched; the ones the AI flags as uncertain — unknown supplier, price outside agreed terms, quantities that do not match the delivery note, suspected duplicate — are queued and reviewed by a person. The team moves from transcribing every invoice to checking only the cases that deserve it.

See your accounts payable cycle automated

Activate the free Demo with 10 documents and check the AI reading on your orders, DDTs and invoices, with 1 model chosen from the predefined ones in a dedicated environment. To see the three-way match and posting into your ERP and calculate the ROI for your case, contact us to plan a call with a demo on your own documents.