AFAS invoice processing,
for the invoices that arrive as PDFs
AFAS invoice processing with an AI agent: Lleverage reads supplier invoices that arrive as PDFs, scans or emails, and checks each line against the receipt and the commitment in AFAS Profit. Invoices inside your tolerances go to your team to post, and Profit’s own approval workflow takes over. A variance waits for finance with the difference named.
How AFAS invoice processing works with an AI agent
AFAS Profit can match a UBL e-invoice line by line against receipts and commitments. A supplier who sends only a PDF gets a header read by Scan & herken and nothing to match, so someone in AP keys the lines by hand. The agent does that part in 4 steps. Why it reads any layout without a template is in our post on template-free AI vs OCR.
Read the PDF and find the supplier
A PDF, a scan or a forwarded email reaches the finance inbox. The agent reads the supplier, the invoice number, the order reference, the VAT and every line, each with a confidence, and finds the purchase relation in AFAS Profit by VAT number, KvK number or IBAN.
Find the receipt and the commitment
Each invoice line is tied to the receipt the warehouse recorded in Profit and to the commitment behind it. When only part of a delivery came in, the agent compares the line with what was received so far, and a line nobody has received yet is held back.
Check price, quantity, VAT and bank account
Price against the commitment, quantity against the receipt, the VAT code against the invoice date, and the IBAN on the invoice against the one on the purchase relation. You set the tolerance per supplier or category, and each check gives its own answer.
Hand the matched invoice to your team
Inside your tolerances the matched purchase invoice, each line accounted for, goes to your team to post in AFAS Profit, and journalising starts Profit’s own approval workflow for the assessor you named. Outside them nothing is handed over, and the person you choose gets the difference with the invoice, the receipt and the commitment.
Supplier invoices matched in AFAS Profit, PDFs included.
The PDF and scanned invoices that Profit cannot match on its own are read line by line and checked against the receipt and the commitment the day they arrive, so your team can post them sooner, the approval workflow starts sooner and invoices are ready for the payment order on time. Your AP team only opens the ones with a real variance.
Learn moreExample data
One PDF invoice into AFAS Profit, matched line by line.
A PDF invoice for EUR 18,240 arrives from Noordkamp Lagers, with no UBL file attached. AFAS Profit already holds the purchase order and the receipt it should agree with, line by line.
Example data
What the agent checks before a purchase invoice goes to your team to post
Price, quantity received, VAT code and the supplier’s IBAN are each checked against the receipt, the commitment and the purchase relation in AFAS Profit, with a tolerance you set. Invoices inside it go to your team to post in Profit, where the approval workflow starts, and anything outside it waits in finance with all three documents open.
Example data
AFAS e-invoice matching and Scan & herken next to Lleverage
AFAS Profit reads purchase invoices as e-invoices: UBL and XML files are matched line by line, and Scan & herken reads PDF invoices that come without a UBL file. We read the AFAS Help Center, afas.nl and the Lleverage docs on 5 November 2026.
| AFAS Profit on its own | Lleverage | |
|---|---|---|
| UBL and Peppol e-invoices | Stronger here. Profit reads the lines of a UBL or XML invoice, finds the creditor by VAT number, KvK number, IBAN, name and address, and matches each line itself. Dutch customers can receive invoices through Peppol from Profit 8. | E-invoices Profit already matches keep going straight to Profit. The agent takes the invoices that arrive as PDFs, scans and emails. |
| PDF invoices without a UBL file | Scan & herken fills the invoice header with the creditor details and totals. Automatic line matching needs a UBL invoice with lines, so a PDF-only invoice cannot be matched that way. | Yes: the agent reads every line of the PDF or scan, with a confidence on each field, and matches those lines too. |
| How invoices get in | Entered by hand, collected by the Communicatieservice from a POP mailbox or a folder, sent through eConnect or the FiElectronicInvoicePurchase UpdateConnector, or received through Peppol. | Yes: the agent picks invoices up from the finance inbox your suppliers already write to, as they arrive. |
| Invoices in other languages | AFAS says invoices in languages other than Dutch or English are recognised less well: the KvK, VAT, IBAN and invoice numbers may be misread, though amounts usually come through. | Yes: reads on meaning, and a field below the confidence line you set waits for a person to decide. |
| Receipts and commitments | For e-invoice lines, Profit matches item, reference and amount against receipts, then commitments, then free matching rules, within the percentage and amount margins on the supplier’s relation profile. | Yes: every line, from a PDF too, against the receipt and the commitment, with price and quantity tolerances per supplier or category. |
| Lines that do not match | When Profit finds no receipt, commitment, matching rule or preferred contra account, the line gets the status Geen match gevonden and is processed by hand in the entry layout. | Yes: the buyer or the warehouse gets the question in Teams, Slack or the inbox with the invoice, the receipt and the commitment, and the agent carries on with the answer. |
| Approval and payment | Journalising starts the Profit workflow for purchase invoices, and the assessor’s Accorderen action unblocks the invoice for the payment order. | Yes: Profit’s workflow keeps the approval, the agent hands your team invoices that already agree to post, and releasing a payment always stays with a person. |
| Getting better | Scan & herken remembers where a value sits on a PDF once someone points it out, which AFAS says can take a few attempts. | Yes: the agent updates its Skills from your team’s corrections, a person reviews each change, it offers to turn an invoice you handled together into a Skill, and a clerk can talk an exception through with the agent on a live call. |
| Building it on the AFAS API | The FiElectronicInvoicePurchase UpdateConnector inserts an e-invoice as a Base64 XML file and PDF. A PDF sent alone goes to Scan & herken, with the same header-only result. | Yes: our engineers connect the agent to AFAS Profit with your team, as a custom integration where needed, and it reads the same records your AP clerk works from. |
| Fits best when | Most suppliers send UBL invoices or use Peppol, and their lines reference your receipts and orders. | Many suppliers still send PDFs or scans, and each of their lines has to agree with what was ordered and received before your team posts it. |
We think AFAS Profit on its own is enough when most of your suppliers send UBL or Peppol invoices: its line matching, margins and scheduled journalising already do the work. We think Lleverage fits when a large share still arrives as PDFs or scans that Profit can only read at header level. More on three-way matching and on how our agents connect to your ERP.
Our engineers set it up with you.
It takes on more of the invoice run as it learns.
Forward deployed engineers match the first invoices beside your finance team and connect the agent to AFAS Profit, so the first PDF invoices come off the desk within a few weeks. From there it automates gradually: a correction becomes a change to the Skill once a person approves it.
They work inside your operation. They agree tolerances and cost centres with your controller. The confidence line is yours.
The finance inbox, the tolerances, the checks and the log are yours to configure. Our documentation and support sit behind your team, and an engineer is a call away whenever you want one.
Talk to us about either ↗Frequently asked questions
Does AFAS Scan & herken read invoice lines?
AFAS describes Scan & herken as filling the header of a PDF invoice: the creditor details and the totals, as far as it can. Line matching against receipts and commitments needs a UBL invoice with lines. For a supplier who sends only PDFs, the Lleverage agent reads each line so it can be matched as well.
Can AFAS Profit match invoices to receipts automatically?
Yes, for e-invoices. The action Verwerken e-factuurregels matches each UBL line to a receipt, then a commitment, then a free matching rule, within the margins on the supplier’s relation profile. Fully matched invoices can be journalised by a scheduled task. The agent brings the same check to invoices that arrive as PDFs, scans or emails.
Is there AI for purchase invoices in AFAS?
Scan & herken is switched on with its own activation, and AFAS lists an AI version of it, on top of Jonas, for customers in the Caribbean. Jonas itself works in Profit workflows, filling fields, summarising, translating and assessing large supplier quotes, and AFAS lists no Jonas task for matching invoice lines. The Lleverage agent does that matching.
How does Lleverage connect to AFAS Profit?
AFAS is one of the ERPs on our integrations page, and our engineers set up the connection with your AFAS administrator. The agent reads the invoice, matches it against the records in Profit and hands it to your team to post, so Profit runs its own checks and starts the approval workflow as it does for a keyed one.
What happens to purchase invoices without a commitment?
Freight, rent and service bills often have no order or receipt behind them. The agent checks the purchase relation, the IBAN and the VAT code, proposes the contra account your rules give that supplier, and sends the invoice to the assessor your rules name. Your team gets nothing to post until that person has answered.
Other processes the agents run
↗
Quote to orderQuote & SellQuotes drafted, orders entered and confirmed the moment they land.
↗
Purchase to paySource & ProcureInvoices, POs and confirmations, handled against the order.
↗
Forecast to producePlan & ProduceThe plan reshuffled when reality changes.
↗
Order to deliveryDeliver & SupportCustomers answered with full context, in their own channel.
↗
Master dataGovern & EnableMaster data kept clean and in sync across every system.