Business Licensing (eBOSS) Overview Public

Business Licensing (eBOSS)

Overview and documentation map for the ERPat Business Licensing (eBOSS) module — the Philippine LGU Business Permits and Licensing Office platform: registry, applications, adviser, clearances, inspections, assessment, and verifiable QR permits.

Guide version: r1 Module version: 1.0.0 Updated: 2026-07-22 Estimated time: 4 min

Business Licensing (eBOSS)

ERPat's electronic Business One-Stop Shop for a Philippine city or municipal Business Permits and Licensing Office (BPLO) — run a business permit end-to-end online: register → advise → clear → inspect → assess → collect → issue → verify.

⛨ One eBOSS sidebar group ◈ 12 staff workspaces ⚑ RA 11032-aligned ₱ Philippine LGU-ready

ERPat eBOSS turns a paper, window-hopping business-permit process into one disciplined digital workflow. A business owner (or your receiving officer) enters the business details once; the Permit Adviser decides which requirements apply and why; reviewing offices run their clearances in parallel; inspectors record findings; an assessment consolidates local taxes and fees into one bill; payment is reconciled and posted to Finance; and a controlled issuance gate releases a digitally verifiable QR permit that anyone can check in public — with every step written to an immutable audit trail.

ℹ️
New here? Start with Getting Started to enable the module, grant eBOSS roles, and set up your LGU profile — then read Daily Operations for the step-by-step procedures your receiving, evaluation, clearance, inspection, assessment, and issuance officers follow. Administrators should read Administration; everyone can keep Data & Screen Reference and FAQ & Troubleshooting open in a second tab.
⚖️
Authority boundary — read this first. eBOSS makes an LGU permit process disciplined and compliance-capable. It does not create legal authority, replace an ordinance, or certify anyone as compliant. It never issues a document that impersonates a national-agency permit — BFP FSIC/FSEC, DENR ECC/CNC, FDA LTO, and DTI/SEC/CDA registrations are only referenced and verified, never counterfeited. Final fees, forms, signatories, and processing times must be approved by the adopting LGU's Legal Office, BPLO, Treasurer, and reviewing offices. See Administration → Authority boundaries.

The module at a glance

One authoritative record

The Business Registry (businesses, branches, activities) and Owners & Representatives are entered once and reused by every application and reviewing office — no re-keying, no conflicting copies.

One application, parallel review

A single Unified Application drives the Permit Adviser, document verification, parallel clearances, and risk-based inspections, each with its own accountable owner and SLA clock.

One bill, one release event

A versioned assessment consolidates local taxes and fees; payment is reconciled and posted to Finance; and the issuance gate releases a signed, QR-verifiable permit — checkable in public verification.


Explore the guide


The 60-second mental model

Register
Business & owners
Advise
Requirements decided
Submit
Unified application
Clear & inspect
Parallel review
Assess & pay
One bill, reconciled
Issue
Gate → sign → release
Verify
Public QR check

You (or the owner in the portal) register the business and its people, run the Permit Adviser so the system decides the exact requirements, and submit one unified application. BPLO does a preliminary assessment and, if anything is missing, issues one consolidated deficiency notice. Reviewing offices run their clearances in parallel and inspectors record findings and corrective actions. An assessment is prepared, approved, and frozen; the owner pays; the payment is reconciled and posted to Finance. Only when every mandatory gate passes can a permit be generated, signed, issued, and released — after which anyone can verify it by QR or reference. Renewals, amendments, and retirements reuse the same spine.

⚠️
What this version does and does not do. This release covers the full local lifecycle above and posts collected payments to ERPat Finance. It does not include an online payment gateway (owners pay at the treasury/cashier and staff record the reference), an automated external data-exchange outbox to national agencies, or a live PNPKI e-signature — the signatory is recorded as an authorized approval and the signing seam is left for a later release. See FAQ → Known limitations.
Was this guide helpful?

Report a content problem