Every Controller knows the feeling. It’s the 2nd of the month. Your inbox is full of invoices that don’t have PO numbers. Your AP specialist is emailing department heads asking who ordered what. And you’re manually pulling GL codes from vendor emails because nobody assigned them when the purchase was made.

The average month-end close for a mid-market company takes 6 to 10 business days. The target is 3 or fewer. That gap has almost nothing to do with what happens at close. It’s caused by what happens, or doesn’t happen, between the 1st and the 30th. At ProcureDesk, we see this pattern every week.

You’re not slow at closing the books. You’re fast at reconstructing a month’s worth of undocumented purchases, unmatched invoices, and missing receipts. The problem is that reconstruction shouldn’t be part of the job at all.

Our customers routinely compress month-end close after cleaning up the upstream purchasing process. myDNA, a genomics company, cut their close from 7-8 days to 3 days after putting a purchase order process in place with ProcureDesk.

This article breaks down the five specific upstream problems that drag out close, what a 3-day close actually looks like when the upstream is clean, and the exact fixes you can put in place to get there.

If you’re a Controller or CFO at a company with 100 to 1,000 employees, this is written for you. The problems described here are specific to mid-market finance teams that have outgrown spreadsheets but haven’t yet put a formal procurement process in place.

TL;DR

1. Slow close means slow decisions. A 9-business-day close means leadership reviews last month’s data when this month is half over.
2. Best-in-class benchmark. Top AP teams close in 3.1 days with a 9% exception rate. Non-automated teams take 17.4 days with 22% exceptions. (Ardent Partners, 2024)
3. It’s a procurement problem, not an accounting one. Slow close traces to invoices without POs, missing GL codes, and retroactive approvals. All originate upstream of finance.
4. The cost of manual AP. At $9.40 per invoice, 100 manually-processed invoices per month cost about $11,300 per year. That excludes Controller time on corrections.
5. A 3-day close is preparation, not speed. Capture the PO, GL code, and approval at the point of request. By the 1st, 80% of close work is done.
6. “No PO, No Pay” changes behavior in 90 days. It works only when the procurement tool makes raising a PO easier than skipping one.
7. Track Days to Close with exception rate. When exception rate drops toward the 9% best-in-class benchmark, DTC compresses in parallel.

The Real Reason Close Takes So Long: It’s a Month-Long Problem

Controllers don’t have a close problem. They have a procurement problem that shows up at close.

Here’s how it works in most growing companies. During the month, employees make purchases through a mix of channels: credit cards, vendor accounts, phone orders, email requests. Some of those purchases have a purchase order. Most don’t. Some have approvals documented somewhere. Many don’t.

By the time the 1st rolls around, your AP team isn’t recording transactions. They’re reconstructing them. They’re digging through emails to find out who ordered what, asking department heads for GL codes that should have been assigned weeks ago, and chasing receipts from people who forgot they received anything.

You can’t speed up close by working harder at close. You speed up close by fixing the upstream process so there’s less to reconstruct when the month ends.

Think of it this way. If 200 invoices arrive during the month and 150 of them have no PO number, no receipt on file, and no GL code assigned, your AP team has 150 transactions to manually research, code, match, and approve during close. That’s not a close problem. That’s a procurement problem.

The numbers back this up. According to Ardent Partners’ 2024 State of ePayables research, the average organization takes 9.2 days to process a single invoice. For companies without automation, that number jumps to 17.4 days. Exception rates, meaning invoices that can’t be processed without manual intervention, run at 22% for non-automated teams. Every one of those exceptions becomes a line item your team has to chase during close.

The companies that close in 3 days don’t have bigger AP teams. They have cleaner upstream data. Everything that can be documented before close is documented before close. The AP team’s job at month-end is to review the 10% that didn’t match cleanly, not to reconstruct the other 90%.

The 5 Specific Things That Slow Down Month-End Close

These aren’t theoretical. They’re the exact problems we see in the finance teams we work with at ProcureDesk, across biotech, construction, education, manufacturing, and professional services. If you’re spending more than 5 days on close, at least three of these are happening in your organization.

1. Invoices Arrive with No Matching Purchase Order

This is the single biggest driver of slow close. An invoice shows up from a vendor, and nobody in AP knows what it’s for. There’s no PO number on the invoice. There’s no record of who ordered it, why, or whether it was approved.

So AP has to play detective. They email the person who might have placed the order. That person doesn’t respond for two days. When they do respond, they can’t remember the details. The invoice sits in limbo while your team pieces together the story.

Coast Flight Training, an aviation academy with three U.S. locations, experienced exactly this problem. Their CFO, Kevin Slatnick, documented a 30% reduction in invoice processing time after they started requiring POs for all purchases and automating the matching process.

2. Missing Receipts Break the 3-Way Match

The 3-way match is the gold standard for invoice validation: match the purchase order, the receipt, and the vendor invoice. When any of those three documents is missing, the match fails and someone has to intervene.

Receipts are the most common missing piece. An employee ordered lab supplies three weeks ago. The supplies arrived. But nobody logged the receipt in any system. Now AP needs that receipt to validate the invoice, and the employee who received the package doesn’t remember the details.

This is especially painful in biotech and manufacturing environments where multiple shipments arrive daily. If receiving isn’t built into the workflow, receipts become a month-end scavenger hunt.

3. Wrong or Missing GL Codes

When GL codes aren’t assigned until the invoice hits AP, your team is making coding decisions on hundreds of transactions at once, under deadline pressure, with incomplete information.

Here’s a scenario we see constantly. An employee orders $8,000 in safety equipment. The invoice arrives at AP with no GL code. The AP specialist codes it to “Office Supplies” because the vendor name isn’t familiar. At month-end, the CFO sees office supply spending 60% over budget and asks what happened. Meanwhile, the safety budget looks underspent. Two journal entries later, the numbers are corrected, but you’ve lost an hour of close time on a single transaction.

Multiply that by 30 or 40 miscoded invoices per month and you start to see the problem. Ardent Partners reports that 53% of AP professionals cite invoice exceptions as their biggest operational challenge. Wrong coding is one of the most common exception types.

Every miscoded invoice means a correction. Every correction takes time. And those corrections are happening during close, which is exactly when your team has the least time to spare.

4. Unapproved Purchases That Get Expensed After the Fact

An employee buys something without a PO. They submit an expense report or the invoice just shows up. Now the Controller has to decide: approve it retroactively or push back and delay payment?

Either way, it eats time. Retroactive approval requires gathering context that should have existed before the purchase. Pushing back creates friction with the employee and delays closing the transaction.

School in the Square, a New York City charter school, was spending two full days processing each purchase cycle before they set up a PO-first workflow. After implementation, that dropped to 4 hours. The difference was eliminating the after-the-fact approval scramble.

5. Vendor Invoice Disputes

The vendor invoices for $12,500. Your team thinks the order was $11,800. There’s no PO to compare against, so you can’t prove who’s right. This triggers a back-and-forth with the vendor that can stretch for days.

Without a PO on file, invoice disputes turn into guesswork. Nobody can prove what was agreed. With a PO, it’s a 30-second comparison: here’s what we ordered, here’s what you invoiced, here’s where it doesn’t match. Dispute resolution drops from days to minutes.

Invoice disputes also damage vendor relationships. When you can’t point to a document that shows the agreed-upon price, the vendor loses confidence in your process. They start padding estimates. They become less flexible on payment terms. A PO on file protects both sides.

This is why many Controllers adopt a “No PO, No Pay” policy. If a vendor invoice doesn’t reference a valid PO number, it doesn’t get paid until one is created and approved. It sounds strict, but it changes behavior fast. Vendors start asking for PO numbers before shipping. Employees start submitting purchase requests before ordering. Within a few months, the number of surprise invoices at close drops dramatically.

What Does a 3-Day Close Actually Look Like?

A 3-day close isn’t aspirational. It’s what happens when the upstream purchasing process is clean.

The difference between a 3-day close and a 10-day close isn’t speed. It’s preparation. A 10-day close means your team is spending the first 7 days gathering information that should have been captured during the month. A 3-day close means that information already exists in the system, and your team is just reviewing it.

Here’s the workflow when procurement is documented in real time:

• Every purchase starts with a request. An employee submits a purchase request in the system. The request includes what they need, the vendor, the amount, and the GL code. The request routes to the right approver automatically.
• Approved requests become purchase orders. Once approved, the system converts the request into a PO and sends it to the vendor. The PO number is attached to the transaction from day one.
• Receipts are logged when goods arrive. The employee who receives the goods confirms delivery in the system. This takes about 30 seconds.
• Invoices match automatically. When the vendor invoice arrives with the PO number on it, the system matches it against the PO and the receipt. If everything lines up, the invoice goes straight to the payment queue. No human touch required.
• GL codes are already assigned. The code was set at the time of the original request. It followed the PO through matching. There’s nothing to re-key at close.

By the time the 1st rolls around, 80% or more of your transactions are already documented, matched, and coded. Close becomes a review of exceptions and a final reconciliation, not a reconstruction of the entire month.

Here’s what a typical 3-day close looks like in practice:

• Day 1: Review any invoices that didn’t match automatically. In ProcureDesk, these show up in an exception queue with the specific mismatch flagged (wrong quantity, price difference, missing receipt). Pull the open PO report to identify committed spend that hasn’t been invoiced yet. Record accruals based on open POs, not guesswork.
• Day 2: Reconcile bank statements and credit card transactions. Review any journal entries needed for corrections. Run variance reports against budget.
• Day 3: Final review of financial statements. Lock the period. Deliver reports to the CFO or board.

Compare that to the typical 10-day close, where days 1 through 5 are spent chasing invoices, matching them manually, correcting GL codes, and getting retroactive approvals. The actual accounting work doesn’t start until day 6.

Ardent Partners’ best-in-class benchmark confirms this is achievable. Top-performing AP teams process invoices in 3.1 days with an exception rate of just 9%, compared to 17.4 days and 22% for everyone else.

myDNA hit this target after implementing ProcureDesk. Their month-end close compressed from 7-8 days to 3 days, and AP processing time dropped by 30%. The improvement wasn’t because their team worked faster. It was because there was less to fix.

The Upstream Fixes That Actually Compress Close

Each of the five problems above has a specific upstream fix. Here they are, in the order you should tackle them.

Fix 1: Require a Purchase Request Before Every Purchase Above Your Threshold

Not after. Not sometimes. Every time. Define your threshold (most ProcureDesk customers set it between $100 and $500), and require a purchase request for anything above that amount.

The purchase request captures the who, what, why, and how much before money moves. It routes to the right approver based on your rules, whether that’s by amount, department, vendor, or any combination.

ProcureDesk’s approval workflows handle this automatically. You set the rules during implementation, and the system routes every request to the right person without anyone having to think about it.

A good rule of thumb: use the 80/20 principle. Senior management should only approve the top 20% of requests by dollar value, which typically covers 80% of total spend. Everything else gets approved by first-line managers who are closest to the need. This keeps the process moving without creating a bottleneck at the top.

Fix 2: Assign GL Codes at the Time of Request, Not at Invoice Entry

When the requester submits a purchase request, they select the GL code. The system can suggest codes based on the vendor, the department, or the item category. If the requester picks the wrong code, the approver catches it during review.

Here’s the before and after.

The code follows the PO through the entire transaction lifecycle. When the invoice arrives and matches the PO, the GL code is already assigned. Your AP team never re-keys it.

This single change eliminates one of the biggest sources of month-end journal entries. Wrong GL codes at invoice entry are a downstream symptom of a system that doesn’t capture the code upstream.

Fix 3: Build Receipts into the Purchase Workflow

Receiving shouldn’t be a separate process that people forget about. It should be a built-in step that happens when goods arrive.

Equality Charter School tackled this directly. Before implementing a PO system, their order placement process took 5 days. After implementation, it dropped to under 24 hours, with an 87% reduction in PO cycle time. Receipts were part of the workflow from day one, so the 3-way match happened automatically.

ProcureDesk notifies the requester when a PO has been fulfilled by the vendor and prompts them to confirm receipt. If they don’t respond, the system sends reminders. No one on your AP team has to chase anyone.

Fix 4: Automate 3-Way Matching

Manual invoice matching is where most AP teams lose the most time. Pulling up the PO, finding the receipt, comparing line items, checking quantities and prices. It’s tedious and error-prone.

Automated 3-way matching does this in seconds. The system reads the invoice (using OCR to extract key data), finds the matching PO and receipt, compares quantities and prices, and routes the invoice based on the result.

• Clean match? Invoice goes straight to the payment queue.
• Missing receipt? System notifies the person who placed the order.
• Price discrepancy? Invoice routes to the buyer or AP team for review.

With ProcureDesk’s 200+ punchout catalog integrations (including Amazon Business, Thermo Fisher, and Grainger), POs created through catalogs contain exact item details. When the vendor invoices against those POs, the match rate is extremely high because the data is structured from the start.

Fix 5: Send POs to Vendors So Invoices Arrive with a PO Number

This is the simplest fix, and it’s the one most companies skip.

When you send a PO to a vendor, the vendor references your PO number on their invoice. That PO number is what allows your system (or your AP team) to match the invoice instantly. Without it, every invoice requires manual research to figure out what it’s for.

ProcureDesk automatically sends POs to vendors after approval. The vendor receives the PO with your PO number, and when they invoice, they include it. The matching loop closes itself.

How Long Does Each Fix Take to Put in Place?

These fixes aren’t multi-quarter IT projects. Here are realistic timelines.

Purchasing policy: 1 week to draft. ProcureDesk offers a free purchasing policy template to get you started. The policy defines your thresholds, approval rules, and vendor management process.

Purchase request process: 2-3 weeks to roll out with a tool like ProcureDesk. This includes setting up approval workflows, configuring GL code mappings, and onboarding your buying team.

GL code assignment at request: Configured during implementation. Takes a few days to map your chart of accounts and set up auto-suggestion rules.

Automated 3-way matching: ProcureDesk implementations run 2-3 weeks, including integration with your accounting system. We support QuickBooks (Online, Desktop, and Enterprise), NetSuite, Sage Intacct, Xero, Microsoft Business Central, and Bill.com.

PO-to-vendor workflow: Enabled on day one of any PO system. Once a PO is approved, it’s sent to the vendor automatically.

The most common objection we hear is adoption. “My team won’t use a new system.” ProcureDesk connects with 200+ vendor punchout catalogs, including Amazon Business. Employees shop the same sites they already use, but through ProcureDesk. There’s no learning curve for requesters. They add items to a cart and submit. The system handles everything else.

ProcureDesk provides white-glove onboarding, meaning our team handles 100% of the setup. No IT team required. Learn more about the purchase order management process in our detailed guide.

The Month-End Close Metric to Track: Days to Close (DTC)

If you want to measure progress, track one number: Days to Close (DTC).

DTC is the number of business days from the end of the month to when the period is locked and financial statements are ready for review. It’s the single most telling metric for the health of your upstream procurement process.

Here’s how to use it:

• Measure your baseline. How many business days does your current close take? If you’re at 8-10, you have significant upstream issues. If you’re at 5-6, you’re closer but still leaving time on the table.
• Track it monthly. DTC should appear on your finance dashboard alongside AP aging and budget variance. It’s that important.
• Set a 6-month target. A team moving from 9 DTC to 4 DTC over 6 months is a realistic, measurable outcome of fixing the upstream process.

ProcureDesk’s spend dashboard gives you real-time visibility into committed spend, open POs, and invoices pending receipt. Accrual prep, which used to be a multi-day exercise, becomes a report you pull in minutes. Open PO reports show you exactly what expenses are committed but not yet invoiced, so your accruals are accurate on day one of close.

When your upstream is clean, DTC stops being a number you dread. It becomes a routine metric that stays stable month after month.

One more thing to watch: the correlation between DTC and invoice exception rate. If your exception rate is above 15%, your DTC will almost certainly be above 5 days. As you fix the upstream and your exception rate drops toward the best-in-class benchmark of 9%, you’ll see DTC compress in parallel.

Track both numbers side by side. When exception rate drops and DTC doesn’t, look at your GL coding process. When DTC drops but exception rate stays flat, you’ve gotten faster at handling exceptions but haven’t eliminated their root cause. Both numbers need to move.

Frequently Asked Questions About Month-End Close

Fix the Upstream. Close Gets Shorter on Its Own.

Month-end close is slow because of upstream procurement problems, not because of what happens at close. The five problems covered here, invoices without POs, missing receipts, wrong GL codes, unapproved purchases, and vendor disputes, all trace back to one root cause: purchases happening without documentation.

Fix the upstream, and close compresses on its own. Your AP team stops playing detective and starts doing what they’re trained for: reviewing exceptions, reconciling accounts, and delivering accurate financial statements.

The Ardent Partners data is clear. Best-in-class AP teams close in 3.1 days with a 9% exception rate. Non-automated teams take 17.4 days with 22% exceptions. The difference is the upstream process.

You don’t need to overhaul your accounting system. You don’t need an ERP migration. You need a procurement layer that documents every purchase before it happens and matches invoices automatically after it does.

ProcureDesk integrates natively with QuickBooks (Online, Desktop, and Enterprise), NetSuite, Sage Intacct, Xero, Microsoft Business Central, and Bill.com. No middleware. No custom scripting. Setup takes 2-3 weeks with our team handling 100% of the configuration. Your finance team keeps working in the accounting system they already know, and ProcureDesk handles the procurement layer on top.

The math is simple. Ardent Partners pegs the average cost of processing an invoice at $9.40. If your company processes 200 invoices per month and half of them require manual intervention because of missing POs or wrong codes, that’s 100 invoices at $9.40 each, or $11,280 per year in avoidable processing costs alone. That doesn’t include the Controller’s time spent reviewing exceptions, correcting journal entries, and explaining budget variances that were really just coding errors.Want a head start before you put a full system in place?

Download the PO Tracking Spreadsheet to start logging POs, vendors, and approval status manually today.