Your ERP is live. Next step: connect the shop floor and the bank

Version 1.0 — Last updated: October 29, 2026

What should come after an ERP go-live? Stop keying in shop-floor, warehouse and bank data by hand after the fact. Production reports should come from the shop-floor MES, warehouse movements from a barcode device, and bank transactions from the bank, each turning straight into an ERP record. Then the figure in the ERP comes from the event itself.

When an ERP goes live, a company's records finally sit in one place. Yet in many Turkey-based companies a large share of those records is still keyed in by hand, after the fact: the production form filled in at the end of a shift, the stock count copied from a spreadsheet in the evening, the bank statement downloaded from online banking the next morning. This post explains why that gap is the ERP's weakest point, and how the shop floor, the warehouse and the bank can be connected to it.

ERP users are still a minority in Turkey

According to the Turkish Statistical Institute (TÜİK), 28.3% of enterprises with 10 or more employees used ERP software in 2025. The rate was 23.6% for enterprises with 10–49 employees, 46.0% for 50–249 and 76.5% for 250 or more. Eurostat puts the EU figure for the same year at 46.45% (both count enterprises with 10 or more employees; the sectors they cover are not identical).

So a Turkish company that runs an ERP is already in the minority. But having an ERP does not mean data reaches it at the right time, from the right source.

The weak point: records entered after the event

Eurostat describes ERP as software delivered in modules that integrate processes such as planning, purchasing, sales, finance and human resources, and defines internal integration as sharing information electronically and automatically between business functions. The key word is "automatically".

When a record enters the ERP hours after the event, typed in by someone, three things happen:

• Delay. Between the event and the record, the ERP shows an old figure, and planning, stock and cash decisions are made on it.
• Transcription errors. Every line retyped from paper or a spreadsheet can be entered wrongly.
• Duplicate data. The same information is kept first on a form or sheet, then in the ERP. When the two drift apart, people argue about which is right.

That is why the step after an ERP is not another module, but data flowing into it from the source. The gap shows up most often in three places: the shop floor, the warehouse and the bank.

Shop floor: production reports from the MES to the ERP

The international ISA-95 standard (Enterprise-Control System Integration) describes this link. Its Part 2 specifies the information exchanged between level 3 manufacturing systems and level 4 business systems, with the stated goal of reducing the risk, cost and errors of implementing that interface (ISA). Put simply, work orders go down to the floor, and production and downtime data come back up.

MES for Workcube does this on the side of Workcube, a Turkish ERP platform. It sends work orders and operations to the floor from one screen. From start/finish reports it creates the production result and operator time, and issues production output and consumption vouchers automatically. A downtime report opens a breakdown record on the machine asset card, and every request is logged. Today it works with trex Dijital's shop-floor MES; because the Workcube side is not written for one specific MES, the ERP side does not have to be rewritten if the MES changes.

What it does not do: OEE calculation, quality control, lot/serial traceability and scheduling are not part of this product.

Warehouse: movements from barcode to ERP

In the warehouse, after-the-fact data usually means paper pick lists and spreadsheet counts. According to GS1, barcodes carry identifiers such as product, shipment and location, and attributes such as batch/lot numbers, serial numbers and dates, in a form that can be scanned electronically. The information is already on the product; the question is who carries it into the ERP, and when.

WAMS Logistics is a Workcube add-on that moves warehouse and field work from paper to a barcode device. Shipment checks are done by scanning the product barcode, shelf location, lot and quantity in turn. The office plans the shelf, lot and quantity allocation, the floor carries it out, and the picked quantity is written back to Workcube. Stock counts and transfers are done on the device; a count arrives in Workcube as a document awaiting approval. When there is no connection, transfers are queued.

What it does not do: goods receipt, put-away, packing, creating dispatch notes or invoices, and serial-number tracking. A count does not correct stock by itself.

Bank: transactions from the bank to ERP records

At the bank, after-the-fact data means posting a downloaded statement line by line. Sharing bank data through regulated services is also growing in Turkey: according to a 2026 press release from the Central Bank of the Republic of Türkiye (CBRT), the open banking ecosystem has reached 16.4 million users and an average of 12.3 million transactions a day, with 53 participants.

Wodiba is a family of Workcube add-ons that brings banking work into Workcube, connecting to banks through Gramoni's open banking infrastructure. Bank transactions arrive automatically, several times a day, and a record and accounting voucher are created for 18 transaction types. The counterparty is matched by tax ID number (VKN), IBAN or a description rule. A transaction it cannot decide on is not guessed: it is listed with the reason, and every decision is logged. The difference between the bank and Workcube is shown on one screen.

Where to start

Start where data is most delayed. A few questions help:

1. Which figure does everyone check in a separate spreadsheet before the morning meeting?
2. Which records are entered in bulk at the end of a shift, day or month?
3. Is the master data ready? For the bank, customer and supplier cards need clean tax IDs and IBANs; for the warehouse, barcodes and shelf locations; for the shop floor, a clear work-order and operation structure.

The third question is often the first job: data flowing from the source is only as good as the master data in the ERP.

If you want to talk about connecting your shop floor, warehouse or bank to Workcube, book a call with Turkey-based Gramoni.