# Can Sage Intacct store vendor contract terms? > Sage Intacct holds vendor records and GL data well, but rate cards, NTE caps and rebate clauses live in PDFs it was never built to parse. Read the full guide. Source: https://valuexpa.com/insights/can-sage-intacct-store-vendor-contract-terms Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-10-22 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. Sage Intacct is a strong general ledger and AP platform for a manufacturer running multi-entity consolidations, but the question buyers ask is narrower: does it hold the contract itself, the rate card, the volume tier, the rebate trigger, in a form that checks an invoice against it. The honest answer is no, not natively, and the gap between what Sage Intacct records and what a contract actually promises is where margin drift accumulates unseen. ## Executive Summary Sage Intacct stores a vendor record, a GL account, a purchase order and the invoice line items tied to it. That structure is built for financial reporting and three-way matching against a PO and a receipt. It is not built to hold a rate schedule, a minimum volume commitment, a rebate tier, or a not-to-exceed cap as an enforceable rule. The mechanism that causes drift is simple: contract terms sit in a PDF, a signed rate card, or an email amendment, entirely outside the fields Sage Intacct validates. AP approves an invoice because it matches the PO. Nobody re-reads the contract to confirm the rate on that PO is still the rate the vendor agreed to eighteen months ago. What changes it is not a bigger ERP module. It is treating the contract as a separate, structured dataset that gets checked against every invoice line, independent of whether Sage Intacct's own fields can hold it. Some teams build that check manually. Others buy it as a service. Either way, the fix lives outside the ERP's native schema. ## 1. What does Sage Intacct actually store for a vendor? **Sage Intacct stores a vendor master record: name, remit-to address, payment terms, default GL account and tax settings. It links purchase orders to vendors and matches invoice lines against a PO and, where configured, a receipt. None of these fields hold a rate schedule, a tiered discount, a rebate trigger or an NTE cap as a rule the system evaluates. The vendor record answers who you pay and how; it does not answer what the contract entitles that vendor to.** The vendor master in Sage Intacct is a financial and operational record, not a legal one. It exists to route payments, apply the right GL coding, and support 1099 reporting. Those fields are complete for that purpose. A contract, by contrast, has variable rates by lane or SKU, minimum volume commitments, rebate thresholds tied to spend bands, and expiration dates on promotional pricing. Sage Intacct has no field type built to hold a conditional rule like "rate drops to $X after 500 units" and test it against every incoming invoice line. This is not a shortcoming specific to Sage Intacct. Every general ledger platform in this tier draws the same line: it manages the transaction, not the agreement behind it. ## 2. Where do contract terms actually live instead? **Contract terms typically live as PDFs attached to a vendor file, stored in a shared drive, or held only in a procurement lead's inbox as a signed amendment. Sage Intacct's attachment feature can hold the PDF itself, but an attached document is not a queryable field. Nothing in the platform reads the rate table inside that PDF and compares it to the number on line 4 of this week's invoice.** Attaching a contract to a vendor record satisfies an audit request: an auditor can open the file and see the agreement exists. It does not satisfy an invoice check, because Sage Intacct's matching logic never opens that PDF. The result is a two-system reality. The ERP holds the transaction. A file server, an email thread, or a procurement lead's memory holds the rule. Nothing forces the two to reconcile on every invoice, only when someone happens to pull the contract and compare it line by line. Over 12 to 18 months, a stale rate card, an expired promotional discount, or an unclaimed rebate tier keeps producing charges that pass a PO match while failing the actual agreement. ## 3. Can a custom object or workflow rule hold contract terms? **Sage Intacct's Platform Services lets an administrator build custom objects and fields, so a team could construct a rate table and attach validation rules. That is engineering work, not configuration, and it has to be rebuilt every time a contract renews, a lane is added, or a rebate tier changes. It is possible. It is not what the platform does out of the box, and it is rarely maintained once the person who built it moves on.** Custom objects can represent structured data: a table of rates by vendor and category, a rebate threshold, an NTE cap. Sage Intacct's workflow rules can, in principle, flag a line that exceeds a stored value. The practical problem is maintenance. A rate card changes when a contract renews, when a vendor adds a fuel surcharge, or when a volume tier resets at the new fiscal year. Each change means someone updates the custom object correctly, on time, for every affected vendor. That labor sits outside the accounting team's normal workflow and outside what Sage Intacct partners typically implement. It is why most organizations skip this route and rely on periodic manual review instead. ### A. What the build actually requires A working custom-object approach needs three components: a data model for the rate rule, a trigger that fires on invoice entry, and a maintenance process that keeps the rule current as contracts change. Sage Intacct's Platform Services supports the first two with developer effort. The third is a process commitment, not a software feature, and it is the piece that most often lapses within a year of going live. ## 4. Does Sage Intacct's three-way match catch a rate violation? **Three-way matching in Sage Intacct checks the invoice against the purchase order and the receipt: quantity, unit price as entered on the PO, and delivery confirmation. It does not test whether the unit price on that PO still reflects the contracted rate, and it does not evaluate a surcharge's expiration condition or a rebate clause at all. The match can pass cleanly while the underlying rate is wrong.** Three-way matching is a control against a different failure mode: paying for goods never received, or paying a different quantity or price than what was ordered. It does its job well within that scope. The PO itself is where the rate enters the system, often typed in by a buyer from a quote or a prior invoice. If that rate was never updated when the contract renewed, or if a surcharge should have expired and did not, the PO carries the error forward and three-way matching confirms it. A rebate clause is invisible to this control entirely, because a rebate is not a line on an invoice. It is a credit the vendor owes based on cumulative spend, tracked nowhere in the match logic. ## 5. What should you check in Sage Intacct before assuming coverage? **Before assuming Sage Intacct enforces a contract, pull three things: the vendor's current PO rate versus the signed rate card, the surcharge lines on the last six invoices versus their stated expiration terms, and any rebate clause versus what has actually been credited. If any of the three shows a gap, the platform's matching logic did not catch it, because none of those checks are part of its native rule set.** This is a diagnostic exercise, not a software fix. It tells you whether the gap is theoretical or already costing money. Start with high-volume vendors in freight, [contract labor](/insights/contract-labor-and-staffing-controls-in-netsuite), and maintenance, where rate tables and surcharges change most often. Pull the current PO price and compare it directly to the last signed rate card or amendment. Next, check surcharge lines. A fuel surcharge or an expedite fee often has a stated end condition, a date or a trigger, and invoices frequently keep charging it after that condition passes because nothing in the ERP tracks the condition itself. Finally, check rebate clauses against actual credits received. A rebate that requires the vendor to calculate and issue it, rather than the buyer to claim it, is the clause most likely to go unclaimed. - **PO rate vs. rate card:** Compare the price on the current purchase order to the signed contract rate. A mismatch means the PO was never updated at renewal. - **Surcharge expiration terms:** Check whether a fuel or expedite surcharge is still being charged after its stated end condition passed. - **Rebate credits vs. clause:** Confirm any earned rebate was actually issued, since Sage Intacct has no field that tracks a rebate obligation. ## 6. Should you build this in Sage Intacct or add a separate layer? **Whether to extend Sage Intacct with custom objects or add a separate contract-checking layer depends on how many vendors carry variable, changing terms and how much internal engineering time is available to maintain the build. A small set of stable contracts can be tracked manually. A large, frequently renewing vendor base with rate tiers and rebate clauses across freight, labor and MRO categories outgrows manual tracking quickly and outgrows a custom object almost as fast.** The decision turns on volume and change frequency, not on Sage Intacct's capability ceiling. A manufacturer with a dozen stable service contracts can review them against invoices manually, on a schedule, without new infrastructure. A manufacturer running variable rate cards across [freight and 3PL](/insights/freight-and-3pl-controls-in-epicor-kinetic), contract labor, and [maintenance and repair](/insights/maintenance-and-repair-controls-in-netsuite), each renewing on different cycles, is comparing hundreds of invoice lines against dozens of shifting agreements every month. Manual review does not scale to that, and a custom object built once tends to fall out of sync with the next renewal. A structured, standalone check of contract terms against invoice lines, built separately from the ERP and covering the categories where drift accumulates, answers this without requiring Sage Intacct to become something it was not designed to be. 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 have a contract management module? Sage Intacct offers attachment fields and, through Platform Services, custom objects that a team can configure to hold structured data. It does not ship a native contract management module that parses rate tables, tracks rebate clauses, or evaluates NTE caps against incoming invoices out of the box. ### Can I attach a PDF contract to a vendor record in Sage Intacct? Yes. Vendor records support file attachments, so a signed contract or rate card can be stored alongside the vendor's financial data. That satisfies document retention for an audit, but the attached PDF is not queried by any matching or approval workflow, so it does not enforce the rate. ### Will three-way matching catch an expired surcharge? No. Three-way matching checks the invoice against the purchase order and the receipt for quantity, price as entered, and delivery. It does not evaluate whether a surcharge's stated expiration condition has passed, because that condition is not a field the match logic reads. ### Is a custom object in Sage Intacct enough to enforce a rate card? It can hold the data, but enforcement also requires a trigger rule and, critically, an ongoing process to update the object every time a contract renews or a rate changes. Without that maintenance commitment, the custom object drifts out of date and stops reflecting the real agreement. ### What is the difference between a rebate clause and a discount on an invoice? A discount reduces the price on the invoice line itself, and Sage Intacct can record it directly. A rebate is a credit owed based on cumulative spend over a period, calculated separately from any single invoice, which is why it is invisible to standard matching logic. ### Should I ask my Sage Intacct implementation partner to build this? You can, and Platform Services supports it technically. Weigh the engineering cost and the maintenance burden against how many vendors carry variable terms. For a large, multi-category vendor base, a standalone contract check maintained outside the ERP is often more durable than a custom build inside it. ### Does this problem exist in other ERPs too, or is it specific to Sage Intacct? It is not specific to Sage Intacct. Every general ledger and AP platform in this tier separates the transaction record from the contract document by design. The gap described here is a category-wide feature of ERP architecture, not a Sage Intacct limitation. ### How do I find out if this is already costing us money? Pull the current PO rate for a sample of high-volume vendors and compare it to the signed rate card, check recent surcharge lines against their stated expiration terms, and confirm any rebate clause has actually been credited. A gap in any of the three indicates uncaptured drift. ### Can Excel fill the gap instead of a custom object? A spreadsheet can hold a rate table, but it carries the same maintenance risk as a custom object: it is only accurate if someone updates it every time a contract changes, and nothing forces that update to happen before the next invoice is approved. ### 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 stores a vendor record, a GL account, a purchase order and the invoice line items tied to it. That structure is built for financial reporting and three-way matching against a PO and a receipt. It is not built to hold a rate schedule, a minimum volume commitment, a rebate tier, or a not-to-exceed cap as an enforceable rule. The mechanism that causes drift is simple: contract terms sit in a PDF, a signed rate card, or an email amendment, entirely outside the fields Sage Intacct validates. AP approves an invoice because it matches the PO. Nobody re-reads the contract to confirm the rate on that PO is still the rate the vendor agreed to eighteen months ago. What changes it is not a bigger ERP module. It is treating the contract as a separate, structured dataset that gets checked against every invoice line, independent of whether Sage Intacct's own fields can hold it. Some teams build that check manually. Others buy it as a service. Either way, the fix lives outside the ERP's native schema. ## 1. What does Sage Intacct actually store for a vendor? Sage Intacct stores a vendor master record: name, remit-to address, payment terms, default GL account and tax settings. It links purchase orders to vendors and matches invoice lines against a PO and, where configured, a receipt. None of these fields hold a rate schedule, a tiered discount, a rebate trigger or an NTE cap as a rule the system evaluates. The vendor record answers who you pay and how; it does not answer what the contract entitles that vendor to. The vendor master in Sage Intacct is a financial and operational record, not a legal one. It exists to route payments, apply the right GL coding, and support 1099 reporting. Those fields are complete for that purpose. A contract, by contrast, has variable rates by lane or SKU, minimum volume commitments, rebate thresholds tied to spend bands, and expiration dates on promotional pricing. Sage Intacct has no field type built to hold a conditional rule like "rate drops to $X after 500 units" and test it against every incoming invoice line. This is not a shortcoming specific to Sage Intacct. Every general ledger platform in this tier draws the same line: it manages the transaction, not the agreement behind it. ## 2. Where do contract terms actually live instead? Contract terms typically live as PDFs attached to a vendor file, stored in a shared drive, or held only in a procurement lead's inbox as a signed amendment. Sage Intacct's attachment feature can hold the PDF itself, but an attached document is not a queryable field. Nothing in the platform reads the rate table inside that PDF and compares it to the number on line 4 of this week's invoice. Attaching a contract to a vendor record satisfies an audit request: an auditor can open the file and see the agreement exists. It does not satisfy an invoice check, because Sage Intacct's matching logic never opens that PDF. The result is a two-system reality. The ERP holds the transaction. A file server, an email thread, or a procurement lead's memory holds the rule. Nothing forces the two to reconcile on every invoice, only when someone happens to pull the contract and compare it line by line. Over 12 to 18 months, a stale rate card, an expired promotional discount, or an unclaimed rebate tier keeps producing charges that pass a PO match while failing the actual agreement. ## 3. Can a custom object or workflow rule hold contract terms? Sage Intacct's Platform Services lets an administrator build custom objects and fields, so a team could construct a rate table and attach validation rules. That is engineering work, not configuration, and it has to be rebuilt every time a contract renews, a lane is added, or a rebate tier changes. It is possible. It is not what the platform does out of the box, and it is rarely maintained once the person who built it moves on. Custom objects can represent structured data: a table of rates by vendor and category, a rebate threshold, an NTE cap. Sage Intacct's workflow rules can, in principle, flag a line that exceeds a stored value. The practical problem is maintenance. A rate card changes when a contract renews, when a vendor adds a fuel surcharge, or when a volume tier resets at the new fiscal year. Each change means someone updates the custom object correctly, on time, for every affected vendor. That labor sits outside the accounting team's normal workflow and outside what Sage Intacct partners typically implement. It is why most organizations skip this route and rely on periodic manual review instead. ### A. What the build actually requires A working custom-object approach needs three components: a data model for the rate rule, a trigger that fires on invoice entry, and a maintenance process that keeps the rule current as contracts change. Sage Intacct's Platform Services supports the first two with developer effort. The third is a process commitment, not a software feature, and it is the piece that most often lapses within a year of going live. ## 4. Does Sage Intacct's three-way match catch a rate violation? Three-way matching in Sage Intacct checks the invoice against the purchase order and the receipt: quantity, unit price as entered on the PO, and delivery confirmation. It does not test whether the unit price on that PO still reflects the contracted rate, and it does not evaluate a surcharge's expiration condition or a rebate clause at all. The match can pass cleanly while the underlying rate is wrong. Three-way matching is a control against a different failure mode: paying for goods never received, or paying a different quantity or price than what was ordered. It does its job well within that scope. The PO itself is where the rate enters the system, often typed in by a buyer from a quote or a prior invoice. If that rate was never updated when the contract renewed, or if a surcharge should have expired and did not, the PO carries the error forward and three-way matching confirms it. A rebate clause is invisible to this control entirely, because a rebate is not a line on an invoice. It is a credit the vendor owes based on cumulative spend, tracked nowhere in the match logic. ## 5. What should you check in Sage Intacct before assuming coverage? Before assuming Sage Intacct enforces a contract, pull three things: the vendor's current PO rate versus the signed rate card, the surcharge lines on the last six invoices versus their stated expiration terms, and any rebate clause versus what has actually been credited. If any of the three shows a gap, the platform's matching logic did not catch it, because none of those checks are part of its native rule set. This is a diagnostic exercise, not a software fix. It tells you whether the gap is theoretical or already costing money. Start with high-volume vendors in freight, [contract labor](/insights/contract-labor-and-staffing-controls-in-netsuite), and maintenance, where rate tables and surcharges change most often. Pull the current PO price and compare it directly to the last signed rate card or amendment. Next, check surcharge lines. A fuel surcharge or an expedite fee often has a stated end condition, a date or a trigger, and invoices frequently keep charging it after that condition passes because nothing in the ERP tracks the condition itself. Finally, check rebate clauses against actual credits received. A rebate that requires the vendor to calculate and issue it, rather than the buyer to claim it, is the clause most likely to go unclaimed. 1. PO rate vs. rate card: Compare the price on the current purchase order to the signed contract rate. A mismatch means the PO was never updated at renewal. 2. Surcharge expiration terms: Check whether a fuel or expedite surcharge is still being charged after its stated end condition passed. 3. Rebate credits vs. clause: Confirm any earned rebate was actually issued, since Sage Intacct has no field that tracks a rebate obligation. ## 6. Should you build this in Sage Intacct or add a separate layer? Whether to extend Sage Intacct with custom objects or add a separate contract-checking layer depends on how many vendors carry variable, changing terms and how much internal engineering time is available to maintain the build. A small set of stable contracts can be tracked manually. A large, frequently renewing vendor base with rate tiers and rebate clauses across freight, labor and MRO categories outgrows manual tracking quickly and outgrows a custom object almost as fast. The decision turns on volume and change frequency, not on Sage Intacct's capability ceiling. A manufacturer with a dozen stable service contracts can review them against invoices manually, on a schedule, without new infrastructure. A manufacturer running variable rate cards across [freight and 3PL](/insights/freight-and-3pl-controls-in-epicor-kinetic), contract labor, and [maintenance and repair](/insights/maintenance-and-repair-controls-in-netsuite), each renewing on different cycles, is comparing hundreds of invoice lines against dozens of shifting agreements every month. Manual review does not scale to that, and a custom object built once tends to fall out of sync with the next renewal. A structured, standalone check of contract terms against invoice lines, built separately from the ERP and covering the categories where drift accumulates, answers this without requiring Sage Intacct to become something it was not designed to be. For the wider pattern this sits inside, start with the [margin drift](/insights/best-invoice-validation-software-smb) guide. ## Common questions ### Does Sage Intacct have a contract management module? Sage Intacct offers attachment fields and, through Platform Services, custom objects that a team can configure to hold structured data. It does not ship a native contract management module that parses rate tables, tracks rebate clauses, or evaluates NTE caps against incoming invoices out of the box. ### Can I attach a PDF contract to a vendor record in Sage Intacct? Yes. Vendor records support file attachments, so a signed contract or rate card can be stored alongside the vendor's financial data. That satisfies document retention for an audit, but the attached PDF is not queried by any matching or approval workflow, so it does not enforce the rate. ### Will three-way matching catch an expired surcharge? No. Three-way matching checks the invoice against the purchase order and the receipt for quantity, price as entered, and delivery. It does not evaluate whether a surcharge's stated expiration condition has passed, because that condition is not a field the match logic reads. ### Is a custom object in Sage Intacct enough to enforce a rate card? It can hold the data, but enforcement also requires a trigger rule and, critically, an ongoing process to update the object every time a contract renews or a rate changes. Without that maintenance commitment, the custom object drifts out of date and stops reflecting the real agreement. ### What is the difference between a rebate clause and a discount on an invoice? A discount reduces the price on the invoice line itself, and Sage Intacct can record it directly. A rebate is a credit owed based on cumulative spend over a period, calculated separately from any single invoice, which is why it is invisible to standard matching logic. --- 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