[MUSIC PLAYING]
PRESENTER: Following the Bulk Payment Results File, or BPRF
for short, being downloaded from the myplace Provider Portal
and uploaded to SupportAbility, the Claims status
of each allocation included in the Direct Bulk Payment Request
is updated automatically.
The BPR then reflects which allocations were successful,
displaying these as "Accepted," and those that have encountered
an error are displayed as "Rejected"
along with the reason for these.
If the BPRF is not uploaded, the Claims status
can be updated manually, if this is required.
The initial processing status of any projected allocations
is "Pending Action," allowing for a corrective course
of action to be taken.
One available course of action is the ability
to retry the rejected claim.
Processing rejected claim for retry
makes the allocation available for inclusion again
in a subsequent BPR.
Once addressing the error outside of SupportAbility
by creating or obtaining a service booking in the portal,
for example, the allocation of waiting retry
is ready for inclusion in a new BPR.
Once included, it is added as a New Payment Request item
with a new Claim Reference.
In order to process a rejected claim,
the "View Financial Information" Staff
Account privilege is required in combination
with either the Edit Client Records Across ALL Services"
privilege or the "Team Leader for ALL Services" privilege.
This video steps through marking a Rejected Allocation
for Retry, processing a Rejected Allocation for Retry,
including an Allocation available for Retry
in a subsequent BPR, including an Allocation
available for Retry in a subsequent Direct Invoice
Batch, and viewing the Allocation Processing Status
Information in the Activity record.
There are two steps to processing a Rejected
Allocation for Retry.
The required Allocation must first
be marked for the intended rejected claim action.
This is to ensure that any required action can
be taken outside of SupportAbility
before the retry is processed.
In this example, this claim has failed due to no service
booking being in place.
A service booking will need to be created in the portal
before the Allocation is included again in the next BPR.
The Notes field can be used to track these and communicate
the Allocation status internally including
important information regarding any action required,
for example.
Once the retry has been processed,
the information entered into the Notes field populates
next to the Allocation in the subsequent BPR.
To mark a Rejected Allocation for Retry,
select the required Allocation noting
that the number of Allocations selected
is displayed at the bottom of the page for reference.
Navigate to the Bulk Actions menu and select Mark for Retry.
The processing status is updated to reflect these.
It is important to note that the Totals section of the BPR
will continue to show the value of this Allocation
as "Pending Action" until the required action is processed.
If you no longer wish to process this Allocation for retry,
the intended action may be removed up
until the retry has been processed.
Navigate to the Bulk Actions menu
and select Remove Action to do so
noting that this is now reverted to "Pending Action"
as it is awaiting processing.
To process Of Rejected Allocation for Retry,
once it has been marked as such, navigate to the Bulk Actions
menu again and this time select Process Action.
A modal appears asking for confirmation of this.
It is important to note that this change cannot be undone.
It is therefore only recommended to process this action
by selecting Confirm when you are ready for these Allocations
to be available for inclusion again in a subsequent BPR.
Once Confirm is selected, the allocation
is now in a state of retry.
When the allocation has been included in a subsequent BPR,
a link to this is displayed here for reference
as demonstrated shortly.
The Total section of the BPR now shows
the value of this rejected Allocation under Retry.
To filter the list of Allocations
to only those processed for retry,
select the relevant icon.
This filter can be cleared by selecting
the cross as required.
When generating of a BPR, an amber notification message
appears when any of the available Allocations
to include are in a state of Retry.
Selecting the Allocations link filters the list
to only show Allocations that are available for retry.
To clear the filter, select the cross icon
in order to view all of the available Allocations again.
When an Allocation available for retry is included,
the BPR rejection reason is displayed for reference
along with any internal notes that have been added.
In this case, a service booking was required, which has since
been created in the portal.
It is important to ensure that the required action has been
taken outside of SupportAbility before,
including this Allocation to avoid it resulting in an error
again.
If we are not ready to include this Allocation yet,
it may be omitted by deselection.
In the scenario where a large number of Allocations
are ready for inclusion, first select all of the Allocations
and then filter the list to locate the Allocation awaiting
retry.
Once located, this can be deselected
noting that only the selected Allocations will
be included when you choose to create the BPR.
When ready to retry the Allocation,
this can be selected for inclusion in the BPR also.
Once an Allocation awaiting retry is included in the BPR,
the previous BPR rejection reason and notes are no longer
displayed and the Allocation is added as a New Payment Request
item with a new Claim Reference in order to uniquely identify
these claim.
If we navigate to the BPR this originated from,
we can see a link to the latest BPR
the Allocation has been included in is available for reference.
The latest financial processing information
is also displayed in the Allocations
Report and the Activity Record which will be reviewed shortly.
If the party responsible for paying the invoice where
the supports delivered has changed
or if the error occurred due to these, by processing
the Allocation for retry, an invoice
can be generated for the correct data as required.
To do so, the Financial Plan Manager
in the client's NDIS Direct Funding record
must be updated and saved before the Allocation
available for retry is included in a subsequent BPR.
Updating the FPM in the client's Funding record
ensures that these Allocations are
available to include in a subsequent Direct Invoice Batch
given they now need to be invoiced to the client's Plan
Manager.
The FPM can just as easily be updated to the client
or the client's billing contact if the invoice is needed
to be issued to them directly.
For those with the required View Financial Information
privilege, the Activity record contains information
regarding the current financial processing
status of each Allocation.
The NDIS Support Allocations window
contains information regarding the latest BPR
status and the latest invoicing status.
The Client section of the Activity record
has a Finance column which includes a link to the latest
finance records.