# Business License Application to Renewal This workflow follows a fictional business-license application through staff review, a charge, payment, issuance, compliance follow-up, and renewal. It preserves the distinction among the applicant account, official application, amount due, payment, and issued license while keeping each date and status available for reporting. > **Demonstration notice:** Exampleville, DOC-BIZ-1001, all people, amounts, addresses, identifiers, and transactions are fictional. Brisk records authorized municipal decisions; it does not determine legal compliance or provide statutory advice.

Workflow at a glance

| | | |---|---| | **Outcome** | Issued and later renewed license with traceable charge/payment history | | **Starts with** | Verified municipal business/account and submitted application | | **Ends with** | Renewal status and a report tied to source records | | **Primary roles** | Intake clerk, reviewer, cashier, licensing supervisor | | **Brisk areas involved** | Municipal Accounts, Applications, Charges, Payments, Licenses, Compliance | | **Common businesses** | Municipal and local-government offices | | **Approximate handoffs** | Four |

Why this workflow matters

An application, approval, fee, receipt, issued license, and renewal are different events. Keeping them as linked records prevents a payment from being mistaken for approval or an approved application from being mistaken for an active license. Queues and reports then have a traceable source. Staff can identify pending, expiring, overdue, and completed work without maintaining a parallel spreadsheet.

Before you begin

Municipal Businesses list containing fictional documentation business DOC-BIZ-1001.
Confirm the responsible business and municipal account before accepting an application.
- Required: [Municipal Account](https://help.brisksystems.us/link/2720#bkmrk-overview), business, license type, jurisdiction process, fee policy, and authorized roles. - Required: review criteria and supporting information defined by the jurisdiction outside this guide. - Required for collection: municipal charge/accounting setup and a safe authorized payment method. - Optional: compliance tasks, auto-renew flag, renewal lead days, and municipal report filters.

End-to-end steps

Municipal License Management queue showing fictional application and license states.
The operations queue lets authorized staff review status without treating approval as issuance.
License Application form for fictional application DOC-BIZ-1001 in Exampleville.
Application number, type, submitted date, requested date, and review due date remain distinct.
1. **Intake clerk — find the responsible party.** Open [Municipal Businesses](https://help.brisksystems.us/link/2721#bkmrk-overview) and the linked account. Verify business identity without exposing confidential tax or personal data. 2. **Intake clerk — record the Application.** Create [License Application](https://help.brisksystems.us/link/2716#bkmrk-create) DOC-BIZ-1001 with type, application number, Draft/Submitted state, submitted date, requested effective date, review due date, and memo. 3. **Authorized reviewer — record the actual decision.** Move through Submitted and In Review, then Approved or Denied only when the jurisdiction’s work supports it. Brisk does not make that legal determination. 4. **Licensing/cashier staff — establish and collect the charge.** Create or confirm the linked [Municipal Charge](https://help.brisksystems.us/link/2722#bkmrk-overview). Record a supported payment; its service recalculates Open, Partially Paid, or Paid from payment/credit applications instead of relying on a manual paid label. 5. **Licensing staff — issue the License.** Convert the approved Application through the supported action. The Application becomes Converted and the [License](https://help.brisksystems.us/link/2718#bkmrk-overview) carries its own number, Active status, issue/effective/expiration dates, conditions, and source application. 6. **Compliance staff — monitor dated work.** Use [Municipal License Operations](https://help.brisksystems.us/link/2950#bkmrk-compliance) for expiring licenses and compliance tasks. An approved application is not active until the separate license exists. 7. **Authorized licensing staff — renew and review.** Follow the supported renewal/update path, preserving old history and recording new effective/expiration context. Reconcile the municipal report to account, application, charge, payment, and License records.

What Brisk keeps connected

Municipal Licenses list containing the fictional issued license and expiration date.
The issued License, not the approved Application alone, carries the active status and effective dates.
Municipal Charges list showing fictional business-license fee records.
The charge is a separate financial record whose status follows recorded payment applications.
| Action | Result or downstream record | Where to verify it | |---|---|---| | Submit/review application | Official application status and dates | License Application detail | | Record charge/payment | Separate obligation and payment history | Municipal Charge and payment detail | | Convert approved application | Issued License linked to source Application | License and Application detail | | Record compliance/renewal | Dated follow-up and updated license context | Compliance Queue, License, reports |

Handoffs and controls

Municipal Reports screen used to review fictional license and payment records.
Municipal reports should reconcile to the underlying account, application, charge, payment, and license records.
Municipal Compliance Queue showing fictional upcoming and incomplete license work.
The queue surfaces dated follow-up while staff remain responsible for the legal decision.
Intake verifies identity and completeness; an authorized reviewer owns the decision; cashier staff own payment evidence; licensing staff own issuance and renewal. Draft, Submitted, In Review, Approved, Denied, Converted, Active, Expired, and Paid describe separate controls. The Application is the decision record; the License is the issued credential.

Exceptions and safe corrections

- Duplicate applicant uncertainty: search businesses/accounts and application number before creating another. - Missing requirements: keep the application in the truthful pending/review state and document follow-up. - Incorrect fee: correct an unposted/open source charge or use approved credit/correction history; never set Paid manually. - Payment pending: verify the payment record before issuing when payment is required. - Wrong license date/status: use authorized correction or renewal steps and retain the source Application link. ### Start here - [Municipal Businesses](https://help.brisksystems.us/link/2721#bkmrk-overview) - [License Applications](https://help.brisksystems.us/link/2716#bkmrk-overview) ### Continue with - [Municipal Charges](https://help.brisksystems.us/link/2722#bkmrk-overview) - [Business License Payments](https://help.brisksystems.us/link/2710#bkmrk-overview) - [Licenses](https://help.brisksystems.us/link/2718#bkmrk-overview) ### Related controls and reports - [Municipal License Operations](https://help.brisksystems.us/link/2950#bkmrk-overview)