Orders are typed by hand
Someone opens the PDF, finds the item number, checks the agreed discount and types. Then the next email. That is a morning, every day.
Doclane reads orders, invoices and claims from the inbox, from a form or by upload. PDF, Excel, plain text in the body, it makes no difference. The records are created in your own system, whether that is Business Central, Uniconta or e-conomic. No web shop, no portal, no new workflows.
Someone opens the PDF, finds the item number, checks the agreed discount and types. Then the next email. That is a morning, every day.
ATM-11017 gets typed as ATM-11071. The wrong pallet goes on the lorry, and the credit note and the phone call follow.
Ask who types the orders. There is usually one name. And a week in July when the pile grows.
The obvious answer is "a web shop" or "an EDI project". But your customers want to order the way they always have. And they should be allowed to.
However your customers prefer: an email you forward (or forward automatically), or a form where they can upload documents. It can be a page we host for you, or a form placed directly on your own website. You choose the channels.
Whether it is an order, a claim, product data or a new customer, the AI finds the right details such as customer, item numbers, quantities, prices and company registration number, and matches them against your own master data.
A sales order, claim, item or customer record is created in the right place in the destination you use. Approve with one click, or let regular customers go straight through. When the AI is unsure, it asks instead of guessing.
You get your own secure receiving address. Forward manually whenever it suits you, or let us set up an automatic rule in your mail system together with your IT or ERP partner, so everything sent to orders@ goes across on its own. Mail that is not an order or a document is filtered out and never stored.
An email you forward. A form they upload to. Or a page you drop straight into your own website. You pick the channels, and the customer notices no difference.
The customer types the company name and registration number. Doclane fetches the rest from the registers as they type, so a typo in the VAT number is caught on screen rather than in finance.
Doclane gets sharper on your documents as they are approved. When someone fixes a field, the work is not wasted: the correction is remembered and applied the next time a similar document arrives.
Minutes per order become seconds. That time goes to customers instead.
Item numbers and quantities are checked against your own master data before anything is posted. A wrong number is caught on screen rather than in the warehouse.
Twice the orders does not require twice the hands. And July stops being a capacity problem.
PDF, Excel, plain text in an email, or a purchase order from the customer's own system. Out comes a sales order with the right item numbers and the customer's own prices.
See the moduleAmounts, lines and supplier are read and matched against master data. The invoice sits structured in your ERP rather than as a PDF in an inbox.
Shortages, damage, wrong deliveries. Often the slowest desk in the building, because every case has to be traced back to the original order. That tracing is exactly what Doclane does first.
See the moduleItem numbers, prices, descriptions, dimensions. In as product sheets and price lists, out as items in your catalogue.
See the moduleThe company register and VIES are checked while the customer fills in the form. Your sales rep adds the internal fields afterwards. Then it becomes a customer record.
See the moduleEvery type ends up in the same place: as correct records in your own system.
Doclane is not built for a single ERP. The document is read the same way regardless of where the record ends up, and the destination only decides how it is written. Three are supported today. More are coming, including PIM and web shop platforms.
Doclane writes to standard objects through the official APIs. Your setup, dimensions and approval flows work exactly as before.
Business CentralDoclane works against Uniconta through the official API and follows the chart of accounts and dimensions you already have in place.
UnicontaDoclane connects to e-conomic through Visma's REST API and creates records in the customer groups and chart of accounts you already use.
e-conomicRunning something else? Write to us. New destinations get built when a customer needs one, not when a roadmap says so.
Doclane reads the document the same way every time. What happens after that is yours to assemble: one branch per document type, and in each branch the steps the case needs. Create in the ERP, send a reply, ask a colleague, or stop and wait for a decision.
Sales order, return order, credit note, customer record or item, in the destination you use.
A template with fields from the document: order number, order lines, amounts and the document number from the ERP.
Carry the branch on only if something holds. Are there photos on the claim, for instance?
By the customer, by the sales rep or by an administrator, before anything is posted.
Company register and VIES, plus company data such as status, address, key figures and owners.
A spreadsheet, for example, generated and forwarded to finance automatically.
Claims alone can run to nine scenarios: shortage, damage, overage, wrong item and sales credit, each with its own decision about a credit note, a return or a new invoice.
Send us two or three of the orders you receive by email. At the demo you will watch them go from inbox to finished order in your own system. 30 minutes, no obligation.
Book a demoBuilt in Denmark by people with 20 years of experience in ERP integrations.