Skip to main content
← Web Service Payloads & REST API Examples

REST · Financials — Receivables

What is the REST API payload to create a Receivables (AR) invoice in Oracle Fusion?

POST /receivablesInvoices — REST payload to create an AR invoice

REST APIOracle Fusion · Financials · ARMedium confidenceCurated

The Receivables Invoices REST resource creates a customer transaction (invoice) plus its lines. Set BusinessUnit, TransactionSource, TransactionType ('Invoice'), TransactionDate/AccountingDate, BillToCustomerNumber and currency; add a receivablesInvoiceLines child array with line description, quantity and unit price. Distinct from bulk AutoInvoice / FBDI.

Endpoint

POSThttps://<your-fusion-host>/fscmRestApi/resources/11.13.18.05/receivablesInvoices

Purpose

Create a single standard Receivables invoice in real time. HTTP POST, Content-Type application/json. The response returns CustomerTransactionId and TransactionNumber. Confirm the child resource name (receivablesInvoiceLines) and attribute names against the REST API reference for your release.

Parameters

BusinessUnitrequiredName of the invoicing business unit.
TransactionSourcerequiredReceivables transaction (batch) source name — must allow manual/API entry.
TransactionTyperequiredA transaction type of class Invoice, e.g. 'Invoice'.
TransactionDaterequiredTransaction date (YYYY-MM-DD).
AccountingDaterequiredGL date — must be in an open AR period.
BillToCustomerNumberrequiredAccount number of the bill-to customer.
TransactionCurrencyCoderequiredCurrency code, e.g. USD.
receivablesInvoiceLinesrequiredChild array — one object per line with LineNumber, Description, TransactionLineQuantity, UnitSellingPrice.

Example request

Request
{
  "BusinessUnit": "US1 Business Unit",
  "TransactionSource": "MANUAL-OTHER",
  "TransactionType": "Invoice",
  "TransactionDate": "2026-08-24",
  "AccountingDate": "2026-08-24",
  "TransactionNumber": "AR-2026-0501",
  "BillToCustomerNumber": "1006",
  "BillToSite": "1006-BILL",
  "TransactionCurrencyCode": "USD",
  "receivablesInvoiceLines": [
    {
      "LineNumber": 1,
      "TransactionLineType": "LINE",
      "Description": "Consulting services - August 2026",
      "TransactionLineQuantity": 10,
      "UnitSellingPrice": 150,
      "TaxClassificationCode": "VAT20"
    }
  ]
}

Example response

Response
{
  "CustomerTransactionId": 300000135792468,
  "TransactionNumber": "AR-2026-0501",
  "TransactionType": "Invoice",
  "BillToCustomerNumber": "1006",
  "TransactionCurrencyCode": "USD",
  "Status": "Incomplete",
  "links": [
    { "rel": "self", "href": ".../receivablesInvoices/300000135792468" },
    { "rel": "child", "name": "receivablesInvoiceLines", "href": ".../receivablesInvoices/300000135792468/child/receivablesInvoiceLines" }
  ]
}

Call lifecycle

  1. 01

    Basic auth or OAuth 2.0 bearer token.

    • User needs the Billing Specialist / create-transaction privilege
  2. 02
  3. 03
  4. 04

Related questions

GroundingCurated

Retrieved from the curated Oracle knowledge layer — table metadata, joins and process flows.

Need a variation, or a different service?

Continue in Ask Oracle AI