Accounts payable for Maplewood vendors who must match a corporate portal

What does a controlled AP process include?

PO creation through approval, invoice match, budget check, duplicate detection, and a pay run someone owns. Quality checks before disbursement are cheaper than clawing back a duplicate from a corporate AP shared-service center that already closed the period. That is AP as a control, not bill-pay folklore.

That workflow is the accounts payable and receivable service—not a vague “we pay the bills” retainer. Bookkeeping still has to rec the bank or you will pay the same invoice twice and never see it on the P&L.

Maplewood campus suppliers live this when the customer’s portal is the real AP system. St. Paul and Roseville operators feel it when volume jumps without a three-way match. Same standard on the Ramsey County hub; different portals.

The SBA cash-and-books guidance will not operate Coupa or SAP for you. We work your side of the portal when you grant access—not as their shared-services team.

A controlled AP process also names who can add a vendor, who can change a bank account, and who can release a pay file. East-metro suppliers get burned when that is “whoever has the password.” Write it down. Then the pay run is a control, not a hope.

If the campus calendar already closed the period, a duplicate will not wait for your next “catch-up Friday.” We will put PO-to-pay on a weekly list the week of the consult. Maplewood operators who wait for a quiet month stay in exception hell until cash is already gone.

Why do east-metro vendors feel the pain first?

Maplewood sits next to campus and retail volume in Ramsey County. Your customer’s portal is not optional. Your QuickBooks file still has to match it. We operate your side of that workflow so cash is not trapped in process errors.

Wrong PO, duplicate invoice, missing receipt—those are not a “slow pay” personality. They are exceptions nobody owns. A QuickBooks cleanup is in scope when vendor masters and undeposited funds are already fiction. AP cadence will not fix a lying subledger.

Receivable follow-up is the other half of cash. If you are also waiting on capital-city customers, see St. Paul accounts receivable. Paying vendors late while you ignore AR is how east-metro operators feel broke with a full pipeline.

Kim’s practice has run purchase-order through pay since 2013. Duplicate detection needs invoice numbers, vendor masters, and receiving. Nothing is magic if receiving never happens on the dock.

Campus calendars also reject invoices for missing packing slips or the wrong ship-to. That is still your AP problem even when operations “already sent it.” We will sit between the dock and the portal until the exception list is owned weekly, not when someone is short cash.

Treat the portal aging as a second subledger, not as a rumor. If Maplewood books say paid and Coupa says open, that is an exception with a date. Hoping the shared-service team notices is how east-metro suppliers finance someone else’s close.

Should AP and AR be the same person in Maplewood?

In a small Maplewood operator, often yes, with a written checklist. In a busier file, split the cadence but keep one reconciling general ledger. Either way, bookkeeping has to be current or both ledgers drift until nobody trusts cash. Name the owner on day one.

One person can own the weekly pay run and the collections list if volume is honest. The failure is when “AP/AR” means nobody. Name the owner. Put exceptions on a date. That is AP/AR operations, not a title on a door.

Corporate calendars on the east metro do not wait. If the parent or the customer closes on the 5th, your packet has to exist. That is close discipline sitting next to payables—not a reason to skip the rec.

Payroll is not a product we sell. Vendor labor still has to code. Tax returns stay with your CPA. We keep the trail those people need.

Segregation still matters at small scale: the person who sets up the vendor should not be the only person who can release payment. Even a two-person Maplewood shop can split “enter” and “approve” on a checklist. That is cheaper than a duplicate that left the bank.

How do portal mismatches actually get resolved?

Export what the portal says is open. Match it to your aging and to receiving. Flag wrong PO, quantity, price, and duplicates. Then work exceptions on a weekly list instead of hoping the customer’s AP team notices the problem for you.

We will log into SAP, Coupa, or similar when you grant access as your function. We will not pretend we work for the campus shared-service center. Your Maplewood entity still needs a GL that ties after the portal says “paid.”

If the portal and QuickBooks never agreed, start with the file. Cleanup, then cadence. Calling AP about invoices they already paid burns the relationship the same way ugly AR does in St. Paul.

Document the match rules so the next owner can run them. A heroic weekend in the portal is not a process. Kim will leave a checklist, not folklore.

If the customer uses three portals, we still run one GL. Map each portal to vendors and POs so Roseville and Maplewood entities do not invent a fourth set of books. The exception list is by customer, the rec is by bank.

What does a healthy east-metro pay run look like?

A dated pay run, exceptions listed, duplicates blocked, and a rec that ties after disbursement. If leadership cannot see what is due this week in Roseville or Maplewood, cash is a story about the checking account, not about vendors. Cash is not the screenshot.

Budget checks before pay are cheaper than clawbacks. Three-way match where you have receiving. Vendor masters that are not a pile of misspelled duplicates. That is controlled AP, not “we clicked pay in the bank app.”

IRS recordkeeping still wants substantiation. Portal PDFs are not a substitute for a vendor bill in the books. Code it, match it, pay it, rec it.

If the customer is in Ramsey County and you are the supplier, this page owns your payables. Their AR is their problem unless you also invoice—then pair it with the St. Paul cash-flow article.

Early-pay discounts and holdbacks belong on the same aging as everything else. If you take a discount the portal never offered, you have created a dispute. If you miss one you earned, you financed the campus. The pay run should show both.

How do we start Maplewood accounts payable support?

Book a 30-minute consultation on the contact page or call 763-242-3743. Bring a sample aging, a portal screenshot, and accountant-user access. Confirmation goes to you and to kim@klueckcontractingllc.com so we can scope PO-to-pay before the next campus due date. We will not start AP without that access.

We map PO through pay, name exceptions, and set a weekly run. AP/AR and bookkeeping are scoped as a pair when both ledgers are drifting.

Name Maplewood, St. Paul, and Roseville entities if they share vendors. Same AP standard; different portals and charts. We will not copy one campus supplier file onto another and call it localization.

You keep admin. We work as an invited accountant in America/Chicago. Legal collections and tax filing stay out of scope. The finish line is a pay run someone else can run.

Bring operations if receiving is the real bottleneck. AP cannot three-way match air. One consult that includes the dock, the portal, and the GL is how Maplewood suppliers stop financing someone else’s process errors.

Questions owners ask next