GFOA Best Practices for Vendor Payment: A Practical Implementation Guide

GFOA best practices are a collection of advisory guidelines published by the Government Finance Officers Association that establish standards for public-sector financial management, including procurement, accounts payable, vendor relations, and cash management. These best practices are not laws, but they represent the professional consensus on how cities and counties should operate — and they are the yardstick auditors, council members, and peer agencies use to evaluate your finance department's performance.

This guide maps the GFOA documents most relevant to vendor payment operations, identifies where most municipal finance offices fall short, and outlines concrete steps to close those gaps. For AP managers and finance directors looking to move from "we know what the standards say" to "here's what we changed on Monday morning," this is your starting point.

Key Takeaways

• GFOA guidance on vendor payment spans at least five published best practice documents covering procurement, AP internal controls, cash management, and vendor relations. Most cities only reference one or two.
• The most common compliance gaps are AP cycle time and vendor communication, not fraud prevention or policy documentation — the areas that get the most attention.
• Paying vendors within 30 days is an implicit GFOA standard, but the average municipal AP cycle runs 45–60 days (GFOA survey data, 2022). Some cities exceed 90.
• You don't need a full AP overhaul to meet GFOA vendor-treatment standards. Targeted fixes — status portals, approval-workflow changes, and early payment programs — can close the biggest gaps within a single budget cycle.
• Early payment programs are one of the lowest-friction tools available for improving vendor experience without adding headcount or changing your ERP.

The GFOA Documents That Apply to Vendor Payment

GFOA publishes best practices as standalone advisories, each approved by the Executive Board. Several directly address how cities should treat vendors in the payment process. Here are the most relevant:

Procurement Procedures (GFOA Best Practice, 2015/Updated)

This document recommends that governments establish procurement policies that are "fair, open, and transparent." It emphasizes vendor access — making sure suppliers can find, understand, and participate in the procurement process without unnecessary barriers. The practical implication for AP: once a vendor wins a contract and delivers, the payment process should reflect the same fairness and clarity that procurement promised.

Internal Controls in Accounts Payable (GFOA Best Practice)

GFOA's AP internal controls guidance covers segregation of duties, three-way matching, and approval hierarchies. Most cities implement these controls well. The gap is rarely in controls themselves — it's in how those controls affect cycle time. When a three-way match fails and no one notifies the vendor for two weeks, the control is working but the vendor relationship is not.

Cash Management and Investment Policies

GFOA recommends that governments maintain cash management policies that "optimize the use of public funds." This includes timing disbursements effectively. In practice, some cities interpret this as a reason to hold payables as long as possible — paying on day 59 of a Net 60 term to maximize float. GFOA does not recommend this. The guidance calls for balancing investment returns with "the government's responsibility to pay obligations in a timely manner."

Vendor Relations and Communication

While GFOA does not have a single standalone document titled "vendor relations," references to vendor communication appear across multiple advisories. The consistent message: governments should provide clear payment terms, accessible status information, and responsive communication when issues arise. A 2019 GFOA research report found that vendor complaints about payment are among the top sources of constituent-service calls to finance departments.

Prompt Payment Policies

GFOA encourages governments to adopt formal prompt payment policies that specify payment timelines, late-payment procedures, and dispute resolution. Approximately 40 states have some form of prompt payment statute for public agencies, but statutory compliance is the floor, not the ceiling. GFOA best practices push cities beyond minimum legal requirements toward a standard that treats timely payment as a policy priority.

Where Most Cities Fall Short

Most municipal finance departments meet GFOA standards in areas like fraud prevention, bid documentation, and contract execution. The gaps tend to cluster in two operational areas that receive less audit attention but have outsized impact on vendor experience.

Gap 1: AP Cycle Time Exceeds 30 Days

According to GFOA's own survey data, the median accounts payable cycle for local governments is approximately 45 days from invoice receipt to payment. For smaller cities with limited AP staff, 60–90 days is common. A 2023 study by the Institute of Finance and Management found that 37% of government invoices are paid late relative to stated contract terms.

GFOA guidance does not mandate a specific number of days, but the repeated emphasis on "timely payment" and "prompt payment policies" establishes 30 days as the implicit benchmark. When your actual cycle is double that, you are outside the spirit of the guidance — even if no auditor flags it.

The root causes are usually mundane: paper-based approval routing, department heads who sit on approvals, three-way matches that stall without a clear exception-handling workflow, or simply not enough AP staff to process the volume. None of these are hard problems. They are priority problems.

Gap 2: Vendors Cannot See Their Payment Status

GFOA's transparency principles extend to vendor communication, but most cities still handle vendor payment inquiries by phone or email. The vendor calls AP, AP checks the ERP, AP calls back (or doesn't). According to a National Institute of Governmental Purchasing (NIGP) survey, fewer than 30% of local governments offer vendors a self-service portal to check invoice or payment status.

This gap creates two problems. First, it generates a high volume of inbound calls that consume AP staff time — the same staff who are already behind on processing. Second, it signals to vendors that the city does not prioritize the relationship, which over time reduces the pool of businesses willing to bid on government work.

Concrete Fixes Mapped to GFOA Guidance

Below is a table mapping each common gap to the relevant GFOA principle and a specific operational fix. These are not multi-year projects. Each can be started within a quarter.

Fix 1: Set and Publish a Payment Target

Choose a number — 30 days is the GFOA-aligned standard — and make it visible. Report AP aging by department in your monthly finance packet. When the parks department is averaging 52 days because their project manager doesn't approve invoices promptly, that visibility creates accountability without AP being the enforcer.

Fix 2: Turn On the Portal You Already Own

If your city runs Tyler Munis or OpenGov, you likely already have a vendor self-service module included in your license. Many cities simply never activate it. Enabling it reduces inbound calls to AP and gives vendors what GFOA guidance says they should have: accessible, timely information about the status of their payment.

Fix 3: Auto-Escalation for Stalled Approvals

Most AP bottlenecks sit not in the AP department but in the operating departments that must approve invoices before AP can release payment. A simple workflow rule — if the approver has not acted in five business days, the invoice escalates to their supervisor or a designated backup — can cut average cycle time by 10–15 days without changing your control environment.

Fix 4: Adopt a Formal Prompt Payment Resolution

GFOA explicitly recommends that governments adopt written prompt payment policies. A council resolution costs nothing and creates institutional commitment. Include: the target payment timeline (e.g., 30 days from receipt of a proper invoice), the procedure when a dispute delays payment, and reporting requirements for AP performance against the target.

Early Payment Programs as a GFOA-Aligned Tool

Even with all of the fixes above, some cities will not reach a consistent 30-day cycle in the near term. Staff turnover, budget constraints, legacy systems, and seasonal volume spikes all create realistic barriers. This is not failure — it's reality.

This is where early payment programs fit. A municipal early payment program allows the city's vendors to receive payment within a few business days of invoice approval, without the city changing its own payment timeline or spending any public funds. The financing provider purchases the approved invoice from the vendor and collects from the city on the normal schedule.

The key features that align with GFOA principles:

• No cost to the government. The vendor pays a flat fee if they choose to accelerate; the city pays nothing. This is consistent with GFOA's cash management guidance — public funds are not used to finance vendor payments.
• Voluntary for vendors. Vendors choose per-invoice whether to accelerate. This respects vendor autonomy and avoids any appearance of mandated programs.
• No process changes for AP. The city continues to approve and pay on its normal schedule. The early payment sits on top of existing workflow, not inside it.
• Improved vendor experience. Vendors get paid in 1–3 days instead of 30–90. This directly supports GFOA's vendor-treatment standards.
• Potential revenue for the city. Some programs, through dynamic discounting structures, return approximately 1% of financed invoice value to the city as cashback.

Lunch, for example, operates this model for cities and school districts — advancing payment to vendors at a flat fee with no cost to the agency. Vendors are not taking on debt; the transaction is a purchase of the approved receivable. If the city pays late, the vendor does not pay more. Every city-approved vendor qualifies automatically with no credit check or application.

This type of program does not replace the operational fixes described above. It complements them. A city that has a 30-day payment target, a vendor portal, and an early payment option is offering vendors a meaningfully better experience than one that has none of those things — and it is much closer to the full intent of GFOA guidance.

Measuring Progress Against GFOA Standards

GFOA's Distinguished Budget Presentation Award and Certificate of Achievement for Excellence in Financial Reporting both evaluate whether a government is following best practices. While vendor payment speed is not a standalone scoring criterion, the underlying principles — transparency, timeliness, accountability — run through every element of both programs.

Track these metrics monthly:

• Average days from invoice receipt to payment, by department
• Percentage of invoices paid within 30 days (target: 90%+)
• Number of vendor payment inquiries received by AP (should decline as portal adoption rises)
• Vendor participation in early payment programs, if offered (indicates vendor satisfaction and need)
• AP cost per invoice (GFOA research suggests a public-sector average of $8–$12 per invoice; automation and process improvement should move you toward the lower end)

Frequently Asked Questions

Does GFOA require cities to pay vendors within 30 days?

No. GFOA best practices are advisory, not mandatory. There is no single document that specifies "30 days." However, the cumulative guidance on prompt payment, cash management, and vendor relations establishes timely payment — generally interpreted as 30 days for a proper invoice — as a clear professional standard. Falling consistently outside that range puts your department out of step with peer norms.

What is the biggest barrier to meeting GFOA AP standards?

For most cities, the answer is approval bottleneck in operating departments, not staffing in the AP office itself. Invoices sit waiting for a project manager or department head to confirm receipt and authorize payment. Auto-escalation workflows and visible reporting on departmental approval times are the most effective fixes.

Are early payment programs consistent with GFOA guidance?

Yes. GFOA guidance prioritizes timely vendor payment, transparency, and responsible cash management. An early payment program that costs the city nothing, requires no process changes, and improves vendor experience is consistent with all three principles. It does not replace internal AP improvements, but it addresses the vendor's experience while those improvements are underway.

How do I start implementing GFOA best practices in my AP department?

Start with measurement. Pull your current average cycle time, break it out by department, and present it to leadership. Then implement the lowest-effort fixes first: activate your ERP's vendor portal, set an approval escalation rule, and draft a prompt payment resolution. For cities looking to add an early payment option for vendors, that process typically takes days to set up, not months.

Where can I find the full text of GFOA best practices?

GFOA publishes all best practices on its website at gfoa.org. They are organized by topic (accounting, budgeting, treasury management, etc.) and are free to access. The documents most relevant to vendor payment are found under "Accounting, Auditing, and Financial Reporting" and "Treasury and Investment Management." GFOA members also have access to additional research reports and implementation guides through the member portal.