From service request to paid invoice: the last unmapped workflow in commercial buildings

Connecting service requests, vendor work, lease responsibility, and invoices in commercial buildings

Water is coming through the ceiling near the conference room. The facilities coordinator opens the work order system, creates a ticket, manually assigns it to the plumbing service type, and sends a separate email because the portal notification may not reach the right service provider.

The service provider's dispatcher checks availability and calls back at 11 a.m. to confirm a visit the next morning. The technician arrives, seals the leaky pipe, and marks the job complete in the service provider's field service app. The repair itself goes smoothly.

Then the invoice arrives as a PDF in the building's AP inbox 2-3 weeks later. It references a work order number that does not match the accounting system's format. The AP clerk searches for a purchase order, but the building's policy did not require one for this general repair under $2,500.

The AP clerk emails the facilities coordinator to confirm completion. The facilities coordinator confirms the work a few days later, but the invoice exceeds the verbal not-to-exceed (NTE) amount by $300. The facilities coordinator escalates the overage to the property manager, who approves it by email sometime the following week. The AP clerk enters the invoice, codes it to building maintenance, and flags the tenant-responsibility question. Another three days later, a lease administrator reviews the lease, determines that the tenant bears 60% of the cost, and completes the allocation. In this illustration, AP pays the invoice 60-90 days after the facilities coordinator’s first email.

The repair crosses four internal functions and involves six staff members, excluding the person reporting the request.

The coordination gap

In JLL's 2025 Occupancy Planning Benchmark, 73% of respondents named portfolio optimization as their top objective.[1] That goal depends, in part, on data that owners can track across work orders, service providers, leases, invoices, and payments.

Existing platforms already cover many parts of this process, and several cover most of it inside their own environments. Prism supports work orders, provider management, certificates of insurance, purchase orders, invoice collection, and payments.[2] ServiceChannel supports request intake, provider work orders, proposals, completion records, and invoice approval.[3] Yardi offers an end-to-end procure-to-pay suite across provider management, purchasing, invoice processing, and payments.[4] PredictAP focuses on invoice capture and coding for real estate AP, then sends coded invoices into existing approval systems.[5]

The remaining opportunity is narrower and more specific: coordinate records and rules across the systems a portfolio already uses, especially when the building team, service provider, lease administrator, and AP team work in different applications. The value comes from maintaining a single traceable record, applying controls at the right stage, and routing each exception to an authorized person in a timely manner.

The repair loop: intake through close

General maintenance starts with awareness of a needed repair. A tenant may contact the building team by email, phone, building app, or work order system. The intake is routed to the facilities coordinator, who assesses urgency, selects a service provider, defines the initial scope, sets an approval limit, and assigns the work. The service provider dispatches a technician, completes the repair, and records the result.

When the service provider and building team use separate systems, each status change can create a manual handoff. The provider may close the job in its field service system while the building's work order remains open. The facilities coordinator then relies on calls, texts, or emails to reconstruct what happened and update the record.

A connected repair loop can synchronize agreed-upon status events without forcing every participant to use the same application. The provider can keep using its field system while the building's work order receives intake, dispatch, arrival, completion, photo, and scope-change data. The system can send an estimate or NTE for approval before the technician leaves, rather than waiting for AP to discover the difference when the invoice arrives.

Accounting: collect, code, pay

An invoice may arrive via physical mail, email,  through a provider's billing system, or AP’s billing system rather than as part of the work order record. When that happens, whoever receives it, the facilities coordinator or AP, must identify the correct property, service provider, work order, approval, and evidence of completion before AP can process the charge. The team may also need to determine the correct GL code and tenant-recovery treatment.

Three-way matching commonly compares a purchase order, a receipt or completion record, and the invoice. For service work, the completed work order can act as the service receipt. When a portfolio permits general repairs without a formal purchase order, the process needs another approved control, such as an estimate or NTE amount linked to the work order.

A connected accounting process can present the invoice with the matched work order, evidence of completion, approved amount, suggested GL coding, and any NTEor duplicate flags. AP still reviews the record and approves payment with blessing from the building team. The system assembles the evidence; the AP team retains payment authority.

The owner does not need to settle all tenant allocations before paying all service providers. The correct sequence depends on the lease, the owner's accounting policy, and the recovery process. Some teams may classify responsibility before coding the invoice. Others may pay the provider and reconcile estimated recoveries later. In either case, the work order, invoice, lease decision, and recovery record should remain linked.

The gates: compliance and lease

Two controls can prevent rework when teams apply them early.

1. The building team should confirm that the service provider is approved for the property and carries the required insurance before dispatch, unless an emergency protocol permits a conditional response. A connected system can surface an expired certificate, missing credential, or property-specific restriction when the facilities coordinator selects the provider.
2. The team should also classify the likely lease responsibility before finalizing coding or tenant billing. Recovery provisions vary by tenant, lease, and work category. A base-building HVAC repair may receive different treatment from work resulting from a tenant's custom installation, but the lease and the owner's policy determine the outcome in each case.

Software can retrieve relevant lease provisions, apply configured rules, and present a recommended classification with an audit trail. A lease administrator or other authorized person should decide genuinely ambiguous cases. The system should bring the evidence to that person rather than make them search across the work order platform, lease files, email, and accounting records.

The record: reporting and insight

When work-order and accounting data sit in separate systems, teams must reconcile records before they can analyze repair costs, provider performance, asset history, or tenant recoveries. Some platforms already provide connected reporting inside their own environments. The harder case appears when a portfolio spreads the relevant data across several products.

A shared identifier should connect the original request, property, asset, provider, scope, estimate, approval, completion evidence, invoice, payment, and recovery decision. With that record, teams can compare repair costs by asset, review response and completion times by provider, identify repeat failures, and decide when replacement may cost less than another repair.

A useful record stays up to date as each participant completes their part of the job, so teams do not have to rebuild the same report each month.

Where people retain authority

A connected process should define where a person must approve, interpret, or inspect.

The property manager or authorized client representative approves the spend when the estimate exceeds a configured threshold or when approval is required by policy. AP reviews and approves payment. A lease administrator decides allocations when the lease language or facts leave room for interpretation. A compliance officer or property manager decides whether an emergency justifies an exception to normal service providers requirements.

Quality control also depends on risk. Photo and checklist evidence may be sufficient for a low-risk routine repair under an approved quality policy. Safety-critical, high-value, warranty-related, disputed, or incomplete work may still require a site inspection.

Automation can handle status checks, reminders, data transfer, document matching, and exception routing. Facilities coordinators can then spend more time on judgment, tenant communication, service provider relationships, and unusual repairs that do not follow the standard path.

The Sentinel Difference

The tenant reports the leak at 8:47 a.m. The system opens the service request and sends the service provider a structured request through the connected process. The provider accepts the work for the NTE provided or returns a scope and estimate by 10:30 a.m., and the property manager approves and coordinates schedules before noon. The technician arrives the next morning, completes the repair, attaches photos, and submits final cost evidence still from the field. Both the service provider's record and the building's system receive the completion update and see the generated invoice.

The service request completion with invoice is sent to the property manager for final approval. A credit card on file is charged the invoiced amount and the payment is processed to the service provider’s ACH on file within 48 hours. AP’s system is updated to reflect full details of the transaction with all the lease, GL code, and approval details in the right places. Under the assumptions in this illustration, the payment clears within four days, and only one staff member, the property manager, intervenes twice.

Sentinel is designed to sit atop an existing technology stack rather than require an owner to replace it.[6] In this operating model, Sentinel coordinates the routine steps, keeps the records aligned, and sends exceptions to authorized people. The property manager retains spending authority, AP retains payment audit and retention accountability , lease administrators decide on ambiguous allocations, and the building team decides the priority of the repair.

Sentinel can eliminate repeated searching, bid tracking, status chasing, and re-entry while people retain authority over decisions with financial, contractual, safety, or relationship consequences.

Sources

Product capability references below come from service provider-published materials. They show what each vendor says its product supports, not independent evidence of adoption or performance.

1. JLL, "The evolving workplace prioritizes experience while optimizing space," 24 June 2025
2. Building Engines, "Vendor Management Software for CRE" and "Work Order Management Software for CRE"
3. ServiceChannel, "Work Order Software" and "Invoice promptly to get paid fast"
4. Yardi, "Procure to Pay Suite"
5. PredictAP, "Invoice capture and coding without manual data entry"
6. Sentinel, "AI Voice for building ops"