# Maintenance and repair Controls in Sage Intacct > What Sage Intacct enforces on maintenance and repair invoices, and where rate cards, not-to-exceed caps, and surcharge terms still need a separate check. Source: https://valuexpa.com/insights/maintenance-and-repair-controls-in-sage-intacct Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-07 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. On maintenance and repair spend, that gap tends to open at the rate card and the not-to-exceed clause, both documents that live outside any ERP's configured fields. Sage Intacct is a strong general ledger and AP platform. This guide describes exactly what it checks on a maintenance invoice, what it does not, and where a manufacturer above $100M in maintenance spend needs a control that sits alongside it rather than inside it. ## Executive Summary Sage Intacct enforces the controls it was built to enforce: purchase order existence, GL dimension coding, and approval workflow before a maintenance invoice posts. None of that reads a vendor's rate schedule, checks a not-to-exceed cap against a work order, or flags a surcharge that should have expired. The system verifies that a maintenance invoice matches an approved purchase order and account; it was never designed to verify that the purchase order itself was priced correctly against the contract behind it. That gap is where margin drift lives on maintenance and repair spend specifically: a technician's labor rate that quietly exceeds the contracted rate card, a not-to-exceed clause on a repair job that the invoice runs past without triggering any Sage Intacct workflow, or a service call surcharge that should have rolled off after a warranty period but keeps appearing. Sage Intacct's dimension tagging can report on all of this after the fact. It cannot stop the payment before it posts, because the contract terms live in a PDF, not in a configured field. What changes it is separating what the ERP checks from what the contract requires, and building the second check outside the system rather than assuming the first one covers it. ## 1. What does Sage Intacct actually check on a maintenance invoice before it posts? **Sage Intacct checks that a maintenance invoice references an approved purchase order or requisition, that the GL account and dimensions (department, location, project) are valid and coded, and that the invoice routes through the configured approval workflow before it posts to the ledger. These are structural and coding checks. None of them read the vendor's contracted labor rate, parts markup, or a not-to-exceed cap, because those terms are not fields the platform is configured to hold.** The core of Sage Intacct's AP control is the purchase order. If a maintenance vendor submits an invoice against a PO, the system confirms the PO exists, is approved, and has enough remaining balance to absorb the invoice line. That closes the door on invoices with no authorization trail at all. Dimension tagging is the other half. Every maintenance invoice can be coded to a location, a department, a project, or an asset, which is what makes month-end reporting on maintenance spend by plant or equipment class possible. This is a real and useful control, and it is the one manufacturers cite most often when asked what Sage Intacct does for maintenance spend. What it checks is structure and authorization, not price. A PO for a not-to-exceed repair and an invoice that matches that PO amount both pass, and so does an invoice that matches a PO which was never actually revised to reflect a change order. The system trusts the number already on the PO. It does not independently verify that number against a contract. ## 2. Can Sage Intacct catch a labor rate that exceeds the contracted rate card? **No. Sage Intacct has no native field for a vendor's contracted hourly labor rate by technician tier, and no rule that compares an invoice line's rate against one. Three-way matching in the platform checks the invoice against the purchase order and receipt; it does not test whether the rate on the purchase order itself was ever validated against the maintenance contract's rate schedule, which typically exists as a separate document outside the ERP.** A maintenance contract usually sets rates by technician tier: standard time, overtime, emergency callout, travel. Those rates sit in a signed agreement, often a PDF exhibit, not in a table Sage Intacct reads. When a vendor invoices above the contracted tier, one of two things happens. If the PO was cut at the correct rate and the invoice matches the PO, the invoice passes matching cleanly, because the PO itself, not the contract, is the reference point. If the PO was never cut with the contract rate loaded in the first place, the error is baked in before the invoice even arrives. Either way, the control the system runs, invoice-to-PO matching, verifies internal consistency. It does not verify the PO against the contract that should have generated it. Closing that gap means checking the rate card against invoiced rates directly, on a schedule, outside the matching workflow Sage Intacct runs. ## 3. Does Sage Intacct enforce a not-to-exceed cap on a repair job? **Sage Intacct enforces the PO's own line amount, not a contractual not-to-exceed clause layered on top of it. If a repair PO is issued at a given amount and the invoice arrives matching that amount, the system is satisfied even if the underlying work order or contract capped total charges at a lower figure, or required a change order above a threshold that nobody entered into the PO before the invoice posted.** A not-to-exceed clause is meant to cap total exposure on a repair regardless of how the labor and parts break out. It is a contract concept, not a purchasing concept, and the distinction matters mechanically. Sage Intacct's PO matching tests whether the invoice fits inside whatever the PO already says, dollar for dollar. If the PO amount itself was set correctly and never revised, matching holds. If a technician finds additional damage mid-repair and the vendor invoices above the original PO, most configurations flag the variance for approval, which is a useful check, but the approval decision is made by a person looking at the invoice, not by the system checking the NTE clause in the contract. The result is that an NTE overrun can clear approval if the approver does not have the contract's cap number in front of them at the moment of review. The system enforces what is configured. It does not go get the number that was never configured. ## 4. What happens to a maintenance surcharge that should have expired? **Sage Intacct has no mechanism that tracks a surcharge's expiration condition, such as a warranty period ending or a promotional rate rolling off. It posts whatever line item and amount the vendor invoices, coded to whatever dimension is assigned. A surcharge that should have stopped after a contract milestone continues to pass every structural check the platform runs, because the check is about coding accuracy, not about whether the charge should still exist.** Maintenance contracts commonly bundle a temporary surcharge into pricing: a fuel or travel surcharge during a startup period, a premium rate during a warranty transition, an expedite fee tied to an initial rollout. These are meant to expire on a date or a milestone stated in the contract. Sage Intacct has no calendar tied to contract clauses. It has no field that says a line item becomes invalid after a given date unless someone manually builds that logic into a recurring transaction template, and even then the logic covers the ERP's own recurring entries, not a vendor's independent invoice. ### A. What the PPI trend adds to this US Bureau of Labor Statistics Producer Price Index data for commercial machinery repair and maintenance (series PCU8113--8113--), read September 6, 2026, showed a July 2026 index value of 237.468, up 9.1% year over year. Rates on maintenance contracts move against that kind of input cost pressure, and a surcharge negotiated during a period of rising costs is exactly the kind of line item that outlives its original justification once conditions change. Sage Intacct will not flag that on its own; a control tied to the contract's expiration terms, checked against the invoice date, has to do it. ## 5. How does GL dimension reporting on maintenance spend differ from a contract compliance check? **Dimension reporting tells you how much maintenance spend hit a location, department, or asset class over a period. Contract compliance tells you whether each invoice within that spend matched the rate, cap, and surcharge terms the vendor agreed to. Sage Intacct is strong at the first and does not attempt the second, and mistaking a clean dimension report for a clean contract is the specific error that lets rate and NTE drift accumulate unnoticed across a fiscal year.** The two functions answer different questions, and Sage Intacct is built to answer only one of them well. A CFO looking at a quarterly maintenance spend report by location is getting an accurate picture of where money went. That picture says nothing about whether the money went out at the right rate. This is also why a rising maintenance spend trend and a rate or NTE compliance problem can coexist invisibly. Spend can climb for legitimate reasons: more equipment, more downtime, higher input costs, while a subset of invoices within that trend are also running above contract terms. Nothing in the dimension report distinguishes the two causes. - **What dimension reporting shows:** Total maintenance spend by plant, department, or equipment class, trended period over period, coded at the time each invoice posts. - **What it does not show:** Whether any individual invoice line matched the contracted rate, stayed inside a not-to-exceed cap, or dropped a surcharge that should have expired. - **Where the two get confused:** A finance team reviewing a clean, well-coded maintenance spend report can reasonably assume the underlying invoices were priced correctly, since nothing in the report suggests otherwise. - **What closes the gap:** Reading the maintenance contracts directly and matching their rate, cap, and surcharge terms against invoice detail, a step outside the dimension structure entirely. ## 6. Should a manufacturer configure more fields in Sage Intacct, or run the contract check separately? **Configuring more custom fields helps only where a contract term is stable and structured enough to encode, such as a fixed hourly rate that never changes mid-contract. It does not help where the term is conditional, such as a cap that depends on cumulative spend across multiple invoices, or a surcharge tied to a date outside the transaction record. For most maintenance contracts, a periodic invoice-to-contract check run outside the ERP catches more than further configuration inside it.** Custom fields and dimensions in Sage Intacct can absolutely encode a static rate, and doing so is worth the setup time where a contract's terms genuinely do not change for its duration. That closes part of the gap at low ongoing cost. Where it breaks down is anything conditional: a not-to-exceed cap that aggregates across several invoices tied to one work order, a rate that steps down after a volume threshold, or a surcharge that should stop on a date unrelated to any transaction in the system. Building that logic into the ERP means replicating the contract's language in configuration and maintaining it every time the contract is renewed or amended, which is a maintenance burden most AP teams do not have capacity for. A periodic check that reads the actual contract PDF against invoice detail, run outside the ERP on a quarterly or annual cycle, catches the conditional terms without asking the ERP to become something it was not built to be, a question closely related to whether you can do [contract-to-invoice matching in Excel](/guides/build-vs-buy-can-you-do-contract-to-invoice-matching-in) or need something more. The same gap between PO matching and contract terms shows up in [maintenance and repair controls in NetSuite](/guides/maintenance-and-repair-controls-in-netsuite) and in maintenance and repair controls in QuickBooks Enterprise, and it repeats for contract labor and staffing controls in NetSuite and IT and professional services controls in NetSuite, since none of these systems were built to read a contract PDF. Manufacturers running [Infor CloudSuite SyteLine](/guides/for-infor-syteline) or [Plex](/guides/for-plex) face the identical gap on their own maintenance vendor contracts. For the wider pattern this sits inside, start with the [margin drift](/insights/best-invoice-validation-software-smb) guide. ## 7. Frequently Asked Questions (People Also Ask) ### Does Sage Intacct do three-way matching on maintenance invoices? Yes, where a purchase order and receipt exist. It matches the invoice against the PO amount and any receipt of goods or completed service. This confirms internal consistency between the transaction documents; it does not confirm the PO was priced according to the vendor contract in the first place. ### Can I load a vendor's rate card directly into Sage Intacct? Not as a native contract object. You can approximate a fixed rate through custom fields or item pricing on recurring purchase orders, which works for a rate that never changes. It does not handle tiered rates, volume-based rate changes, or caps that depend on cumulative spend. ### Will Sage Intacct flag an invoice that exceeds its purchase order? Typically, yes, through a variance or exception in the approval workflow, depending on configuration. Whether that exception gets caught depends on the approver recognizing the overage against the contract's actual not-to-exceed clause, which the system does not display automatically. ### Is GL dimension reporting enough to catch maintenance overbilling? No. Dimension reporting shows where maintenance spend landed by location, department, or asset. It does not test whether the rate, cap, or surcharge on any invoice matched the underlying contract, which is a separate check the ERP does not run. ### What is a not-to-exceed clause in a maintenance contract? It is a cap on total charges for a repair or service call, regardless of how labor and parts break out on the invoice. It protects the buyer from scope creep during a job. Sage Intacct enforces whatever PO amount is entered, not the underlying NTE clause itself. ### How does the PPI data for commercial machinery repair relate to maintenance contract drift? Per the US Bureau of Labor Statistics, the Producer Price Index for commercial machinery repair and maintenance (series PCU8113--8113--) stood at 237.468 in July 2026, up 9.1% year over year (read September 6, 2026). Rising input costs are a reason surcharges get added to contracts; they are not a reason a surcharge should persist once its stated expiration condition has passed. ### Should I build a custom rate validation report inside Sage Intacct? It is worth doing for contracts with a single, unchanging rate. For contracts with tiered rates, cumulative caps, or time-based surcharges, replicating the contract logic in the ERP is a maintenance burden; a periodic check against the contract document itself, run outside the system, is usually more reliable. ### Does Sage Intacct integrate with maintenance management or CMMS systems? Sage Intacct supports integrations with various operational systems through its API and marketplace, and many manufacturers connect a CMMS for work order data. The integration passes transaction data between systems; it does not add contract rate or cap validation to either side unless that logic is built separately. ### What is margin drift on maintenance and repair spend specifically? It is the gap between a maintenance contract's rate card, cap, and surcharge terms and what a vendor's invoice actually charges. It shows up as a labor rate above the contracted tier, a repair invoice that exceeds a not-to-exceed cap, or a surcharge that continues past its stated expiration. ### 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 Sage Intacct enforces the controls it was built to enforce: purchase order existence, GL dimension coding, and approval workflow before a maintenance invoice posts. None of that reads a vendor's rate schedule, checks a not-to-exceed cap against a work order, or flags a surcharge that should have expired. The system verifies that a maintenance invoice matches an approved purchase order and account; it was never designed to verify that the purchase order itself was priced correctly against the contract behind it. That gap is where margin drift lives on maintenance and repair spend specifically: a technician's labor rate that quietly exceeds the contracted rate card, a not-to-exceed clause on a repair job that the invoice runs past without triggering any Sage Intacct workflow, or a service call surcharge that should have rolled off after a warranty period but keeps appearing. Sage Intacct's dimension tagging can report on all of this after the fact. It cannot stop the payment before it posts, because the contract terms live in a PDF, not in a configured field. What changes it is separating what the ERP checks from what the contract requires, and building the second check outside the system rather than assuming the first one covers it. ## 1. What does Sage Intacct actually check on a maintenance invoice before it posts? Sage Intacct checks that a maintenance invoice references an approved purchase order or requisition, that the GL account and dimensions (department, location, project) are valid and coded, and that the invoice routes through the configured approval workflow before it posts to the ledger. These are structural and coding checks. None of them read the vendor's contracted labor rate, parts markup, or a not-to-exceed cap, because those terms are not fields the platform is configured to hold. The core of Sage Intacct's AP control is the purchase order. If a maintenance vendor submits an invoice against a PO, the system confirms the PO exists, is approved, and has enough remaining balance to absorb the invoice line. That closes the door on invoices with no authorization trail at all. Dimension tagging is the other half. Every maintenance invoice can be coded to a location, a department, a project, or an asset, which is what makes month-end reporting on maintenance spend by plant or equipment class possible. This is a real and useful control, and it is the one manufacturers cite most often when asked what Sage Intacct does for maintenance spend. What it checks is structure and authorization, not price. A PO for a not-to-exceed repair and an invoice that matches that PO amount both pass, and so does an invoice that matches a PO which was never actually revised to reflect a change order. The system trusts the number already on the PO. It does not independently verify that number against a contract. ## 2. Can Sage Intacct catch a labor rate that exceeds the contracted rate card? No. Sage Intacct has no native field for a vendor's contracted hourly labor rate by technician tier, and no rule that compares an invoice line's rate against one. Three-way matching in the platform checks the invoice against the purchase order and receipt; it does not test whether the rate on the purchase order itself was ever validated against the maintenance contract's rate schedule, which typically exists as a separate document outside the ERP. A maintenance contract usually sets rates by technician tier: standard time, overtime, emergency callout, travel. Those rates sit in a signed agreement, often a PDF exhibit, not in a table Sage Intacct reads. When a vendor invoices above the contracted tier, one of two things happens. If the PO was cut at the correct rate and the invoice matches the PO, the invoice passes matching cleanly, because the PO itself, not the contract, is the reference point. If the PO was never cut with the contract rate loaded in the first place, the error is baked in before the invoice even arrives. Either way, the control the system runs, invoice-to-PO matching, verifies internal consistency. It does not verify the PO against the contract that should have generated it. Closing that gap means checking the rate card against invoiced rates directly, on a schedule, outside the matching workflow Sage Intacct runs. ## 3. Does Sage Intacct enforce a not-to-exceed cap on a repair job? Sage Intacct enforces the PO's own line amount, not a contractual not-to-exceed clause layered on top of it. If a repair PO is issued at a given amount and the invoice arrives matching that amount, the system is satisfied even if the underlying work order or contract capped total charges at a lower figure, or required a change order above a threshold that nobody entered into the PO before the invoice posted. A not-to-exceed clause is meant to cap total exposure on a repair regardless of how the labor and parts break out. It is a contract concept, not a purchasing concept, and the distinction matters mechanically. Sage Intacct's PO matching tests whether the invoice fits inside whatever the PO already says, dollar for dollar. If the PO amount itself was set correctly and never revised, matching holds. If a technician finds additional damage mid-repair and the vendor invoices above the original PO, most configurations flag the variance for approval, which is a useful check, but the approval decision is made by a person looking at the invoice, not by the system checking the NTE clause in the contract. The result is that an NTE overrun can clear approval if the approver does not have the contract's cap number in front of them at the moment of review. The system enforces what is configured. It does not go get the number that was never configured. ## 4. What happens to a maintenance surcharge that should have expired? Sage Intacct has no mechanism that tracks a surcharge's expiration condition, such as a warranty period ending or a promotional rate rolling off. It posts whatever line item and amount the vendor invoices, coded to whatever dimension is assigned. A surcharge that should have stopped after a contract milestone continues to pass every structural check the platform runs, because the check is about coding accuracy, not about whether the charge should still exist. Maintenance contracts commonly bundle a temporary surcharge into pricing: a fuel or travel surcharge during a startup period, a premium rate during a warranty transition, an expedite fee tied to an initial rollout. These are meant to expire on a date or a milestone stated in the contract. Sage Intacct has no calendar tied to contract clauses. It has no field that says a line item becomes invalid after a given date unless someone manually builds that logic into a recurring transaction template, and even then the logic covers the ERP's own recurring entries, not a vendor's independent invoice. ### A. What the PPI trend adds to this US Bureau of Labor Statistics Producer Price Index data for commercial machinery repair and maintenance (series PCU8113--8113--), read September 6, 2026, showed a July 2026 index value of 237.468, up 9.1% year over year. Rates on maintenance contracts move against that kind of input cost pressure, and a surcharge negotiated during a period of rising costs is exactly the kind of line item that outlives its original justification once conditions change. Sage Intacct will not flag that on its own; a control tied to the contract's expiration terms, checked against the invoice date, has to do it. ## 5. How does GL dimension reporting on maintenance spend differ from a contract compliance check? Dimension reporting tells you how much maintenance spend hit a location, department, or asset class over a period. Contract compliance tells you whether each invoice within that spend matched the rate, cap, and surcharge terms the vendor agreed to. Sage Intacct is strong at the first and does not attempt the second, and mistaking a clean dimension report for a clean contract is the specific error that lets rate and NTE drift accumulate unnoticed across a fiscal year. The two functions answer different questions, and Sage Intacct is built to answer only one of them well. A CFO looking at a quarterly maintenance spend report by location is getting an accurate picture of where money went. That picture says nothing about whether the money went out at the right rate. This is also why a rising maintenance spend trend and a rate or NTE compliance problem can coexist invisibly. Spend can climb for legitimate reasons: more equipment, more downtime, higher input costs, while a subset of invoices within that trend are also running above contract terms. Nothing in the dimension report distinguishes the two causes. - What dimension reporting shows: Total maintenance spend by plant, department, or equipment class, trended period over period, coded at the time each invoice posts. - What it does not show: Whether any individual invoice line matched the contracted rate, stayed inside a not-to-exceed cap, or dropped a surcharge that should have expired. - Where the two get confused: A finance team reviewing a clean, well-coded maintenance spend report can reasonably assume the underlying invoices were priced correctly, since nothing in the report suggests otherwise. - What closes the gap: Reading the maintenance contracts directly and matching their rate, cap, and surcharge terms against invoice detail, a step outside the dimension structure entirely. ## 6. Should a manufacturer configure more fields in Sage Intacct, or run the contract check separately? Configuring more custom fields helps only where a contract term is stable and structured enough to encode, such as a fixed hourly rate that never changes mid-contract. It does not help where the term is conditional, such as a cap that depends on cumulative spend across multiple invoices, or a surcharge tied to a date outside the transaction record. For most maintenance contracts, a periodic invoice-to-contract check run outside the ERP catches more than further configuration inside it. Custom fields and dimensions in Sage Intacct can absolutely encode a static rate, and doing so is worth the setup time where a contract's terms genuinely do not change for its duration. That closes part of the gap at low ongoing cost. Where it breaks down is anything conditional: a not-to-exceed cap that aggregates across several invoices tied to one work order, a rate that steps down after a volume threshold, or a surcharge that should stop on a date unrelated to any transaction in the system. Building that logic into the ERP means replicating the contract's language in configuration and maintaining it every time the contract is renewed or amended, which is a maintenance burden most AP teams do not have capacity for. A periodic check that reads the actual contract PDF against invoice detail, run outside the ERP on a quarterly or annual cycle, catches the conditional terms without asking the ERP to become something it was not built to be, a question closely related to whether you can do [contract-to-invoice matching in Excel](/guides/build-vs-buy-can-you-do-contract-to-invoice-matching-in) or need something more. The same gap between PO matching and contract terms shows up in [maintenance and repair controls in NetSuite](/guides/maintenance-and-repair-controls-in-netsuite) and in maintenance and repair controls in QuickBooks Enterprise, and it repeats for contract labor and staffing controls in NetSuite and IT and professional services controls in NetSuite, since none of these systems were built to read a contract PDF. Manufacturers running [Infor CloudSuite SyteLine](/guides/for-infor-syteline) or [Plex](/guides/for-plex) face the identical gap on their own maintenance vendor contracts. For the wider pattern this sits inside, start with the [margin drift](/insights/best-invoice-validation-software-smb) guide. ## Common questions ### Does Sage Intacct do three-way matching on maintenance invoices? Yes, where a purchase order and receipt exist. It matches the invoice against the PO amount and any receipt of goods or completed service. This confirms internal consistency between the transaction documents; it does not confirm the PO was priced according to the vendor contract in the first place. ### Can I load a vendor's rate card directly into Sage Intacct? Not as a native contract object. You can approximate a fixed rate through custom fields or item pricing on recurring purchase orders, which works for a rate that never changes. It does not handle tiered rates, volume-based rate changes, or caps that depend on cumulative spend. ### Will Sage Intacct flag an invoice that exceeds its purchase order? Typically, yes, through a variance or exception in the approval workflow, depending on configuration. Whether that exception gets caught depends on the approver recognizing the overage against the contract's actual not-to-exceed clause, which the system does not display automatically. ### Is GL dimension reporting enough to catch maintenance overbilling? No. Dimension reporting shows where maintenance spend landed by location, department, or asset. It does not test whether the rate, cap, or surcharge on any invoice matched the underlying contract, which is a separate check the ERP does not run. ### What is a not-to-exceed clause in a maintenance contract? It is a cap on total charges for a repair or service call, regardless of how labor and parts break out on the invoice. It protects the buyer from scope creep during a job. Sage Intacct enforces whatever PO amount is entered, not the underlying NTE clause itself. --- 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