Reference · built on requestOperator by FibricFinance & billing

Month-End Cutoff

Shipments, receipts, and invoices dated near period close, with corrections and accruals proposed before the period locks.

Request accessPricing ↗

About

Close is the week when a shipment posted on the first of the month belongs to the last, and a receipt sitting in the warehouse has no bill. This operator watches the days on either side of the period boundary. It reads posted sales shipments and purchase receipts in Business Central, item fulfillments in NetSuite, ShipStation shipments by shipDate, and purchase order rows in Katana by received_date. It compares each document's date with the period it posted to and with the invoice or bill that should follow it.

Where a document sits in the wrong period, or has no invoice or bill yet, it proposes the fix: a posting date correction, an accrual with its reversal, or an invoice to raise. It watches the period's closed and dateLocked flags, and stops proposing entries for a period once it is locked.

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

  • Business Central salesShipments and purchaseReceipts with postingDate, orderNumber, and lines, read for the days around the period boundary
  • Business Central accountingPeriods with startingDate, closed, and dateLocked, which tell it when a period can no longer take entries
  • NetSuite item fulfillments recorded separately from billing when Advanced Shipping is on, and the Period Close Checklist state, including Lock A/R and Lock A/P
  • ShipStation shipments by shipDate and orderNumber, which is when goods left, regardless of when the ledger posted them
  • Katana purchase order rows with received_date and arrival_date, for goods received before the vendor's bill
  • Sales invoices and purchase invoices in the ledger, matched to shipments and receipts by orderNumber
  • Journals it proposed at earlier closes, so a reversal is tied to the accrual it undoes

Proposed actions

  • Target capability: propose moving a shipment or receipt whose postingDate falls in the wrong period, with the ship date and the boundary shown
  • Target capability: propose an accrual for goods received with no bill by close, as a Sage Intacct GLBATCH with a REVERSEDATE in the next period
  • Target capability: propose a sales invoice for a shipment that left the dock in the period but has no invoice, built from the shipment lines
  • Target capability: propose a cutoff list for the controller: every document within the window you set, its date, its period, and its match
  • Target capability: propose the Resolve Date/Period Mismatches items on the NetSuite checklist as one batch, each with the correcting date

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

What you can build

  • Find the shipment that posted a day late

    Business Central salesShipments whose postingDate is the first day of the new period are compared with the ShipStation shipDate. Where goods left in the old period, a posting date correction is proposed.

    With Microsoft Dynamics 365 Business Central, ShipStation

  • Accrue what arrived without a bill

    Katana purchase order rows with a received_date inside the period and no purchase invoice become one Sage Intacct journal proposal each, with the reversal dated to the next period.

    With Katana Cloud Inventory, Sage Intacct

  • Work the NetSuite checklist with evidence

    Item fulfillments dated inside the period whose invoice posted after it are listed against the Resolve Date/Period Mismatches task, each with a proposed correcting date, before Lock A/R.

    With NetSuite

  • Stop at the lock

    When the accountingPeriod shows dateLocked, proposals for that period end. Anything found later is proposed for the open period, with the original date carried on it.

    With Microsoft Dynamics 365 Business Central

Requirements

  • A ledger connector that exposes accounting periods and posted documents: Business Central, NetSuite, or Sage Intacct
  • A shipping or inventory source with ship and receipt dates independent of the ledger: ShipStation, Katana, or both
  • The cutoff window in days on each side of period end, and the accrual and reversal accounts to use
  • Order numbers carried on shipments, receipts, invoices, and bills, which is how documents are paired
Authentication
It holds no credentials. It reads periods, documents, and journals through the ledger, shipping, and inventory connectors you attach, with the scopes you grant.

Limits

  • It compares dates and matches by order number. Whether title passed at the dock or on delivery is your rule, set per customer or vendor.
  • Business Central exposes salesShipment and purchaseReceipt as read-only resources. A posting date change is entered in Business Central by a person from the proposal.
  • Once a period shows closed or dateLocked, it proposes nothing dated inside it. Late items are proposed for the open period with a note.
  • It posts, moves, or reverses nothing on its own. Each item waits for the controller.

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 Month-End Cutoff ↗

Questions and answers

What does the controller approve, one item or the whole close?
Either. Each correction, accrual, or invoice is its own proposal and can be approved alone. The cutoff list can also be approved as a batch, in which case each item still leaves its own receipt.
What is written down for the auditor?
For every approved item: the document, its original date and period, the proposed date or entry, the match it was based on, who approved it, when, and the reversing entry where one applies. Declined items keep the reason.
Does it ever post an entry or change a date by itself?
No. A journal, an invoice, or a date change happens only after a person approves, and only once. Where the ledger offers no write for a change, the proposal is a prepared entry for a person to key.
Ask about Month-End Cutoff

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