France E-Invoicing September 1st Deadline

APPG • Accounts Payable Intelligence

France E-Invoicing Goes Live September 1: What Accounts Payable Needs to Know

France's new B2B electronic invoicing requirements begin September 1, 2026. For Accounts Payable teams, the change reaches far beyond tax compliance and into invoice intake, ERP workflows, master data, exceptions and controls.

By Accounts Payable Professionals Group  |  August 31, 2026

France's B2B e-invoicing rollout begins September 1, 2026, changing how Accounts Payable teams receive and process invoices.

For years, electronic invoicing has been discussed as part of the future of Accounts Payable. In France, that future arrives on September 1, 2026.

Starting September 1, businesses established in France and covered by the reform must be able to receive electronic invoices, regardless of company size.

Large companies and intermediate-sized enterprises (ETIs) must also begin issuing electronic invoices and meeting applicable e-reporting requirements.

An ETI, or entreprise de taille intermédiaire, is a French business-size classification generally covering companies between a traditional SME and a large enterprise. Employee count, annual turnover and balance-sheet criteria are used to determine the formal classification.

SMEs and micro-enterprises must be able to receive electronic invoices beginning September 1, 2026, but receive until September 1, 2027 to begin issuing them.

For AP professionals, this is much more than a tax change.

It changes the invoice lifecycle.

France E-Invoicing Timeline

September 1, 2026

All covered businesses
Must be able to receive electronic invoices.

Large companies + ETIs
Must receive and issue electronic invoices and meet applicable e-reporting requirements.

SMEs + micro-enterprises
Must receive electronic invoices beginning September 1, 2026. Their issuance requirement begins September 1, 2027.

The deadline has not moved.

France has announced that the startup phase will be handled with an approach of tolerance and support toward businesses that encounter difficulties implementing the reform on September 1. That should not be interpreted as a postponement. The legal implementation date remains September 1, 2026. AP teams should continue implementation and remediation work while documenting problems and good-faith efforts to comply.

An Emailed PDF Is No Longer Enough

One of the most important points for AP teams is understanding what France means by an electronic invoice.

A scanned paper invoice, ordinary PDF or invoice attached to an email does not satisfy the new electronic invoicing process.

The invoice must contain structured information and move through an approved electronic invoicing platform, known in France as a plateforme agréée.

Electronic invoice formats can include UBL, CII, and mixed or hybrid formats containing structured data together with a human-readable invoice representation.

A widely used hybrid implementation is Factur-X, which combines a readable PDF representation with structured invoice data.

The change is not simply from paper to PDF. It is from documents to structured invoice data.

What AP Will Actually See on Day One

Instead of relying on an AP email inbox, compliant B2B invoices covered by the reform will arrive through the organization's approved platform or a compatible solution connected to it.

The invoice contains structured data that can be passed into the ERP or AP automation system for validation, matching and processing.

AP therefore needs to know which platform receives invoices, how the platform connects to the ERP, which business entity an invoice belongs to, what happens when validation fails and who owns each exception.

A rejected electronic invoice is no longer simply a PDF that an AP employee edits or asks someone to resend by email. AP, suppliers and platform administrators need defined procedures for correcting errors, responding to status messages and resubmitting invoices appropriately.

SIREN, SIRET and Invoice Routing Matter

France's electronic invoicing directory helps determine where an invoice should be delivered.

The directory uses French business identification and routing information to help invoices reach the appropriate recipient and approved platform.

For multinational AP departments, this deserves special attention.

A corporate group may have several French entities or establishments. Having the correct supplier name is not necessarily enough. AP, procurement and vendor-master teams need to make sure the correct legal entity and routing information are being used.

Master-data warning: A perfectly structured invoice can still fail if it is routed to the wrong entity or if the underlying business identifiers are incorrect.

Four New Invoice Elements AP Should Know

France's reform also adds information that must appear on invoices as the new requirements take effect.

Four Required Elements

1. Customer SIREN number
2. Transaction category, identifying whether the invoice relates to goods, services, or both
3. VAT-on-debits information, when applicable. In practical terms, this identifies situations in which the supplier has opted to account for VAT based on invoicing rather than waiting for collection.
4. Complete delivery address when it differs from the customer's billing address

For AP departments, this highlights the growing importance of master-data quality.

An automated invoice with incorrect master data is still an incorrect invoice.

AP Should Watch the Exceptions

The greatest benefit of e-invoicing may not be faster data entry.

It may be eliminating data entry altogether for many routine invoices.

That allows AP professionals to spend more time on transactions that require judgment.

But automation also makes exception management more important.

What happens when the supplier cannot be matched?

What happens when the purchase order number is incorrect?

What happens when structured invoice data fails validation?

What happens when the quantity invoiced does not agree with the goods receipt?

What happens when the platform detects a problem or an invoice is rejected?

Those questions need documented answers before invoice volume begins moving through the new channel.

The Fraud Risk Changes, Too

Structured e-invoicing can reduce some of the risk created by invoices arriving through uncontrolled email channels. But electronic invoicing does not eliminate AP fraud.

The risk surface changes.

AP teams still need strong controls around supplier identity, vendor-master changes, platform access, bank-account changes, payment approvals and segregation of duties.

There is also a behavioral risk: employees may assume an invoice is legitimate simply because a system successfully accepted it.

A technically valid invoice is not proof that every part of the transaction is legitimate.

Invoice validation should complement vendor-master controls, bank-change verification, purchase-order controls and payment authorization. It should not replace them.

Who Is Actually in Scope?

The core electronic invoicing mandate applies to domestic B2B transactions involving businesses established in France and subject to VAT.

AP teams should also distinguish this reform from France's existing public-sector invoicing environment. Business-to-government invoicing has already operated through Chorus Pro.

Cross-border transactions and businesses without a French establishment can be treated differently, and e-reporting obligations may still apply to certain transactions.

Multinational organizations should therefore avoid assuming that every French-related invoice follows exactly the same process. Tax and legal teams should confirm the treatment of cross-border and special-case transactions.

A Day-One Checklist for Accounts Payable

AP leaders with French operations should confirm that the operational side of the process is ready, not simply that a compliance project has been marked complete.

France E-Invoicing AP Checklist

• Confirm that the organization has selected an approved electronic invoicing platform.
• Confirm that each applicable French entity is configured to receive electronic invoices.
• Verify the correct SIREN, SIRET and electronic routing information.
• Test receipt of an invoice from the approved platform into the ERP or AP system.
• Confirm that required invoice fields map correctly into the ERP.
• Test applicable structured and hybrid invoice formats supported by the organization's solution.
• Test purchase-order and non-PO invoice workflows.
• Test a validation failure or rejected invoice from beginning to resolution.
• Test duplicate-invoice handling.
• Confirm who owns supplier communication when an invoice is rejected.
• Review vendor-master and company data for accuracy.
• Confirm that approval rules remain in place after automation.
• Confirm that segregation of duties remains intact.
• Make sure the invoicing platform does not unintentionally create a route around established AP approvals.
• Confirm who owns problems involving the platform, ERP, tax data, master data and supplier communication.

This Is Bigger Than France

The larger lesson for Accounts Payable professionals is global.

Invoices are gradually changing from documents that AP employees read and enter into structured financial data that systems receive, validate and process.

That does not make Accounts Payable less important.

It changes where AP provides value.

The Changing Role of AP

As structured e-invoicing expands, AP professionals may spend less time manually entering invoice information and more time monitoring automated invoice flows, maintaining master data, resolving exceptions, investigating anomalies, enforcing controls and making sure automation produces the correct accounting and payment result.

September 1 is France's deadline. For the AP profession, it is another sign of where invoice processing is headed.

Sources & Further Reading

1. French Ministry of Economy and Finance
   Official overview of France's electronic invoicing reform, including the September 2026 and September 2027 implementation timetable, approved-platform requirement, new invoice information requirements and startup guidance.
   Official E-Invoicing Guidance
2. French Ministry of Economy and Finance
   Official guidance covering mandatory invoice information and the additional data requirements introduced with electronic invoicing.
   Invoice Requirements
3. French Ministry of Economy and Finance
   Official guidance concerning France's electronic invoicing directory and invoice routing.
   E-Invoicing Directory
4. French Ministry of Economy and Finance
   Current government summary of the September 1, 2026 implementation of France's electronic invoicing requirements.
   September 2026 Requirements
5. Direction générale des Finances publiques (DGFiP)
   French tax administration resources and information concerning electronic invoicing and approved platforms.
   French Tax Authority

APPG Editorial Note: Electronic invoicing requirements can depend on the type of business, transaction, tax treatment and jurisdiction involved. Accounts Payable professionals should confirm the requirements that apply to their organization with appropriate tax, legal and technology advisers. This article is intended for professional education and does not constitute tax or legal advice.

APPG Leadership

Robert Ruhno

Executive Director

Robert leads APPG's mission, editorial direction, member community, and efforts to advance the Accounts Payable profession.

Mariann Ruhno

Chief Education Officer

Mariann leads APPG's education strategy, professional-development resources, and initiatives designed to help AP professionals strengthen their skills and careers.

Practical education, reporting, and community resources for Accounts Payable professionals.

LinkedIn X Facebook Instagram

Back to top ↑

Workday AI Growth in Accounts Payable

Workday says thousands of customers are already using its AI agents. For Accounts Payable professionals, the shift could change which skills matter most.

August 29, 2026  |  Accounts Payable Professionals Group

Artificial intelligence is moving deeper into finance, and Workday's latest results show that businesses are ready to use it.

Workday reported $2.649 billion in revenue for its fiscal second quarter, up 12.8% from a year earlier. Subscription revenue reached $2.471 billion, an increase of 13.9%.

But the number Accounts Payable professionals should pay closest attention to is not revenue.

It is AI adoption.

5,500+ Workday customers are now using at least one of the company's own AI agents. Workday says that number increased more than 35% from the previous quarter.

Workday also reported that AI drove more than 25% of its new annual contract value during the quarter.

That matters because Workday sits inside the finance and business operations of more than 11,500 organizations worldwide, including more than 65% of the Fortune 500.

AI Is Moving Into Finance Work

Workday is moving beyond AI that simply gives employees information. The company is developing AI agents designed to perform parts of business processes.

One example is Workday's Financial Audit Agent, which is now generally available. Workday says the agent is designed to significantly reduce the time required to build audit evidence packages.

The company has also introduced Adaptive Decision Intelligence. The technology allows finance and operations teams to ask questions using everyday language, model different scenarios in minutes and act on the results.

This points toward a larger change in Accounts Payable.

AP professionals have already watched automation take over parts of invoice capture, coding, matching, approval routing and duplicate detection.

AI agents could push automation further by handling longer processes and taking actions within rules established by the organization.

What Does This Mean for AP Professionals?

It does not mean that AP professionals suddenly become unnecessary.

In fact, more automation can make AP knowledge even more important.

Someone still needs to decide what an AI agent is allowed to do. Someone must review exceptions, protect vendor information, maintain segregation of duties, investigate suspicious activity and make sure payments follow company policy.

The skills that matter may change.

The AP Professional Takeaway

An AP professional who understands Workday, internal controls, invoice workflows, vendor management and AI may become more valuable as companies automate more routine processing.

Controls Still Matter

Workday itself appears to recognize the importance of controlling AI agents.

The company introduced Agent Passport, which tests and verifies AI agents before they enter production and continuously monitors them afterward. Workday says the system can be used with both Workday-built and third-party agents.

For AP departments, that idea should sound familiar. Technology may change, but good controls remain essential.

An AI agent that can review invoices or prepare financial information may save time. An agent with too much authority, weak monitoring or unnecessary access to vendor and payment information could also create new risks.

AP leaders should ask the same kinds of control questions they already ask about employees, systems and financial processes:

• What information can the AI agent access?
• What actions can it take?
• Which actions require human approval?
• How are its decisions recorded?
• Who reviews exceptions?
• What happens when the agent makes a mistake?

The Opportunity for AP

The message from Workday's latest results is clear: AI in finance is moving from experiment toward everyday business use.

For AP professionals, now is the time to learn how these systems work and prepare to manage them.

The future of AP may involve less manual processing, but organizations will still need people who understand controls, suppliers, exceptions, fraud risks and how money moves through an organization.

Those professionals could become the people organizations rely on to make sure AI does the work correctly.

Join the Conversation

How is your organization using AI in Accounts Payable today?

Are you already working with AI agents, or is your team still focused on traditional AP automation? Share your experience with the Accounts Payable Professionals community.

Sources & Further Reading

• Workday: Fiscal 2027 Second Quarter Financial Results
• Workday

APPG Leadership

Robert Ruhno

Executive Director

Robert leads APPG’s mission, editorial direction, member community, and efforts to advance the Accounts Payable profession.

Mariann Ruhno

Chief Education Officer

Mariann leads APPG’s education strategy, professional-development resources, and initiatives designed to help AP professionals strengthen their skills and careers.

Practical education, reporting, and community resources for Accounts Payable professionals.

LinkedIn X Facebook Instagram

Back to top ↑

Invoice Booking Errors AP Controls

Controls & Risk

When Invoice Booking Errors Increase: A Practical AP Control Plan

More duplicate payments and posting mistakes do not always mean an AP team needs more approvals. The first step is finding where the errors begin, then placing the right control at that point.

A recent discussion in the Accounts Payable Professionals Group raised a common concern: What should an AP department do when invoice booking mistakes suddenly increase?

The most effective answer is a combination of root cause analysis, preventive controls, automated checks, and focused human review. Adding another approval to every invoice may slow the process without fixing the real problem.

Key principle: Put the strongest control as close as possible to the point where the error begins. Use later reviews as a safety net, not as the primary defense.

1. Classify the errors before changing the process

Review a useful sample of recent errors and place each one into a clear category. Examples include duplicate invoice entry, incorrect vendor, wrong amount, tax error, incorrect purchase order, duplicate freight, missed credit memo, prepayment not applied, and invoice paid after a partial payment.

Record the cause, employee or processing queue, invoice source, vendor, business unit, entry method, and dollar impact. A Pareto chart can then rank the causes by frequency or financial impact. The familiar 80/20 rule is a guide, not a promise. The purpose is to identify the few causes creating most of the risk.

Also ask what changed before the error rate increased. Look for new employees, reduced staffing, rushed training, a system update, a changed interface mapping, a new invoice channel, OCR extraction problems, or a larger number of manual uploads. A technical error may begin with system configuration, process design, or unclear instructions rather than the person posting the invoice.

2. Strengthen duplicate detection

A duplicate check based only on the invoice number is too weak. Suppliers may add spaces, dashes, leading zeros, or different date formats. Configure the ERP or AP automation platform to compare several fields, such as supplier, invoice type, amount, currency, date, and invoice number.

Establish a consistent invoice-number entry rule and include it in training and desktop procedures. When the system permits, test normalization rules for nonmeaningful spaces, punctuation, and capitalization. Keep the multi-field comparison in place because consistent data entry alone cannot catch every duplicate.

This is consistent with current ERP functionality. Oracle documents a duplicate check using supplier, invoice type, amount, currency, and date. SAP also compares multiple invoice fields, including vendor, company code, currency, amount, reference number, and document date.

3. Match invoices before posting or payment

Use three-way matching for PO invoices whenever practical. The invoice should agree with the purchase order and the goods or services receipt. Set reasonable tolerance limits for price and quantity differences. Route exceptions to the right owner instead of allowing AP staff to force a match or repeatedly override warnings.

Non-PO invoices still need a clear business purpose, correct coding, proper approval, and supporting documentation. High-risk invoices, including large amounts, unusual vendors, manual payments, and invoices entered close to a payment run, may need additional review.

4. Separate entry, approval, and payment duties

One person should not control invoice entry, approval, vendor changes, and payment release. A maker-checker workflow is useful when the checker reviews meaningful evidence instead of simply clicking approve. The GAO Green Book emphasizes preventive controls and segregation of incompatible duties as important parts of an effective control system.

Smaller teams may not be able to separate every duty. In that case, use compensating controls, such as an independent payment-run review, bank-account reconciliation, audit-log review, or management review of high-risk transactions.

Review system access and configuration changes as part of the same control framework. Restrict who can change duplicate-check settings, approval rules, tolerance limits, interface mappings, and user roles. Test key controls after an ERP update or workflow change, and document the results before relying on the revised process.

5. Give prepayments and partial payments their own workflow

Prepayments and partial payments create special duplicate-payment risk. Track them in a dedicated prepayment account or ERP process, require supporting approval, and apply the balance to the final invoice before payment. Avoid informal workarounds, such as posting a negative pro forma invoice, unless accounting policy, system design, and the controller have specifically approved the method.

Vendor statements can help identify unapplied credits, missing invoices, and payments the supplier has not allocated correctly. Reconcile statements for high-value and high-volume suppliers before major payment runs, while recognizing that a supplier statement is a detective control and may not show a duplicate that exists only inside the buyer's system.

6. Review exceptions and measure whether controls work

Run prepayment exception reports for same-vendor, same-amount invoices, repeated bank accounts, invoices just below approval limits, unusual manual entries, and payments made outside the normal cycle. Review overridden duplicate warnings as a separate population.

Track errors per 1,000 invoices, duplicate warnings overridden, payment errors prevented, dollars recovered, and repeat errors by cause. Report the trend each month. If a control produces many false positives, adjust it carefully. If the same cause keeps returning, the corrective action has not worked.

Use targeted training and quality reviews instead of broad retraining when the data points to one failure. A short review of invoices from the affected queue can confirm whether the new procedure is being followed. Periodic audits can then test whether the control continues to operate as designed.

A practical 30-day response

1. Build an error log and review the last 60 to 90 days.
2. Use a Pareto chart to identify the leading causes.
3. Confirm duplicate-check settings and review all overrides.
4. Test PO matching, approval thresholds, and segregation of duties.
5. Create a controlled workflow for prepayments and partial payments.
6. Review system changes, access rights, training, and invoice-number procedures.
7. Measure the results and repeat the analysis after 30 days.

The bottom line

Strong AP controls combine people, process, and technology. Automation should stop likely errors and surface exceptions. AP professionals should investigate those exceptions, document decisions, and correct the process behind repeat failures. The goal is focused control that prevents the right mistakes before money leaves the organization without adding friction to every invoice.

Explore more from APPG: Controls & Risk  |  Internal Controls  |  AP Automation

Editorial Note: This article was developed with the assistance of artificial intelligence and reviewed and approved by Robert Ruhno, Executive Director of the Accounts Payable Professionals Group, and Mariann Ruhno, Chief Education Officer of the Accounts Payable Professionals Group.

APPG Leadership

Robert Ruhno

Executive Director

Robert leads APPG’s mission, editorial direction, member community, and efforts to advance the Accounts Payable profession.

Mariann Ruhno

Chief Education Officer

Mariann leads APPG’s education strategy, professional-development resources, and initiatives designed to help AP professionals strengthen their skills and careers.

Practical education, reporting, and community resources for Accounts Payable professionals.

LinkedIn X Facebook Instagram

Back to top ↑

Strong AP Controls Around the World

Controls & Risk

Strong AP Controls Look Surprisingly Similar Around the World

Regulations may differ from country to country, but the everyday controls that protect Accounts Payable remain remarkably consistent.

In the United States, SOX made control testing and documentation standard practice. The UK is moving toward the Provision 29 framework. Canada, India, China, South Africa, and many other countries have their own regulatory and governance frameworks that encourage similar behavior.

The AP Reality

The regulation may have a different name, but the controls AP teams perform every day often look very much the same.

The Daily Work Is Surprisingly Consistent

For Accounts Payable teams, many of the fundamental controls cross national borders.

• Invoices must be properly approved.
• Vendor master changes need controls.
• Payments require segregation of duties.
• Reconciliations need documented review.
• Exceptions must be investigated and resolved.

Whether you call it a SOX control or something else, the practice is largely the same, and it matters.

Automation Changes the Work, Not the Accountability

The tools are changing quickly. Automation and artificial intelligence can route approvals, flag unusual transactions, capture timestamps, maintain audit trails, and help identify exceptions before payments are released.

But technology does not remove accountability.

Good governance still depends on people making informed judgments, reviewing exceptions, questioning unusual activity, and understanding why controls exist in the first place.

That may be one of the most important lessons for AP teams as automation expands. Technology can perform more of the work, but responsibility for the integrity of the process still belongs to the organization and the people overseeing it.

Key Takeaway

No matter where you work, strong controls build trust. And trust is the foundation of every finance team.

Explore More From APPG

Controls & Risk  |  Internal Controls  |  AP Automation

Editorial Note: This article was developed with the assistance of artificial intelligence and reviewed and approved by Robert Ruhno, Executive Director of the Accounts Payable Professionals Group, and Mariann Ruhno, Chief Education Officer of the Accounts Payable Professionals Group.

APPG Leadership

Robert Ruhno

Executive Director

Robert leads APPG’s mission, editorial direction, member community, and efforts to advance the Accounts Payable profession.

Mariann Ruhno

Chief Education Officer

Mariann leads APPG’s education strategy, professional-development resources, and initiatives designed to help AP professionals strengthen their skills and careers.

Practical education, reporting, and community resources for Accounts Payable professionals.

LinkedIn X Facebook Instagram

Back to top ↑

5 AP Developments to watch in 2026

APPG • Accounts Payable Intelligence

Five Accounts Payable Developments AP Professionals Need to Watch in 2026

From mandatory e-invoicing and agentic AI to payment fraud and ISO 20022, major changes are reshaping how accounts payable teams process invoices, manage risk and protect company payments.

Updated August 2026 • Accounts Payable Professionals Group

THE AP BRIEF

Accounts payable is becoming more automated, connected and dependent on structured financial data. At the same time, fraud and control risks remain. AP professionals should understand five developments that could affect invoice processing, vendor management, payments, compliance and internal controls.

Accounts payable is changing quickly. Artificial intelligence is moving deeper into AP workflows. Governments are requiring structured electronic invoices. Fraud remains a major threat. Payment networks are changing how transaction data moves between organizations.

For AP professionals, these developments are more than technology news. They affect invoice processing, internal controls, vendor management, payments, compliance and the skills AP teams will need.

Here are five developments AP professionals should be watching.

1 France Is About to Make E-Invoicing a Reality

France will begin a major electronic invoicing reform on September 1, 2026.

By that date, companies covered by the reform must be able to receive electronic invoices. Large and mid-sized companies must also begin issuing electronic invoices. Small and micro-enterprises have until September 1, 2027 to meet the issuing requirement.

This is important because an electronic invoice is not simply a PDF sent by email. Structured invoice data allows systems to process information automatically.

For AP teams, this can change invoice intake, validation, tax handling, matching, exception management and archiving.

Why AP should care: AP departments with operations in France should make sure their ERP, vendors, invoice workflows and approved electronic invoicing platforms are ready. Even organizations outside France should watch this development because structured e-invoicing mandates continue to expand internationally.

2 AI Agents Are Moving Into Accounts Payable

AP automation has been around for years. The next stage is different.

Oracle Fusion Cloud's 26B release includes a Payables Agent focused on invoice ingestion, compliance and control. Oracle also has a Payments Agent connected with payment options, offers and execution.

This points toward a future in which AI does more than extract invoice data.

An AI agent may help complete tasks, identify exceptions, recommend actions and move transactions through a workflow.

How much authority should an AI agent have inside accounts payable?

AP leaders will need clear rules for segregation of duties, approvals, audit trails, vendor master changes, invoice exceptions and payment authorization.

Why AP should care: Automation and authority are not the same thing. Organizations need to determine which AP activities can become autonomous and which decisions still require human review or approval.

3 Business Email Compromise Remains a Serious Payment Threat

Fraud continues to be one of AP's greatest risks.

Business Email Compromise, commonly called BEC, is especially dangerous because criminals may impersonate executives, vendors or other trusted parties.

The goal is often simple: convince someone to send a legitimate payment to the wrong bank account.

Artificial intelligence can make these attacks more convincing by helping criminals create realistic messages and other deceptive communications.

AP departments should pay special attention to vendor banking changes, unusual payment requests, first-time payments, rush payments and changes in normal communication patterns.

Control reminder: Independent verification remains one of the strongest defenses. A request to change banking information should be verified using trusted contact information already on file rather than information supplied in the change request.

4 ISO 20022 Continues to Change Global Payments

ISO 20022 is changing how financial information moves through the global banking system.

Its structured format allows payment messages to contain richer and more consistent information. That can improve payment processing, reconciliation, investigations and automation.

Swift had previously planned to require its Stop and Recall process for payment cancellations beginning in November 2026. Swift has since moved the mandatory requirement to November 2027.

That revised timeline is important for AP and treasury teams planning their payment roadmaps.

The larger trend has not changed. Payment systems continue moving toward richer structured data and greater standardization.

Why AP should care: AP professionals handling international payments should understand how ISO 20022 can affect payment information, exceptions, recalls, reconciliation and communication with financial institutions.

5 E-Invoicing Is Moving Directly Into ERP Systems

E-invoicing is also becoming part of the ERP environment.

Microsoft Dynamics 365 Business Central introduced functionality supporting France's electronic invoicing requirements. The functionality supports structured formats and connections needed for electronic invoice processing.

This is an important signal.

E-invoicing, AP automation, tax compliance and ERP workflows are beginning to merge.

AP professionals may eventually spend less time entering invoice data and more time monitoring automated workflows, resolving exceptions, maintaining vendor data, reviewing controls and protecting payment integrity.

Why AP should care: The AP department of the future may not be measured mainly by how many invoices employees manually process. It may be measured by how effectively the team manages an automated financial process.

What Should AP Teams Be Watching?

Development	Primary AP Impact	What to Watch
France E-Invoicing	Invoice processing and compliance	September 1, 2026 implementation
Agentic AI	Automation and internal controls	Human versus AI authority
BEC Fraud	Vendor and payment security	Banking changes and payment exceptions
ISO 20022	Global payment processing	Structured payment data and exceptions
ERP E-Invoicing	Invoice workflow automation	ERP integration and data quality

AP Action List

AP leaders do not need to wait for these trends to fully mature. Teams can begin preparing now.

• Review upcoming e-invoicing requirements in countries where your organization operates.
• Ask ERP and AP automation vendors about structured e-invoice capabilities.
• Review segregation of duties before introducing agentic AI into AP workflows.
• Strengthen controls around vendor bank account changes.
• Require independent verification for unusual or high-risk payment instructions.
• Review how ISO 20022 may affect international payments and reconciliation.
• Track AP exceptions and risk prevention alongside traditional productivity metrics.

What AP Professionals Should Take Away

These five developments point in the same direction.

Accounts payable is becoming more automated, more connected and more dependent on structured data.

At the same time, fraud and control risks remain.

The strongest AP departments will therefore need both technology and controls.

Automation can handle more routine transactions. AP professionals can then focus their attention on exceptions, compliance, vendor risk, payment security, data quality and financial controls.

The future of AP is not simply touchless processing. It is intelligent automation backed by strong financial controls.

That is not the disappearance of accounts payable.

It is the evolution of the profession.

Sources & Further Reading

1. French Ministry of Economy and Finance: Electronic invoicing requirements and implementation timetable. Official French electronic invoicing guidance
2. Oracle: Oracle Fusion Cloud Financials 26B readiness information covering AI capabilities including Payables and Payments agents. Oracle Fusion Cloud Financials 26B
3. Federal Bureau of Investigation: Business Email Compromise and cyber-enabled financial fraud information. FBI cybercrime information
4. Swift: ISO 20022 migration and continued payments modernization. Swift ISO 20022 guidance
5. Microsoft: Dynamics 365 Business Central electronic invoicing functionality and French localization documentation. Microsoft Dynamics 365 Business Central

Editorial note: Regulatory requirements and technology release schedules can change. AP professionals should verify requirements that apply to their organization with appropriate tax, legal, banking and technology advisers.

↑ Back to top