End-user instruction center

ERPat User Guide

Learn how to use active ERPat modules through role-based instructions, standard operating procedures, field legends, standards, compliance reminders, and step-by-step workflows. Every guide is synchronized from the owning module and versioned whenever its instructions change.

Active modules40
Published guides357
SOPs3
Updated this month13
01Getting StartedBeginner-friendly first steps SOPStandard ProceduresRequired operational workflows AaLegends & FieldsStatus, badge, and field meanings Controls & ComplianceReview points and reminders

End-user guides from active ERPat modules

Showing 7 of 357 synchronized guides.

sales ×
Sales Reference Public

Module Research Notes

Evidence gathered from the current Sales module files — controllers, models, configs, and migrations — before writing these user guide pages.

Sales Reference Public

Administration and Controls

How administrators keep Sales secure and reliable: permissions, menus, settings, public pages, API surfaces, migrations, and change management.

Sales Reference Public

Daily Operations

The routine operating manual for staff who run Sales day to day — the core screens, records, and workflows to use once setup is complete.

Sales Reference Public

Data and Screen Reference

A compact reference of the screens, data records, routes, permissions, and supporting files that make up the Sales module package.

Sales Reference Public

FAQ and Troubleshooting

Answers to the most common setup, access, workflow, and support questions for the Sales module, with troubleshooting and support guidance.

Sales Reference Public

Getting Started

A practical first-run checklist for enabling Sales, granting the right permissions, preparing your starter data, and training the first users.

Sales Overview Public

Sales

Standalone ERPat Sales module: clients, customers, invoices, estimates, estimate requests, the public estimate-request intake form, sales matrix/summary, client groups, and stores. Controllers, views, routes, menu and config are owned by this package and loaded at runtime through the HMVC compatibility layer (App_Router + module package paths). Sales-domain.