Subscriptions

Subscriptions

Purpose and when to use this record

BriskDefine storesa subscriptionsrepeating ascustomer partsale, billing frequency, line items, and whether payment is direct or posted to receivables.

At a glance

• Identify it by: Label.

• Check its business context: Customer, and Payment Method.

• Why care: Customer, warehouse, quantities, prices, tax, payment, and fulfillment represent different parts of the salestransaction. module.Review Thiseach generatedbefore referencetreating the sale as complete.

Before you begin

You need the Brisk permission for the action you are taking on subscriptions. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Have valid Customer records ready first. Those selections determine where this subscription belongs and which later screens can find it.

Create a recordsubscription

TheCreate evidencea packetsubscription identifiesafter searching for the viewperson, organization, item, location, or resource under alternate names and sourceidentifiers. locationMerge or correct an existing master record instead of creating a duplicate.

1. Select the business context first: Customer, and Payment Method.

2. Enter the required identifying and operational values: Label, and Customer.

3. Review Frequency, and Billing Mode deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the subscription, then confirm Label on its detail page before continuing.

After saving: Monitor each generated billing cycle and resolve failed direct payments or receivable balances without creating duplicate subscriptions.

Delete a subscription

Delete this subscription only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

Before confirming, check for thisrelated action.Recurring ConfirmSales, user-facingand stepsSubscription beforeRows. approvingBrisk may refuse deletion when another record depends on this page.one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Label. After confirmation, return to the Subscriptions list and make sure only the intended subscription was removed.

ViewReview recordsubscription details

The evidence packet identifiesUse the viewdetail page as the shared record of what this subscription currently means. Verify Frequency, Billing Mode, Subtotal, Tax Total, and sourceTotal locationbefore relying on it for thisa action.decision.

Confirm

Follow user-facingCustomer, stepsand beforePayment approvingMethod to determine whether the issue is on this subscription or on one of those linked records.

Next check: Monitor each generated billing cycle and resolve failed direct payments or receivable balances without creating duplicate subscriptions.

Edit an existing subscription

Edit this subscription to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

1. Open the detail page. Compare Customer, and Payment Method with the supporting document or approved request.

2. Recheck Frequency, Customer, Billing Mode, Subtotal, Tax Total, and Total. These values are most likely to change customer totals, tax, payment, fulfillment, and receivables.

3. Save the change, return to the list, and confirm that the subscription now appears under the expected Frequency, and Billing Mode.

After the change: Monitor each generated billing cycle and resolve failed direct payments or receivable balances without creating duplicate subscriptions.

Find and review recordssubscriptions

The evidence packet identifiesUse the viewSubscriptions list to find the correct record before opening or changing it. Compare Label, Frequency, Customer, and sourceBilling locationMode. Records with similar names or numbers can still belong to different Customer, and Payment Method.

• Keyword search checks Memo, and Label.

• Narrow the list with Customer filters.

• The date filter uses Datecreated; choose a range that matches the business event you are reconciling.

Open the subscription whose Label, Frequency, Customer, and Billing Mode match the task. If it is missing, clear the list filters and recheck Customer, Datecreated, Frequency, and Billing Mode rather than creating a replacement immediately.

Fields and business rules

Brisk stores 9 user-relevant fields for this action.subscription, Confirmincluding user-facing2 stepslinked-record selections and 2 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this full reference.

page.

Edit

anrecord

Confirmuser-facingstepsbeforeapproving this page.

Delete a record

Confirmuser-facingsteps

Field	Required	What it controls
Label	Yes	A label to identify this subscription in the business.
Frequency	No	Determines the frequency with which a subscription should occur. Available values: Daily, Weekly, Bimonthly, Monthly, Quarterly, Biannually, Annually.
Customer	Yes	The customer that made this purchase.
Billing Mode	No	Controls whether subscription billing charges a stored payment method or posts to receivables. Available values: Charge Customer Account, Direct Pay When Available, Direct Pay Required.
Payment Method	No	Stored card or ACH method used when this subscription is direct billed.
Memo	No	An open text field for employees to make notes about this transaction.
Subtotal	No	The total sales price of all line items before approvingsales thistax.
Tax existingTotal	No	The evidencetotal packetsales identifiestax the view and source locationdue for this action.sale.
Total	No	The evidencetotal packetvalue identifies the view and source locationrecorded for this action.subscription.

before

What approvinghappens thisnext

Monitor each generated billing cycle and resolve failed direct payments or receivable balances without creating duplicate subscriptions.

Common mistakes and troubleshooting

• The record will not save: Recheck Label, and Customer and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The values look right but the result is wrong: Open Customer, and Payment Method from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.