Reference · built on requestOperator by FibricFinance & billing

Unbilled Shipment

Shipments and finished work with no invoice behind them, each proposed as an invoice before the period closes.

Request accessPricing ↗

About

Goods leave and work gets done. The invoice is a separate act, and sometimes nobody performs it. This operator reads what shipped and what was completed, then looks for the invoice that should follow. Shipments come from ShipStation by orderNumber and shipDate, from Business Central salesShipments, or from NetSuite item fulfillments where shipping and billing are separate steps. Completed work comes from Asana tasks with a completed_at date or monday.com items in the column you mark as done.

For each shipment or task with no invoice, it proposes the invoice: customer, lines, quantities, and the order it fulfils, ready to post. A person approves it, changes it, or marks it as not billable, and that answer is kept so the item is not raised again.

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

  • ShipStation shipments with orderNumber, shipDate, shipmentItems, and voided, which say what left and when
  • Business Central salesShipments with orderNumber and postingDate, and salesInvoices with orderNumber and status, paired by order
  • NetSuite item fulfillments recorded without an invoice when Advanced Shipping keeps fulfillment and billing separate
  • Xero ACCREC invoices with Reference and InvoiceNumber, queried by ModifiedAfter, matched to the order reference
  • Asana tasks in the billable projects you name, with completed, completed_at, and custom_fields carrying the customer and rate
  • monday.com items and column_values on the boards you name, with the status column that marks work delivered
  • Items a person marked not billable earlier, which it does not raise again

Proposed actions

  • Target capability: propose a Business Central salesInvoice built from the shipment lines, linked by orderNumber, left in Draft for posting
  • Target capability: propose a NetSuite invoice transformed from the sales order for a fulfillment that has no invoice
  • Target capability: propose a Xero ACCREC invoice, left as a draft, for completed Asana or monday.com work, with the task named in the Reference
  • Target capability: propose marking a shipment or task not billable, with the reason, so it leaves the list
  • Target capability: propose a reminder to the account owner in Slack when an item stays unbilled past the days you set

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

What you can build

  • Invoice every shipment before close

    ShipStation shipments with a shipDate in the period and no Business Central salesInvoice carrying the same orderNumber become one draft invoice each, built from shipmentItems.

    With ShipStation, Microsoft Dynamics 365 Business Central

  • Bill fulfilled orders NetSuite has not billed

    Where Advanced Shipping keeps fulfillment and invoicing apart, item fulfillments with no invoice are proposed as invoices transformed from their sales orders.

    With NetSuite

  • Turn finished project work into a Xero invoice

    Asana tasks completed in a billable project, with a customer and rate in custom_fields, are proposed as one Xero ACCREC invoice per customer per month, with each task listed.

    With Asana, Xero

  • Chase the item nobody owns

    A monday.com item marked delivered and still unbilled after your interval is posted to the account owner's Slack channel, with approve and not-billable choices.

    With monday.com, Slack

Requirements

  • A source of shipments or completed work: ShipStation, Business Central, NetSuite, Asana, or monday.com
  • A ledger connector holding invoices: Business Central, NetSuite, or Xero
  • A shared key: the order number on shipment and invoice, or the customer and task id on the work item and the invoice reference
  • The interval after shipment or completion at which an item counts as unbilled, and the projects or boards that are billable
Authentication
It keeps no credentials of its own. It reads shipments, work, and invoices through the connectors you attach, with the scopes you grant.

Limits

  • It matches by order number or task reference. A shipment with no order number, or a task with no customer field, is listed, never drafted.
  • Prices come from the order or the task's rate field. Where neither exists, the draft carries quantities and blank prices for a person to fill.
  • ShipStation returns only shipments with labels generated in ShipStation. Shipments labelled elsewhere are not seen.
  • It posts no invoice and sends no reminder on its own. Each one waits for approval.

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 Unbilled Shipment ↗

Questions and answers

What am I approving, the invoice itself?
Yes. Each proposal is a complete draft invoice: customer, lines, quantities, prices where known, and the shipment or task it bills. Approve it, edit lines, or mark the item not billable with a reason.
How do I know an item was billed and not raised twice?
Each approval leaves a receipt naming the shipment or task, the invoice number created, who approved, and when. The receipt is checked before any item is proposed again, so a billed shipment stays billed.
Does it post or send invoices without me?
No. Drafts are created only on approval, once. Posting and sending remain steps a person takes in the ledger, or a separate approval if you want the post included.
Ask about Unbilled Shipment

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