Search Results

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...

Advanced Reports Purpose and when to use this record Build a reusable report from selected data, filters, columns, grouping, sorting, totals, and access settings. At a glance Identify it by: Report Title, Allow Date Filters, Date Field, Date Behavior, and Be...

Pdf Renderers Purpose and when to use this record Configure a printable document template for a particular record or list and control where users can select it. At a glance Identify it by: Name. Check its business context: Content Type. Why care: A repor...

Reports Purpose and when to use this record Define a reusable business report, its data source, date behavior, category, filters, and system/custom status. At a glance Identify it by: Report Title, Allow Date Filters, Date Field, Date Behavior, and Beginning...

Service Orders Purpose and when to use this record Coordinate approved service work, including customer equipment, priority, warehouse, technician activity, parts, labor, and status. At a glance Identify it by: Service Order #, Status, and Service Date. Ch...

Technicians Purpose and when to use this record Maintain the dispatch identity, linked employee, active state, display color, and mobile label for a service technician. At a glance Identify it by: First Name, Last Name, and Mobile Label. Check its business...

Users and Access Purpose and security boundary Use user records to give one person an identifiable Brisk sign-in and only the access required for that person's work. User administration is restricted setup work. Never copy passwords, recovery codes, API tokens...

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...

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...

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...

This workflow follows a reported service problem through the service order, booking, dispatch, technician activity, office review, billing, and payment. The office and technician continue from connected customer, equipment, schedule, time, parts, labor, and bi...

This workflow turns maintained warehouse reorder settings into reviewed purchase orders, a partial receipt, and an updated inventory position. It begins with item and vendor setup and ends when purchasing and receiving can explain what Brisk suggested, what st...