---
title: "Approving beneficiary requests - NexPay"
description: "When someone submits their details, a reviewer checks and approves them. Here's what to look at, how to approve or reject, and what the requester sees."
lastModified: "2026-06-02"
lang: "en"
url: https://nexpay.com.au/training/recipients/approving-beneficiary-requests
---
## Site navigation

- For businesses
  - [For ed. agents](/for-education-agents.md)
  - [For schools & colleges](/for-schools.md)
  - [For universities](/for-universities.md)
  - [For accommodation](/for-accommodation.md)
  - [Why NexPay?](/about.md)
  - [Pricing](/pricing.md)
  - [AI automation](/payments-ai-automation.md)
- [For students & parents](/for-students-and-parents.md)
- Help & resources
  - [Training](/training.md)
  - [Blog](/blog.md)
  - [Events](/events.md)
  - [Zapier integration](/zapier.md)
  - [Claude & ChatGPT](/mcp.md) — Claude & ChatGPT integration
- [Contact](/contact-us.md)
- [Login](https://portal.nexpay.com.au/login)

# Approving beneficiary requests - NexPay

## At a glance

- **Intended for:** Managers & reviewers
- **Reading time:** 4 minutes
- **Last updated:** 1st June 2026

**TL;DR:** Submitted beneficiary requests land in the Requests view for review. Open one to see the recipient's details, bank information, any documents, and job details. If everything checks out, Approve — the recipient becomes ready to receive funds. If something's wrong, Reject with a reason (and optionally notify the applicant by email). Reviewing is a manager-level task.

{/* Body content for approving beneficiary requests */}

## The check that protects every payment

When you ask someone to submit their own bank details, there's a deliberate gate before those details can be used: a review. A person checks what was submitted and decides whether it's good to go. It's a small step that prevents a much bigger problem — money sent on details that were never verified.

This article is for whoever does that reviewing. It covers what to look at, how to approve or reject, and what the applicant experiences.

> **For managers:** Reviewing requests is part of keeping your recipient list trustworthy. A careful approval now saves a failed or misdirected payment later.

## Finding requests to review

Submitted requests appear in the **Requests** view within the Recipients area, each showing its status. Open one to see the full picture the applicant provided. A request that's been completed and is waiting on you is the one to act on.

## What to review

Opening a request shows you everything the applicant entered, grouped for easy scanning:

- **Their details** — type (individual or business), contact information, date of birth, tax ID, and address
- **Bank information** — account number, and the country-specific fields (IBAN, SWIFT, BSB, sort code, ABA, transit and institution numbers, branch), plus the bank's address
- **Documents** — any files they attached, which you can download and check
- **Job details** — occupation and place of employment, if you requested them
- **Any prior rejections** — a history of what was flagged before, with reasons and dates

Your job is to make sure it all hangs together: the bank details are complete and consistent for the destination country, the documents match, and nothing looks off.

> **Quick tip:** If a single detail is unclear, it's better to reject with a specific reason than to approve and hope. A clear "the account number and IBAN don't match — please re-check" gets you correct details faster than a payment that fails later.

## Approving

If everything checks out, choose **Approve**. The recipient becomes ready to receive funds and joins your list like any other approved beneficiary. From there, anyone can include them in a payment.

## Rejecting

If something's wrong, choose **Reject**. You'll enter a **reason** — this is required, so the rejection is on record and the applicant knows what to address. You can also tick to **send the applicant an email notification**, so they're told directly and can correct and resubmit.

Because requests keep a rejection history, a resubmitted request shows you what was previously flagged — making it quick to confirm the issue was actually fixed.

> **Important:** A clear rejection reason is a kindness, not a formality. The applicant can only fix what they understand, so a specific, plain-language reason turns a rejection into a quick correction rather than a frustrating loop.

## Who can review

Reviewing and approving is a manager-level capability. If you open a request and don't see the approve and reject options, your account likely doesn't have review permission yet. That's an access setting — ask your admin, or whoever manages your organisation's NexPay access. See [roles and what you can see](/training/getting-started/roles-and-what-you-can-see.md).

## Your next step

- **Need to send a request first?** See [requesting beneficiary details](/training/recipients/requesting-beneficiary-details.md).
- **Approved a recipient?** They're ready in [managing beneficiaries](/training/recipients/managing-beneficiaries.md).
- **Ready to pay them?** Go to [creating a payment](/training/payments/creating-a-payment.md).
- **Don't have review access?** Read [roles and what you can see](/training/getting-started/roles-and-what-you-can-see.md).

## Checkpoint

After reading this, you should be able to:

- Find submitted requests in the Requests view
- Review a recipient's details, bank information, documents, and job details
- Approve a request so the recipient can receive funds
- Reject a request with a clear, required reason and optionally notify the applicant
- Recognise that reviewing is a manager-level permission

## Frequently asked questions

### Where do I find requests waiting for review?

In the Recipients area, open the Requests view. Submitted requests appear there with their status. Open one to review the full details the applicant provided.

### What should I check before approving?

Look over the recipient's identity and bank details, any uploaded documents, and the job details if you asked for them. Make sure the bank information looks complete and consistent for the destination country. If anything is unclear or doesn't add up, it's better to reject with a clear reason than to approve and risk a failed payment.

### How do I reject a request?

Choose Reject and enter a reason — this is required, so there's a record of why. You can also tick to send the applicant an email notification so they know what to fix. They can then correct and resubmit.

### What happens when I approve?

The recipient becomes ready to receive funds and joins your recipient list like any other approved beneficiary. From that point you can include them in payments.

### Who can review and approve requests?

Reviewing is a manager-level capability. If you don't see approve and reject options on a request, your account may not have review permission — ask your admin, or whoever manages your organisation's NexPay access.

### Can I see why a request was rejected before?

Yes. A request keeps a history of rejections with their reasons and dates, so if something comes back around, you can see what was flagged previously and whether it's been addressed.

## More on NexPay

**Platform**

- [For students & parents](/for-students-and-parents.md)
- [For ed. agents](/for-education-agents.md)
- [For universities](/for-universities.md)
- [For schools](/for-schools.md)
- [For accommodation](/for-accommodation.md)
- [AI automation](/payments-ai-automation.md)
- [Pricing](/pricing.md)

**Help & resources**

- [Training](/training.md)
- [Contact](/contact-us.md)
- [Developers](/api.md)
- [Zapier integration](/zapier.md)
- [Claude & ChatGPT](/mcp.md) — Claude & ChatGPT integration

**Company**

- [About](/about.md) — About NexPay
- [Jobs](/about.md#jobs)
- [Blog](/blog.md)
- [Media](/media.md)
- [Events](/events.md)

**Trust & locations**

- [Trust & Regulatory](/trust.md)
- [Our offices](/locations.md)

**Legal**

- [Terms and Conditions](/terms-and-conditions/)
- [Privacy policy](/privacy-policy/)
- [Cookie Policy](/cookie-policy/)
- [Complaints Policy](/complaints-policy/)
- [Financial Services Guide](/financial-services-guide/)
- [Product Disclosure Statement](/product-disclosure-statement/)
- [AML Policy](/aml-policy/)
- [Target Market Determination](/target-market-determination/)
- [Group Regulatory Disclosure](/group-regulatory-disclosure/)
- [Fees & FX Schedule](/fees-and-fx/)
- [Developer & API Terms](/developer-terms/)

## NexPay

NexPay Pty Ltd (ABN 56 153 910 984) holds Australian Financial Services Licence No. 560782 and is authorised to provide non-cash payment services to retail and wholesale clients in Australia.

- **Address:** Level 12, 64 York St, Sydney NSW 2000, Australia
- **Support:** [support@nexpay.com.au](mailto:support@nexpay.com.au)
- **Status:** [https://nexpay1.statuspage.io/](https://nexpay1.statuspage.io/)

**Follow NexPay**

- [LinkedIn](https://au.linkedin.com/company/nexpay)
- [Instagram](https://www.instagram.com/nexpayau/)
- [Facebook](https://www.facebook.com/NexPayAU)

© NexPay Pty Ltd