{"id":76445,"date":"2026-10-15T14:17:02","date_gmt":"2026-10-15T12:17:02","guid":{"rendered":"https:\/\/juvo.be\/?p=76445"},"modified":"2026-10-20T17:41:22","modified_gmt":"2026-10-20T15:41:22","slug":"accounts-payable-automation","status":"publish","type":"post","link":"https:\/\/juvo.be\/en\/accounts-payable-automation\/","title":{"rendered":"Accounts payable automation: from invoice receipt to a proposal in your ERP"},"content":{"rendered":"

[et_pb_section fb_built=”1″ _builder_version=”4.20.4″ _module_preset=”default” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row column_structure=”1_2,1_2″ _builder_version=”4.17.6″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”1_2″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n

What percentage of your incoming invoices are currently processed into a posting proposal in your ERP without human intervention?<\/strong> If you want to automate accounts payable, we provide you with a single workflow: whatever comes in goes through that workflow and appears as a posting proposal in your ERP\u2014and that\u2019s where it stops. What\u2019s correct moves on; what\u2019s incorrect goes into a workbin with the reason noted. <\/p>\n

So what exactly happens<\/strong> between the time we receive the request and the booking proposal?<\/p>\n

[\/et_pb_text][\/et_pb_column][et_pb_column type=”1_2″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_image src=”https:\/\/juvo.be\/wp-content\/uploads\/juvo-accounts-payable-automatiseren-hero.webp” alt=”AP team lead with a coffee at her desk, her laptop showing a short worklist of a few open invoices.” title_text=”juvo-accounts-payable-automatiseren-hero” _builder_version=”4.27.9″ _module_preset=”default” border_radii=”on|6px|6px|6px|6px” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.20.4″ _module_preset=”default” background_color=”RGBA(255,255,255,0)” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row make_equal=”on” _builder_version=”4.17.6″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_text admin_label=”Tekst” _builder_version=”4.27.9″ _module_preset=”default” background_color=”#F2F2F2″ min_height=”100%” custom_padding=”25px|25px|25px|25px|true|true” border_radii=”on|6px|6px|6px|6px” global_colors_info=”{}”]<\/p>\n

What We Automate for You<\/h2>\n

 <\/p>\n

For us , automating invoice processing covers the entire chain, from receipt to posting proposal<\/strong>, and that chain begins with a single data model, regardless of the channel through which an invoice is received. Invoices received via Peppol comply with the European standard EN 16931. Invoices received via email, PDF, or scan are converted to the same data model as Peppol, so that no separate rules are needed for each channel further down the line. <\/p>\n

Based on that data model, the invoice moves through the chain. Each step in the chain makes a single decision and explains why, with a score and the reason; you can always check why an invoice was approved or rejected. At the end, the posting proposal enters the ERP system via the standard invoice import; the ERP remains the system where postings are made and payments are processed. <\/p>\n

We make a proposal; you approve it. Your ERP system posts the transaction and makes the payment. By design, the agent does not post transactions, make payments, approve them, or modify supplier data. <\/p>\n

And what about the team lead who keeps your AP team running? The workbench only shows him which lines are incorrect, along with the reason. Correcting them is faster than retyping them. <\/p>\n

So why is there still manual work involved today, if invoices are already recognized?<\/p>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.20.4″ _module_preset=”default” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row admin_label=”Row” _builder_version=”4.17.6″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n

Where Things Are Getting Stuck Today<\/h2>\n

 <\/p>\n

The manual work that remains involves structure, not sloppiness. In accounts payable, a lot is already set in stone: the format of a Peppol invoice and the VAT rules. As of January 1, 2026, VAT-registered companies in Belgium must exchange their B2B invoices in a structured format, using Peppol as the standard<\/strong>. Still, an exception\u2014such as a missing purchase order, a price that\u2019s just off, or an approver on vacation\u2014might end up on someone\u2019s desk on your team. <\/p>\n

According to Ardent Partners<\/strong> (AP Metrics that Matter in 2025), 53% of the AP and finance managers surveyed cite invoice exceptions as one of their biggest challenges. This is an indicative figure and not a survey specific to Belgium. <\/p>\n

Detection is not the same as resolution. We don\u2019t see the benefit in typing faster, but rather in the percentage of invoices that don\u2019t need to be reviewed by a human,<\/strong> and in how quickly the rest are resolved. By that measure, a tool that detects anomalies and places them in a queue merely shifts the workload and doesn\u2019t actually resolve anything. <\/p>\n

What kind of verification is required for an invoice<\/strong>, with and without a purchase order?<\/p>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.20.4″ _module_preset=”default” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row admin_label=”Row” _builder_version=”4.27.7″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n

With or without an order form: two routes, one supply chain<\/h2>\n

 <\/p>\n

An invoice with a purchase order and an invoice without a purchase order require different verification procedures.<\/p>\n

 <\/p>\n

Invoices with a purchase order<\/h3>\n

 <\/p>\n

For invoices accompanied by a purchase order, we perform a line-item comparison<\/a>: we compare the invoice line by line with the purchase order and the receipt. This allows us to catch any discrepancies in price or quantity<\/strong> that might be overlooked in the total.<\/p>\n

 <\/p>\n

Invoices Without a Purchase Order<\/h3>\n

 <\/p>\n

Without a purchase order, the validation process relies on coding and the approval workflow<\/strong>. We generate the coding based on previous bookings, and the invoice is sent to whoever the approval workflow designates.
Two routes, one supply chain: what benefits do they offer together? <\/p>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.20.4″ _module_preset=”default” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row admin_label=”Row” _builder_version=”4.17.6″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n

What It Offers<\/h2>\n

 <\/p>\n

We measure the results using four metrics,<\/strong> and each one is clearly defined here. For the cost per processed invoice and the touchless rate, we\u2019ll agree on the target values with you during the baseline measurement. <\/p>\n

Cost per processed invoice<\/strong>. In *AP Metrics that Matter in 2025*, Ardent Partners reports a cost of $2.78 per processed invoice for the top-performing group, compared to an average of $9.40; amounts are in dollars, as published, and fully loaded. Ardent Partners defines the top-performing group as the 20% of companies with the lowest average cost per invoice and the shortest average processing time. Keep these figures in context: the sample is predominantly North American (59% of respondents), and 53% work for a large company with revenue exceeding $1 billion. For us, the cost per processed invoice is a target value that we agree upon together during the baseline assessment, measured across all incoming invoices during the period, including licenses, infrastructure, and management. <\/p>\n

Processing time<\/strong>. The same measurement shows 3.1 days per invoice for the top-performing group, compared to an average of 9.2 days, using the same sample size. We measure the processing time ourselves, from receipt to final approval. This is a measurement standard, not a target value. <\/p>\n

Touchless rate<\/strong>. The touchless rate\u2014broken down by invoices with and without purchase orders\u2014is a target value that we agree upon together during the baseline measurement. \u201cTouchless\u201d means that an invoice enters the ERP system as a proposal without human intervention, where the ERP then posts it. This is how we define automatic invoice posting: the proposal enters the ERP system without human intervention, and the ERP posts it. <\/p>\n

Exceptions resolved autonomously<\/strong>. This metric does not have a target value, but it does have an agreed-upon definition. We define the subset of exceptions that are resolved without human intervention during the baseline measurement: which cases count, what \u201cresolved\u201d means, and over what time period. <\/p>\n

Anyone who says, \u201cWe\u2019ve already tried this,\u201d<\/strong> won\u2019t get a promise from us, but rather a measurement metric. The baseline measurement follows the same definition as the follow-up measurement; otherwise, you\u2019ll be measuring an improvement that doesn\u2019t exist. <\/p>\n

The question remains<\/strong> whether this applies to your situation.<\/p>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.27.8″ _module_preset=”default” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row admin_label=”Row” _builder_version=”4.17.6″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n

Who This Isn’t For<\/h2>\n

 <\/p>\n

There are three situations in which<\/strong> this approach is not appropriate\u2014or at least not yet.<\/p>\n

Do you process few invoices?<\/strong> If the number of invoices per month falls below a certain threshold, this won’t pay for itself\u2014and we’ll be upfront about that.<\/p>\n

If you don’t enter purchase orders<\/strong>, start with the master data rather than AI.<\/p>\n

If you have an ERP migration planned, you don\u2019t have to wait for it<\/strong>: the agents run on top of your ERP, and at go-live, you switch the source, not the agent. Waiting is only advisable if go-live is within three months, or if the new ERP resolves the issue on its own. Before going live, the workflow runs in the shadow of the current process, using actual invoices, without posting any entries\u2014this is the shadow run. <\/p>\n

If this applies to your situation<\/strong>, how do you get started?<\/p>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.27.8″ _module_preset=”default” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row admin_label=”Row” _builder_version=”4.17.6″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n

How We Get Started<\/h2>\n

 <\/p>\n

Our AP automation process begins with an AI Discovery Session<\/strong> lasting half a day to a full day; the outcome is a shortlist based on impact and effort, in that order. After the AI Discovery Session, we\u2019ll build a working prototype using your own invoices within a few weeks. Then you decide: move forward, make adjustments, or stop. We scale up what works. <\/p>\n

If you’d like to assess your numbers yourself first<\/strong>, you can do so with the self-assessment<\/a>. A 20- to 30-minute online consultation is all it takes to see where AI can deliver value for you. <\/p>\n

Where is this approach already being implemented<\/strong> today?<\/p>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.20.4″ _module_preset=”default” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row admin_label=”Row” _builder_version=”4.17.6″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_text admin_label=”Tekst” _builder_version=”4.27.9″ _module_preset=”default” background_color=”#F2F2F2″ min_height=”100%” custom_padding=”25px|25px|25px|25px|true|true” border_radii=”on|6px|6px|6px|6px” global_colors_info=”{}”]<\/p>\n

Where this chain is already in operation today<\/h2>\n

 <\/p>\n

The same approach is currently in use in multiple client implementations across<\/strong> finance, customer service, and logistics. In a previous project by our team, the reconciliation of supplier statements went from requiring a team of five people to taking less than two hours of work per week. In another project by our team, order processing went from requiring eight full-time employees to requiring less than one. These are document flows other than invoices, but they use the same validation logic. <\/p>\n

[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.20.4″ _module_preset=”default” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”][et_pb_row admin_label=”Row” _builder_version=”4.17.6″ _module_preset=”default” width=”100%” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.6″ _module_preset=”default” global_colors_info=”{}”][et_pb_cta title=”Do you know your AP scores, or are you just guessing?” button_url=”https:\/\/juvo.be\/en\/get-in-touch\/” url_new_window=”on” button_text=”Schedule a 30-minute call” _builder_version=”4.27.9″ _module_preset=”default” link_option_url=”https:\/\/juvo.be\/en\/get-in-touch\/” global_colors_info=”{}”]<\/p>\n

A 20- to 30-minute online conversation is all it takes to see where AI can deliver value for you.<\/p>\n

[\/et_pb_cta][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"

What percentage of your incoming invoices are currently processed into a posting proposal in your ERP without human intervention? If you want to automate accounts payable, we provide you with a single workflow: whatever comes in goes through that workflow and appears as a posting proposal in your ERP\u2014and that\u2019s where it stops. What\u2019s correct […]<\/p>\n","protected":false},"author":15,"featured_media":78576,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_titles_title":"Accounts payable automatiseren: tot een voorstel in je ERP","_seopress_titles_desc":"Accounts payable automatiseren van ontvangst tot een voorstel in je ERP. Wat de oplossing doet, wat het oplevert, en voor wie ze niet bedoeld is.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"","_seopress_news_disabled":"","_seopress_video_disabled":"","_seopress_video":[],"_seopress_pro_schemas_manual":[],"_seopress_pro_rich_snippets_disable_all":"","_seopress_pro_rich_snippets_disable":[],"_seopress_pro_schemas":[],"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"categories":[88,86],"tags":[],"class_list":["post-76445","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-artificial-intelligence","category-procesautomatisering"],"acf":[],"_links":{"self":[{"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/posts\/76445","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/comments?post=76445"}],"version-history":[{"count":38,"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/posts\/76445\/revisions"}],"predecessor-version":[{"id":79244,"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/posts\/76445\/revisions\/79244"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/media\/78576"}],"wp:attachment":[{"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/media?parent=76445"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/categories?post=76445"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/juvo.be\/en\/wp-json\/wp\/v2\/tags?post=76445"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}