Skip to main content
Mapping

Validation rules

Which plan you need. Setting up a supplier's own validation rules is Enterprise plan and up. Saving a new version of a profile and activating one are both refused below that plan; reading the versions you already have is not, so a workspace that downgrades can still see what its suppliers enforce. ProcuLink's built-in checks are separate and are on every plan, Pilot included — see below.

Validation rules are the checks you set for a supplier, on top of the built-in ones. They live on each supplier's Validation rules tab — open Partners, pick a supplier, then Validation rules. That is the only place a rule of your own is set.

What runs without any rules of your own

On every plan, and with no acceptance profile configured at all, ProcuLink checks every order it validates:

  • the order carries a PO number and a currency,
  • every line has a quantity greater than zero,
  • every line has a unit price that is not negative — a price of exactly zero is flagged as a warning ("confirm this is intentional") rather than treated as an error, because a genuinely free line has to be able to go out.

A second set runs immediately before an order is transformed, and holds it back rather than emitting a broken document: a line still flagged for review, a line whose supplier item code is unresolved, a missing buyer item code on the formats that make it mandatory (EDIFACT ORDERS and X12 850), a negative unit price, and a quantity of zero or less.

None of this needs setting up and none of it can be switched off. Everything below is what you add on top.

Setting up checks for a supplier

Rules are grouped into a versioned acceptance profile: you draft a new version, then activate it, which archives the previous one. Each rule specifies:

  • scope — the whole order, or every line,
  • field — e.g. currency or buyer name on the order; supplier/buyer item code, description, quantity, or unit price on lines,
  • operator — required, equals, not_equals, in (comma-separated list), contains, min, max, greater_than, less_than, max_length,
  • severity — error, warning, or info,
  • a block-on-fail flag carried with the rule and its results.

Each rule shows the standards references for its field (UBL, EDIFACT, X12, cXML), so you can point at the exact element when a supplier asks which one you mean.

Where results surface

Validating an order evaluates it against the supplier's active profile and records a pass/fail result for every rule (line rules produce one result per line, so you see exactly which line failed what). Re-validating replaces the previous results — the report always reflects the current state of the order.

Two places lean on these rules beyond the order screen:

  • Connection testing — a connection revision's test pack includes a standards check, and replay shows which validation results would flip between pass and fail under a draft revision before you publish (supplier connections).
  • Pinned orders — an order processed under a published connection revision validates against the profile bound to that revision, so publishing new rules never rewrites the verdict on historical orders.

Need help designing checks for a supplier? Email support@proculink.eu or start from supplier connections.