These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Cross-border Trade SCM
- Features
- Organization and access
Organization and access
Give each purchase and declaration a clear organizational owner.
OverviewDue purchase requests×
Cross-border Trade SCM · Organization and access
New
Due purchase requests
Purchase requests
| Record number | Subject | Required by | Status | Owner | Counterparty | |
|---|---|---|---|---|---|---|
| PR-93323 | Draft pr-480 | 04 Oct | Draft | SPP-8399 | ||
| PR-70373 | Submitted pr-390 | 07 Oct | Submitted | SPP-2778 | ||
| PR-34140 | Approved pr-170 | 05 Oct | Approved | SPP-7024 | ||
| PR-96635 | Ordered pr-870 | 14 Oct | Ordered | SPP-7457 | ||
| PR-93146 | Received pr-304 | 03 Oct | Received | SPP-5098 |
6 of 6 records
Draft pr-480Purchase requests · PR-93323
DraftRequired by04 Oct
CounterpartySPP-8399
What you can do
Set the organization
Organization records identify trading entities by name, code, time zone and currency. Suppliers and team members belong to an organization; a purchase request and customs declaration also carry an organization reference. A team member connects to a platform user identity and carries a role name. These links give the Admin a starting point for checking who should work on each case.
How the work is organized
- Trading entity. Keep organization code, time zone, currency and active state with each business unit.
- Membership. Link each active team member to a platform user and the organization that owns their work.
- Counterparty boundary. Compare supplier, purchase and declaration organizations before assigning access or reviewing a case.
Agree the organization code and currency before importing active suppliers and members. The purchase request records its amount in USD, even when the organization’s currency is different. The Admin should decide how that difference will be handled in downstream finance work; the record should not be read as a converted ledger entry.
What to agree during setup
Choose who maintains organization and team member records, including active flags and user links. Decide how the Buyer is assigned to a purchase within the same organization as its supplier. Rehearse access with another organization so the Admin can find a mismatched supplier or declaration link before the operating cycle expands.
Check the handoff on an actual case
Set up a pilot organization and active team member, then add an active supplier in that organization. Assign the Buyer as owner of a purchase request and link a declaration to the same organization. The Trade Operations Lead checks the chain before inviting more users into the operating cycle.
Have the Admin open the pilot Buyer’s team membership, platform user and organization, then trace the request to its supplier and declaration. A second participant should test the same case from a different organization. Record which references require correction before anyone uses the case for review or filing.
During the pilot, use a second user to confirm that identity and team membership point to the intended organization. Check a supplier from a different organization as an exception case before inviting the wider team.
What your team sees
- My purchase requests — Owner-linked purchases for the current team member.
- Active suppliers — Counterparties linked to the operating organization.
Follow the work through
See the first handoff and the next decision for a case-level rehearsal.
What it keeps track of
Data model- Organizations
- Trading organizations that own cross-border purchase and customs operations.
- Team members
- Authenticated platform identities with organization membership and role scope.
- Users
- Users
- Suppliers
- Eligible active suppliers in the same organization.
- Purchase requests
- Cross-border purchase demand with lifecycle, owner, counterparty and revision.
- Customs declarations
- Customs declarations supporting record verified customs release.
Who uses it
Permissions- Admin
- Maintains identity and organization records.
- Buyer
- Owns demand.
- Trade Operations Lead
- Reviews the cross-record chain.
Set up Cross-border Trade SCM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.