FINANCE

Generate Deferral Schedule from a Manually Entered Contract

When finance adds a non-Stripe contract row in Airtable and marks it ready, this builds the deferral schedule using the chosen recognition method and writes the monthly rows…

CategoryFinance
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerAirtable contract record marked ReadyAirtableAirtable
  • LogicBranch on recognition method
  • ActionCompute and validate monthly amounts
  • ActionInsert deferral rows into BigQueryGoogle BigQueryBigQuery
  • OutputUpdate Airtable record to ScheduledAirtableAirtable

What it does

Covers contracts that never touch Stripe — wires, POs, and enterprise deals booked by hand. When an operator fills in an Airtable contract record and flips a Ready toggle, it reads the terms and the selected recognition method, generates the schedule, and lands it in the same BigQuery table as your automated deals.

When to use it

Use this when a meaningful slice of revenue is invoiced outside Stripe and finance keeps it in Airtable. It gives manual deals the same structured, auditable deferral treatment as subscription revenue without a separate spreadsheet.

How it works

  1. 1An Airtable trigger fires when a contract record is updated with the Ready flag set.
  2. 2A logic step branches on the recognition method field: straight-line, milestone, or usage-stub.
  3. 3An action computes the monthly amounts for the chosen method and validates totals reconcile to the contract value.
  4. 4A BigQuery action inserts the deferral rows, tagged with the Airtable record ID.
  5. 5The output updates the Airtable record to Scheduled with a link back to the generated rows.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  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.