Your business runs on four things. Suntel360 builds all four, to one standard.
Suntel360 is ERP, HRMS, ATS and CRM software from Suntel Global: four independent multi-tenant products for stock and accounts, payroll, hiring and sales, built and supported by one engineering team.
Record types in each product
Sample data- ERPSI-0771Sales InvoiceSUBMITTEDPosted to the accounts the moment it was raised. It cannot be edited from here.
- HRMSLVE-3320Leave RequestAPPROVEDBalance committed. Carries through to attendance and the next payroll run.
- ATSAPP-8842ApplicationINTERVIEWStage four of six, with the screening score and interview feedback attached.
- CRMDEAL-1290DealNEGOTIATIONWeighted into the forecast at the probability set for this stage.
Order to Ledger
Inside ERP: a quotation becomes a sales order, then a delivery and an invoice that each post to the general ledger.
Quotation submitted
The quotation is submitted and locked. A change after submission means cancelling it and amending a new version, so the history stays intact.
Sales order from the quotation
The sales order is created from the submitted quotation, carrying the customer, items and prices across.
Delivery note issues stock
A delivery note is created from the sales order. Submitting it issues the stock and, where perpetual inventory is enabled, posts the stock movement with its cost of goods sold.
Sales invoice posts the receivable
The sales invoice is created from the sales order. Submitting it writes the receivable and the revenue to the general ledger in the same transaction.
Stock issued, invoice raised, and every ledger line posted by the documents themselves.
Attendance to Payslip
Inside HRMS: biometric punches become daily attendance, which the payroll run reads before payslips go out.
Device punches synced
A scheduled job pulls punch records from each ESSL biometric device and files them against the matching employee record.
Daily attendance resolved
Shift rules pair each day's punches, and hours worked set the daily status: present or half day, with late as a separate flag.
Payroll run created
An authorised operator creates the payroll run, which rebuilds each employee's attendance figures first. Missing holidays block the run until someone acknowledges them.
Payslips emailed
Payslips are generated as PDFs for the run and emailed to each employee.
Payroll calculated from reconciled attendance, and each employee emailed their own payslip.
Job to Offer
Inside ATS: a job opens with its hiring team, applications are screened, interviews held and an offer made. The hiring team syncs to HRMS.
Job opened with its hiring team
A recruiter opens the job and assigns the hiring team. The assignment syncs to each member's HRMS employee record, the one live link between Suntel360 products.
Application screened
A recruiter runs a resume analysis on the application. It always includes a rule-based skills match, and adds an AI match score where your organisation has switched AI screening on.
Interview scheduled
Interviews are scheduled once the application reaches the interview stage, and each interviewer records feedback against it.
Offer made and accepted
The offer is created in ATS and its status tracked through to acceptance, with the appointment letter sent from ATS.
Offer accepted. Candidate data stayed in ATS; only the hiring-team assignment reached HRMS.
Contact to Forecast
Inside CRM: a contact becomes a deal, a meeting moves it on, and the weighted forecast updates.
Contact created
A contact is added by hand, by bulk import, or as a lead from the website chatbot.
Deal opened
A deal is opened against the contact and moves through the stages your team configured, each with its own win probability.
Meeting completed
A meeting is scheduled against the deal and marked complete once it has happened.
Weighted forecast updated
The forecast multiplies each open deal's value by its win probability (the stage's, unless the deal sets its own) and groups deals closing in the period into commit, best-case and pipeline bands.
While the deal is open and due to close in the period, it counts at its own win probability, or its stage's if it has none.
What changes
What running your back office on this actually feels like
Six things that change, each one shown rather than asserted. No percentages, because we have not measured yours — pick any of them and watch what it means.
Scattered entries, already filed by the time you close
Stock movements, invoices, payments and depreciation all post as they happen. Closing the books becomes a review rather than a reconstruction, because the entries were written when the events occurred.
Two teams, two screens, one figure
The figure your operations team sees and the figure your accountant sees come from the same record. There is no export, no reconciliation step, and no argument about whose spreadsheet is current.
Entered once, carried the length of the chain
A quotation becomes an order, an order becomes a delivery, a delivery becomes an invoice. Biometric punches become attendance. Each handoff carries the data forward instead of asking somebody to enter it again.
Every change, with who and when
Who approved this, when did it change, why was this cancelled, which batch did that go out in. These are answerable from the system months later rather than from memory.
The same screen, seen by three different roles
People see what their role allows. Managers see their teams. Private documents stay private. Changing someone's access takes effect immediately, not the next time they sign in.
Hardware you no longer own, replaced by a browser tab
It runs as a managed cloud service. There is no hardware to buy and no operating system to patch. Your team uses a browser.
Who it is for
Find the operation that looks like yours
ERPCore
BOMWork orderJob costLedger
HRMSLight touch
ATSNot used
CRMNot used
Manufacturing
Manufacturing
You make things to order or to stock, and the gap between what the shop floor knows and what accounts knows is filled in by hand at month end.
- Bills of materials and routings that turn into scheduled work
- Raw material, work in progress and finished goods valued as they move
- Job costing that reaches the accounts without re-keying
- Shift attendance from the same biometric devices you already own
Distribution and trading
Stock sits across several locations, prices differ by customer, and nobody can say what margin a specific order actually earned.
- Multi-warehouse stock with batch and serial tracking
- Customer-specific price lists and tax handling
- Order to cash from quotation through payment, in one chain
- Reorder rules that fire off real balances, not a monthly guess
Services and projects
Your cost is people and time, and profitability per project is a spreadsheet somebody rebuilds every quarter.
- Projects and tasks with timesheets that carry a cost
- Billing tied to the work that was actually delivered
- Leave and attendance kept on the same employee record in HRMS
- Client relationships and pipeline in one place
Staffing and recruitment
You hire continuously, at volume, and the hiring pipeline lives somewhere completely separate from the employee records.
- A candidate pipeline from application through offer
- Recruiters who sign in with their existing employee account
- Hiring-team assignments reflected on the employee record
- A talent pool that survives a single rejection
Multi-entity groups
Several companies under one roof, each with its own books, and each entity's books sit in a different currency, revalued by hand at month end.
- Each entity isolated with its own accounts and calendar
- Its own currency and exchange-rate handling
- One vendor relationship across every entity
- Consistent roles and permissions everywhere
The four products
Each one deep enough to run the function it names
Not four thin modules behind one brand. Each carries its own records, its own process and its own access model — and each is worth buying on its own.
Order to cash · ERP
Sample dataFollow one order all the way into the ledger
01 / 05
Quotation
A price offered, nothing committed. Quotations carry no ledger impact — an offer is not a transaction, and pretending otherwise is how forecasts end up in the accounts.
No ledger impact
General ledger
USD— no entries —
Sales Order
The customer accepts. Still no posting: an obligation to deliver is not revenue. What changes is that the order now anchors every document after it.
No ledger impact
General ledger
USD— no entries —
Delivery Note
Goods leave the warehouse. Where perpetual inventory is enabled, this is the first posting in the chain — stock value moves to cost of goods sold, under the STOCK voucher type.
Posts as STOCK
General ledger
USD| Dr/Cr | Account | Amount |
|---|---|---|
| DR | Cost of Goods SoldCOST_OF_GOODS_SOLD | 6,400.00 |
| CR | Stock in HandSTOCK | 6,400.00 |
Debits equal credits
Sales Invoice
Revenue is recognised and the customer owes you. The receivable created here is what the payment entry will later settle against — by document, not by guesswork.
Posts as SALES_INVOICE
General ledger
USD| Dr/Cr | Account | Amount |
|---|---|---|
| DR | Trade DebtorsRECEIVABLE | 9,600.00 |
| CR | Sales RevenueINCOME_ACCOUNT | 9,600.00 |
Debits equal credits
Payment Entry
Cash arrives and is allocated against the invoice. The receivable clears, the cycle closes, and every posting still names the document that caused it.
Posts as PAYMENT_ENTRY
General ledger
USD| Dr/Cr | Account | Amount |
|---|---|---|
| DR | Bank AccountBANK | 9,600.00 |
| CR | Trade DebtorsRECEIVABLE | 9,600.00 |
Debits equal credits
How it compares
Against a spreadsheet, and against four separate tools
Including the two rows where we are not the obvious answer. A comparison table that wins every row is not a comparison table.
150 record types across the suite
Hover to pause
Getting started
What buying this actually involves
Implementation is the part most vendors under-scope. Here is the real shape of it, before you ask.
- Before you commit
A working session on your own scenarios
Not a canned demo. You bring real situations — your chart of accounts, a typical order, a hiring round — and we run them. If something does not fit, this is where you find out, from us.
- Scoping call to understand structure and volume
- Working session against your scenarios
- Written quote, with what is and is not included
- Security review support if procurement needs it
HONESTY CHECK:What most vendors skip: telling you plainly what their system cannot do before you sign. - First few weeks
Configuration and migration
We set up the structures your organisation actually uses, and bring across the data you are keeping. This is the part most vendors under-scope; we would rather price it honestly up front.
- Chart of accounts, fiscal calendar and cost centers
- Warehouses, items, price lists and tax templates
- Employees, shifts, leave policies and biometric devices
- Roles and permissions mapped to your reporting lines
- Migration of opening balances and master data
HONESTY CHECK:What most vendors skip: honest scoping of historical data migration complexity. - Go live
Run in parallel, then switch
You keep the old process running alongside for a cycle so nobody is betting a month end on a first attempt. When the numbers agree, you stop doing it twice.
- Team training by role, not one long session for everyone
- A parallel cycle against your existing process
- Reconciliation of the two before cut-over
- Direct access to the team during your first close
HONESTY CHECK:What most vendors skip: parallel running. They switch systems cold and hope month-end balances match. - Afterwards
Support from the people who built it
The same team that wrote the software supports it. There is no partner network in between, which means a real problem reaches someone who can change the code.
- Email support on every plan
- Priority support and a named contact on larger agreements
- Agreed response commitments where you need them
- Configuration help as your structure changes
HONESTY CHECK:What most vendors skip: direct engineering support without an offshore partner network in between.
Why us
Four reasons this is different from the last evaluation you ran
One vendor, four products, no finger-pointing
When something breaks between two systems, the usual answer is that each vendor blames the other. There is only one team here, and it is accountable for all four products.
We tell you what is not built
This site says plainly that the products do not share a database, that a hired candidate does not yet become an employee record automatically, and that forecast bands are not configurable. You will find those limits here rather than in month three.
Built for organisations, not for a demo
Multi-entity, multi-currency, multi-warehouse, role-based access and immutable financial records are in the product because real deployments needed them.
Buy only what you need
The four products do not depend on each other. Start with one, add another when there is a reason to, and never pay for a suite you are not using.
Under the hood
Not a database. A way of building.
The four products do not share tables or a login. What they do share is the engineering standard underneath them — and for an enterprise buyer, that is the part that determines what the next five years cost.
Managed cloud, defined in version control
Every product runs as a managed cloud service, defined in version-controlled templates. There is no server for your team to patch.
Multi-tenant isolation in every product
Every request is scoped to your organisation. In ERP the tenant is part of every storage key; in HRMS, ATS and CRM the organisation is checked on the records each request returns. Every record belongs to exactly one tenant.
Access checked on every request
In ERP, HRMS and CRM, permissions resolve fresh against a live lookup on each request rather than being baked into a long-lived token — so revoking access takes effect on the next call, not the next login. ATS has no login of its own and authenticates against the same HRMS employee record.
State machines, not status fields
Documents move through defined states with defined transitions. A submitted record is not edited in place; it is cancelled and superseded. That is what makes an audit trail worth reading a year later.
Audit logs kept separately from the record
In HRMS, ATS and CRM, history is written to its own log rather than inferred from the current state of a row, so who changed what survives every later edit.
One vendor accountable for all four
The same team builds, deploys and supports every product to the same operational standard. There is no integration partner to escalate through when two products disagree.
Your IT team will want more than this. See the full architecture or read the security page.
Straight answers
The questions evaluators actually ask
Including the ones where the answer is no.
Is this one product or four?
Four. Each runs as its own multi-tenant service with its own tables and its own access control. We could describe it as one platform, but a technical evaluator would find out otherwise in the first architecture call, so we say it plainly instead.
Do the four products share a database or a single login?
No. There is no shared database, no common ledger across products, and no suite-wide single credential. The one live connection is ATS authenticating recruiters against HRMS employee records and syncing hiring-team job assignments back.
Then why buy them together?
Because they are built, deployed and supported to one standard by one team, and because the one integration that exists is one we own end to end. If you only need one, buy one — the products do not depend on each other.
Can we start with one product and add others later?
Yes. Each product stands alone, so adoption order is yours to choose. Adding a second later does not require re-implementing the first. Each product keeps its own data and access control, so the first one carries on unchanged; the only built-in link is ATS using HRMS for recruiter sign-in and hiring teams.
What is on the integration roadmap?
Any further links are on the roadmap, not live. We publish what runs today rather than what is planned, so this page will change when the code does.
How is it priced?
Per product, quoted against your organisation's size and the modules you actually need. There is no published price list and no self-serve trial — enterprise deployments differ too much for either to be honest.
Where does the data live?
In an encrypted, managed database scoped to your organisation. Region questions are answered directly on request, and we will walk your security team through the topology under NDA before you commit.
Can we see it running?
Yes. A working session against your own scenarios is how these evaluations should go — talk to sales and we will set one up. Bring a real process, such as an order, a payroll cycle or a hiring round, and we will run it in the product with you rather than show slides.
See Suntel360 on your own business scenario
Not a canned demo. You bring a real situation — your chart of accounts, a typical order flow, a hiring round — and we show you how the system handles it.