Use to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Run this when numbers have to move from somewhere else into the finance ledger, or when a sheet needs checking before anyone reads from it. A number that arrives unchecked is not a fact yet.
The source — a sheet, a saved query export from the business intelligence (BI) workspace, a report email, or a plain export file — and the target ledger shape.
Source column to ledger column, one row per mapping, with the transform written out next to it. Unmapped columns get listed, not dropped silently. Show the mapping table before the first load, not after.
Replace on the natural key — date plus line plus source — newest wins. Log how many rows were replaced so the load is auditable afterwards.
Write the formula next to the value on first build. Unparseable rows go to a needs-a-look list with their row numbers; they never land in the totals.
Row counts match, rollups reconcile to the source total, and dates cover the period claimed. If any check fails, say which one and hold the read. A read shipped on a failed check is worse than a late read.
What triggers the refresh, who owns the source, and what stale looks like. A ledger older than its own refresh promise gets called stale in every read that uses it.
One source of truth, one writer per sheet, and a dated snapshot before any structural change. Clever automation is the thing that breaks quietly in month four.
The mapping table, the load summary with its counts and the needs-a-look list, and the QA result with each check named.
A connector fails: take the export path and keep the same mapping and the same QA. The source has no usable key: build the read in chat only and do not write the ledger — a load you cannot dedupe will double a number later.
Structural changes to a sheet, new writers, and anything that leaves the team wait for the owner's yes.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.