EdgeBridge · Devices connected to the ERP

The devices on your floor, talking straight to your books — fingerprint to payslip.

TamilAccounting runs in the cloud; your attendance terminals, RFID readers and printers sit on the shop floor. EdgeBridge is a small gateway installed on site that carries what those devices see into the ERP — a punch becomes attendance, a tag read becomes a sighting of a known item — and carries print jobs back out to the printers on your own network.

Biometric attendance Access cards at the door RFID item tags Asset & tool tracking Stock counts by reader On-site printing
Without a gateway

Where device data goes wrong on the way to the books

Most businesses already own the devices. The trouble is everything between the device and the ERP: exports, spreadsheets, guesses and retyping.

Attendance on a USB stick

Someone downloads punches from the terminal, tidies them in a spreadsheet and keys them into payroll. Every month, the same afternoon of copying.

Cost: payroll that runs late, and typing errors that change somebody’s pay.

“User 41” is anybody’s guess

The terminal only knows a number. Matching it to an employee by eye — or because the digits look similar — files one person’s attendance against another.

Cost: paying the wrong person for days somebody else worked.

New starters missed until payday

A new joiner is enrolled at the terminal but never set up in the ERP. Their punches are dropped quietly and nobody notices until the payslip is short.

Cost: disputes, manual corrections and a team that stops trusting the system.

The cloud cannot see your printer

A cloud ERP has no way to reach a printer or reader on your office network, so documents get emailed to a PC beside the printer and printed by hand.

Cost: a person whose job is to stand between the ERP and the printer.

Tools “somewhere on site”

Costly tools and equipment move between stores, bays and sites. Nobody records where they were last seen, so finding one means walking every shed.

Cost: hours lost searching, and replacements bought for items that were never lost.

One tag, a hundred movements

A reader re-reads a tag for as long as it sits in range. A simple integration turns every read into a stock movement — or a goods receipt.

Cost: stock and ledger figures inflated by reads, not by real movements.

With EdgeBridge

From a finger on a sensor to a line in the ERP

The gateway is a messenger. Deciding who a device id belongs to, and what a read means, is done in the ERP — by rules an administrator sets, never by guessing.

Gateway on siteInstalled on your network, next to the devices
Registered onceIts own key; a connection test names your company
Ids linkedDevice users to employees, tags to items, readers to places
Device readsA finger, a card at the door or a tagged item
Event deliveredOn the Events list within seconds, with the raw data
InterpretedRepeat reads collapsed, unverified matches refused
RecordedClock-in or clock-out, or a sighting at a location
UsedPayroll, stock reconcile and invoices pick it up
How it works

Attendance, tagged items, counts and printing

One gateway, several kinds of device, each one feeding the part of the ERP that needs it.

Biometric attendance

Punches that land on the right employee, every time

You can enrol an employee onto the terminal from the ERP, so the ERP assigns the device id instead of working it out later. The link stays pending until the terminal confirms the enrolment. The Device Users list shows everyone the terminal knows, and which of them are not yet linked to an employee.

  • Each punch becomes a clock-in or clock-out on the employee’s daily attendance
  • Repeat presses within a minute (you choose the gap) are ignored, not counted twice
  • Unverified matches and demo events never become attendance
  • Punches are filed at the time the terminal recorded, even if they arrive later
  • Link a new device user and their earlier punches are read again — nothing is lost
HR & payroll
RFID tags & read points

Know where every tagged item was last seen

A tag only tells you what passed. What a read means comes from where it happened: each read point — a reader and antenna — is given a purpose and a location by an administrator. Rewire the antennas and nothing moves the wrong way, because nothing was assumed.

  • Tags linked to items, assets or employee access cards — one at a time, many at once or from a spreadsheet
  • Read points for asset tracking, a door, a billing counter, or reads you want ignored
  • A tag sitting in range is one visit, not hundreds of reads; you set the window
  • Unknown tags and readers are listed with the link to add, never silently dropped
  • An access card at a door clocks the employee in or out, like a fingerprint
Counts & the billing counter

Count a showroom in minutes — and you still decide what posts

Open a count on a location and sweep it with a reader. Every read there goes into the count instead of becoming a sighting. When you close it, the ERP shows what the reader found, what it expected to be there and any tags it does not know. You push the lines you accept into Inventory Reconcile, which makes the adjustment as usual.

  • One open count per location, with each tag counted once however often it is read
  • Found, expected and unknown side by side — a missed read is not booked as a loss
  • At the billing counter, tagged pieces laid on the reader collect in a basket
  • Saving the sales invoice frees the tags of the pieces billed, up to the quantity sold
Inventory in detail
Gateway console & printing

See every message, and print to the printer down the hall

Every request a gateway makes, every event it delivers and every command sent back is listed, with the raw data and what the ERP did with it: processed, ignored with the reason, or an error. Nothing happens out of sight.

  • Inbound requests, Events and Outbound commands, each with its own filters
  • A printer on your own network can be reached through the gateway — print profiles keep sending each report to its printer
  • Commands are queued and show when the device has acknowledged them
  • You choose how long events and request logs are kept
Also included

Built to be trusted with attendance and stock

Pay and stock are worked out from what the devices report, so the safeguards matter as much as the features.

A key per gateway

Each gateway has its own registration key, shown once when you create it and stored only in scrambled form. A wrong key is refused.

Limits on every gateway

An hourly request limit and a maximum batch size per request, so a faulty device cannot flood the ERP.

Pause without losing data

Switch off accepting events and the gateways keep what they have queued, delivering it once you switch back on.

Demo events kept out

Events from the gateway’s simulator are refused unless you turn them on for a demonstration — a demo can never become real attendance.

Several sites, one company

Links can be specific to one terminal, one gateway or the whole company, so two branches can each have their own “user 1”.

Where each punch came from

HR’s daily attendance names the gateway or door for each device punch, next to ERP logins, portal clock-ins and hand entries.

Link in bulk

Link device users and tags one at a time, many at once on a single screen, or from a spreadsheet you already have.

An overview at a glance

Events today, which gateways are reporting and when each was last seen, events waiting, errors and refused requests — on one screen.

Watch it in action

From the gate to the payslip

The full HR walkthrough — attendance, leave and payroll — and a short on how one fingerprint at the gate reaches the payslip. Recorded on a demo company.

Quick takes · under a minute or two
Who it is for

Businesses whose devices already know the answer

If a terminal or reader on your floor already records it, EdgeBridge gets it into the ERP without anyone retyping it.

01

Factories and plants

Shift workers punching at the gate, with attendance flowing to payroll instead of through a spreadsheet.

02

Multi-site businesses

Terminals at several branches behind one or more gateways, each branch’s device ids kept apart.

03

Showrooms with tagged stock

Jewellery, apparel and other tagged pieces counted with a reader and freed at the billing counter.

04

Workshops and tool cribs

Costly tools and equipment with a tag, and a record of where each one was last seen.

05

Offices with local printers

Delivery notes, invoices and pick lists sent from the cloud ERP to the printer on your own network.

06

HR and payroll teams

No more monthly export: every punch is already on the employee’s attendance, with its source shown.

Why businesses stay

Bring your data. We’ll keep it right — and keep making it better.

Switching software is the hard part. We help you move, keep your records sound, and keep improving the system with you.

Data migration & opening balances

Move across from Tally, Zoho, QuickBooks, Xero, Sage 50 or SMACC, or from Excel templates for items, customers, suppliers, employees, chart of accounts and opening balances. You preview every row before it is saved — and our team helps you through it.

Your data, kept right

Your database is backed up three times a day — every 8 hours — and your files are backed up too. Each company keeps its own separate database; roles decide who can see, enter, approve or void; every change is on the audit trail; and everything exports to Excel or PDF whenever you want it.

Always improving, with you

We follow up regularly with the businesses that use it, and their requests become features. Updates arrive on your account automatically — nothing to download or reinstall.

Connected to what comes next

GST e-invoice and e-way bill, ZATCA, WooCommerce, WhatsApp, biometric devices, online payment gateways, mobile apps and an AI assistant — and new connections are added as the market moves.

FAQ

EdgeBridge: common questions

Each verified punch from a linked device user is recorded as a clock-in or clock-out on that employee’s attendance for the day, at the time the terminal recorded it. That is the same attendance HR sees in Daily Attendance and payroll is worked out from, so there is no export or import step. HR can still correct an entry by hand.

It is kept, not thrown away. The event is marked as ignored with a message naming the device user, and the Device Users list shows everyone the terminal has enrolled who is not yet linked. When you link them, their earlier ignored punches are read again and recorded.

No — a read on its own never posts. Asset tracking records a sighting of the item at a location. A count shows found, expected and unknown tags, and only the lines a person pushes into Inventory Reconcile become a stock adjustment, with the usual accounting entry. At the billing counter, the sales invoice does the selling, the stock movement and the ledger entry; EdgeBridge only frees the tags of the pieces billed.

Each event carries the time the device recorded it, and that is the time the ERP files it under — a punch delivered late still lands on the right day. When the ERP is set not to accept events, the gateways keep what they have queued and deliver it once events are accepted again.

EdgeBridge has its own permissions: one to watch the traffic and events, one to manage gateways, keys and links, and one for settings. So a supervisor can follow what is arriving without being able to change who a device id belongs to.

Biometric attendance terminals, RFID readers and network printers on your site, through the gateway. Tell us the models you have and we will confirm before you buy anything.

Let your devices do the data entry.

Start free with HR and inventory, then connect a gateway when you are ready to bring the terminals and readers in.

Global Coverage

Multi-Country ERP — One Platform

Supports GST (India), VAT (UAE, South Africa, Egypt, Iraq, Botswana), and local compliance across all regions.

🇮🇳 India (GST)
🇦🇪 UAE (VAT)
🇸🇦 Saudi Arabia
🇶🇦 Qatar
🇧🇭 Bahrain
🇴🇲 Oman
🇰🇼 Kuwait
🇪🇬 Egypt
🇮🇶 Iraq
🇿🇦 South Africa
🇧🇼 Botswana
🇲🇾 Malaysia
🇸🇬 Singapore
🇦🇺 Australia
🇬🇧 United Kingdom
🇺🇸 USA
🌏 & More Regions