Hi, I’m Rediza Gerez.

The AP SOP was revised as the handoff with Purchasing changed. It covers three-way matching, bill review, supporting records, and documented exceptions in ServiceTitan.

Illustrative example. A PO is marked received, but the invoice quantity is higher than the receipt. Compare the three records and send the mismatch to the person who can confirm what arrived before recording the bill.

The agreement sets out who owns the next action, when Purchasing needs to respond, and when a COD discrepancy goes to a supervisor.

The guidance explains what evidence AP needs for a COD purchase, with emphasis on pairing the vendor invoice with proof of delivery.

The policy guidance describes which items belong in monthly reconciliation and how exceptions to that scope are handled.

The draft maps the purchase order, receipt, official invoice, bill, and payment statement for permit-related services. It also covers vendor-specific payment paths and invoice variances.

This proposal ties a city permit PO to an installation milestone and separates payment approval from the later steps of invoice follow-up, billing and PO closure.

The guidance explains what AP needs to confirm when a job-related service is complete or canceled before moving the PO and bill forward.

The workbook brings invoice and PO status together, with separate views for bills ready for payment and bills already paid.

The dashboard shows receipts that still need bills so AP can prioritize follow-up and identify what is blocking each item.

The workbook helps AP compare vendor statements with its records and log each discrepancy, next action, owner, and status.

Illustrative example. A supplier statement lists an invoice that AP cannot find. Log it as missing, assign a follow-up owner and keep it open until AP has the invoice or has confirmed why it is absent.

The aging report aligns with vendor portal balances and shows outstanding obligations alongside items needing action.

The reconciliation update gives Finance a view that distinguishes resolved items from exceptions still being followed up.

The workbook groups completion and pending counts across vendor reconciliation, open receipts and statement review. Its reporting unit is the control item. A single purchase can appear in multiple source reports.

The daily routine covers work assignments, progress reporting, and handoffs for items still waiting on another team.

The workshop covers which issues AP can resolve and which go back to Purchasing, with examples involving receipts, charges and order corrections.

The working-session deck maps ownership from purchase order to bill and gives both teams prompts for discussing returns, corrections and escalation.

AP and Purchasing use a recurring review of unresolved items to agree on owners, follow-up, and status updates.

The guide turns the SOP into a walkthrough with practice scenarios, an exception checklist, a knowledge check, and sign-off.

Illustrative example. A vendor emails a document labeled order confirmation. What should the processor verify before using it as support, and where should they document the decision?

The scorecard gives interviewers common questions, criteria for evaluating answers, and space to record evidence and scores.

The framework records the issue, expected improvement, support provided and next review, with a place for the team member’s response.

The three-month review workbook groups contributions by controls, process, team development, and reporting, with supporting examples for discussion.

The project connects the Permits and AP handoffs for intake, purchase order follow-up, invoice attachment, and billing status. The walkthrough above uses a sample request.

The training shows how to submit and track a request, attach the official invoice to the existing record, and hand it back to AP for review.

The team documentation covers how to log Teams follow-ups in a tracker and who handles each responsibility, control, and maintenance task.

The design outlines an exception queue with an owner, status, next action and aging, with reminders and escalation as possible automation steps.

The proposed checker would flag missing information or dates that need review before the processor moves the invoice forward.

Warehouse posts delivery photos in Teams, and the workflow files them by vendor in OneDrive and logs them in a tracker shared with Purchasing and AP. Read the case study.