FINANCE

Approval-gated recognition recompute for amended contracts in Notion

When a contract amendment is marked approved in a Notion finance tracker, recompute the revenue-recognition waterfall and write the new schedule plus a human-readable…

CategoryFinance
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNotion amendment row status set to ApprovedNotionNotion
  • LogicConfirm transition into Approved status
  • ActionFetch amendment terms (Notion) + prior schedule (Snowflake)SnowflakeSnowflake
  • LogicRecompute waterfall from effective date
  • ActionPersist new schedule to SnowflakeSnowflakeSnowflake
  • OutputWrite before/after + new waterfall to Notion pageNotionNotion

What it does

Treats a Notion finance tracker as the system of record for contract amendments. When a row's status flips to Approved, the flow recomputes that contract's deferred-revenue waterfall and posts both the new period-by-period schedule and a before/after comparison back into the Notion page, so revenue accountants review the impact inside the tool they already work in.

When to use it

Use it when amendment review is a manual approval step and you want recognition recalculated only after sign-off — not on every raw Stripe ping. Good for teams whose deal desk lives in Notion.

How it works

  1. 1A Notion database change triggers when an amendment row is set to Approved.
  2. 2A filter confirms the status transitioned to Approved (not another edit).
  3. 3The flow fetches the amendment terms from the Notion record and the prior schedule from Snowflake.
  4. 4It recomputes the remaining recognition waterfall from the amendment effective date.
  5. 5The new schedule is persisted to Snowflake.
  6. 6A before/after table and the new waterfall are written back into the Notion page as the audit trail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect SnowflakeWarehouses, queries, shares.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.