> For the complete documentation index, see [llms.txt](https://apis.rightrev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apis.rightrev.com/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/invoice-ingestion-via-json-file.md).

# Invoice Ingestion via JSON file

This API is to upload and collect Invoice data in JSON file format

Method - POST

API End Point

```
/apis/oingest/v1/invoices
```

**Sample API End Point ( Invoices )** 

<figure><img src="https://3364757261-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F193S0RVwbPrcp6u9CoPJ%2Fuploads%2Ffw9Y68h9Bdmh6shrSJlZ%2Fimage.png?alt=media&amp;token=8a57c6f3-bff6-4c3f-8649-9d381f84040c" alt=""><figcaption></figcaption></figure>

**Payload**

```
"[
  {
    ""source_system"": ""Salesforce"",
    ""transaction_type"": ""Invoice"",
    ""bill_number"": ""BN_001"",
    ""bill_date"": ""2021-01-01"",
    ""bill_financial_id"": ""BFID_001"",
    ""bill_qty"": 5,
    ""bill_amount"": 30000,
    ""revenue_start_date"": ""01/01/2021"",
    ""revenue_end_date"": ""12/31/2021"",
    ""transaction_currency"": ""USD"",
    ""functional_currency"": ""USD"",
    ""global_currency"": ""USD"",
    ""functional_exchange_rate"": 1,
    ""global_exchange_rate"": 1,
    ""reference_financial_id"": ""OFID-001""
  },"	

```

**Response**

```
{
    "file_id": "9d0924c1-45c7-4488-bec5-d71495f4be93",
    "message": "File successfully uploaded"
}
```

**Description of the fields**

<table><thead><tr><th width="184">Fields</th><th width="484">Description</th><th width="128">Example</th><th width="122">Required</th></tr></thead><tbody><tr><td>source_system</td><td>The system or application from which the invoice transaction originated.</td><td>Salesforce</td><td>TRUE</td></tr><tr><td>transaction_type</td><td>The category or nature of the transaction - Invoice</td><td>Invoice</td><td>TRUE</td></tr><tr><td>bill_number</td><td>The invoice or bill identifier assigned by the source system</td><td>BN_001</td><td>TRUE</td></tr><tr><td>bill_date</td><td> The date on which the invoice was issued.</td><td>01/01/2021</td><td>TRUE</td></tr><tr><td>bill_financial_id</td><td> The unique identifier assigned to the invoice.</td><td>BFID_001</td><td>TRUE</td></tr><tr><td>bill_qty</td><td>The quantity of goods or services invoiced.</td><td>5</td><td>TRUE</td></tr><tr><td>bill_amount</td><td>The total monetary amount billed on the invoice.</td><td>30000</td><td>TRUE</td></tr><tr><td>revenue_start_date</td><td>The date when revenue recognition begins for the invoice.</td><td>01/01/2021</td><td>TRUE</td></tr><tr><td>revenue_end_date</td><td>The date when revenue recognition ends for the invoice.</td><td>12/31/2021</td><td>TRUE</td></tr><tr><td>transaction_currency</td><td>The currency in which the transaction was originally recorded.</td><td>USD</td><td>TRUE</td></tr><tr><td>functional_currency</td><td>The reporting currency of the company or business unit.</td><td>USD</td><td>TRUE</td></tr><tr><td>global_currency</td><td> The standardized currency used for consolidated global reporting.</td><td>USD</td><td>TRUE</td></tr><tr><td>functional_exchange_rate</td><td>The exchange rate used to convert transaction currency to functional currency.</td><td>1</td><td>TRUE</td></tr><tr><td>global_exchange_rate</td><td>The exchange rate used to convert transaction currency to global currency.</td><td>1</td><td>TRUE</td></tr><tr><td>reference_financial_id</td><td>A linked Order Financial ID of the Invoice</td><td>ODIF_001</td><td>TRUE</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://apis.rightrev.com/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/invoice-ingestion-via-json-file.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.