# Who should approve IT and professional services invoices > IT and professional services invoices need a business reviewer and a contract reviewer, not just a cost center manager who signs on trust. Read the full guide. Source: https://valuexpa.com/insights/who-should-approve-it-and-professional-services-invoices Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-03 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. IT and professional services invoices are where that gap hides best, because the person approving the invoice rarely holds the statement of work in front of them while doing it. Most approval chains route these invoices to whoever owns the cost center: an IT director, a project sponsor, an operations manager. That person can confirm the work happened. They usually cannot confirm the rate, the hours, or the scope boundary the contract actually sets. Those are two different jobs, and one signature is being asked to cover both. ## Executive Summary The question "who should approve this invoice" is really two questions wearing one signature line. The first is whether the work described happened and was useful: a project sponsor or the manager who requested the engagement answers that from firsthand knowledge. The second is whether the invoice matches what the contract or SOW actually authorizes: the rate card, the not-to-exceed cap, the approved change order. That question needs someone reading the contract, not someone reading the invoice. Most approval failures on IT and professional services spend are not fraud. They are a single approver being asked to answer both questions at once, with only the invoice in front of them and no contract to check it against. A business approver signs off on value delivered. A contract or AP reviewer signs off on price and scope conformance. Splitting the two catches drift that a single busy approver, working from the invoice alone, has no way to see. The fix is not a longer approval chain. It is a shorter one with the right two people in it, and a rule that the contract terms travel with the invoice to whoever checks price. ## 1. Who confirms the work actually happened? **The business approver is the person who requested or sponsors the engagement: a project owner, an IT director, or a department manager. They confirm the deliverable exists, the hours claimed match effort they observed, and the invoice describes work they recognize. They are not the right person to check the rate against the master service agreement, because they typically do not hold the rate card.** This approver's authority comes from proximity to the work, not from the contract. They were in the meetings, reviewed the deliverable, or supervised the consultant day to day. That makes them the only credible source for one question: did this happen. Asking this same person to also validate the billed rate against the master service agreement stretches their role past what they can actually see. They were not given the contract at onboarding and are not expected to reread it every invoice cycle. Treating their sign-off as proof of contract conformance is where the gap opens. ## 2. Who checks the invoice against the contract? **A second reviewer, usually in AP or procurement, checks the invoice against the signed contract terms: the rate card, the not-to-exceed cap, and any approved change order. This reviewer needs the contract document itself, not a memory of what was negotiated, and needs it attached to the purchase order so it travels with every invoice against that engagement.** This role exists to catch what the business approver structurally cannot. A rate that crept up mid-engagement, a resource billed at a senior rate for work a junior consultant performed, or hours that pushed past an approved cap all show up in a side-by-side comparison against contract terms, not in a review of the deliverable. The reviewer does not need to understand the technical work. They need the contract on file and a habit of opening it every time. Where the contract lives in a shared drive nobody checks, this role collapses into a rubber stamp regardless of who holds the title. ## 3. What happens when one person does both jobs? **A single approver covering both roles tends to default to the question they can actually answer: did the work happen. Rate creep, scope creep, and off-contract resources pass through because nobody with the contract in hand was in the approval path. The invoice looks reasonable on its face, which is exactly the condition margin drift depends on.** This is not a story about a careless approver. It is what happens when a workflow assigns one person two jobs that require two different documents. A project sponsor with the SOW open still has no visibility into the rate card negotiated by procurement eighteen months earlier. The practical result is that [scope creep in professional services SOWs](/guides/scope-creep-in-professional-services-sows) and labor rate deviations against master service agreements both pass approval unchallenged, because the person checking is the person closest to the work, not the person closest to the contract. ## 4. How does approval differ for a fixed-fee SOW versus time and materials? **A fixed-fee SOW approval hinges on deliverable acceptance: did the milestone ship as defined. A time and materials engagement hinges on rate and hours: was each consultant billed at the agreed rate, and did total hours stay inside any cap. The two need different evidence attached to the invoice, and a single approval template built for one will miss what the other requires.** On a fixed-fee engagement, the business approver's sign-off carries most of the weight, because the contract question is largely settled at the milestone price. The contract reviewer's job narrows to confirming no change order was billed without a matching approved amendment. On time and materials, the contract reviewer's job grows. Every invoice line carries a rate and a role that has to match the rate card, and hours have to be checked against any not-to-exceed cap. A business approver alone, confirming only that the consultant showed up, has no way to catch a role billed at the wrong tier. ## 5. What documentation should travel with every invoice? **Every IT or professional services invoice needs three things attached or referenced at approval: the signed SOW or MSA rate card, any approved change order, and a record of hours or milestones the business approver can verify firsthand. Without the contract document itself present at approval, the contract reviewer's sign-off is a formality rather than a check.** The single most common reason a two-approver structure still fails is that the second approver never actually sees the contract. It sits in procurement's files, referenced by number, while the invoice sits in an AP queue with none of the underlying terms attached. Attaching the rate card and any change orders to the purchase order at intake, so they surface automatically at invoice approval, removes the excuse. It also creates the audit trail an approver needs to justify a rejection, rather than approving on trust because pulling the contract would take another day. ### A. What a change order approval should confirm A change order should be approved against the original SOW's boundaries before any invoice against it is paid, not discovered after the fact when the invoice arrives with an unfamiliar line item. The approver checking the change order needs the original contract in front of them, the same requirement as the rate card check. ## 6. Who should approve when the invoice includes off-contract resources? **An invoice line for a consultant or role not named in the SOW should route to whoever holds the contract, not to the business approver alone, because approving it requires a judgment about whether the engagement's scope actually covers that resource. Business approvers commonly accept the line because the person was useful, not because the contract permits billing for them.** Off-contract resources are one of the clearer signals that a two-approver structure is working as intended. The business approver has every incentive to say yes: the extra person helped. Whether the contract authorizes billing for that person is a separate question entirely, and it is the one a contract-side reviewer exists to ask. Where this check is absent, [off-contract resources](/guides/off-contract-resources-people-billed-outside-the-agreement) accumulate quietly across an engagement's life, each one individually small, each one invisible to an approver who is only checking whether work got done. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## 7. Frequently Asked Questions (People Also Ask) ### Should the same person approve every IT vendor invoice regardless of size? No. A dollar threshold should route larger or longer-running engagements through both a business approver and a contract reviewer, while small, one-time purchases may only need the business approver. The threshold should reflect the engagement's total contract value, not the size of any single invoice, since staged billing can otherwise stay under a per-invoice limit. ### Does procurement or AP own the contract-check role? Either can, as long as whichever team holds it also holds the actual contract documents at the time of approval. What matters is that the role exists and has the SOW or MSA in hand, not which department it sits in. ### What if the business approver and the contract holder are the same person? On small vendors or single-consultant engagements this can be unavoidable. In that case, build in a periodic second review, such as a quarterly reconciliation against the rate card, rather than relying on the same person catching their own contract-conformance gaps invoice by invoice. ### How does a not-to-exceed cap change the approval requirement? An NTE cap means every invoice approval needs a running total of hours or fees billed to date against that cap, not just a check of the current invoice. The contract reviewer needs that cumulative figure, which the business approver alone will not be tracking. ### Should legal be part of invoice approval? Not routinely. Legal's role is negotiating the contract terms up front. Invoice approval is an operational check against terms already agreed, and routing every invoice through legal would slow payment without adding a check legal is positioned to make. This is general information, not legal advice. ### What triggers escalation beyond the two standard approvers? A rate that does not match the rate card, hours that push past an approved cap, or a resource not named in the SOW should all escalate to whoever owns the vendor relationship, rather than being approved or rejected unilaterally by either the business or contract reviewer. ### Can approval responsibility be automated instead of assigned to two people? Automation can route the invoice and flag mismatches against stored contract terms, but a person still needs to confirm the work happened and a person still needs to decide what to do with a flagged mismatch. Automation supports the two-role structure; it does not replace either role. ### Why does this matter more for IT and professional services than for goods purchases? A goods purchase order specifies a fixed price and quantity that a three-way match can verify mechanically. IT and professional services contracts carry rate cards, tiered roles, and scope boundaries that live in prose, not in a PO line, which is why a contract-literate reviewer is needed in addition to a receiving check. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary The question "who should approve this invoice" is really two questions wearing one signature line. The first is whether the work described happened and was useful: a project sponsor or the manager who requested the engagement answers that from firsthand knowledge. The second is whether the invoice matches what the contract or SOW actually authorizes: the rate card, the not-to-exceed cap, the approved change order. That question needs someone reading the contract, not someone reading the invoice. Most approval failures on IT and professional services spend are not fraud. They are a single approver being asked to answer both questions at once, with only the invoice in front of them and no contract to check it against. A business approver signs off on value delivered. A contract or AP reviewer signs off on price and scope conformance. Splitting the two catches drift that a single busy approver, working from the invoice alone, has no way to see. The fix is not a longer approval chain. It is a shorter one with the right two people in it, and a rule that the contract terms travel with the invoice to whoever checks price. ## 1. Who confirms the work actually happened? The business approver is the person who requested or sponsors the engagement: a project owner, an IT director, or a department manager. They confirm the deliverable exists, the hours claimed match effort they observed, and the invoice describes work they recognize. They are not the right person to check the rate against the master service agreement, because they typically do not hold the rate card. This approver's authority comes from proximity to the work, not from the contract. They were in the meetings, reviewed the deliverable, or supervised the consultant day to day. That makes them the only credible source for one question: did this happen. Asking this same person to also validate the billed rate against the master service agreement stretches their role past what they can actually see. They were not given the contract at onboarding and are not expected to reread it every invoice cycle. Treating their sign-off as proof of contract conformance is where the gap opens. ## 2. Who checks the invoice against the contract? A second reviewer, usually in AP or procurement, checks the invoice against the signed contract terms: the rate card, the not-to-exceed cap, and any approved change order. This reviewer needs the contract document itself, not a memory of what was negotiated, and needs it attached to the purchase order so it travels with every invoice against that engagement. This role exists to catch what the business approver structurally cannot. A rate that crept up mid-engagement, a resource billed at a senior rate for work a junior consultant performed, or hours that pushed past an approved cap all show up in a side-by-side comparison against contract terms, not in a review of the deliverable. The reviewer does not need to understand the technical work. They need the contract on file and a habit of opening it every time. Where the contract lives in a shared drive nobody checks, this role collapses into a rubber stamp regardless of who holds the title. ## 3. What happens when one person does both jobs? A single approver covering both roles tends to default to the question they can actually answer: did the work happen. Rate creep, scope creep, and off-contract resources pass through because nobody with the contract in hand was in the approval path. The invoice looks reasonable on its face, which is exactly the condition margin drift depends on. This is not a story about a careless approver. It is what happens when a workflow assigns one person two jobs that require two different documents. A project sponsor with the SOW open still has no visibility into the rate card negotiated by procurement eighteen months earlier. The practical result is that [scope creep in professional services SOWs](/guides/scope-creep-in-professional-services-sows) and labor rate deviations against master service agreements both pass approval unchallenged, because the person checking is the person closest to the work, not the person closest to the contract. ## 4. How does approval differ for a fixed-fee SOW versus time and materials? A fixed-fee SOW approval hinges on deliverable acceptance: did the milestone ship as defined. A time and materials engagement hinges on rate and hours: was each consultant billed at the agreed rate, and did total hours stay inside any cap. The two need different evidence attached to the invoice, and a single approval template built for one will miss what the other requires. On a fixed-fee engagement, the business approver's sign-off carries most of the weight, because the contract question is largely settled at the milestone price. The contract reviewer's job narrows to confirming no change order was billed without a matching approved amendment. On time and materials, the contract reviewer's job grows. Every invoice line carries a rate and a role that has to match the rate card, and hours have to be checked against any not-to-exceed cap. A business approver alone, confirming only that the consultant showed up, has no way to catch a role billed at the wrong tier. ## 5. What documentation should travel with every invoice? Every IT or professional services invoice needs three things attached or referenced at approval: the signed SOW or MSA rate card, any approved change order, and a record of hours or milestones the business approver can verify firsthand. Without the contract document itself present at approval, the contract reviewer's sign-off is a formality rather than a check. The single most common reason a two-approver structure still fails is that the second approver never actually sees the contract. It sits in procurement's files, referenced by number, while the invoice sits in an AP queue with none of the underlying terms attached. Attaching the rate card and any change orders to the purchase order at intake, so they surface automatically at invoice approval, removes the excuse. It also creates the audit trail an approver needs to justify a rejection, rather than approving on trust because pulling the contract would take another day. ### A. What a change order approval should confirm A change order should be approved against the original SOW's boundaries before any invoice against it is paid, not discovered after the fact when the invoice arrives with an unfamiliar line item. The approver checking the change order needs the original contract in front of them, the same requirement as the rate card check. ## 6. Who should approve when the invoice includes off-contract resources? An invoice line for a consultant or role not named in the SOW should route to whoever holds the contract, not to the business approver alone, because approving it requires a judgment about whether the engagement's scope actually covers that resource. Business approvers commonly accept the line because the person was useful, not because the contract permits billing for them. Off-contract resources are one of the clearer signals that a two-approver structure is working as intended. The business approver has every incentive to say yes: the extra person helped. Whether the contract authorizes billing for that person is a separate question entirely, and it is the one a contract-side reviewer exists to ask. Where this check is absent, [off-contract resources](/guides/off-contract-resources-people-billed-outside-the-agreement) accumulate quietly across an engagement's life, each one individually small, each one invisible to an approver who is only checking whether work got done. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## Common questions ### Should the same person approve every IT vendor invoice regardless of size? No. A dollar threshold should route larger or longer-running engagements through both a business approver and a contract reviewer, while small, one-time purchases may only need the business approver. The threshold should reflect the engagement's total contract value, not the size of any single invoice, since staged billing can otherwise stay under a per-invoice limit. ### Does procurement or AP own the contract-check role? Either can, as long as whichever team holds it also holds the actual contract documents at the time of approval. What matters is that the role exists and has the SOW or MSA in hand, not which department it sits in. ### What if the business approver and the contract holder are the same person? On small vendors or single-consultant engagements this can be unavoidable. In that case, build in a periodic second review, such as a quarterly reconciliation against the rate card, rather than relying on the same person catching their own contract-conformance gaps invoice by invoice. ### How does a not-to-exceed cap change the approval requirement? An NTE cap means every invoice approval needs a running total of hours or fees billed to date against that cap, not just a check of the current invoice. The contract reviewer needs that cumulative figure, which the business approver alone will not be tracking. ### Should legal be part of invoice approval? Not routinely. Legal's role is negotiating the contract terms up front. Invoice approval is an operational check against terms already agreed, and routing every invoice through legal would slow payment without adding a check legal is positioned to make. This is general information, not legal advice. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us