Integrations

Integrations: connecting Lean ERP to your other software

You manage invoices, orders and items in Lean. Your accounts stay in your accounting package, and your windows are designed in your window software. On this page you can read which integrations Lean has, what they exchange and how we set them up.

Book an online demo →Invoicing in Lean →

How does an integration with Lean ERP work?

Lean ERP runs your operations: quotes, orders, purchasing, stock, production, planning and invoicing. An integration means that what starts in Lean is not retyped in another package. The most requested integration is the one with accounting: you create the invoice in Lean, and Lean passes it on to your accounting package.

There are three forms. An online connection talks directly to the other package, through that package's connection interface (API). A file connection produces a file that the other package or your accountant imports. A project-based integration is built for your situation, on the API of Lean or of the other package.

Each detail page states plainly which form it is, which data is passed on and what the limitations are.

Connecting to your accounting package

Lean is not an accounting package. Your accounts stay where they are; Lean supplies the invoices.

Exact OnlineOnline connection: sales and purchase invoices, contacts, and payments back to Lean. Also with several administrations.

YukiOnline connection for sales invoices. The open items in Yuki come back to Lean.

WingsOnline connection, with the Wings account number per customer and per invoicing entity.

OctopusOnline connection that posts in successive steps, contacts included.

AdmisolFile connection for sales and purchase invoices, sent by e-mail.

VeniceProject-based integration through a queue, set up per customer.

Bob (Sage)How the invoices are passed on is agreed per customer, together with your accountant.

WinBooksHow the invoices are passed on is agreed per customer.

Exact Online ›Yuki ›Wings ›Octopus ›Admisol ›Venice ›

Lean also connects to other accounting and invoicing packages, such as Billit, Horus, BoCount, BaseCone and ExpertM. Ask us about them during the demo.

What happens to an invoice?

For every accounting package it follows the same four steps. Only the last one, the hand-over itself, differs per package.

1
Create the invoiceYou create the sales invoice or enter the purchase invoice in Lean, from the order or the project.
2
PrepareYou mark which invoices may go to accounting. Lean checks first: does the invoicing entity go to accounting, does a purchase invoice match its lines, does the customer have an account number where one is needed?
3
Pass onLean passes on the marked invoices: through the online connection, or as a file.
4
FeedbackFor each invoice you see whether it was processed, or which message the accounting package returned.

Journal codes (sales, credit note, purchase), financial year and connection details are set per invoicing entity. If you work with several companies, each entity has its own settings. An entity that does not go to accounting can be excluded.

E-invoicing via Peppol and EDI

Lean sends sales invoices via Peppol, in the same dispatch as the e-mail to your customer. For each invoice you see the Peppol status, and an invoice that did not arrive stands out. Incoming invoices received via Peppol appear among your incoming purchase invoices, where you approve them and link them to the order.

For customers who want to receive invoices by EDI, dispatch can run through Transus.

Invoicing in Lean ›

Windows and doors: Klaes, Reynaers and Ramasoft

Do you design windows in Klaes, ReynaPro (Reynaers) or Ramasoft? Lean reads the quote files from those packages, so the lines land in the order without retyping. With Ramasoft, the production files of an order can come along too.

Quotes from the IMOS design package can also come in through the Lean API and become a quote in Lean.

Lean for windows and doors ›

Wholesalers: Cebeo, Rexel and Würth

Do you buy from Cebeo, Rexel or Würth? When creating an item, you search the wholesaler's catalogue directly, with your own customer details at that wholesaler. You take over the item number and description instead of retyping them.

Which wholesalers we connect for you is decided at the start of the project.

Purchasing in Lean ›

Other ERP systems: SAP and Microsoft Dynamics NAV

Sometimes Lean runs alongside another ERP system, for example for the shop floor of one site. With SAP this is project-based: which data flows in which direction (production orders, items, confirmations) is laid down per project in a specification. With Microsoft Dynamics NAV (Navision), Lean exchanges invoices as a file in a shared folder.

An integration with another ERP is always a project, never a standard connection.

Track & trace: Traxgo and GeoDynamics

Lean retrieves registrations from Traxgo, for example the badge swipes of a time clock, and calculates the hours worked from them. A synchronisation with GeoDynamics also exists. What exactly comes across depends on how you use Traxgo or GeoDynamics; we look at that together.

Timesheets and work orders ›

Web shops: WooCommerce, Shopify and Bol.com

Do you also sell online? A connection with WooCommerce, Shopify or Bol.com is not a standard connection in Lean. We assess it per project, on the open Lean API: which orders come in, and which items and stock go to the shop.

Open API for bespoke integrations

Is your package not on the list? Lean has an open API. Other software can use it to fetch or supply data, for example a quote from a design package or attendance registration for a government declaration. Lean can also send data to another API itself. Each application gets its own secure access.

An integration on the API is bespoke work: we agree which data, in which direction and how often, and build it with our own developers.

How implementation works ›

Frequently asked questions

Do I have to change accounting package to work with Lean?

No. Lean is not an accounting package. You create the invoices in Lean and your accounts stay in your own package. The connection available for your package is described on this page.

What is the difference between an online connection and a file connection?

An online connection talks directly to the accounting package and gives feedback per invoice. With a file connection, Lean produces a file that is imported into the accounting package; you then mark the invoices as processed in Lean.

Do payments come back to Lean?

With Exact Online and Yuki, the amount paid comes back to Lean. With the other packages, you record payments in Lean itself.

Can Lean pass on the accounts of several companies?

Yes. Each invoicing entity has its own journals and connection details. With Exact Online and Wings, each entity can go to its own administration.

Lean ERP ›Invoicing ›Purchasing ›Implementation ›

Book an online demo

Bring one bottleneck. See how Lean handles it.

We start from a situation in your work. You see what works in the software today, and we discuss how it fits your process.