Start with your overview
Use the dashboard to orient yourself, review business activity and follow the navigation to the work assigned to your team.
Use this step-by-step guide to understand where work happens, what to check before you act, and how each team's work affects the rest of the business.
Empowa360 connects the records teams use every day. What you can see and do depends on your role, permissions and branch access.
Use the dashboard to orient yourself, review business activity and follow the navigation to the work assigned to your team.
Customers, products, invoices, stock and employee records are used across related workflows. Check the record details before taking action.
Many processes move through clear stages, such as a quotation to an invoice or a purchase order to a goods receipt. Complete or approve each step you are authorized to perform.
The same simple routine helps whether you work in sales, operations, finance or another team.
Menu labels and available actions can vary by language, role and configuration. If an area is missing, first check your branch and ask whether your role has the required access.
Choose a workflow to understand what it is for and how it connects to the rest of the business.
CRM keeps customer and lead information and activity together. Follow a lead through the pipeline, then continue with the customer in Sales.
Typical flow: Lead → customer → quotation → sales order.
Sales manages quotations, orders, invoices, payments, credit notes and returns. Each stage gives the team a clear view of the customer transaction.
Typical flow: Quotation → order → invoice → payment.
POS is the cashier workflow for in-person sales. A cashier works in a register shift, adds products, records payment and provides a receipt.
Remember: A register needs an open shift to make sales.
Explore POS features →Inventory organizes products and tracks quantities by warehouse. Stock movements record changes such as receipts, sales, transfers and adjustments.
Useful check: Review available stock at the relevant warehouse before fulfilling work.
Explore inventory features →Purchasing links supplier records to requests, orders, receipts, supplier invoices and payments. Receiving goods updates the stock workflow.
Typical flow: Request → purchase order → goods receipt → supplier invoice → payment.
Finance tracks accounts, income, expenses, transfers, budgets and balances. Accounting organizes journal entries and produces the general ledger and financial statements.
In short: Finance records money movement; Accounting provides the formal ledger view.
Explore finance features →HR maintains employee, attendance, schedule and leave information. Payroll uses employee and compensation details to prepare payroll runs and payslips.
Separate responsibilities: HR maintains people records; Payroll handles pay runs.
Explore HR features →Projects bring projects, tasks, milestones and timesheets together. Billable time can inform customer invoicing.
Explore project features →Support tickets help teams organize requests, assign work, reply to customers and track service targets. Internal notes are for staff, not customer replies.
Marketing supports campaigns and promotions; Partners tracks agreements and referrals; Assets tracks company equipment, assignment and maintenance.
Explore asset features →Reports summarize activity across business areas. Imports and exports help move supported records in or out, subject to your access and branch scope.
Branches organize operations, while warehouses and POS registers are associated with branch activity. Your branch access affects the records available to you.
Follow the sequence, check the result, and stop if a record or amount does not match the real business event.
Result: The customer has a traceable sales record; the invoice balance reflects payments, and related stock or accounting effects follow the configured workflow.
Use POS instead when the sale is a cashier checkout at a register. Avoid recording one customer payment in both POS and Sales.
Remember: POS records the sale, payment and related stock movement together. For a refund, find the original sale and use the refund workflow; do not make an unrelated negative sale.
Do not edit stock as a shortcut. Sales, POS, Purchasing, transfers and approved adjustments should create the movement record that explains why stock changed.
Keep the documents aligned: Purchase order = what was ordered; goods receipt = what arrived; supplier invoice = what is owed; payment = what was paid.
Corrections: Posted accounting entries should be reversed or corrected through the authorized workflow, not erased. Closed fiscal periods restrict new postings for dates within that period.
Protect confidentiality: Payroll and employee records contain sensitive information. Use only the access needed for your role and share payslips only with authorized recipients.
Useful hand-off: Link the supporting customer or transaction record instead of copying sensitive details into unrelated notes.
This example shows how different teams can contribute to one business outcome. The exact actions depend on permissions and the organization's workflow.
Choose the report for the question you need to answer, then set the correct date range, branch and other available filters. Check the report title, period, currency and totals before sharing it.
A report summarizes records; it does not replace checking a disputed source transaction.
Use Imports for a supported CSV, XLSX or JSON file. Upload it, map each file column to the intended field, review the preview and validation errors, then confirm only when the sample rows and totals make sense.
Review the import report afterward. Correct or revert only through the supported import workflow; financial transactions have additional restrictions.
Use Exports to select a resource and format. The exported data is limited by the permissions and branch scope of the user running the export.
Store and share the downloaded file as confidential business data; it may contain personal or financial information.
Check that you are signed in with the right account and branch. Access is permission-based and many records are branch-scoped. Ask your administrator to confirm access; do not use another person's login.
Check the selected product, variant, warehouse and available quantity. Available stock may exclude units reserved for another order or cart. Do not retry by creating an untracked stock increase.
Do not click submit again immediately. Return to the relevant list or search for the record using its reference, customer or date. Check status and amount before deciding whether another action is needed.
Find the source invoice, payment, expense or supplier record. Check dates, branch, account, reference and whether a duplicate was recorded. Use the authorized correction, refund, return or reversal workflow.
Check the message status in the relevant email logs or outbox, if available to your role. Confirm the recipient address and ask the responsible administrator to review delivery configuration or retry policy.
Read the message and record status. The action may require approval, a prior step, a different permission or an open fiscal period. Do not change dates or bypass approvals to force it through.
When escalating an issue, share the module, record reference, branch, date, exact message and steps already tried. Do not send passwords, payment credentials or unnecessary personal data.
Check that you have the right customer, supplier, product, branch and date. Read the record status and confirm the action you are about to take.
Your role may not have permission, or the record may need another workflow step first. Ask your organization's Empowa360 administrator or process owner.
Use the appropriate correction, return, reversal or approval workflow rather than trying to hide the original business activity.
Use approved sample records and demonstrate the tasks relevant to each role. Avoid exposing confidential customer, employee or financial information.
Explore Empowa360 with a guided product demonstration.