Invoicing & ERP integrations

How to connect NeoManager with easySales: a complete setup guide

By easySales Team · Updated 14 September 2026 · 3 min read

How to connect NeoManager with easySales: a complete setup guide

Connect NeoManager to easySales as billing software, as an ERP or as a stock source: server details, invoice numbering, customer matching, payment type mapping, article ids and what each message means.

What connecting NeoManager gives you

NeoManager is business software you run on your own server, and easySales talks to it over that server's Web Connector. Depending on how you want to work, it can be the place your invoices are issued, the place your orders are processed, the place your stock comes from — or all three.

That is the first thing to know about it: NeoManager appears in three places in easySales, not one.

Page What the connection does
Integrations → Billing Software easySales issues the invoice for an easySales order, in NeoManager, and attaches the PDF to the order.
Integrations → ERP systems easySales sends the order to NeoManager; the invoice is issued there and easySales fetches it back onto the order.
Integrations → Stock sources Product stock is read from a NeoManager warehouse into easySales.
The three places NeoManager appears

All three ask for the same server coordinates, and you can connect any combination of them. Most sellers start with Billing Software, and this guide starts there too.

Before you start

✓

NeoManager, installed and reachable

The integration talks to the Web Connector on your own NeoManager server, so you need its address and port, and the server has to answer from outside your network.

✓

A user for easySales

A NeoManager user name and password, and the company name as NeoManager holds it. The user name is written on the invoices, so a dedicated user makes them easy to recognise.

✓

The ids your consultant gives you

The warehouse (Gestiune), and the article ids for the discount and the shipping charge. They are ids inside your own NeoManager, so nobody outside it can tell you what they are — ask your NeoManager consultant for them by name.

Step 1 — Find the NeoManager card

Go to Integrations → Billing Software and search for neomanager.

The Billing Software page in easySales filtered to NeoManager, showing the connected NeoManager card.
Integrations → Billing Software filtered to `neomanager`.

Press Connect on the card, or Edit if you have connected it before.

Step 2 — Where your NeoManager is

The top of the NeoManager billing connection form, showing Connection name, Port, IP Address, Warehouse and Company.
NeoManager runs on your own server, which is why this block exists.
Field What it is
Connection name What you see inside easySales. Name it after the company or the warehouse it invoices for.
IP Address The address of the server NeoManager is installed on.
Port The port its Web Connector answers on.
Warehouse The NeoManager Gestiune id the invoices are issued from. Several ids exist in most installations; use the one your stock is on.
Company The company name exactly as NeoManager knows it — it is part of the login, not a label.
Username and Password The NeoManager user easySales signs in as. The user name is also written on the invoice as the one who issued it, so give easySales a user of its own.
Source A name of your choosing that NeoManager tags these documents with, so you can tell which ones came from easySales.
The server block

Step 3 — How invoices are numbered and dated

The NeoManager billing form showing Invoice Series, Invoice Number, Next invoice number and Invoice date.
Who numbers the invoice, and which date it carries.
Field What it does
Invoice Series The series the invoices are issued on. Dashes, underscores and slashes are removed before it is sent, so DMS-2026 arrives as DMS2026.
Invoice Number = Auto NeoManager numbers the invoice itself, from its own counter on that series.
Invoice Number = Next invoice number easySales sends the number. The field below holds the next one to use, and it moves on by itself after each invoice, keeping the leading zeros — 00147 becomes 00148.
Invoice date = Order date The invoice carries the date the order was placed.
Invoice date = Invoice create date The invoice carries the date it was issued.
Numbering and dating

Step 4 — Customers and payment types

The NeoManager billing form showing Duplicate handling for individual customers and the payment type mapping rules.
Rules are checked from the top; the first match wins.

Duplicate handling for individual customers decides what happens when a private customer orders from you again.

Option What happens
Always create a new customer A new customer record in NeoManager for every order. Nothing is ever matched, so nothing is ever attached to the wrong person — at the cost of a long customer list.
Match existing customer by phone number An existing individual with the same phone number is reused, and the invoice goes to that record. When no one matches, a new customer is created as before.
Duplicate handling for individual customers

Companies are not affected by this setting: a company order is always matched against NeoManager by its fiscal code, and only created when nothing matches.

Payment type mapping decides which NeoManager payment type ends up on the invoice.

With the box ticked, you write the rules yourself. Each rule points an easySales payment mode — or the payment method as the marketplace spelled it — at one NeoManager payment type. The rules are checked from the top and the first match wins; drag a rule by its handle to change the order.

Type Usually used for
NeoManager default Leave the choice to NeoManager's own setting for the customer.
Card Paid online by card.
Ramburs Cash on delivery.
Ordin de plată Bank transfer.
Pe loc Paid on the spot.
La termen Payable at a later date, on terms.
Efect comercial and Exceptat Commercial paper and exempt documents, for the cases your accountant asks for by name.
The NeoManager payment types

Step 5 — Which NeoManager article each line is booked to

The NeoManager billing form showing Discount ID, Shipping tax ID, Client group ID, Source, Username and Password.
The two article ids the discount and shipping lines are booked to.

An invoice line has to name an article in NeoManager. The products name themselves, through their Stock code; the discount and the shipping do not, so you give them an article id here.

Line Article in NeoManager
a product the product's Stock code in easySales
the discount Discount ID
the shipping charge Shipping tax ID
What each line is booked to

Step 6 — The notes template

The notes template of a NeoManager billing connection, with the Order and Products variable buttons above a box containing an order number and the sales channel.
What the template produces becomes the invoice's Observations.

What the template produces becomes the invoice's Observations in NeoManager. The buttons above the box insert values from the order — order number, sales channel, invoice series, the quantity and SKU of each product.

The ERP connection

Billing Software has easySales issue the invoice. The ERP connection turns that around: easySales sends the order to NeoManager, the invoice is issued there, and easySales fetches it back and attaches it to the order. Choose it when NeoManager, not easySales, is where orders are processed.

The NeoManager ERP connection form, showing Alias, IP, Port, Source, Company, Username and Password.
The ERP connection asks for the same server.

The server block is the same. Below it, the ERP form asks for a few more ids.

The NeoManager ERP form showing Client group ID, Discount ID, Fee ID, Shipping tax ID and Warehouse ID.
The ERP form asks for one id the billing form does not: Fee ID.
Field What it is
Client group ID The NeoManager customer group that new customers are created in.
Discount ID The article the discount line is booked to.
Fee ID The article any other charge on the order is booked to.
Shipping tax ID The article the shipping line is booked to.
Warehouse ID The Gestiune the order is sent to.
The extra ids on the ERP form

Two settings sit at the bottom of that form. Duplicate handling for individual customers works exactly as it does on the billing connection. TipOperatieStoc decides what NeoManager does with the stock when the order lands:

Option What happens when the order arrives
1 Everything on the order is reserved.
2 Everything on the order is put on order.
3 What is in stock is confirmed; the rest is reserved.
4 What is in stock is confirmed; the rest is put on order.
5 Everything is confirmed, and the whole order fails if the full quantity cannot be held.
TipOperatieStoc — what NeoManager does with the stock

The stock source connection

The NeoManager stock source form, showing Warehouse name, IP Address, Port, Source, Company, Warehouse, Username and Password.
The stock source is also what links a product to its NeoManager article.

This one reads stock out of a NeoManager warehouse and writes it onto your products in easySales. It is also what teaches easySales which NeoManager article each product is, and it does that by SKU.

Invoices you have to correct

An invoice issued through easySales is a real NeoManager document from the moment it is created, and the two systems part company as soon as you want to undo one.

Where invoices go wrong

Message What it means
Invoice series not found. Invoice Number is set to Next invoice number but the field under it is empty. Fill in the number to start from.
A expirat sesiunea The session with NeoManager timed out. easySales signs in again and retries by itself; if it keeps coming back, the Web Connector is restarting or unreachable.
Could not connect to host / Error fetching http headers The server did not answer. Check that the IP address and port are right and that the machine is reachable from outside your network.
NeoManager login returned an empty session token. The server answered but would not sign easySales in. Check Company, Username and Password — the company name has to be exactly as NeoManager holds it.
What the messages mean

Frequently asked questions

It depends on what you want it to do. Billing Software if easySales should issue your invoices in NeoManager. ERP systems if orders should be handed to NeoManager and the invoice issued there. Stock sources if your product stock lives in NeoManager. They are independent, they use the same server details, and you can connect any combination of them.

Because NeoManager runs on your own server rather than as an online service. easySales connects to that server's Web Connector, which means the address has to be reachable from the internet. Your NeoManager consultant and whoever manages your firewall arrange that between them.

The company name exactly as NeoManager holds it. It is part of the login rather than a label, so a different spelling stops the connection from authenticating.

The Gestiune id the documents are issued from. Most installations have several, and which one you use is a question for your NeoManager consultant — the invoices and the stock movements follow it.

Auto hands the numbering to NeoManager, which is the safer choice when anything else issues invoices on the same series. Next invoice number has easySales send the number and advance the counter after each invoice, which is what you want when easySales is the only thing issuing on that series and you need the numbering to stay unbroken.

Article ids inside your NeoManager. Products carry their own article id through their Stock code, but the discount line and the shipping line do not have a product behind them, so you name the article each of them should be booked to. Ask your NeoManager consultant for the two ids.

Those products have no Stock code in easySales, and the Stock code is what names the NeoManager article. Connect NeoManager as a stock source as well — matching on SKU, it fills the Stock code in for every product it recognises — or type the article id on the product yourself.

Their SKUs do not match. NeoManager sends its articles with the SKU each one carries, and easySales matches on that string exactly. A product spelled differently in the two systems — a space, a dash, a different case — never matches, so nothing is written to it.

Yes. Set Duplicate handling for individual customers to Match existing customer by phone number. An order from an individual whose phone number is already in NeoManager is then attached to that customer instead of creating a new one. Companies are always matched by fiscal code and were never affected.

With Payment type mapping switched off, from the order: online becomes Card, cash on delivery becomes Ramburs, bank transfer becomes Ordin de plată, unknown becomes Pe loc. With it on, your own rules are checked from the top and the first one that matches decides.

Hungarian forint and Bulgarian lev orders are invoiced in their own currency, with the VAT rate of that country. Orders in any other currency are invoiced as Romanian lei, so if you sell in euro, check the resulting document before you rely on it.

No. Deleting the invoice in easySales detaches it from the order here; the document stays in NeoManager and has to be cancelled there. The same applies to credit notes — a storno is issued in NeoManager directly, not through this integration.

Was this guide helpful?