Suppliers and organizations

A buyer prepares a request under one legal entity and chooses a supplier associated with that entity. The supplier record keeps an active flag, code, contact and eligibility note. The organization record carries its own currency and time zone. Team membership links the authenticated user to the organization and role scope used when an action is checked.

The supplier belongs to a legal entity, and the team member belongs to an organization. Those references let App Administrator check eligibility and acting scope before a Buyer selects a counterparty. Currency and time zone live on the organization record.

• Prepare. Put the owner, supplier and operating entity on the record before review.
• Decide. Check the submitted scope and leave a decision with a reason when human approval is required.
• Verify. Compare the stored effect with the intended action before treating the work as complete.

Agree the legal entity for each buying team and who maintains supplier codes. Decide what makes a supplier eligible for a new request, and how inactive suppliers are handled on existing records. Membership scope should be reviewed before buyers or approvers act. A supplier contact is a record of who to reach; it is not proof of supplier acknowledgement.

Rehearse a Buyer assigned to one organization selecting a supplier from another. App Administrator should confirm the membership and supplier organization before the request is submitted. Review the active setting and eligibility note for the intended supplier.

Open an active supplier and verify its organization. Create a draft request under the same organization and assign the buyer. Review the membership record used for that buyer. Then inspect an approved commitment to see whether its counterparty and order reference match the supplier intended.

Have the Buyer identify the operating entity and supplier on the draft. Have App Administrator compare both with the membership record. An inactive or cross-organization supplier should be corrected before approval.

When a buyer moves between entities, App Administrator checks the active membership and role scope before the next request. The supplier remains tied to its organization, so the team can review an old request without silently changing its counterparty.

• Supplier directory — Active suppliers with their code, contact and organization.
• My team membership — The signed-in member’s organization, role scope and active setting.

Follow request to commitment, receipt and invoice match, and landed cost review for the related decisions.