> For the complete documentation index, see [llms.txt](https://kb.maica.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.maica.com.au/general-information/client-management-settings/claim-management/reconciling-bulk-payment-request-bpr-file.md).

# Reconciling Bulk Payment Request (BPR) File

In the previous section, we explained how to generate and download the Bulk Payment **Request** (BPR) file.  This article explains the next two steps in the process:

1. Importing the Bulk Payment Request **Results** File
2. Importing the Bulk Payment Request **Remittance** File

## Bulk Payment Request Result File 

Once the BPR file is downloaded from Maica and uploaded to the **myplace provider portal** for processing, PRODA will provide a corresponding **Results** file, containing important status detail for all the `Payments Request` records (rows) in your BPR File.  From our experience, it generally takes will take approximately 20 to 30 minutes for the Bulk Payment **Results** File to be made available from the portal to be downloaded. 

The **Results** file contains the `Status` returned by PRODA for each `Payment Request`, or row, uploaded in the initial BPR File.  The following two `Status` values are contained within the BPR Results File (in the `Payment Request Status` column):

* `SUCCESSFUL`
* `ERROR`

A `Rejection Reason` is provided for those records that resulted in an `ERROR`. Lastly, the BPR Results File contains the `Paid Total Amount` and whether the Agency has applied a `Capped Price` to this.

### Importing the Results file via Maica

Once you have downloaded the Bulk Payment Request **Results** File, the next step is to import this file back into Salesforce to update each of the `Payment Request` records that was included in the initial `Request` file.  The import will align the `Status` of each of these Payment Request records with the PRODA Status contained in the Results file.

The good news is that Maica handles all of this for you!  All you need to do is click on the App Launcher in Salesforce and search for **Data Import:**

<figure><img src="/files/plvU7XOoN2gGcdkIFO6c" alt=""><figcaption><p>Data Import Tab</p></figcaption></figure>

Using the Upload Files feature, select the file results file to be imported into Salesforce, then click on the **Flow Setting** dropdown and select **NDIS Bulk Payment Request Results File.  You can see an example of this below.**

<figure><img src="/files/KfTb2ZvluPI8b2IlmAdg" alt=""><figcaption><p>Data Import Flow to process the NDIS Bulk Payment Request Results File</p></figcaption></figure>

Lastly, click the **Import** button to process each row contained within the **Results** file, updating the corresponding `Payment Request` record matching on the unique `Claim Reference Index` (`maica__Claim_Reference_Index__c`) generated. &#x20;

{% hint style="info" %}
`Claim Reference Index` is a copy of the `Claim Reference` (Formula) field used to optimise the Import Flow for high data volume processing as it is indexed by Salesforce.
{% endhint %}

<figure><img src="/files/o9HmONa7KqFSp3iUgEdP" alt=""><figcaption><p>Bulk Payment Request Results File - Import File Processing</p></figcaption></figure>

### BPR Results File - Field Mapping

For each `Payment Request` record in Salesforce, the **Results** import will update the `Status` as per the following:

<table><thead><tr><th width="221">Results File Column</th><th>SF Payment Request Field</th><th>Mapping Notes</th></tr></thead><tbody><tr><td><code>Claim Reference</code></td><td><code>Claim Reference Index</code></td><td>Used to retrieve the Payment Request record.  No update</td></tr><tr><td><code>Payment Request Status</code></td><td><code>Status</code></td><td>IF <code>SUCCESSFUL</code> = <code>Pending Payment</code><br><br>IF <code>ERROR</code> = <code>Rejected</code></td></tr><tr><td><code>Error Message</code></td><td><code>Error Details</code></td><td>Mapped to this field as the <code>Reject Reason</code> picklist is used for API error.</td></tr></tbody></table>

{% hint style="info" %}
All other columns in the BPR Results file are **skipped** as part of the Salesforce import
{% endhint %}

#### Pending Payment Status&#x20;

The image below provides an example of the `SUCCESSFUL` scenario, where the `Payment Request` `Status` is updated.

<figure><img src="/files/TVCG8X7JQ9Yyhm254OhP" alt=""><figcaption><p>Example of a Successful Payment Request</p></figcaption></figure>

#### Rejected Status

The image below provides an example of the `ERROR` scenario, where both the `Payment Request` `Status` and `Error Details` is updated.

<figure><img src="/files/gkHtpXH5NS8HmnqSw7n2" alt=""><figcaption><p>Example of a Rejected Payment Request</p></figcaption></figure>

## Bulk Payment Request Remittance File&#x20;

The final step in the Bulk Payment Request Claiming process is to upload the **Remittance** file when this is received from the NDIA.

This process replicates the steps described for the **Results** file (see :point\_up:), however, in this scenario, you need to upload the received **Remittance** file and select **NDIS Remittance Advice Import** Flow Setting.

<figure><img src="/files/T0Nn9XQDcAF0ZIa7dSiV" alt=""><figcaption><p>Bulk Payment Request Remittance File - Import File Processing</p></figcaption></figure>

The Total Amount of the `Payment Request` paid by the NDIA and the date the funds were physically paid to your organisation's nominated account will be updated on `Paid Amount` and `Paid Date` respectively.&#x20;

### BPR Remittance File - Field Mapping

The **Remittance** file and how the `Payment Request` records are updated in Salesforce is a little different to the **Results** file, in that only those `Payment Request` records with a `Status` of `Pending Payment` are updated.

Essentially, this means that the Remittance file only contains the details of **successful** `Payment Request` records.

{% hint style="info" %}
Any `Payment Request` records updated to the `Rejected`Status by the **Results** file import **will not** be updated by the **Remittance** import.
{% endhint %}

For each `Payment Request` record in Salesforce, the **Remittance** import will update the following:

| Remittance File Column | Payment Request Field   | Payment Request Field                                   |
| ---------------------- | ----------------------- | ------------------------------------------------------- |
| `ProvClaimRef`         | `Claim Reference Index` | Used to retrieve the Payment Request record.  No update |
| `AmountPaid`           | `Paid Amount`           |                                                         |
| No column mapping      | `Status`                | `Paid`                                                  |
| No column mapping      | `Paid Date`             | Set to `TODAY`                                          |

The image below provides an example of a `Payment Request` updated by the **Remittance** import.

<figure><img src="/files/P06pav4I3iQ3lG2HifjI" alt=""><figcaption><p>Payment Request set to Paid via the Remittance Import process</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.maica.com.au/general-information/client-management-settings/claim-management/reconciling-bulk-payment-request-bpr-file.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.