What is Dynamics GP Received Not Invoiced?

Definition

Dynamics GP Received Not Invoiced describes purchasing transactions where goods or services have been received and recorded in Microsoft Dynamics GP, but the corresponding vendor invoice has not yet been entered or posted. This situation represents an accrued purchasing obligation because the business has received economic value even though the supplier invoice is still outstanding.

The concept is closely related to goods received not invoiced, commonly abbreviated as GRNI. Monitoring these transactions is important for accurate month-end cut-off, expense recognition, inventory accounting, accounts payable reconciliation, and financial reporting.

Table of Contents

How Received Not Invoiced Works

The process generally begins with a purchase order. When goods arrive, the receiving transaction records the quantity received in Dynamics GP. If the supplier has not yet submitted an invoice, the receipt remains unmatched to a vendor invoice. The accounting treatment can therefore recognize the receipt while the final supplier liability is completed when the invoice arrives.

For example, a company orders inventory worth $12,500 and receives the complete shipment on December 29. The supplier sends the invoice on January 4. At December 31, the company has received the inventory even though the invoice is not yet recorded. The received-not-invoiced balance helps ensure the December financial statements recognize the appropriate transaction in the correct reporting period.

Accounting and Month-End Treatment

Received-not-invoiced transactions are particularly important during period close because the receipt date and invoice date can fall in different accounting periods. Finance teams review open receipts, identify goods or services already received, estimate the related obligation when necessary, and ensure the appropriate accounting treatment is reflected in the reporting period.

A Goods Received Accrual provides a useful accounting framework for recognizing the obligation associated with goods received before supplier billing is recorded. When the actual invoice is posted, the temporary accrual or receipt-related accounting is reconciled according to the organization's Dynamics GP configuration and accounting procedures.

Accurate cut-off requires finance teams to consider receiving dates, purchase order values, expected invoice amounts, partial receipts, returns, price differences, and transactions posted immediately before or after period end.

Reconciliation and Exception Management

A practical reconciliation compares open purchase receipts with vendor invoices and related accounts payable records. Finance teams should investigate aged balances, partial receipts, quantity differences, price variances, canceled orders, and receipts for which invoices remain outstanding.

  • Open receipt: Goods have been received but no matching invoice has been recorded.
  • Partial receipt: Only part of the purchase order has been received and invoiced.
  • Invoice variance: The invoice quantity or price differs from the recorded receipt or purchase order.
  • Aged receipt: A receipt remains unmatched for an extended period and requires follow-up.

These reviews help prevent purchasing accruals from remaining unresolved and provide stronger visibility into outstanding supplier obligations.

Dynamics GP Integration and Financial Reporting

Received-not-invoiced information can affect inventory, accounts payable, accruals, and general ledger reporting. Organizations extending Dynamics GP with other finance applications should establish clear ownership of purchasing, receiving, invoice, and accounting data.

ERP integration should also preserve consistent account mappings. Keep Your GL Codes Aligned in Any ERP System explains why connected ERP environments need consistent relationships between related GL accounts. Similarly, What Drives COA Differences in ERP Platforms? provides context for why chart-of-accounts structures can differ across Dynamics and other ERP systems.

Businesses reviewing their ERP architecture can also use How to Choose the Right ERP Consulting Firm in 2026 as a reference when evaluating Dynamics expertise, finance workflow extensions, ERP integration, and automation strategy.

Automation and Dynamics GP Received Not Invoiced

Finance teams can use AI-enabled workflows to identify receipts without corresponding invoices, organize supporting transaction data, and route items for appropriate accounting review. The Hyperbots Platform supports company-specific configurations involving ERP integration, workflows, roles, and GL structures through a no-code framework.

Process Specific Capabilities can support finance workflows using domain-relevant data, while Ready to Deploy Capabilities provide pre-trained agents and ERP connectors for finance processes. Self Learning Capabilities allow co-pilots to learn from human actions and refine workflow and GL-coding decisions.

A Human in the Loop approach can route unusual receipts, accounting exceptions, and approval decisions to finance professionals while preserving the underlying transaction context. This supports structured review of received-not-invoiced balances and related accrual activities.

Best Practices

Effective management of Dynamics GP received-not-invoiced transactions depends on consistent receiving procedures and timely reconciliation. Finance teams should establish a defined month-end review process rather than relying solely on invoice arrival to identify liabilities.

  • Review open receiving transactions before every period close.
  • Compare receipts with purchase orders and subsequent vendor invoices.
  • Investigate aged and unusually large received-not-invoiced balances.
  • Document procedures for estimates, accruals, reversals, and invoice matching.
  • Review cut-off transactions around the beginning and end of each reporting period.
  • Maintain consistent GL mappings across purchasing and accounting workflows.

Summary

Dynamics GP Received Not Invoiced represents goods or services recorded as received before the related vendor invoice has been entered. Proper management supports accurate expense and inventory recognition, period-end cut-off, accrual accounting, and financial reporting. By reconciling receipts with invoices, investigating outstanding balances, maintaining appropriate GL mappings, and applying structured workflow controls, finance teams can improve the accuracy and timeliness of their month-end close.