Search Results

Custom Fields Purpose and when to use this screen Custom Fields adds organization-specific information to supported Brisk record types when no standard field represents the requirement. Use it for durable business facts that need consistent entry and lookup—no...

Local Workstation Setup Purpose and when to use this screen Local Workstation Setup stores Point of Sale identity and cash-drawer selection in this browser on this machine. Use it for a fixed register, shared counter computer, or browser profile that should co...

Time Clock Purpose and when to use this screen Use Time Clock for the signed-in employee’s ordinary start and stop actions. The page displays the current clock state and the ten most recent entries so the employee can catch an obvious missed punch before it re...

Time Manager Purpose and when to use this screen Time Manager gives department managers a weekly view of employee punches and a controlled way to correct missing, overlapping, or inaccurate time. Superusers can work across departments; other managers can selec...

User Preferences Reference How these settings apply The User Preferences Reference overview screen in the Brisk documentation demo. Configure the signed-in user's layout, workflow defaults, profile, and other personal behavior by screen section. User preferenc...

Close Accounting Periods Purpose and when to use this screen Period close establishes operational and financial cutoffs and makes reports available from a stable boundary. Close from the smallest period outward: work periods first, then the month, then the yea...

Data Import Purpose and when to use this screen Data Import loads supported CSV datasets while preserving a run record, row-level diagnostics, source-system identity, and dry-run/apply distinction. Use it for controlled migration or conversion—not as a shortcu...

Customer Payment Methods Purpose and when to use this record Maintain a customer-authorized tokenized card or ACH method without storing raw payment credentials in Brisk. At a glance Identify it by: Nickname, and Status. Check its business context: Custome...

Customer Receivable Payment Plans Purpose and when to use this record Schedule authorized collections against a customer’s receivable balance and track each run without duplicating payments. At a glance Identify it by: Start Date, Next Run Date, and End Date...

Email Payments Purpose and when to use this record Create and monitor a signed online payment request for a customer or sale, including allowed tenders, amount, and remote status. At a glance Identify it by: Status. Check its business context: Customer, an...

Emv Terminals Purpose and when to use this record Configure the processor terminal identity used for card-present payments and assign it to the correct user or workstation. At a glance Identify it by: Name, and Pairing Code. Why care: Customer, source docu...

Payment Plans Purpose and when to use this record Review legacy or provider-managed amount, cadence, duration, and processor identifiers. These records are reference-only in Brisk-managed billing mode; use Customer Receivable Payment Plans for supported schedu...

Payment Subscriptions Purpose and when to use this record Review a provider-managed recurring subscription's customer, plan, amount, cadence, status, vault reference, and gateway identifier. These records are read-only in Brisk-managed billing mode. At a glanc...

Follow complete Brisk workflows using fictional sample data. These examples show how sales, inventory, purchasing, service, ecommerce, accounting, manufacturing, payments, and government records can remain connected from the first action through reporting and ...

This workflow follows a named customer order from entry through fulfillment, payment or receivable status, inventory activity, and financial review. The original request, customer PO, item rows, and downstream records remain traceable, so the next employee can...

This workflow follows a counter sale from the cashier’s cart through tender, receipt, inventory review, operating reports, and work-period close. It shows why checkout is only the first control point: the business must still explain stock movement, tender tota...

This workflow follows an on-account sale from its source transaction through aging, statement review, approved finance charges, safe collection, and balance application. It keeps the reason for the receivable visible while separating customer communication, pr...

This workflow follows a customer-facing storefront order into Brisk’s back-office order, payment review, fulfillment work, inventory history, and reporting. Checkout crosses a deliberate application boundary, but staff continue from the created Sale and Ecomme...