Reference · built on requestOperator by FibricReporting & analysis

Board Pack

Assembles the board pack from finance, commerce, and warehouse figures, each number sourced, and proposes the draft for sign-off.

Request accessPricing ↗

About

A board pack is a set of numbers that must agree with each other and with the systems they came from. Board Pack assembles it on the schedule you set. It reads the profit and loss and balance sheet from Xero's Reports endpoint or from NetSuite through SuiteQL, order counts and revenue from the Shopify Admin API, and the derived measures your analysts keep in Snowflake or BigQuery.

Each figure in the draft carries its source: the report, the query, the period, and the time it was read. The operator writes the draft into the pack's Google Sheet, proposes the sign-off to the finance owner, and holds the pack until a person signs. Nothing leaves the sheet without that signature.

This is a reference listing. It documents what Fibric would read from Board Pack 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

  • ProfitAndLoss and BalanceSheet reports from the Xero Accounting API Reports endpoint, by fromDate, toDate, and periods
  • Transaction and account rows from NetSuite through SuiteQL on the REST /query/v1/suiteql endpoint
  • Orders with financial status, totals, and created date through the Shopify Admin GraphQL orders query
  • Analyst tables and views in Snowflake through the SQL API, or in BigQuery through jobs.query
  • The prior period's pack in the Google Sheet, so each figure can show its movement and its earlier source
  • Sign-off and change requests on the draft it proposes

Proposed actions

  • Target capability: propose writing the draft figures and their sources into the pack's Google Sheet through spreadsheets.values.update
  • Target capability: propose the pack for sign-off in Slack, listing each figure, its source, and any figure that changed since the last draft
  • Target capability: propose uploading the signed pack as a file to the board folder through Google Drive files.create
  • Target capability: propose a note on any figure whose two sources disagree, for the finance owner to resolve before sign-off

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

What you can build

  • Monthly pack from Xero and Shopify

    Board Pack reads the month's ProfitAndLoss from Xero, order counts and gross sales from Shopify, and writes both into the pack sheet with a source line under each figure. It proposes sign-off in Slack to the finance owner.

    With Xero, Shopify, Google Sheets, Slack

  • NetSuite ledger, Snowflake margins

    Revenue comes from NetSuite through SuiteQL; contribution margin comes from a Snowflake view the analysts maintain. The operator lays both in the sheet, flags where the two revenue lines differ, and holds sign-off until the owner resolves it.

    With NetSuite, Snowflake, Google Sheets

  • File the signed pack where the board reads it

    Once signed, the operator proposes uploading the pack to the board's shared folder through Google Drive files.create, named by period. The folder keeps one file per period.

    With Google Drive

Requirements

  • A Xero organisation with the accounting.reports.read scope granted, or a NetSuite account with REST web services and SuiteQL enabled
  • A Shopify app with read_orders, plus read_all_orders if the pack reaches back past sixty days
  • A Google Sheet that is the pack's working copy, with the spreadsheets scope granted to the connector
  • A named finance owner who signs the pack, and a Slack channel where the sign-off is proposed
Authentication
Board Pack keeps no keys. It reads through the Xero, NetSuite, Shopify, Snowflake, and BigQuery connectors you authorize, writes to sheets and files through the Google Sheets and Google Drive connectors, and proposes sign-off through Slack.

Limits

  • SuiteQL returns at most 100,000 rows per query. Larger pulls need SuiteAnalytics Connect and are outside this listing.
  • Shopify's read_orders scope covers the last sixty days. Older orders need read_all_orders, which Shopify grants on request.
  • It reads the reports the ledger produces. It does not post journals, close periods, or restate prior packs.
  • Figures are as-of the read time recorded beside them. A ledger entry booked after the read appears in the next draft.

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 Board Pack ↗

Questions and answers

What does a person approve?
Two things. First, writing the draft figures into the pack sheet. Second, the sign-off itself, proposed to the finance owner with every figure and its source in view. A figure with two disagreeing sources is called out and blocks sign-off until someone resolves it.
What record does it leave?
For each pack: the source of every figure (report, query, period, read time), the draft as written, who signed it and when, and any figure that was edited by hand before signing. The record stays with the period so a later reader can trace a number back.
Does it change the ledger or the store?
No. It reads reports from Xero or NetSuite and orders from Shopify. Its only writes are the pack sheet and the file upload, and both wait for approval. It never posts a journal or edits an order.
Ask about Board Pack

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