Reference · built on requestOperator by FibricReporting & analysis

Restatement Notice

Notices when late refunds, cancellations, or reloads change a figure you already reported and proposes a restatement note to its recipients.

Request accessPricing ↗

About

A weekly report goes out on Monday. On Wednesday a refund lands against an order from the reported week, and the net sales figure people already read is wrong. Restatement Notice keeps the published figure: the period, the query, the value, the time it went out, and who received it. It then watches for records that move that period: Shopify orders with a later updatedAt, refunds with a createdAt after publication, cancelledAt set, and Magento orders whose total_refunded or total_canceled changed.

When the recomputed figure differs by more than the threshold you set, it proposes a note to the same recipients: the figure as published, the figure now, the period, and the records that moved it. A person approves before the note goes out, as a reply in the original Slack thread or an email to the same list.

This is a reference listing. It documents what Fibric would read from Restatement Notice and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Published figures you record in BigQuery, Snowflake or PostgreSQL: report id, period, metric, value, query, publish time and recipient list
  • Shopify orders with updatedAt after the publish time, their refunds with createdAt and totalRefundedSet, cancelledAt, and currentTotalPriceSet
  • Magento orders from GET /V1/orders filtered on updated_at, with total_refunded, total_canceled, status and state
  • Rows changed in the metric's source tables, through the BigQuery CHANGES function with _CHANGE_TYPE and _CHANGE_TIMESTAMP, or a Snowflake stream with METADATA$ACTION
  • The Slack ts of the message that carried the report, so a note can be threaded under it
  • Prior restatements for the same period, so a figure restated twice shows both notes

Proposed actions

  • Target capability: propose a restatement note to the report's recipients, stating the published figure, the recomputed figure, the period and the records that moved it
  • Target capability: propose a Slack reply through chat.postMessage with thread_ts set to the original report message, and reply_broadcast where you choose
  • Target capability: propose an email through Twilio SendGrid or Amazon SES to the same addresses the report went to, with the note as its body
  • Target capability: propose a new published-figure row with the restated value and its publish time, keeping the original row intact
  • Target capability: propose a hold on the next scheduled report for a period whose sources are still changing, with the reason stated

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Restate last week's net sales after late refunds

    Refunds with createdAt after Monday's publish time are summed against the reported week. If the change clears your threshold, a note with both figures is proposed as a reply in the report's Slack thread.

    With Shopify, BigQuery, Slack

  • Correct an order count after Magento cancellations

    Orders whose state moved to canceled after the monthly report went out lower the count. The note lists the increment_ids and goes to the same SendGrid personalizations the report used.

    With Magento, Snowflake, Twilio SendGrid

  • Catch a reloaded table before the next report

    The BigQuery CHANGES function shows rows in the sales table rewritten for a closed period. The operator proposes a hold on the next report and an Amazon SES note explaining what was reloaded.

    With BigQuery, Amazon Simple Email Service

  • Keep both versions of the figure

    Each approved restatement adds a row to the published-figures table with the new value and time, so a later reader in PostgreSQL sees the figure as first reported and as restated.

    With PostgreSQL

Requirements

  • A warehouse where each published figure is stored with its period, query, publish time and recipients: BigQuery, Snowflake or PostgreSQL
  • A commerce connector whose orders carry update times and refund records: Shopify or Magento
  • A messaging connector that reached the original recipients: Slack, Twilio SendGrid or Amazon SES
  • A threshold you set per metric: the smallest change that earns a note
  • For BigQuery CHANGES, enable_change_history set to TRUE on the source table; for Snowflake, a stream on it
Authentication
Restatement Notice signs in nowhere by itself. It reads figures, orders and change history through your warehouse, store and messaging connectors, and a note is never sent until a person approves it.

Limits

  • A figure can be restated only if it was recorded when published. A number typed into a slide by hand is outside the operator's view.
  • The note reaches the recipients on the stored list. A report forwarded onward by one of them is not followed.
  • A Snowflake stream goes stale if unconsumed past the table's retention, extended to 14 days by default. Older changes are found by recomputing.
  • The operator compares figures. It does not decide the accounting treatment of a refund, and it never edits an order.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Restatement Notice ↗

Questions and answers

What does the reviewer see before a note goes out?
The note itself: the figure as published, the figure now, the difference, the period, the records that moved it, and the recipient list. The reviewer can edit the wording, drop a recipient, or reject the note. Nothing is sent before that.
How small a change triggers a note?
You set the threshold per metric, as an amount or a share of the published figure. Changes below it are logged against the period and folded into the next note if one is sent, but they do not raise a note on their own.
What record is kept of a restatement?
One entry per restatement: the report, the period, the published and restated values, the records that moved the figure with their ids and times, who approved the note, when it went out, and the Slack ts or email MessageId that carries it.
Ask about Restatement Notice

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy