Reference · built on requestOperator by FibricFinance & billing

Receipt Not Invoiced

Goods received with no vendor invoice after the agreed interval, with an accrual and a vendor query proposed for each.

Request accessPricing ↗

About

Goods arrive before the vendor's invoice does. Between the two, the liability exists but the ledger does not show it. This operator watches receipts in your inventory or procurement system and vendor bills in your ledger. When a receipt has no bill after the interval you set for that vendor, it raises the case.

For each open receipt it proposes two things: an accrual entry for the period, and a query to the vendor asking for the invoice. You approve, edit, or decline each one. When the bill arrives, it proposes the reversal. Every approval leaves a receipt: what was posted or sent, who approved it, and how to undo it.

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

  • Purchase order receipts in your inventory system: Katana purchase order rows with a received_date, or a purchase_order.received event
  • Fishbowl Advanced purchase orders in Partial or Fulfilled status, with quantityFulfilled and dateLastFulfilled on each line
  • Posted purchase receipts in Business Central, each carrying its orderNumber, vendorNumber, postingDate, and purchaseReceiptLines
  • Vendor bills and purchase invoices in the ledger: QuickBooks Online Bill, Xero ACCPAY invoices, Business Central purchaseInvoices
  • The interval agreed with each vendor, and the accrual account you name for received-not-invoiced liabilities
  • Journals it proposed earlier, so a reversal is tied to the accrual it undoes
  • Delivery and bounce events on the vendor queries it sent, through Amazon SES or Twilio SendGrid

Proposed actions

  • Target capability: propose an accrual journal for each receipt without a bill, dated to the period you name, with the receipt and order attached
  • Target capability: propose a vendor query by email naming the purchase order, the receipt date, and the quantity received
  • Target capability: propose the reversing entry once the vendor bill is matched to the receipt
  • Target capability: propose closing a purchase order line short where the vendor confirms nothing further will ship or be billed
  • Target capability: propose a reminder to the buyer in Slack or Microsoft Teams when a query goes unanswered past a second interval

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

What you can build

  • Accrue what the warehouse has received

    At period end, Katana receipts with no QuickBooks Online Bill become one accrual proposal each. You approve the batch, the journals post, and each carries the purchase order it covers.

    With Katana Cloud Inventory, QuickBooks Online

  • Ask the vendor before the close, not after

    Fishbowl Advanced lines fulfilled past the agreed interval trigger a vendor query, sent through Amazon SES once a buyer approves. Bounces come back as new cases.

    With Fishbowl Advanced, Amazon Simple Email Service

  • Keep buyers in the loop

    Business Central purchase receipts without a purchaseInvoice are posted to the buyer's Slack channel with the vendor's silence measured in days. The buyer approves the query from the message.

    With Microsoft Dynamics 365 Business Central, Slack

  • Reverse the accrual when the bill lands

    When an ACCPAY invoice appears in Xero carrying the same purchase order, it proposes the reversing manual journal against the accrual it raised earlier.

    With Xero

Requirements

  • An inventory or procurement connector that exposes purchase orders and their receipts: Katana Cloud Inventory, Fishbowl Advanced, or Business Central
  • A ledger connector where vendor bills and journals live: QuickBooks Online, Xero, Sage Intacct, or Business Central
  • An email or chat connector for the vendor query and the buyer reminder: Amazon SES, Twilio SendGrid, Slack, or Microsoft Teams
  • A default interval, any per-vendor overrides, and the accrual account to post to
  • Purchase order numbers carried on receipts and on bills, which is how the two are matched
Authentication
It holds no credentials of its own. It reads and proposes through the inventory, ledger, and messaging connectors you attach, each with the scopes you grant.

Limits

  • It matches a bill to a receipt by purchase order number and vendor. A receipt with no purchase order is listed, never matched.
  • Price differences between the order and the bill are reported, not resolved. Quantity is what it matches on.
  • Where the ledger connector proposes bills but not journals, the accrual arrives as a prepared entry for you to post by hand.
  • It does not post, send, or close anything on its own. Each proposal waits for a person.

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 Receipt Not Invoiced ↗

Questions and answers

What does a person approve?
Each accrual and each vendor query is its own proposal. You see the receipt, the purchase order, the vendor, the days since receipt, and the exact journal lines or the message text. You approve it, edit it, or decline it. A batch can be approved at once.
What record is left behind?
One receipt per approved proposal: the inventory receipt it covers, the journal or message it produced, who approved it, when, and the reversing entry that undoes it. Declined proposals are kept with the reason.
Will it ever post an accrual or email a vendor on its own?
No. Nothing is written to the ledger and nothing is sent to a vendor until a person approves. An approved item runs once, never twice, and a repeat of the same receipt is recognized and skipped.
Ask about Receipt Not Invoiced

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