# EUDR: timber’s deadline is 30 December. What the regulation means for your data in Business Central

> From 30 December 2026 the EU Deforestation Regulation applies to large and medium companies. For timber it means a due diligence reference on every purchase and sale, origin, species and supplier risk. How AI in Business Central can help, and what I’m planning.

On 30 December 2026 the EU Deforestation Regulation (EUDR) applies to large and medium companies. For timber, furniture and packaging it is not abstract: no due diligence statement, no placing on the market and no export.

Most timber companies I talk to are not worried about the principle. They buy from known suppliers and many already work with certified wood. They are worried about the data. Where does the reference number go? Who checks that the geolocation file actually arrived? And what happens on the day a truck is ready to leave and one supplier document is missing?

## What the EUDR asks for, in ERP terms

Strip away the legal language and the regulation turns into very concrete data per transaction:

- **A due diligence statement reference** per purchase and per sale. Statements are filed in the EU’s information system, and their reference numbers have to travel along the chain.
- **Origin and geolocation** of the plots where the wood was harvested, plus the country of production.
- **Species**, with common and scientific name, and the quantity.
- **Certificates and supplier risk.** Certification helps with risk assessment, but it does not replace due diligence.

Who has to file their own statement and who only passes references on depends on your role in the supply chain, and the rules were amended in 2025. Micro and small companies have their own provisions. That part is a question for your legal advisers. The data part lands in the ERP either way.

## Where the data lives today

Mostly not in the ERP. It arrives as:

- PDFs attached to emails: delivery notes, certificates, statement confirmations
- spreadsheets with plot coordinates
- supplier portals with their own exports
- notes in someone’s inbox

Business Central has purchase lines, item tracking and lots. It has no fields for a due diligence reference, a species or a geolocation file, and nothing that blocks a shipment when they are missing.

## What I’m planning

I’m mapping this out now for timber and wood-processing companies in the Alps. To be clear: **this is in planning.** There are no results yet, and I will not invent any.

The idea follows the same principle as the rest of my “Hack Business Central” series: **the ERP keeps the rules and the audit trail, the AI reads the documents.**

1. **Give the data a home.** An AL extension adds EUDR fields where they belong: due diligence reference, country of production, species, geolocation reference and certificate on purchase lines, carried through item tracking to sales.
2. **Let AI read the supplier documents.** The assistant reads the PDFs and spreadsheets a supplier sends, pulls out reference numbers, species and origin, and proposes them for the right purchase line.
3. **A person confirms.** Nothing is written as fact until someone has checked it. The proposal shows which document and which page each value came from.
4. **Check before goods leave.** Before a sales shipment is posted, rules in AL check that every relevant line has a confirmed reference. Missing data is flagged early, not discovered at the gate.
5. **Keep the trail.** Who confirmed what, when, from which document. The ERP holds the audit trail, not someone’s inbox.

Reading supplier documents is where AI helps. Deciding whether a lot is compliant is not its job. The rules for that stay in AL, transparent and testable.

## What I expect to be hard

- **Document quality.** Scans, mixed languages, suppliers who send the same information in a different layout each time.
- **Mixed lots.** Wood from several origins in one delivery, or one log split into many products.
- **Geolocation files.** Coordinates and polygons need validation, not just storage.
- **Changing guidance.** The regulation has already been amended once. The data model has to absorb changes without a rebuild.

## Limits, honestly

- **It is not legal advice.** Your role under the EUDR and your obligations are for your advisers to determine.
- **It doesn’t file statements on its own.** Submission to the EU system stays a deliberate step by a person.
- **AI extraction can be wrong.** That is why every value is a proposal with its source until someone confirms it.
- **It depends on suppliers.** If a document never arrives, the best the system can do is notice early and say so.

## Read more

The pattern behind this, and the three use cases that already work, are in the white paper: [Ask Business Central: three AI use cases that work today](https://karrenberg.it/blog/business-central-ai-use-cases-486c94?lang=en).

## Is your team facing a similar problem?

If EUDR is on your desk this month, tell me where your data actually lives today. That answer shapes what I build. [Discuss your challenge](https://karrenberg.it/?lang=en#contatto). I usually reply within two working days.

---
Simon Milos Karrenberg · https://karrenberg.it/blog/eudr-timber-business-central?lang=en
