> For the complete documentation index, see [llms.txt](https://docs.nexusglobalpayments.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexusglobalpayments.org/messaging-and-translation/message-pacs.002-payment-status-report/pacs.002-differences-from-cpmi-cbpr+-guidelines.md).

# pacs.002 Differences from CPMI/CBPR+ Guidelines

The differences described in [pacs.008 Differences from CPMI Harmonisation Requirements](/messaging-and-translation/message-pacs.008-fi-to-fi-customer-credit-transfer/pacs.008-differences-from-cpmi-harmonisation-requirements.md) also apply when the same fields are used in `pacs.002.` In addition, for the **`pacs.002`** **confirmation message**, the Nexus message guidelines have the following differences from the CBPR+ guidelines:

* The Original Group Information (OrgnlGrpInf) is **optional** in Nexus in line with the CPMI recommendations, while this is mandatory in CBPR+.
* The Original End-to-End Identification (OrgnlEndToEndId) is **optional** in Nexus in line with the CPMI recommendations, while this is mandatory in CBPR+.
* The Status Reason Information is **mandatory** (in case the transaction status is `RJCT`) in Nexus in line with the CPMI recommendations, while this is optional in CBPR+.