ResMan AP workflow: what syncs, what does not, and where automation fits

ResMan holds your chart of accounts, your suppliers, your properties, and your GL. It is the system of record and it should stay that way.

What it was not built to do is receive a photographed handwritten invoice from a plumber, split a nine-invoice batch PDF across nine properties, and route the result through a PM, a regional, and a CapEx director who are all in the field.

That gap is the whole reason an AP layer exists.

Four things sync, and the interval is the part to ask about

Suppliers. The supplier master comes from ResMan, so an invoice validates against the vendor list your accounting team maintains rather than a copy.

Properties. Including the chart of accounts per property, which matters because not every account exists at every property, particularly across affordable and conventional assets.

Chart of accounts. The coding target.

Invoices and status, both directions. Coded invoices post in, and status comes back.

The question worth asking any vendor, ours included, is the interval in minutes. BillRoute syncs in real time. A batch sync on a several-hour cycle means an invoice can be coded and validated against a supplier record that has since changed, and you find that at close rather than at coding.

What does not sync, stated plainly

ResMan is our only PMS integration. No Yardi, no RealPage, no AppFolio, no Entrata.

That limits who we can serve. It is also the reason a deployment is measured in weeks rather than the six to twelve months a Yardi integration commonly runs. If you are on ResMan the trade is entirely in your favor. If you are not, this is a short evaluation and you should know that here rather than on a call.

Second limit: the integration is bounded by what the ResMan API exposes. Where the API does not reach, some flows use automation against the ResMan interface instead. That works, and it is a different reliability profile than an API call. Worth asking about for your specific workflow rather than taking a general assurance.

Why the PMS maintenance and AP modules get skipped

Not a criticism of ResMan specifically. It is true of every PMS.

These modules are built for the accounting function, which is the correct priority for a system of record. The consequence is that they assume data arrives structured. Somebody has already decided this is an invoice, from this vendor, for this property, at this amount.

Everything hard about AP in property management happens before that point. Deciding whether the PDF is an invoice at all, splitting the batch, reading the handwriting, filtering out the W-9 the vendor attached to be helpful.

A layer in front does the deciding and hands the PMS a clean coded transaction. The PMS stays the record.

Coupa sits in the middle for teams that already have it

Some portfolios run procurement through Coupa. Those teams do not need a second approval system and should not be sold one.

BillRoute routes invoices through existing Coupa workflows rather than replacing them, and standard ERP data formats are supported for teams whose stack is something else again.

Worth knowing: in our own operator, pulling purchase order creation off Coupa reduced the Coupa license count. That is a real outcome and also a reason to be skeptical of us on this specific point, since consolidating onto fewer tools happens to favor the vendor describing it.

Five questions for a ResMan AP evaluation

These work on us.

What is the sync interval, in minutes, and is it one-way or two-way?

Which ResMan objects sync, specifically, and which are read-only?

What happens to an invoice coded against a supplier record that changed mid-cycle?

Where does the integration use the API and where does it use interface automation?

What is the implementation timeline, and does it require anything from ResMan's side?

That last one matters more than it sounds. A PMS integration that requires a vendor-side project has a timeline you do not control.

Where the gains actually came from

On the reference portfolio, 24,000 units and 2,665 invoices in a representative month: a 98% automation rate, 197 invoices reaching a person, 40 hours a month returned, and more than $150,000 a year in cost, against a legacy per-page tool tracking toward nearly $10,000 a month.

None of that came from ResMan doing less. It came from ResMan receiving clean coded transactions instead of receiving whatever a vendor emailed.

What is your sync interval today?