NR Building Solutions

For clients

Our process — bid to invoice

What happens between a bid request and a closed invoice at NR Building Solutions, including purchase order handling, change orders raised on the day, punch close-out and vendor-portal invoicing.

The short version

Bid request → walk or scope review → bid → purchase order → schedule → mobilize → daily photo reporting → punch → invoice.

The full sequence, with the detail that actually matters at each step, is on how we work. This page covers the three parts of it that a client-side process person cares about: purchase orders, change orders and close-out.

Purchase orders

You issue a PO against the accepted bid. Our invoice matches it line for line.

That sounds unremarkable and it is the single most common source of friction between an operator and a contractor. An invoice that does not reconcile to a purchase order is somebody's afternoon in your office, every month, and it usually happens because work was done that was never separately approved.

Which is what the change-order rule below is for.

Change orders happen on the day

A home opened up reveals conditions nobody could price from a walk. A supply line weeping behind a wall. Framing damage under a window. A roof leak that tracked somewhere unexpected. Rot in a section of deck that sounded solid.

These are normal. What is not normal — and what we do not do — is absorb them silently and hand you a number at the end.

  1. Found

    The crew stops and photographs the condition before doing anything else with it.

  2. Priced

    Itemized line items for the additional scope, against the same rate structure as the original bid.

  3. Decided

    You approve it, defer it, or decline it. Declining is a legitimate answer and we will close up around it and note it.

The point of raising it on the day is that you keep the decision. A change order presented at invoicing is not a decision, it is a bill — and the work has already been done.

Close-out

A written punch list, walked with you or your community manager, closed out with photographs, and only then an invoice.

A job we consider finished and you consider unfinished is a failure of the close-out process rather than of the work. The punch list exists to make that disagreement happen while a crew is still on site, which is the only point at which it is cheap to resolve.

Invoicing

Against the purchase order, broken out the way you account — by community, by property code, by cost center — and submitted through your vendor portal where you run one.

For portfolio operators, consolidated invoicing broken out by community, region and cost center is set up at onboarding against your chart of accounts. See national accounts.

Common questions

Yes. Through this site, by phone, or through whichever work-order platform your portfolio runs — all three land in the same place. A request that arrives in somebody's inbox depends on that person being available; a request that arrives in the system does not.

They are raised on the day the condition is found, with a photograph, and priced then. Not absorbed silently and not saved for the invoice. That way you can decide whether to do the work at all, which is a decision you lose if you are told about it afterwards.

A written list, walked with you or your community manager, closed out with photographs. It exists so that a disagreement about whether a job is finished happens before invoicing rather than after.

Where you run one, yes — Yardi, RentManager, ServiceChannel, Corrigo and the others our clients use. The invoice arrives in your workflow rather than as an email somebody has to key in.