Skip to content
Vibedata

Build something that is not there yet

Age payables from open items as of any date and reconcile the total

  • When AP can't say how much sits past terms without pulling a manual extract from the ledger.
  • When an early-payment discount window passed unnoticed because nobody was watching the aging.

Build an as-of-date payables aging model over open items, with buckets on the agreed basis and a tie-out to the AP control account. Covers the aging and its reconciliation, not duplicate-invoice detection.

Area
Transformation
Runs on
  • Microsoft Fabric Lakehouse
  • Microsoft Fabric Warehouse
  • MotherDuck
  • DuckDB
Built with
  • dbt
Domain
Finance
Industry
Manufacturing, Retail, Public sector
Readiness
SupportedEverything this Recipe composes runs today, without a case that proves this exact shape.
Before you start
needs an agreed aging basis (invoice date or due date)

Sample This Recipe has not been materialized in the Cookbook repository yet. Its trigger, description, prompt, agent guidance and acceptance conditions, and the explanation below, are prototype drafts. Its name, job, area and readiness come from the reconciled Cookbook seed snapshot. Readiness is a separate question from this one: it says whether the capability exists, not whether the writing has been reviewed.

Use this Recipe

Use the VibeData Recipe `finance-ap-aging` at https://getvibedata.ai/cookbook/finance-ap-aging Read the Recipe and execute it in the context of the current Intent.

Recipe id finance-ap-aging · Not yet materialized in the Cookbook repository, so the pointer addresses this page.

Verified by

What has to be observably true before this Recipe is finished.

  • the sum of aged balances equals the AP control account balance for the same as-of date
  • an as-of date in the past reproduces the aging bucket totals reported on that date
  • partially paid items age on the remaining open balance, not the original invoice amount
  • invoices approaching an early-payment discount deadline are flagged before the deadline passes
Recipe promptThe task specification the agent reads. Reference only — it is not what you copy.
Deliver: Age payables from open items as of any date and reconcile the total.

Build an as-of-date payables aging model over open items, with buckets on the agreed basis and a tie-out to the AP control account. Covers the aging and its reconciliation, not duplicate-invoice detection.

Execute inside the current Intent. Its Domain, repository, platform, environment and attached sources are the context for this work — read them rather than asking for them.

The work is done when:
- the sum of aged balances equals the AP control account balance for the same as-of date
- an as-of date in the past reproduces the aging bucket totals reported on that date
- partially paid items age on the remaining open balance, not the original invoice amount
- invoices approaching an early-payment discount deadline are flagged before the deadline passes

Report the evidence for each condition above with the result. A condition you cannot meet is something to say, not something to work around.
Agent guidanceHow the agent approaches the work, and what it will not do.

Profile the inputs the grain, joins and measures actually depend on before proposing a model. Put the design up for review — grain first — then build in an isolated copy with tests and documentation landing beside the model rather than after it.

Composes

  • dbt model authoring and layering
  • dbt in the project
  • isolated-copy execution and gate verification

Asks first

Semantic decisions the Intent cannot supply. Never context Studio already holds.

  • which Fabric target this work lands on, when the Domain carries both a Lakehouse and a Warehouse
  • the grain the requester expects, where the request leaves it open to more than one reading

Guardrails

  • Build in an isolated copy. Production is read, never written.

What you need

  • Microsoft Fabric Lakehouse, Microsoft Fabric Warehouse, MotherDuck, or DuckDB.
  • A dbt project you can build, and read access to the models it starts from.
  • dbt in the project, or the intent to add it.
  • Needs an agreed aging basis (invoice date or due date).

How it goes

  1. State the outcome in one sentence, in the language the request arrived in.
  2. Let it profile the inputs the grain, the joins and the measures actually depend on.
  3. Review the design. Disagreeing about grain here costs a sentence; after the model exists it costs a rewrite.
  4. Let it build in an isolated copy, with the tests and the documentation landing beside the model rather than after it.
  5. Read the acceptance conditions against the run.

What you end up with

The deliverable, in your own repository, as transformation work a reviewer who knows the project reads as native to it. Alongside it, the evidence for every one of the acceptance conditions above — which is the part that is still there in three weeks when somebody asks.

Next to this one