Integration-specific validation
Integration-specific validation hooks are configured for each customer's ERP integration. The exact checks you see depend on the integration your environment uses.
The system rules described in Validation Rules run on every Mod AI entity. On top of those, certain integrations include extra validation checks specific to that ERP. These are called validation hooks.
If you are on a custom integration and you see validation errors that are not covered in the system rules reference, those errors come from your integration's hooks.
Integrations with custom hooks
Hooks are deployed alongside the integration. If your entity uses one of the following integrations, custom validation may apply:
- NetSuite (specific configurations).
- SAP (specific configurations).
- Blackbaud Financial Edge NXT.
- Custom integrations built for individual customers.
The default integration (no custom hooks) runs only the system rules.
What hooks check
Hooks check things that are specific to a particular ERP or customer setup. Common patterns:
- ERP-specific field validation. The integration knows that certain fields in your ERP have specific format requirements (for example, project codes that must match a particular pattern), and the hook enforces that on incoming invoices.
- Extra duplicate logic. Some integrations add detection patterns beyond the system duplicate rule.
- Pre-export readiness. Before pushing the invoice to the ERP, a hook verifies the invoice has every field the ERP requires for posting. Missing fields surface as errors.
- Price drift detection. The platform compares each invoice line's unit price against the last approved invoice for the same vendor and item and surfaces a price change detected notice when prices deviate significantly.
How to know if your integration has hooks
Two ways to check.
When a hook fires on a sample invoice, its result surfaces as a notice (or in the Validation Failed panel if it blocks). If you see a notice you do not recognize from the Validation Rules reference, it is likely coming from a hook.
You can also ask your Mod AI contact. Hook deployments are tracked internally and your account team knows what is configured for your entity.
Hooks are not user-configurable
Unlike system rules, hooks cannot be configured from the UI. Their behavior is set in code by Mod AI engineers when the integration is built or updated. If a hook's behavior is wrong for your needs, raise it with your account team.
Hooks and rule severity
Severity overrides (requested via your Mod AI implementation manager) only apply to system rules. Hooks ship with their own severity baked in.
If a hook is producing too many false positives at error severity, that is a request to make to Mod AI directly, not a configuration change you can do yourself.