Professional services: how-to handbook

Salon demo: 4 appointments in Booked, Arrivals, In service and Completed. Choose a record and inspect History & next action before progressing it.

1. Administrator: select the compatible professional-services foundation, its parent modules and the optional salon-appointments block. Select Salon front desk · appointments in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes.
2. Open /pos-login, choose Salon front desk · appointments in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
3. Choose the appropriate queue (All appointments, Booked, Arrivals, In service, Completed). Use Book appointment to create a record, or open History & next action on an existing one.
4. Select the client and active staff member. Enter the service, chair and total occupied time including processing/buffer time.
5. Create the booking. Active appointments cannot overlap for the same staff member or chair; adjacent time windows are allowed.
6. Record arrival, start service and completion. Use cancelled or no-show only from the permitted stages; retain evidence in history.
7. Record cancellation or no-show only when offered. Keep service billing in the separately authorised Business portal. Completing an appointment does not complete or invoice a service engagement.
8. Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.

Before you proceed: Scheduling and operational progress only. Staff qualification rules, multiple processing phases, visit checkout, deposits, rebooking and stylist commissions are not implemented. This operational desk has no new payment engine.

Laundry demo: 4 tickets in Received, Washing, Ready and Released, each with two generated bag codes. Open the Ready ticket to practice checking every expected bag before release.

1. Administrator: select the compatible professional-services foundation, its parent modules and the optional laundry-custody block. Select Laundry front desk · intake & collection in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes.
2. Open /pos-login, choose Laundry front desk · intake & collection in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
3. Choose the appropriate queue (All tickets, Intake, Processing, QC, Ready to collect, Released). Use Receive laundry to create a record, or open History & next action on an existing one.
4. Select the client, kg or piece basis, gross quantity, tare, bag count and promised time. Pieces must be whole and have zero tare.
5. Keep the generated bag codes with each bag. Progress sorting, washing, drying, packing, QC and ready with evidence; return to sorting for rework.
6. At release scan/type every expected bag code exactly once and record the verified recipient and handover evidence. Verify payment separately in the billing workflow.
7. Keep promised time and net quantity visible. Use History & next action to review the last evidence; use permitted rework transitions when needed. Check payment separately in commercial billing; this desk does not enforce payment before release.
8. Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.

Before you proceed: Operational ticket and bag custody only. No price/rush rules, payment enforcement, garment photos, bag splitting, representative registry or scale integration. This operational desk has no new payment engine.

Services demo: 3 site visits linked to an existing open job: Scheduled, Dispatched and Completed. Schedules are fixed examples from the seed date; check the actual date before demonstrating dispatch.

1. Administrator: select the compatible trades or professional-services foundation, its parent modules and the optional service-visits block. Select Services front desk · site dispatch in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes.
2. Open /pos-login, choose Services front desk · site dispatch in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
3. Choose the appropriate queue (All visits, Scheduled, Dispatched, On site, Completed). Use Schedule site visit to create a record, or open History & next action on an existing one.
4. Select an open job or service engagement, active staff member, site and visit window. The corresponding parent module must be selected.
5. Schedule the visit; active visits cannot overlap for the same staff member. Record dispatch and arrival with evidence.
6. Complete the visit with actual site evidence. Complete/review the authoritative job or engagement and issue eligible billing separately.
7. A visit completion does not complete the parent job or engagement. Record delivery checks and approved work in the Business portal, then use eligible commercial billing separately. Scheduling cannot overlap for the same staff member.
8. Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.

Before you proceed: Site-visit scheduling and evidence only. No travel optimization, variations, retention/progress billing, native reception checkout or automatic parent completion. This operational desk has no new payment engine.

Typed operational records reuse existing customers, orders and jobs without posting stock or money.

1. Ask the administrator to select the appropriate optional specialist blocks plus the matching parent blocks. Use Business sign in with Operations View or Edit; the package label alone grants no access.
2. Open Operations → Specialist operations. Choose an eligible workflow, expand Step by step and open the public specialist handbook for the exact workflow instructions and current limits.
3. Find an existing customer/staff/source and save the specialised intake. Keep bag codes and source references. Every write is versioned/audited; custody movements are append-only.
4. Progress only through the displayed next actions and record evidence. Laundry release needs all bag codes; food pickup needs a ready order; retail handover needs completed fulfillment; vehicle release needs job completion.
5. Review history and use the original billing, stock, checkout and job workspaces for their authoritative actions. These operational records do not confirm payment or automatically complete another module.

Before you proceed: Operational annexes only. See the per-workflow handbook for missing specialist money/shift/device features. Seven dedicated operational desks are available through POS sign in when configured. Full specialist financial modes remain planned; no new payment/provider confirmation or workflow screenshot coverage.

Maintain employee details separately from login accounts.

1. Open Employees / HR and maintain the employee name, position, start date and active status.
2. Use Employee Scheduling to record planned work windows.
3. Only the owner uses Staff Management and Role Management to assign login access.
4. If Attendance & leave is enabled, the owner links an active employee to the correct staff account before personal submissions.

Before you proceed: Employee schedules are planned hours, not approved attendance or payroll inputs.

Start with your own account and the modules enabled for your business.

1. Sign in through Staff Login using your assigned email and current password.
2. Open Overview for your foundation dashboard. Use Business to review current positions, Needs attention and dated workload creation. Use System & workflow for foundation/data freshness and source queues. Open ERP apps to find enabled modules.
3. Select a 7, 30 or 90-day activity window and an authorized workspace. Expand Daily values to read the chart data or Export visible data for CSV. The date window applies to created-record activity, not the current/all-history cards. Use My profile to change your own details or credentials.
4. If a module is missing, ask the owner about department access and the platform administrator about foundation selection.

Before you proceed: Creation activity includes later cancelled records and is not revenue, completion or profit. Today is incomplete; a zero preceding period has no percentage comparison. Queues may overlap. System status does not measure hardware, infrastructure or gateway health. An expired subscription can make records read-only.

Give each staff member the department access needed for their work.

1. As owner, open Role Management and create or review a department role.
2. Choose None, View or Edit per department. Keep Finance and HR restricted to the appropriate staff.
3. Open Staff Management, create or review the account and assign its role.
4. Ask the staff member to refresh their portal and verify the visible modules. Staff can change their own credentials in My profile.

Before you proceed: Only owners manage staff accounts and roles. Foundation selection also controls which modules appear.

Maintain customer, vendor and staff identities without forcing them into renter records.

1. Open Contacts and search before creating a duplicate.
2. Choose a person or organization, enter the name and available contact details.
3. Assign the roles needed by your workflow, such as Customer or Vendor; a contact can have several roles.
4. Select that contact when creating a sale, purchase, engagement, job, membership or activity.

Before you proceed: A customer contact does not automatically create a renter account or a portal login.

Review posted journals across the tenant, then close a reviewed ended month.

1. Open Financial reports and choose the reporting month.
2. Review monthly income, cumulative trial balance and month-end balance sheet; export accounts for review.
3. Investigate missing transactions, unvalued stock or liabilities before relying on the reports.
4. Only an owner with Finance edit closes an ended month after reviewing reconciliation. New journals in that month are then blocked.

Before you proceed: There is no reopening or automatic profit-transfer workflow. Reports reflect recorded journals, not unrecorded taxes or opening balances.

Submit your own actual work and leave for independent HR review.

1. The owner links your active staff account to an active employee in Attendance & leave and sets the hourly rate.
2. Open My work & payslips. Clock in/out or submit a past completed shift with the actual break minutes.
3. Submit leave with kind, start/end dates and reason. Annual and sick leave use the allocated year balance.
4. Another owner/manager with HR edit reviews your submission. Check the resulting status and leave balance.
5. Review your own published payslips when retail payroll is enabled.

Before you proceed: Staff see their own attendance/leave; HR administrators review independently. Dated rosters, breaks, overtime/correction requests and indicators are available in Workforce planning. Indicators and configured rules are not a statutory premium engine.

Track customer work and independently reviewed actual minutes.

1. Select an active Customer contact and create an engagement with its staff lead and PHP hourly rate.
2. Staff record actual dates/minutes against the engagement. These are time entries, not planned schedules.
3. An eligible owner/manager with Operations edit reviews another person’s submitted time; self-approval is rejected.
4. Review accepted time and progress, then complete or cancel the engagement when appropriate.

Before you proceed: Actual time requires independent review. Only approved billable time is selectable in Commercial invoices; agreed monthly contracts use accepted period milestones instead. Time entries do not automatically create wages or execute payments.

Coordinate typed work with contacts, assignees, due dates and progress notes.

1. Choose or create the appropriate activity category.
2. Create an activity with title, category, optional contact/assignee and due date.
3. Review open and overdue work. Update progress as work moves forward.
4. Complete or cancel the activity and retain its history for follow-up.

Before you proceed: Activities do not generate donation accounting, specialized rentals or arbitrary custom ERP workflows.

Keep supporting business files beside the records they explain.

1. Open Documents and search for an existing file before uploading another copy.
2. Add the document and the available business reference using your allowed storage workflow.
3. Review access and the linked record before sharing the document outside your business.
4. Use the supporting document when reviewing contracts, repairs or other operational work.

Before you proceed: Stored signed files are not an electronic-signature workflow. Advanced versions, retention and approval automation are not implemented.

Use the same reviewed payroll engine across industry foundations.

1. Select Payroll, Workforce and Financial reports in the foundation. Assign HR and Finance access separately.
2. Resolve pending corrections and overtime, then load approved pay inputs. Premium amounts require separately reviewed calculation.
3. Create a draft with effective-dated configured rules. Split periods crossing a rule change.
4. A different owner or manager with HR and Finance Edit approves. A beneficiary cannot approve. Record actual payout and remittance references; staff view only their own payslips.

Before you proceed: No automatic statutory tables, tax annualization, government submission, bank transfer execution or premium calculation. Existing retail payroll records are reused.

Keep planned work separate from reviewed actual attendance.

1. HR assigns a dated Philippine-time shift with planned breaks and late grace. Overlapping shifts and approved leave conflicts are rejected. Overnight shifts retain their starting work date.
2. Staff use My work to clock in, and My shifts & requests to start and end breaks. End a recorded break before clock-out; recorded punches determine its minute total automatically.
3. Request overtime or an attendance correction with a reason. Missing clock-outs stay incomplete until corrected.
4. An independent owner or manager reviews the queue. Approved corrections return attendance for fresh review. Payroll-frozen attendance cannot be rewritten.

Before you proceed: Extra and night-window minutes are indicators, not statutory pay premiums. No biometric integration, geofencing, automatic stale approval or automatic clock-out.

Compare approved time to budgets and review milestones.

1. Choose an existing open engagement in Industry operations and save planned hours and fee budget.
2. Add dated deliverables, activate the engagement, and submit evidence as work is delivered.
3. A different owner or manager accepts or rejects; rejected work can be resubmitted. Accept every milestone before completing the engagement.

Before you proceed: Approved time value uses saved hourly rates; it is not labor cost, invoiced revenue, profit or statutory accounting.

Create invoices from approved work without billing it twice.

1. Open Commercial invoices with Finance access. Select approved service time, an accepted milestone, a completed job, or a won agency fee.
2. Use either time or milestone billing for a service engagement. Time uses saved approved rates; milestones and job contracts require the agreed price. Agency fees use the closed deal and an explicit billing contact.
3. Save the draft. A different owner/manager with Finance Edit checks source evidence and issues the invoice. Cancel unused drafts to release their source claims.

Before you proceed: Internal PHP records; no statutory certification or automated tax engine. Retainers and recurring service agreements are managed in Service contracts & retainers. Recognition there is limited to ended accepted milestones on independent invoice issue.

Preserve original invoices and record adjustment evidence.

1. Open an issued invoice and record the actual manually confirmed tender. Cash received and applied amounts are separate; external methods require a real reference and confirmation.
2. An owner/manager different from the invoice issuer records a credit within the uncredited invoice amount. Original invoice lines remain unchanged.
3. Refund only an available credit balance against the original payment and method. Review saved entries and cash change, then print or save PDF.

Before you proceed: No payment-provider execution or fiscal certification. Refunds cannot exceed original net payment.

Inspect inactive connections and signed delivery/reconciliation queues.

1. An owner/manager with Admin access opens Integration gateways. A trusted operator configures the per-business adapter and secret on the server.
2. Inspect outbound events before delivering/retrying. The adapter must honor the event idempotency key and verify the timestamp/HMAC contract.
3. Inspect incoming event payloads and record reconciliation evidence. They remain held for review and never automatically alter bookings, payments or filings.

Before you proceed: Provider-specific mappings, sandbox certification and operational activation remain required. Secret keys and adapter URLs are never returned to the browser.

Services: capacity and billable utilization

1. Configure each staff member’s available minutes for the actual date. No standard workday is assumed.
2. Allocate open engagement work within capacity; approved leave blocks new positive allocations. Set an allocation to zero to release it.
3. Mark actual time billable or non-billable before submission. Another eligible reviewer approves it. Compare approved billable minutes with configured capacity.

Before you proceed: Daily planning is separate from payroll/rosters. Non-billable time cannot be selected for commercial billing. Reports show at most 5,000 rows over 63 days.

Services: actual project expenses

1. Select an active/completed engagement in Service capacity and record actual expense date, amount and unique supporting receipt reference.
2. Another Operations owner/manager reviews the evidence. Self-approval and duplicate active receipt references are rejected.
3. Use the financial/payroll workflow for actual reimbursement or supplier payment, keeping the same supporting reference.

Before you proceed: These are project management expense records. Approval does not create a payable, payment, tax credit or accounting journal; the latest 500 are displayed.

Owner/manager: private client and owner access

1. Verify the active contact identity and authority, then issue a private seven-day link in Client & owner access. Copy the link only to the intended recipient through your established private channel.
2. The recipient opens the separate Client & owner portal. Their own eligible work, quotes, invoices, listings, briefs and unit resolutions appear; actual quote/milestone acceptance and eligible unit voting are available.
3. Revoke the grant when access is no longer needed. Access is rechecked on each request. Renew by issuing another link after identity review.

Before you proceed: Bearer links are credentials and are shown only once. No automatic invitation delivery, payment collection, owner staff powers or renter/POS credential reuse. Client sessions last two hours; links expire after seven days. Record limits are displayed in the portal.

Generate agreed monthly delivery periods and apply independently reviewed advances to earned invoices.

1. Use a fresh active engagement with no milestones or active billing. Record a signed calendar-month agreement, fixed monthly fee and number of periods. Another Finance/Operations owner or manager activates it.
2. Generate each monthly delivery milestone on demand. Future periods cannot be submitted/accepted. Use delivery workflows for actual evidence and independent or client acceptance. Bill only accepted ended periods at the agreed fee; another Finance reviewer issues the invoice.
3. Record an actual advance receipt with net amount, tender/reference and cash handed over where applicable. Another Finance owner/manager checks and posts the receipt to client-advance liability. Cash change is returned separately from the net advance.
4. Apply a posted original receipt to an issued contract invoice. Another Finance reviewer posts it only within the current invoice and original receipt balances. No second cash receipt is created.
5. After a credit adjustment, reverse only the credited part of an original application back into the advance balance. Refund only an unapplied original receipt through its original tender, with actual refund evidence and another reviewer.

Before you proceed: Fixed-fee whole calendar months, no automatic background billing. Recognition posts on independent invoice issue after ended-period acceptance; no over-time progress, variable consideration, multiple performance obligations, tax or foreign currency. Advance events are immutable after review. Do not treat unapplied advances as revenue.