Purchase order accruals are the estimated liabilities recorded at financial close for goods received but not yet invoiced. For mid-market companies running 50 to 100 purchase orders monthly, missing these accruals results in auditors flagging the balance sheet for unrecorded liabilities and formal Q2 variances. ProcureDesk automates the received-not-invoiced list by connecting the PO, goods receipt, and invoice, preventing prior-period financial corrections.

At Q1 close, the failure takes a specific form: goods received in March, invoice arriving in April. This leaves the quarterly P&L understating expenses before it reaches the CFO.

ProcureDesk solves this upstream. By using automated 3-way matching to connect the purchase order, the goods receipt, and the vendor invoice in one system, the received-not-invoiced list exists with 100% accuracy before the close even begins.

TL;DR

• Q1 Accrual Risk is Peak: High purchase volumes and cross-period deliveries create significant unrecorded liability exposure on the Q1 balance sheet.

• Manual Tracking is Flawed: Disconnected procurement and AP systems force finance teams to rely on stale warehouse data, email chasing, and estimates.

• Subledger Corruption is Costly: Manual journal entries posted directly to AP create reconciliation discrepancies and trigger early audit findings during interim procedures.

• System Unification is Essential: Connecting the purchase order, goods receipt, and vendor invoice into one P2P platform establishes a single source of truth.

• Three-Way Matching is the Key: Automating the match replaces accounting guesswork with a 100% accurate, real-time “received-not-invoiced” report on Day 1 of close.

• Data Integrity Protects the P&L: Building accrual registers from confirmed receipt data ensures reversals post correctly, avoiding negative expense balances in subsequent periods.

• Faster Close Enables Strategy: Eliminating the manual accrual scramble compresses the close cycle and brings unmanaged tail spend under strict central financial control.

Why Q1 Close Is the Hardest Close for Purchase Order Accruals

Every close has an accrual problem. Q1 has three of them at once.

Volume. Three months of purchase activity means more open POs at March 31 than at any other quarter end. A company running 50 POs a month enters Q1 close with up to 150 potential received-not-invoiced items to identify and price.

Carry-over. POs placed in late December for goods delivered in January straddle two reporting periods. The controller must confirm whether each liability belongs in Q4 or Q1. Without a current receipt record, that answer requires chasing the warehouse team during the most pressured week of the year.

Scrutiny. Quarterly numbers go to leadership, boards, and often investors. An accrual corrected quietly in November becomes a formal Q2 variance against a Q1 comparable.

Auditors time interim procedures around Q1, requesting March 31 workpapers as early tests of opening balances. A missed accrual at Q1 can surface as a formal finding before the annual audit starts. Fixing the accrual problem starts upstream. For the broader impact of disconnected procurement on close timing, see How to Reduce Month-End Close Time.

What Manual Accrual Tracking Looks Like When It Fails

The failure sequence is the same at almost every mid-market company. Here is how it plays out.

Step 1. Pull the open PO report.

The controller exports every PO with no matching invoice in the AP system. For a company running 50 to 100 purchase orders a month, that list runs 30 to 80 lines at Q1 close. The report confirms the PO exists and the dollar amount. It says nothing about whether goods were received.

Step 2. Cross-reference the goods receipt log.

The controller goes to a second source: a warehouse receiving spreadsheet, a Slack channel where the operations team posts delivery notes, or a folder of scanned packing slips. This source is rarely current. Receipts entered during the week before close often miss deliveries from the final three business days of March.

For how this same gap affects invoice approval timing, see AP Invoice Approval Process.

Step 3. Email the operations team.

For every PO where receipt status is unclear, the controller sends a follow-up. Replies take a day, sometimes longer. Some do not arrive. The controller makes a judgment call on incomplete data, then builds an accrual register that reflects guesses as much as confirmed facts.

Step 4. Post the accrual entries.

Each entry debits the expense account and credits Accrued Liabilities. Not Accounts Payable. That distinction is not cosmetic: AP balances come from the AP subledger. A manual journal entry posted directly to AP corrupts the subledger reconciliation and creates discrepancies during audit.

Free Resource: Need a better way to track outstanding liabilities once those invoices finally do arrive? Download our free Accounts Payable Aging Report Template for Excel and Google Sheets to prioritize your vendor payments.

Step 5. Schedule the reversals.

Each accrual entry needs a reversal dated the first day of April. A reversal dated April 2 instead of April 1 leaves a negative balance in the expense account for part of the month. Auditors flag negative expense balances. So do management reports.

The root cause of every failure at steps 2 and 3 is the same: the purchase order, the goods receipt, and the invoice live in three separate places, and no finance system owns the connection between them. 

How a Connected P2P System Changes Every Failure Point

When the PO, the goods receipt, and the invoice all live in one system, the five-step failure sequence compresses to one: pull a list.

Failure 1 resolved: the open PO report shows receipt status. In ProcureDesk, every purchase request moves through approval and converts to a PO. That PO sits in the same system where the receiving team logs the goods receipt and where AP processes the matching invoice. The controller does not need to cross-reference a separate warehouse spreadsheet. Receipt status against every open PO is visible at any point in the period.

Failure point 2 resolved: the stale goods receipt log. When the receiving team marks a PO as received inside ProcureDesk, that status updates immediately across the system. A controller checking open POs at 9pm on Day 3 of close sees the same receipt status the warehouse logged at 4pm. No delay between the dock and the finance view. No email required.

Failure point 3 resolved: the judgment call on incomplete data. ProcureDesk’s 3-way matching procurement software connects each invoice to the corresponding PO and the goods receipt. When a vendor invoice has not arrived by close, the controller can see exactly which POs are in received-not-invoiced status based on confirmed receipt data. The accrual decision is not an estimate from an operations manager’s memory.

Failure point 4 resolved: the accrual register. With every received-not-invoiced PO visible in one current data source, the controller builds the register from confirmed data. Each line carries the expense account coding set when the PO was created. The controller is reviewing a list, not reconstructing one from three disconnected sources.

Failure point 5 stands: reversal entries must still be dated correctly. ProcureDesk works alongside QuickBooks, NetSuite, Xero, and Sage Intacct. It does not replace those systems or post journal entries directly to your general ledger. The accrual reversal entries on April 1 are still posted by your team in your GL. What changes is that those entries are based on confirmed receipt data rather than estimates and follow-up emails.

ProcureDesk is built for companies with 50 to 500 employees. That covers the manufacturing, distribution, and biotech companies where indirect, MRO, and lab supply purchases generate the most received-not-invoiced exposure at quarter end.

The 200+ punchout catalog connections include Amazon Business, Thermo Fisher Scientific, and Grainger. Those purchases move through ProcureDesk’s PO system from the start. They do not appear later as a credit card line requiring a retroactive accrual with no receipt documentation, a critical step in gaining control over your tail spend management.

Funai Lexington Technology uses ProcureDesk for manufacturing procurement connected to QuickBooks. Their case shows what the procurement-to-AP link looks like in practice for a mid-market operation. 

See the Funai Lexington Technology case.

How to Set Up PO Accrual Tracking Before Your Next Close

Step 1. Identify every vendor category with received-not-invoiced exposure.

List every category where invoices routinely arrive after the period closes: MRO and indirect supplies, contract services, freight carriers, and professional services. Confirm whether POs go out before the purchase happens or after. Any category without pre-purchase POs cannot produce a reliable accrual register at close.

Step 2. Require a PO before every purchase in those categories.

A goods receipt without a matching PO leaves no financial record until the invoice arrives. The PO is what creates the link between receipt and recorded liability. In ProcureDesk, purchase requests require approval before a PO is issued. No vendor order goes out without one.

Step 3. Confirm that goods receipt entry happens at the time of delivery.

The received-not-invoiced list is only as accurate as the receipt data behind it. If your current process logs receipts two or three days late, the accrual register runs behind by the same margin. Adjust the receiving workflow before the next close period starts, not during it.

Step 4. Pull the received-not-invoiced report on Day 1 of close.

With receipt status current in the system, run the report on the first business day of close. Apply your materiality threshold. Which PO amounts are large enough to affect the quarterly P&L? Build the register from confirmed data before deadline pressure removes the option for careful review.

Step 5. Post accruals with reversal dates set to the first day of the new period.

Date every reversal April 1, not April 2. A reversal dated one day late creates a negative expense balance for part of the following month. That negative balance appears in management reports and flags during audit review. 

Frequently Asked Questions

What is a purchase order accrual? 

A purchase order accrual records a liability for goods received before period close but not invoiced. Under GAAP, receipt triggers the event. The entry debits the expense account and credits Accrued Liabilities. For companies managing 50+ monthly POs, this prevents understating quarterly expenses.

How do you record an accrual for goods received but not invoiced? 

At period end, identify every PO with a confirmed goods receipt and no matching invoice. Post a journal entry debiting the expense account and crediting Accrued Liabilities. Include the PO number and receipt date in the entry description to satisfy audit sampling requirements.

What causes accrual errors at month-end close? 

The most common cause is a 3-to-5 day lag between goods arriving at the dock and the receipt entering the finance system. Accruals are also missed when a purchase bypasses the PO process entirely, leaving no three-way matching record of the obligation.

What is the journal entry for accrued expenses at month end? 

The standard accrual entry debits the specific expense account and credits Accrued Liabilities. When the actual vendor invoice arrives in the following period, the accrual reverses on Day 1. This ensures a zero net effect across the reporting window, matching the GAAP principle.

How long should the month-end close process take? 

High-performing finance teams close in 3 to 5 business days. Ledge’s 2025 benchmarks show 50% of teams take 6 or more days. Manual PO accrual reconciliation across disconnected warehouse and AP systems is the primary delay extending close past Day 5.

How does ProcureDesk handle PO accruals at quarter-end close? 

ProcureDesk connects the PO, goods receipt, and vendor invoice in one platform. Controllers identify received-not-invoiced status using real-time data instead of emailing operations. The system syncs with QuickBooks, NetSuite, Xero, and Sage Intacct, allowing your team to post accurate GL entries in minutes.

If you process more than 100 invoices a month and your accrual register relies on open PO exports, warehouse emails, and judgment calls, the problem is upstream.

ProcureDesk connects the PO, the goods receipt, and the invoice in one system. It deploys in 2 to 4 weeks alongside your existing accounting software. See what the received-not-invoiced register looks like when it is current before close begins.

Use the ROI calculator to run the numbers, or request a 20-minute walkthrough built around a Q1 close scenario.