When does an AI agent use this pattern?

When the trigger described above matches the situation the agent is handling. The agent queries FusedFrames at runtime, this pattern is returned and the agent follows the recorded reasoning and steps to reach the recorded outcome.

How were the steps captured?

By the desktop app on the machine of someone who actually does this work. It records clicks, keystrokes, copy and paste, drag and drop, selected text and screen regions across NetSuite and Stripe, then groups them into the meaningful steps shown above.

Where does the reasoning come from?

From the operator. When the desktop app sees a decision the action alone cannot explain, it asks why in the moment. The operator's answer is recorded and becomes the reasoning attached to the pattern, so the AI agent gets the thinking and not just the steps.

What if my team handles this differently?

Capture how your team actually does it. The desktop app records what your operator does on your tools and the web app distills that into a pattern shaped by your team. Each team's library reflects their own approach rather than the example shown here.

What if a case looks like this pattern but does not quite fit?

The pattern is linked to 1 alternative. The agent can follow the connections shown on this page to a related pattern that matches the case more closely.

How does my AI agent actually call this pattern?

Through the read-only REST API or the npm CLI. Create an API key in the dashboard, choose whether it accesses all libraries or specific ones and have your agent query at runtime. The response is structured JSON ready for tool use.

Is the data shown on this page from a live customer?

No. Example libraries on this site are illustrative. Patterns in your own account are built from your team's captured actions and stay private to your workspace.

How do I build a pattern like this for my team?

Install the desktop app on the machine of the person who already does this work, ask them to handle a real case end to end, then distill the captured action into a pattern in the web app. The pattern you end up with mirrors how your team actually operates.

Pausing NetSuite revenue recognition after a customer enters dunning

After two failed Stripe charges on the same subscription, the FP&A analyst sets the customer's NetSuite recognition schedule to Hold with reason 'dunning'. Recognition only resumes the day a successful charge clears, not the day the customer commits to pay.

Tags

revenue-recognitiondunningnetsuitefp-and-acontrolshold

Lets your agent filter to the right pattern

Categories and tags scope the retrieval set, so your agent receives only the patterns relevant to the task instead of scanning the full library.

What and why

The observed behaviour and the reasoning behind it.

Behaviour

After two failed Stripe charges on the same subscription, the FP&A analyst pauses revenue recognition for the customer in NetSuite by setting the recognition schedule status to Hold and adding a hold reason of `dunning`, then exits the customer from the new pipeline reports until the dunning resolves. Recognition resumes the day a successful charge clears, not the day the customer commits to pay.

Reasoning

Continuing to recognise revenue for a customer who is not paying inflates monthly revenue and creates a deferred revenue versus accounts receivable mismatch that has to be unwound later. Pausing at the second failure is the gate that prevents recognition drift; waiting until actual churn means the team has to write off recognised revenue across multiple periods. Resuming on commitment rather than on cleared payment is a common trap because committed-but-uncleared payments fail at roughly one in five and the recognition has to pause again, which the auditor will flag as control weakness.

Gives your agent an operator's reasoning

Behaviour records the action; reasoning records the rationale. Your agent applies both to handle cases that diverge from the captured examples.

Cause and effect

What initiates this pattern and what it produces.

Trigger

A subscription has had at least two Stripe charges fail in a single billing period and the customer has been in dunning for at least seven calendar days.

Outcome

Recognition is held on the customer's recognition schedule, the customer is excluded from new pipeline reporting and the deferred revenue balance stops accruing for the duration of the dunning. The FP&A close pack reflects the held customer separately so leadership has accurate revenue figures while collection continues.

Tells your agent when to act and what to verify

Your agent stays within the scope set by the trigger and outcome, so it doesn't extend beyond the work or finish before the outcome is met.

Standard operating procedure

Step-by-step instructions to reproduce this pattern.

NetSuite

Open the customer's recognition schedule from the customer record sidebar.

The recognition schedule lives on the customer record, not the invoice. Opening from the invoice level only pauses recognition for that single invoice and the next billing cycle's recognition will start running again automatically. Always work from the customer level.

Expected: The recognition schedule for the customer is open and editable.

NetSuite

Confirm there have been at least two failed Stripe charges in the current billing period.

Two is the gate. Pausing on a single failure causes too much manual reconciliation work for charges that recover on the first manual retry. Three failures means the FP&A trigger is too late and revenue has already drifted across at least one weekly close. Two is the right balance.

Expected: Two or more failed charges are confirmed on the customer's billing history.

NetSuite

Change the recognition schedule status from Active to Hold.

Use Hold, not Cancel. Cancel removes the schedule and the historical recognition is lost. Hold preserves the schedule, freezes recognition at the current period and lets recognition resume cleanly when the dunning clears. A cancelled schedule has to be rebuilt manually which is a half-day of work.

Expected: The schedule status reads Hold and recognition stops on the next day.

NetSuite

Set the hold reason to `dunning` and add a free-text note with the dunning attempt count and the named accounts payable contact.

The reason field drives downstream FP&A reporting filters. Always use the exact word `dunning` in lower case so it matches the close-pack filter. Free-text notes carry the dunning attempt count so anyone picking up the case knows how far through the cadence the customer is.

Expected: The hold reason is set to `dunning` and the free-text notes carry the cadence position.

NetSuite

Exit the customer from the new pipeline reports by toggling the customer's pipeline-eligible flag off.

Pipeline reports drive renewal forecasting. Leaving a customer in dunning eligible for pipeline overstates new and renewal forecasts and gets the team into trouble at the next FP&A review. Toggle off until dunning clears, then toggle back on the day the charge succeeds.

Expected: The customer no longer appears on new pipeline reports.

NetSuite

Add a flag on the close pack to surface the held customer separately so leadership sees the impact.

FP&A close pack is the leadership view of the period. Held customers should appear in their own row with the held amount and the cadence position so leadership has accurate figures without anyone having to chase them. Use the `Recognition Held` group, not the `Churn` group; held is recoverable, churn is not.

Expected: The close pack reflects the customer in the Recognition Held group with the held amount and cadence position.

NetSuite

Schedule the recognition resume only when a successful Stripe charge clears, not when a commitment is made.

Committed-but-uncleared payments fail at roughly one in five. Resuming recognition on commitment causes a second pause when the payment fails, which the auditor will read as control weakness. Wait for clear cash and only then move the schedule status from Hold to Active.

Expected: Recognition resumption is conditional on cleared cash, with no manual override.

Hands your agent your team's exact steps

Your agent executes the documented procedure in order, against the applications named at each step, producing consistent output across human and agent runs.

Book a demo

Related patterns

How this pattern connects to other patterns in the library.

Often previous

Retrying a failed Stripe subscription charge on a three-day cadence Sending a personalised dunning email to a high-value customer in arrears

Alternative to

Voiding a duplicate NetSuite invoice and refunding the Stripe charge

Lets your agent confirm the match and its scope

Alternative patterns let your agent compare candidates and select the closest match. Previous and next patterns define position in the workflow, so the agent operates within the scope of this one.

Supporting actions

Actions that provide evidence for this pattern.

Held NetSuite recognition for Aurelius Partners after 2 failed charges

Set hold reason `dunning` on cus_RvUprq schedule with attempt count 2/3

Excluded Northgate Capital from new pipeline report for May

Surfaced Halberd Cybersecurity in close pack Recognition Held group

Shows your agent the evidence behind the pattern

Each pattern is derived from captured action sequences. Your agent can reference the source actions to verify any field, so nothing it acts on is authored by hand or hallucinated.

Metadata

Timestamps and identifiers.

Evidence	Observed 11 times across 1 connection
Applications	NetSuite, Stripe
First seen	13 Feb 2026, 15:42
Last seen	4 May 2026, 16:18

Helps your agent rank patterns by confidence

Action count and last-seen timestamp weight each pattern by frequency and recency, so your agent selects the highest-scoring match rather than the first returned.

Questions

Frequently asked questions

Book a demo View all examples

Speak to the founder

Get a demo. Watch a live capture, then an AI agent query the result.

Ask anything. Pricing, security or integrating with your stack.

No purchase obligation

Book a call

Start capturing

Record in minutes. Install once and work as normal.

Plug AI agents in. One API call from any AI agent stack.

Refund on unused credits if you cancel