Employee records
Employee records for the personnel information your business is authorised to maintain.
- Records to define
- Employee profiles and employment references
- Review together
- Required fields, privacy, access and retention
Bring people operations together. A modular toolkit designed for teams across industries.
Monthly plans apply to each selected MicroERP. An industry ERP can combine several modules; agree the selected apps and implementation scope. Lifetime licensing and self-managed software are available by quote.
HR & Payroll Pro is a proposed focused workspace for HR & Payroll. Bring people operations together. Its starting scope centres on Employee records, leaves, attendance, payroll; the goal is to connect those records and handoffs in one agreed workflow rather than add every possible module.
This is a planned Micro-ERP concept. The details below describe a requirements starting point, not a running application or a confirmed delivery commitment. Your proposal confirms the modules, permissions, reports, integrations and acceptance criteria.
Each item below is a scope discussion for this concept. Agree the screens, business rules and acceptance checks before development.
Employee records for the personnel information your business is authorised to maintain.
Leave requests and decisions linked to the employee and period involved.
Attendance records for the people, sessions or shifts included in your workspace.
A payroll preparation scope based on the records and calculation rules you approve.
Workspace settings for the fields, stages and responsibilities confirmed in your scope.
Reports whose fields and export formats are agreed before implementation.
Defined permission boundaries for the roles using the agreed app scope.
A proposed daily journey. Your team's exceptions, approvals and handoffs shape the final version.
Proposed handoff: Employee records for the personnel information your business is authorised to maintain. Agree required fields, privacy, access and retention and who may complete or correct this stage.
Proposed handoff: Leave requests and decisions linked to the employee and period involved. Agree eligibility, balances, approvers and exceptions and who may complete or correct this stage.
Proposed handoff: A payroll preparation scope based on the records and calculation rules you approve. Agree jurisdiction-specific rules, deductions and authorised release and who may complete or correct this stage.
Review leave and attendance review and payroll preparation with the authorised team. Agree how incomplete work, corrections and exports should be handled.
Proposed roles; confirm access, approval authority and audit requirements for your business.
Proposed responsibility: approve workspace settings, invite authorised team members and confirm which permissions each role receives.
Proposed responsibility: maintain the day-to-day Employee records records within the agreed viewing and editing permissions.
Proposed responsibility: review the leaves and attendance and payroll handoffs and exceptions assigned to this role.
Proposed responsibility: review the agreed measures and export only the records permitted by the access policy. Roles can be combined for a small team.
Define the fields, ownership and retention of these proposed records.
Proposed report: confirm the source records, filters, reporting period, calculation rules and authorised audience. The fields and export formats are agreed in the proposal.
Proposed report: confirm the source records, filters, reporting period, calculation rules and authorised audience. The fields and export formats are agreed in the proposal.
Connection scope depends on available APIs, permissions and a tested data mapping.
Discuss importing the Employee records and leaves records you already maintain. A sample file, field mapping, duplicate rules and reconciliation checks are needed before any migration is confirmed.
List the systems, payment services, peripherals or data feeds you need. Each connection requires documented access, a supported API or interface, permission review and separate acceptance criteria. No particular connector is guaranteed by this listing.
Planned: supported file exports to a customer-owned drive or supported structured records to a customer-owned database. Connector support, schema, access, sync direction and retained hosted copies are confirmed in your proposal; provider costs remain yours.
Planned built-in Intellistra assistance, approved automation and custom workflow design use separately purchased usage credits. AI, SMS, WhatsApp and other metered online actions need agreed channels, permissions and a published rate card before use.
Use managed, shared server infrastructure with a monthly or lifetime licence. Server service is separate from the licence. Included storage, actual GB-month overage, backups and support need agreed terms.
Choose a dedicated server environment with a monthly or lifetime licence. Capacity, server fees, administration, updates, backups and support responsibilities are confirmed separately in your quote.
Purchase a distinct one-time software package for your own environment. Licence rights, package contents, handover, maintenance and support are agreed before purchase. Your team pays its infrastructure and storage costs.
A hosted lifetime licence covers the agreed software scope without recurring licence renewal. Shared or dedicated server service, paid usage, storage overage, updates and support remain separate under the agreed service terms.
AI, SMS, WhatsApp and other agreed metered actions use purchased usage credits. Core app workflows do not require those extra-action credits. Cloud storage overage is measured separately in actual GB-months; it is not an AI or messaging credit charge.
Your final quote must confirm the included storage quota, GB-month rate, credit rate card, measurement rules and service terms. No numeric quota or usage rate is approved here. Checkout, a credit wallet and storage billing are not currently available on this website.
Review licensing & usage · Read planning terms · Build my requirements brief
After initial online setup, use configured core workflows and locally available data on your device offline. Reconnect and verify your system to sync saved changes.
Planned for upcoming Micro-ERP releases. Availability and implementation must be confirmed in your final proposal.
After initial online setup, keep using configured core workflows and available data on your device. Save changes locally during an internet interruption, within the 48-hour verification window.
After successful online service verification, pending local changes sync with your configured system and agreed destinations. Any conflicts stay visible for review.
Your system must verify with the authorized service within 48 hours of its last successful verification. Internet access alone does not renew the window. At the deadline, ERP use locks until verification succeeds; pending local changes remain saved.
Use a supported connector for files or exports on your own drive, or structured records in your own database. You control the destination and permissions; scope and sync direction are agreed in your proposal.
You pay your chosen drive/database provider. Any EasyManageX-hosted copies follow your cloud storage allowance and usage charges.
AI, SMS, WhatsApp and other internet-dependent services wait until connected.
The same offline verification policy applies to shared-server and dedicated-server hosted plans, with monthly or lifetime licences, and to self-managed software purchases.
Plan AI assistance, clearer reports and reviewed automation around your business, with a custom workflow design capability shaped for your team.
Planned for upcoming Micro-ERP releases. Intellistra currently presents private-beta prototypes; included capabilities and supported integrations need final proposal confirmation.
Plan an assistant that answers business questions using approved, configured ERP context. Access stays within the records and permissions agreed for your build.
Explore management summaries, receivables insights and purchase-approval context from supported read-only records. Reporting coverage is confirmed for your integration.
Plan supported tasks and follow-up workflows with review, permissions and approval steps. Record-changing actions need a validated implementation before they become available.
A planned EasyManageX capability to shape custom steps, roles, rules and approvals around your process. Your final proposal defines the designer and supported execution scope.
Use reviewed Assistant and AutoConnect concepts to plan connections and field mappings. Connector availability, schema and approved access are agreed before integration.
Plan identity, scoped permissions, approval checkpoints and audit history for AI-assisted work. You review the authorized actions and boundaries for your workspace.
AI runs on usage credits. Rates, credit rules and included capabilities are confirmed in your proposal.
Intellistra AI needs internet access; AI requests wait while your Micro-ERP is offline.
Approved context, supported connections and explicit permissions define what AI can access or do. Actions that change records require a validated implementation and the agreed approvals.
The form gives an indicative custom development budget and delivery window. A confirmed schedule follows scope review.
Share your industry, the Employee records, leaves, attendance, payroll work you want to improve, active-team band, locations, expected volume and must-have outputs.
Review the local planning estimate and proposal. Final delivery dates, commercial terms, server capacity, licence scope and usage rates need a confirmed requirements review.
Financial, tax, payroll or regulated-process rules need review by your responsible adviser. This concept does not claim automatic statutory compliance. Use redacted sample data for the requirements stage; passwords, API keys and live sensitive records do not belong in the public request form.
An agreed implementation would validate Employee records, leaves, attendance, payroll, role permissions, exception handling, reporting calculations and any approved integrations against your acceptance checklist.
Agree data mapping, opening balances where relevant, staff training, backup responsibilities, rollback and support. Go-live follows acceptance; this catalogue page does not activate or deliver an app.
This listing describes configurable catalogue scope with an illustrative preview. Use its Demo link to review the available primary workspace. Specialized features, integrations and rollout dates require confirmation. Published monthly plans apply per selected MicroERP; industry implementation is quoted separately.
The starting module scope is Employee records, leaves, attendance, payroll, Configurable workspace, Export-ready reports, User permissions. The feature details above explain the records and configuration decisions to discuss. Your confirmed proposal defines the actual screens, fields, permissions, reports and acceptance criteria.
Yes, you can request a tailored scope. Share how your team handles Employee records, leaves, attendance, the exceptions, approval roles and outputs you need. Custom development, integrations and migration are assessed separately rather than assumed to be included in the monthly MicroERP subscription.
The planned choices are shared server or dedicated server with a monthly or lifetime licence, or a distinct self-managed software purchase for your own environment. The quote confirms the active-team band, software scope, server service and support responsibilities; usage credits and hosted storage overage are separate.
Planned: agreed core workflows can continue on a configured device after initial online setup and sync on reconnection. The device must complete service verification within 48 hours of its last successful verification; at the deadline it locks until verification succeeds, preserving pending local work. Supported own-drive or database sync requires an agreed connector and does not replace that verification. These runtimes are not implemented by this website.
Use the request form on this page to describe your workflow, active-team size, priorities and setup preference. It generates a local planning proposal from your editable requirements. After you review it and consent, submitting saves the request and asks the configured service to email the client and team; delivery is not guaranteed. Final price and delivery are confirmed after requirements review.
Start with this concept, edit the requirements, and review an instant development estimate. Add contact details only when you want to email the proposal and request a review.
Your scope notes and workflow are prefilled. Edit them to describe what your business needs; the catalogue concept is a starting point for review.
Manage leads, pipelines and opportunities. A modular toolkit designed for teams across industries.
Solo up to 3 users, Startup up to 15, MSME up to 100; Enterprise on request. One monthly fee per selected MicroERP. AI/SMS/WhatsApp credits and actual GB-month cloud storage overage are separate.
Sell faster with streamlined billing and checkout. A modular toolkit designed for teams across industries.
Solo up to 3 users, Startup up to 15, MSME up to 100; Enterprise on request. One monthly fee per selected MicroERP. AI/SMS/WhatsApp credits and actual GB-month cloud storage overage are separate.
Know what is in stock, where and why. A modular toolkit designed for teams across industries.
Solo up to 3 users, Startup up to 15, MSME up to 100; Enterprise on request. One monthly fee per selected MicroERP. AI/SMS/WhatsApp credits and actual GB-month cloud storage overage are separate.

Organise employee changes, attendance exceptions, leave approvals and payroll cutoffs with a practical input workflow and clear responsibility for unresolved records.
Read the guide
Define service duration, preparation time, resource availability and booking changes before evaluating appointment software for a busy service business.
Read the guide
Review missing punches, overnight shifts, roster changes and attendance corrections against the assigned schedule, with explicit evidence and review boundaries.
Read the guide