Supplier for one PO

Hi ​@Josef ,

This is a common scenario  — but using a single “dummy supplier” that you keep changing is not recommended in IFS Cloud / IFS Apps.

 Why a “dummy supplier” is risky

Using one supplier and modifying it each time can cause:

• ❌ Loss of historical accuracy (who you actually bought from)
• ❌ Incorrect audit / compliance data
• ❌ Issues with:
  • Accounting
  • Tax / VAT
  • Supplier statistics
• ❌ Confusion in reporting

 In short: it breaks traceability

 Recommended Approaches

 Option 1: Use a Generic “Misc Supplier” (Controlled way)

You can create one supplier like:

• MISC_SUPPLIER / ONE_TIME_SUPPLIER

 But:

• Do NOT overwrite master data each time
• Instead:
  • Use:
    • Address fields
    • Reference fields
    • Notes

To store:

• Actual supplier name
• Contact details
• Invoice reference

 Option 2: Minimal Supplier Creation (Best Practice)

Instead of full master data:

• Create supplier with:
  • Minimal required fields only
• No need to fully configure everything

 This keeps:

• Data clean
• Audit correct

 Option 3: Supplier Request / Approval Process

• Allow quick creation of:
  • Temporary suppliers
• With:
  • Approval workflow

 Keeps control + avoids duplication

🔹 Option 4: Reuse Supplier with Multiple Addresses

If applicable:

• One supplier → multiple addresses
• Use address to differentiate

 But only if:

• Same legal entity

 About “One-Off Supplier”

You mentioned it’s not suitable — that’s fine, but:

 That feature is actually designed for:

• Exactly this use case

If it doesn’t fit, usually it’s because:

• Process/config needs adjustment

 Best Practice Recommendation

✔️ Avoid changing supplier master repeatedly
✔️ Either:

• Use controlled “misc supplier”
• Or create minimal new suppliers