How-toOracle Fusion Cloud Payables and ProcurementPayables / Supplier Model

One-Time Supplier in Oracle Fusion

Question
one time supplier in oracle fusion

Also searched as

  • oracle fusion one-time payment supplier
  • how to pay a one time vendor in fusion
  • fusion payables one time supplier setup
  • oracle fusion supplier creation api

Short answer

A one-time supplier in Oracle Fusion is a generic supplier record used to pay a payee you will not transact with again, so you do not clutter the supplier master. Payee name and bank details are captured on the invoice rather than on a permanent supplier profile, which makes controls on who can use it essential.

Applies to: Oracle Fusion Cloud Payables and Supplier Model, releases with one-time payment support; exact option names vary by quarterly update

How to set up and use a one-time supplier

  1. 1Decide with finance and audit whether one-time payments are allowed at all, and for which spend categories, thresholds and business units.
  2. 2Open Navigator > Procurement > Suppliers > Manage Suppliers and create a supplier flagged for one-time use. In current releases the supplier type or one-time option on the create dialog drives this; confirm the label in your release.
  3. 3Give it a clear name such as ONE-TIME SUPPLIER and assign it to the business units and a site that carries payment terms and the payment method you want.
  4. 4Restrict who can pick it. Use the Payables invoice entry roles and data security so only AP specialists, not requesters, can use the record.
  5. 5On the invoice, enter the payee details in the one-time payment area: name, address and bank account or other payment details for that single payment.
  6. 6Validate and approve the invoice as usual, then pay through a payment process request with the payment method configured for one-time payees.
  7. 7Report on one-time payments monthly and review them against policy, since they bypass supplier onboarding checks.

Why not just create a normal supplier

Supplier onboarding in Fusion Procurement includes registration, qualification, tax and bank validation and an approval flow. Doing that for a one-off refund to a customer, a jury duty reimbursement or a single permit fee is disproportionate and fills the master with dead records that nobody maintains.

The trade-off is control. A one-time supplier has no history, no duplicate check against an established profile and no onboarding approval, so it is a common route for fraud and for duplicate payments. Treat it as an exception path, not a convenience.

Supplier creation through the API

If you automate supplier setup, Fusion exposes a suppliers REST resource under /fscmRestApi/resources/<version>/suppliers, with child resources for addresses, sites and contacts. A POST there creates a normal supplier. For one-time payees it is usually better to keep a single generic supplier and pass payee details at invoice level than to create a supplier per payment.

Confirm attribute names with the describe endpoint for your release before you build against them. Supplier creation through the API also needs the right procurement role, because the supplier model has its own security and approval settings.

GET https://<pod>.fa.<region>.oraclecloud.com/fscmRestApi/resources/<version>/suppliers/describe

Controls to put in place

Limit the number of one-time suppliers to one per business unit or legal entity, cap invoice amounts through approval rules, and require a documented reason. Add a Payables report or an OTBI analysis on invoices where the supplier is the one-time record, and review it each close.

Watch for splitting: several small one-time payments to the same payee, entered separately to stay under an approval threshold, is exactly the pattern internal audit will look for.

Try it here, free

Oracle Fusion Suppliers Table Report SQL Template

Open full tool

Fill in a few fields to generate a BI Publisher SQL query that reports Oracle Fusion suppliers and their sites, with notes on supplier import templates.

Common pitfalls

  • !Letting requesters or buyers use the one-time supplier on purchase orders, where it removes the supplier controls the PO process relies on.
  • !No approval threshold on one-time invoices, which makes them an easy payment route.
  • !Creating one supplier per one-off payee anyway, which defeats the purpose and pollutes the master.
  • !Bank details typed on the invoice without a second review, causing misdirected payments.
  • !Ignoring tax reporting. Payments to individuals can still need 1099 or equivalent reporting, so confirm with your tax team.

How an ERP-grounded AI assistant handles this

A grounded assistant can query paid invoices against the one-time supplier, group them by payee name and amount, and flag likely splits or repeat payees that should become real suppliers. Run privately against your own Fusion reporting data, it gives AP a review queue without exporting payment details.

See ERPray

Frequently asked questions

What is a one-time supplier in Oracle Fusion?

It is a generic supplier record used for payees you pay once. The payee's name and payment details are entered on the invoice instead of building a permanent supplier profile with sites, contacts and bank accounts.

Can I use a one-time supplier on a purchase order?

It is technically a supplier like any other, but it is bad practice on purchase orders. Procurement controls such as qualification and sourcing assume a managed supplier. Use it only for Payables invoices where policy allows.

How do I stop misuse?

Restrict the roles that can select it, put approval thresholds on its invoices, and review a periodic report of every payment made to it, looking for repeat payees and split amounts.

Can I create suppliers through the REST API?

Yes, Fusion provides a suppliers resource with child resources for addresses, sites and contacts. Check the describe output for your release, and note that normal supplier creation can trigger the same onboarding and approval rules as the UI.

Related

Error fix

Oracle Fusion Payables: invoice on hold or stuck at Needs Revalidation

An invoice in Fusion Payables is either Validated, Needs Revalidation, or Never Validated. Holds are placed by validation when a check fails, so the fix is to read the hold name on the Holds tab, correct the underlying data (match, price, tolerance, account, tax), and run Validate again. Manual release is possible but only for hold types your role may release.

How-to

Oracle Fusion Procurement: approved requisition not creating a purchase order

An approved requisition becomes a purchase order only if its lines are processable: a supplier and site can be sourced, a buyer is assigned or derived, the procurement business unit is configured as a service provider for the requisitioning unit, and the Process Requisitions job picks the lines up. Check line status and the job log in that order.

Error fix

Fix The Oracle Fusion "You Don't Have Access To This Data" Error

This generic Oracle Fusion security message means the function privilege and the data security scope did not both line up for that user on that record - most often the job role is assigned but the matching data role, security profile, or business unit and ledger context in Manage Data Access for Users is missing. Fix it by checking data access setup for the user's role, not by re-granting the same job role again.

How-to

Project Creation API in Oracle Fusion

Oracle Fusion Cloud creates projects through the Project Management REST API: a POST to the projects resource under /fscmRestApi/resources/ with a JSON body naming the project, number, organization, legal entity, project unit and usually a source template. Tasks, team members and classifications are then added through child resources of the new project.

Error fix

Fix FBDI Import Failures From Interface Table Validation Errors

When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.

Error fix

Clear An Oracle Fusion ESS Job Stuck In Blocked Status

A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.

AI for ERP

AI for Oracle Fusion Cloud Procurement: Requisitions, POs and Suppliers

Private AI for Oracle Fusion Cloud Procurement: requisitions, purchase orders, supplier performance and invoice match exceptions, answered with REST and BICC data.

AI for ERP

Fusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM

How Fusion Cloud ERP AI supports GenAI implementation: OCI Generative AI Service for Fusion-only use cases, a private LLM for sensitive or cross-system data.

Stuck on Oracle Fusion Cloud Payables and Procurement?

Talk to engineers who work inside Oracle Fusion Cloud Payables and Procurement every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Integrations

Comparisons

Software

TermsOracle EBS Concurrent Program