Auditing IT and professional services spend in Sage Intacct

Executive Summary

Sage Intacct approves an IT or professional services invoice by matching it to a purchase order or a budget line, not to the underlying statement of work. That gap is structural: the platform has no field for a blended rate ceiling, a not-to-exceed cap, or a milestone deliverable, so nothing in the approval workflow can catch an invoice that quietly drifts off contract terms.

The fix is a standing reference table built from the actual contract documents: approved roles and rates, NTE caps, milestone schedules, and renewal terms, checked against each invoice line before or after payment. Sage Intacct's dimension structure of department, project, and vendor can carry that reference once it exists, but the platform does not generate it on its own.

For a company above $100M in revenue, the exposure compounds across multiple concurrent vendors, contract renewals, and rate escalations that nobody tracks centrally. The rest of this page walks through where the gap shows up and how to close it without adding headcount to AP.

1. Why doesn't Sage Intacct catch IT and professional services overbilling?

Sage Intacct's invoice approval workflow checks an invoice against a purchase order or a project budget, both of which are dollar totals. It has no native field for a contracted hourly rate by role, a not-to-exceed cap, or a milestone deliverable schedule, so an invoice that is internally consistent with the PO can still be inconsistent with the statement of work. The system approves what fits the budget line, not what the contract actually authorized, and those two things diverge.

A purchase order in Sage Intacct is usually raised as an estimated total or a not-to-exceed dollar amount tied to a project. Once that number is set, the platform's own controls stop there. It confirms the invoice does not exceed the PO ceiling and that the project or department code matches.

What it cannot confirm is whether the hours billed match the roles authorized in the statement of work, whether a rate escalation clause applied correctly, or whether a fixed-fee milestone was billed as fixed fee or slipped into time and materials. Those terms exist only in the contract document, filed separately from the transaction.

This is a mechanism gap, not a configuration problem. Turning on more approval rules inside Sage Intacct tightens the PO match. It does not create the missing comparison against the statement of work, because the platform was never given that data to check against.

2. Where do rate card violations show up in a professional services invoice?

A rate card violation appears when an invoice bills a role at a rate the statement of work never approved, or applies a rate increase before the contract's escalation clause permits it. It also appears when a vendor bills a senior title for work performed at a junior level, a substitution the contract usually restricts. None of these show as errors in Sage Intacct because the invoice total can still land within the PO ceiling while individual line rates drift.

Professional services contracts define a rate table by role: project manager, senior consultant, analyst, and so on, each with a ceiling rate and sometimes a blended average across the engagement. The statement of work then names which roles are authorized for which phase of work.

Drift happens two ways. First, the vendor bills a role at a rate above the card, often because the invoice was generated from an internal billing system that was never updated to match the signed contract. Second, the vendor substitutes a more senior, more expensive resource for one the contract scoped at a lower level, without a change order.

Both are line-level problems. A PO-level check in Sage Intacct averages across all lines and can miss a rate violation entirely if the invoice total still fits the ceiling.

3. How do not-to-exceed caps get missed on IT services invoices?

An NTE cap gets missed when the cap applies to a specific phase or deliverable inside a larger engagement, but the purchase order in Sage Intacct was set at the total contract value. The invoice can be well under the overall PO ceiling while blowing through the cap on the specific phase it belongs to, and nothing in the approval chain checks the invoice against the phase-level term instead of the project-level total.

Not-to-exceed clauses are usually written against a defined scope: a discovery phase, an implementation milestone, a support tier. The contract states a ceiling for that scope specifically, separate from the total engagement value.

When the project is set up in Sage Intacct, a common practice is to load the full contract value as a single PO or budget line, because tracking each phase as a separate line adds setup work. That collapses the phase-level caps into one project-level number.

An invoice for a phase that has already run over its individual cap can still pass approval, because the running total against the full project budget has room left. The overrun surfaces only when someone pulls the original statement of work and checks phase by phase, which the standard AP workflow does not do.

4. What should an IT and professional services audit check line by line?

A line-level audit checks four things against the contract, not the PO: the billed role against the approved rate card, the billed hours or milestone against the statement of work's defined scope, the phase spend against its specific NTE cap, and the invoice date against any rate escalation or renewal clause that may have changed the applicable price. Each check requires the contract document itself, since none of these terms exist as structured data inside Sage Intacct.

These four checks require a reference table built once from the contract set: every active statement of work, its rate card, its phase caps, and its escalation terms, entered in one place. Sage Intacct's project and vendor dimensions can then tag each invoice line for comparison against that table.

Building the table is manual work the first time. Maintaining it means updating it at every contract renewal or amendment, which is where a reference table goes stale if nobody owns the update.

A. Rate and role match

Compare every billed role and rate to the statement of work's approved rate table. Flag any line where the title billed does not match a role the contract authorizes, or where the rate exceeds the ceiling for that role.

B. Scope and milestone match

Confirm the deliverable or hours billed fall inside the defined scope for that phase. A milestone billed as complete before its stated deliverable was met is a compliance issue, not just a timing one.

C. Cap and escalation match

Track cumulative spend against each phase's individual NTE cap, not the project total. Separately, check the invoice date against any escalation clause to confirm a rate increase was actually due.

5. Can Sage Intacct's dimensions be configured to prevent this drift going forward?

Sage Intacct's dimension structure, department, project, vendor, and custom dimensions, can carry a contract reference once it exists, tagging each invoice line against an approved rate or cap for automated comparison. What the platform cannot do on its own is generate that reference from a statement of work PDF or flag a violation without a rule built against data that lives outside the system. Configuration extends an existing control; it does not create the missing one.

A custom dimension can be added to hold a contract reference ID, and a smart rule can flag an invoice line that references a rate above a stored ceiling for that dimension. This is a real improvement over PO-only matching, and worth doing once a company has committed to maintaining the contract reference table.

The sequence matters. Building the dimension and the rule before the underlying rate cards and caps are extracted from the actual contracts means configuring against guessed values, since nobody has yet gone through every statement of work to record what it actually says.

The diagnostic work, extracting the real terms from every active contract, has to happen first. Configuration inside Sage Intacct is the mechanism that enforces the terms afterward, not the step that discovers them.

6. How do you size the exposure from IT and professional services drift?

There is no category-specific figure available for IT and professional services alone, because no dataset breaks findings down by category. Rate card violations, phase-level NTE overruns, and role substitutions are recurring, material sources of exposure in this category, and expensive to leave unchecked because the reference data lives in a contract document rather than in the ERP. Sizing them for a specific company requires running the line-by-line check against the real contracts, not applying a portfolio-wide number.

What can be said about IT and professional services specifically is qualitative: rate card violations, phase-level NTE overruns, and role substitutions are recurring, material, and easy to miss because the terms that would catch them live outside Sage Intacct entirely.

Margin drift across a full diagnostic, spanning every service vendor category together, typically runs 1% to 3% of service vendor spend, and diagnostics across ValueXPA engagements have found $300K to $4.5M per year in total, across ValueXPA diagnostics. That range describes the whole engagement, not any single category inside it, and is not a substitute for a category-specific finding.

The only way to get a number specific to IT and professional services at a given company is to run the reference-table check described above against the real contracts and the real invoices.

7. Should a $100M+ manufacturer build this check in-house or bring in a diagnostic?

Building the reference table in-house is possible with existing AP and procurement staff, provided someone is assigned to extract terms from every active statement of work and maintain the table through renewals. A fixed-scope diagnostic does the same extraction and line-by-line comparison against historical invoices in a bounded window, useful when the volume of active IT and professional services contracts is too large to review without dedicated time.

The in-house path costs staff time rather than a fee, and keeps the contract knowledge internal, which matters for a company with a small, stable vendor list. It requires someone with the authority to pull every statement of work and the discipline to update the table at each renewal.

A diagnostic engagement compresses that extraction and review into a prioritized roadmap in 2 to 4 weeks, across ValueXPA diagnostics, and the client retains 100% of recoveries found, across ValueXPA diagnostics, since the model is fixed-scope rather than contingency.

Neither path is automatically right. A company with two or three active IT vendors and a small AP team can likely run this in-house. One with a dozen concurrent statements of work, multiple renewal dates, and no one currently assigned to contract compliance is the case where a bounded external review pays for the staff time it would otherwise take to build the same table from scratch.

For the wider pattern this sits inside, start with the margin drift guide. See also build vs. buy: can you do contract-to-invoice matching in excel? and margin drift diagnostic for infor cloudsuite syteline.

8. Frequently Asked Questions (People Also Ask)

Does Sage Intacct support statement of work tracking natively?

No. Sage Intacct tracks purchase orders, project budgets, and dimensions like department and vendor. A statement of work is a contract document with rate tables, phase caps, and milestone definitions, none of which have a native field in the platform. That data has to be extracted and maintained outside the system, then linked back through a dimension.

What is a rate card violation in a professional services contract?

It is an invoice line that bills a role at a rate above what the statement of work's approved rate table allows, or bills a rate increase before the contract's escalation clause takes effect. It can also be a title substitution, where a more senior and more expensive resource is billed for work the contract scoped at a lower level.

Can a purchase order catch a milestone billed early?

A purchase order in Sage Intacct checks a dollar total against a budget line. It does not check whether the deliverable tied to a milestone was actually completed before the invoice was issued. That comparison requires the statement of work's own deliverable definitions, checked separately from the PO.

How often should the contract reference table be updated?

At every contract renewal or amendment. A reference table built once and never revisited goes stale as soon as a rate card changes or a new statement of work is signed, which means the checks run against it start comparing invoices to outdated terms.

Does a not-to-exceed cap apply to the whole project or to each phase?

It depends on how the contract is written, but professional services contracts can set NTE caps against a specific phase or deliverable rather than the entire engagement. If Sage Intacct only tracks the total contract value as one PO, phase-level overruns can pass approval unnoticed.

Is this general information or legal advice about contract terms?

This is general information about how to reconcile invoices against contract documents. It is not legal advice. Questions about how a specific statement of work or master service agreement should be interpreted belong with legal counsel or the contract owner.

What data does a custom dimension need to hold to support this check?

At minimum, a contract reference ID that links an invoice line back to its statement of work, along with the approved rate ceiling or NTE cap for that dimension value. The dimension itself does not generate this data. It has to be extracted from the contract and entered once the reference table exists.

Can AP staff run this audit without procurement or legal involvement?

AP staff can perform the line-by-line comparison once the reference table exists, but building that table usually requires pulling contracts from procurement or legal, since AP does not typically hold the signed statements of work. Coordinating that handoff once, at setup, is usually enough.

What triggers a rate escalation clause in a services contract?

Escalation clauses vary by contract, but common triggers include a contract anniversary date, a defined renewal period, or an index tied to a published rate. The invoice audit has to check the invoice date against the specific trigger written into that contract rather than assume a standard timing.