Mudança de Mindset

PIX Payments
SAP PIX payments solution for FI

SAP GS FIN
September, 2022
PUBLIC
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related document, or to develop or release any functionality
mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be
changed by SAP at any time for any reason without notice. The information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality.
This presentation is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or
non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation,
except if such damages were caused by SAP’s intentional or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue
reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Agenda
• PIX Overview
• Accounts Payable
– Bank Master Data – onPrem
– Bank Master Data - SAP S/4HANA OP 2021
– Bank Master Data – SAP S/4HANA Cloud
– Define Payment System and Alias Types SAP S/4HANA OP 2021
– Define Payment System and Alias Types SAP S/4HANA Cloud
– Supplier Master Data up to SAP S/4HANA OP 2021
– Supplier Master Data SAP S/4HANA Cloud
– Post Supplier Invoice up to SAP S/4HANA OP 2021
– Post Supplier Invoice to SAP S/4HANA Cloud
– Payment method for Outgoing Payments
– CNAB240 Return Files Processing
• Accounts Receivable
– House Bank Master Data onPrem
– House Bank Master Data SAP S/4HANA Cloud
– Set up Correspondence up to SAP S/4HANA OP 2021
– Set up Correspondence SAP SHANA OP 2021
– Set up Correspondence SAP S/4HANA Cloud
– Post Customer Invoice
– CNAB750 v2 Return Files Processing onPrem
– CNAB750 v2 Return Files Processing SAP S/4HANA Cloud

PIX overview
PIX overview and SAP Notes
• SAP Notes
PIX payments for outgoing and incoming
payments will be enabled for batch
processing The complete list of the SAP Notes that have
to be implemented for PIX solution is available
in the PIX Collective note:
• SAP delivers:
• CNABs 240 (BR_FEBRABAN_A) and 750 3127880 - Collective Note for Brazilian Pix
(BR_FEBRABAN_750) Payments in Finance
• Not in scope:
• API Online
• Component for Incident Processing:

• FI-LOC-FI-BR-PMT

Accounts Payable
Bank Master Data
onPrem
Bank Master Data
• Run the report IDFI_PIX_CREATE_BANK to create

the internal banks of type 5 - Payment system
• Report will create the master data of the
following technical banks:
• PIX_CPF
• PIX_CNPJ
• PIX_EMAIL
• PIX_PHONE
• PIX_RANDOMKEY
and insert them into the table BNKAIN with the

field BINTK = 5 (Payment System)

Bank Master Data
SAP S/4HANA OP 2021
Bank Master Data
• In the transaction FIPAYTSYST create at

least one Technical Bank for the country
Brazil
• Enter Bank Key and Bank name

Bank Master Data
SAP S/4HANA Cloud
Bank Master Data
• In the FIORI App Manage Banks create

at least one Technical Bank for the
country Brazil
• Enter Bank Key, Bank name and Bank

Number
• Technical Bank must have Bank Category

Payment System

Define Payment System and Alias Types
SAP S/4HANA OP 2021
Define Alias Types
• In the IMG Cross-Applications Components – Bank Account Aliases – Define Alias

Types for Bank Accounts (view V_ALIAS_TYPE) define possible Alias Types, Description
and Validation Rules as regular expression
• It is required to have the Alias Types named in this way to work with PMW format
BR_FEBRABAN_A

Define Alias Types
Examples of regular expression used for validation:
• Email with limited length to 77:
^(?=.{6,77}$)\w+(\.\w+)*@(\w+\.)+(\w{2,4})
• Any string of length 32 characters:
^[0-9a-fA-F]{8}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{12}
• Phone:
([0,+]{0,1}\s*[0-9]{2,3})?\s*$?[0-9]{2}$?\s*[0-9]{4,5}[- ]*[0-9]{4}

Define Payment System
In the IMG Cross-Applications Components – Bank Account Aliases – Define Payment

systems (view cluster VC_PAYT_SYST)
1. Define Payment System
2. Define country in which Payment System is valid

(only one country is allowed per Payment System)

3. Assign Alias Types to Payment System

Define Payment System and Alias Types
SAP S/4HANA Cloud
Define Alias Types
• Configuration activity Define Alias Types for Bank Accounts in the configuration
environment
• It is required to have the Alias Types named in this way to work with PMW format
BR_FEBRABAN_A

Define Alias Types
Examples of regular expression used for validation:
• Email with limited length to 77:
^(?=.{6,77}$)\w+(\.\w+)*@(\w+\.)+(\w{2,4})
• Any string of length 32 characters:
^[0-9a-fA-F]{8}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{12}
• Phone:
([0,+]{0,1}\s*[0-9]{2,3})?\s*$?[0-9]{2}$?\s*[0-9]{4,5}[- ]*[0-9]{4}

• Configuration activity Define Payment systems in the configuration environment
1. Define Payment System
2. Define country in which Payment System is valid
(only one country is allowed per Payment System)

3. Assign Alias Types to Payment System

Supplier Master Data
up to SAP S/4HANA OP 2021
Maintain PIX key in the Supplier Master Data in the field Account Holder
(BUT0BK\LFBK\KNBK-KOINH)
Fields that are required to maintain a bank detail with alias are:
• Bank Country
• Bank Key (Internal Bank with category type 5)
• (technical) Bank Account with mandatory prefix <ALIAS>
• Account Holder (contains PIX key)
•Reference Details – can be used in case the length of email exceeds 60 characters entered in Acc.
Holder field
The field Account Holder has the length of 60 characters. If Bank Key PIX_EMAIL is used,
the additional 17 char could be maintained in the field Reference Details

• The bank account consists of a prefix <ALIAS> and a any string
• e.g. <ALIAS>123456 or <ALIAS>EMAIL
• Prefix <ALIAS> is a must to identify these special bank details
• The PIX key is maintained in the Account Holder field

• And in the case of PIX_EMAIL the Reference Details can be used for least 17 characters
• The Bank Key contains Bank Key that is created by program IDFI_PIX_CREATE_BANK

Validation on the value entered in the Alias Holder field is implemented for each PIX key

SAP S/4HANA Cloud
To maintain Bank Account Alias in BP Master Data:

App Maintain Business Partners:
• Click on Alias Button
• Select Payment System and Alias Type
• Enter Bank Account Alias

Or App Manage Business Partner Master Data:

• Create Bank Account
• Enter Payment System and Alias Type and Bank
Account Alias

Validation on the value entered in the Bank Account Alias field is implemented for each Alias Type

Post Supplier Invoice
• Select proper PIX key which will be used for payment via Partner Bank Type (PIX transfer)

Supplier Invoice with QR Code Information
• When the company receives the PIX invoice

with QR code, the payment is done via
CNAB 240 with segments J and J52PIX
• The information from the QR Code have to

be stored in Supplier Invoice and then read
during payment media creation.
• Dynamic QR Code:
– Enter URL Link- 77 character long string
Static QR Code:
- Enter Transaction ID - 35 character long string
and select PIX key via Bank Partner Type
• PIX URL and Transaction ID are stored in

the table IDFI_PIX_DOC

SAP S/4HANA Cloud
• Select proper PIX key which will be used for payment via Partner Bank Type (PIX transfer)

Supplier Invoice with QR Code Information
• When the company receives the PIX invoice

with QR code, the payment is done via
CNAB 240 with segments J and J52PIX
• The information from the QR Code have to

be stored in Supplier Invoice and then read
during payment media creation.
• Dynamic QR Code:
– Enter URL Link- 77 character long string
Static QR Code:
- Enter Transaction ID - 35 character long string
and select PIX key via Bank Partner Type
• PIX URL and Transaction ID are stored in

the table IDFI_PIX_DOC

Manage Journal Entry
as of SAP S/4HANA OP 1909+ and SAP S/4HANA Cloud
• To specify URL Link or Transaction ID in the Supplier invoice open the document
in the App Manage Journal Entry and select Manage Additional Payment
Attributes

Manage Journal Entry
• Enter URL Link (Dynamic QR Code) or Transaction ID (Static QR Code)

Payment method for Outgoing payments
The payment method must have the following
parameters:
Payment Method For:
• Outgoing Payments
Payment Method classification

• Bank transfer
Required master record specifications:

• Bank Details
– Account number required
Payment Medium:
• Format
– BR_FEBRABAN_A
Format Supplement
– PIX – PIX transfer and QR-Code PIX payments

SAP S/4HANA Cloud
The payment method must have the following
parameters:
Payment Method For:
• Outgoing Payments

• Bank transfer
Required master record specifications:

• Bank Details
– Alias required
Payment Medium:
• Format
– BR_FEBRABAN_A
Format Supplement
– PIX – PIX transfer and QR-Code PIX payments

as of SAP S/4HANA OP 2021 and SAP S/4HANA Cloud
Permitted Payment System:
• Assign valid Payment System to Payment

method

Payment medium file with A and B segments
• Payment medium file with A and B segments is generated for

PIX transfer when PIX key is selected via Bank Partner Type
• In the segment B alias is provided. Information 10 in the

position 33-67 contains text entered in the BSEG-SGTXT
(short text of document line-item)
• In segment A all information needed for clearing are present.

Payment medium file with J and J52 PIX segments
• Payment medium file with J and J52 PIX segments are generated when PIX URL or
Transaction ID are provided in Supplier Invoice (PIX Info button)
• In segment J 52 PIX
• URL Link is provided for Dynamic QR Code
• Transaction ID and PIX key are provided for Static QR Code
• In segment J all information needed for clearing are present.

Bank Account as a PIX key
PIX transfer with Bank Account
• For the PIX Payments with Bank Account it is required to provide also the bank account type:
• "01" - Current account
• "02" - Payment Account
• "03" - Savings Account
• Account type must be maintained in the BP master data in the Bank Account field after the
slash (XXXXXX-XX*/ZZ*)

PIX transfer with bank account
• Bank account type is filled into BR_FEBRABAN_A

format in the segment B into the field 10.3B
Information 11.
• If bank account type is not maintained in the BP

master data, account type“01“ is used by default
• Payment method for PIX transfer with bank account

must have Format supplement PIX
• Alias Required is not set

CNAB240 Return File Processing
Rejection Return File
via FF_5
• Rejection Return File is returned by bank

and it contains up to five rejection error
codes that explain the reason of rejection
• To upload the file run transaction FF_5

and select Bank Specific Format B
Cobrança/Pagar Itau - Brazil
• Error codes are maintained in the view

J_1B_ERROV

• External transaction 000AG is used with

posting rule B02D (no posting, just display
the list of error codes)
• External transaction is always ‚‘000‘+ error

code from the file, i.e. 000AG for error
code AG

Confirmation Return File
via FF_5
• Confirmation Return File is returned by

bank and it contains payment confirmation

and select Bank Specific Format
B Cobrança/Pagar Itau - Brazil

• External transaction 00000 is used with

posting rule B00C (clear debit G/L
account)
• Interpretation Algorithm is 20 (Document

Number Search)

SAP S/4HANA Cloud

and it contains up to five rejection error
• To upload the file, open the Manage

Incoming Payment Files app and select
Bank Specific Format CNAB 240
Payment Format
• Error codes are maintained in

configuration activity Error Codes
(102138)

SAP S/4HANA Cloud
• The error codes are displayed in the

Memo Line of the Bank Statement Item.

SAP S/4HANA Cloud

bank and it contains payment confirmation

Payment Format

Accounts Receivable
House Bank Master Data
onPrem
• Create the PIX key for the relevant House Bank account in the view V_IDFI_PIX_ALIAS
• IMG: Financial Accounting - Bank Accounting - Bank Accounts - Country-/Region-Specific

Functions – Brazil - Define PIX Keys for Bank Account
• Valid From must start from the current date, validity interval must not overlap with other PIX ID
• The PIX key which have LeadingKey flag set will be taken into payment run. Only one PIX key
assigned to the same House Bank and Account ID could have LeadingKey flag set

• Create the PIX key for the relevant House Bank Account in the view V_IDFI_PIX_KEY
• IMG: Financial Accounting - Bank Accounting - Bank Accounts - Country-/Region-Specific

Functions – Brazil - Define PIX Keys for Bank Account
• Valid From must start from the current date, validity interval must not overlap with other PIX ID
• The PIX key which have LeadingKey flag set will be taken into payment run. Only one PIX key
assigned to the same House Bank and Account ID could have LeadingKey flag set

ISPB code for House Bank
• Assign ISPB code to Company Code and

House Bank in the view FIAPBRD_ISPB.

SAP S/4HANA Cloud
• Maintain the PIX key for the relevant

House Bank account in the Alternative
Bank Account Number field

ISPB code for House Bank
• Assign ISPB code to Company Code and

House Bank in the configuration activity
Assign ISPB Codes to Bank Codes
(102140)

Set up Correspondence
Allocate correspondence program
• In order to print received QR Code, the

correspondence must be set up
• Correspondence Type SAPBR is

delivered for PIX QR Code Brazil
• Allocate correspondence program

RFKORDPIX_PDF and variant
BR_PIX_QR (variant must already
exists) to your Company Code and
Correspondence Type SAPBR in the
transaction OB78

Define call up point and assign PDF form to print program
• Define trigger point when correspondence

will be called in the transaction OB79
• Assign PDF form to the print program

RFKORDPIX_PDF in the view V_T001F2

PDF form and Interface
• SAP Standard delivered form is IDFI_PAYM_BR_PIX_PDF
• SAP Standard delivered interface is IDFI_PAYM_BR_PIX

QR Code form output
• Print out will be automatically triggered and sent to spool (transaction SP01) upon return file
upload
• If needed print out can be repeated in the transaction F.64 (correspondence maintenance)

QR Code form output example

SAP S/4HANA OP 2021
Allocate Output Management for Automatic Correspondence


• Allocate Application Object Type

FFO_CORR_INTDOC and Output Type
INTDOC to Correspondence Type
SAPBR in the view V_T048O
(transaction SM30)

Define call up point and Parameters Group
• Define trigger point when correspondence

will be called in the transaction OB79
• Add parameters group BELNR to the

correspondence SAPBR in the view
V_FIN_CORR_PGRP in the transaction SM30

Define standard variant in the view V_FIN_CORR_VRNT
• Define Parameters Variant SAPBR in the
view V_FIN_CORR_VRNT in the
transaction SM30

Define standard correspondence type in the view V_FIN_CORR_TYPE
• Define Correspondence Identifier SAPBR

in the view V_FIN_CORR_TYPE in the
transaction SM30

Output Control – Define Output Types
• Define Output Type INTDOC for

Application Object Type
FFO_CORR_INTDOC in the view
APOC_I_OUTP_TYPV in the transaction
SM30

Output Control – Assign Form Templates
• Assign the form name FIN_FO_CORR_INTDOC_PIX_BR in the view APOC_C_FORMV in

the transaction SM30

Output Control – Output Parameter Determination (transaction OPD)
• Select Rules for Internal Document, Determination Step: Form templates

• Add the Form FIN_FO_CORR_INTDOC_PIX_BR to the first raw and set Sender
Ctry/Reg., Corr. Identifier and Company Code

Output Control – Define Rules for Determination of Master Form Template
• Define the rule for the Master Form Determination based on Company Code
• Assign Master Form Template APOC_DEMO_FORM_MASTER_BR to the Form Template

FIN_FO_CORR_INTDOC_PIX_BR

SAP S/4HANA Cloud


1. Add Correspondence SAPBR in the

configuration activity Define Variants for
Correspondence Types.
2. Add Corr. Identifier SAPBR in the

configuration activity Assign Labels and
Company Codes to Correspondence
Type Variants

3. Assign form template FIN_FO_CORR_INTDOC_PIX_BR to application object

FFO_CORR_INTDOC in the Assign Form Templates configuration activity.

4. Maintain Form Derivation Rule ID

FORM_MASTER_BR_PIX in
configuration activity Define Rules
for Determination of Master Form
Template

QR Code form output
In Display Correspondence History app, you can display the PDF Form with QR Code.

Post Customer Invoice
Post Customer invoice
• No special handling needed. Posting on a

Customer with Payment Method with
format BR_FEBRABAN_750

Payment method for incoming payments
The payment method must have the

following parameters:
Payment Method For:

• Incoming Payments

• Bill/exch.pyt.req
Posting Details:
• Sp. G/L Ind. B/Ex. B/Ex.Pmt.Req
Payment Medium:
• Format
– BR_FEBRABAN_750

Payment Medium Creation onPrem
• Transaction FBPM
• Fill in parameter Validity after Due date

(QR code validity after maturity)

Payment method for incoming payments
SAP S/4HANA Cloud
The payment method must have the

following parameters:
Payment Method For:

• Incoming Payments

• Bill/exch.pyt.req
Posting Details:
• Sp. G/L Ind. B/Ex. B/Ex.Pmt.Req
Payment Medium:
• Format
– BR_FEBRABAN_750

Payment medium creation SAP S/4HANA Cloud
• Set the parameter Validity after Due date

(QR code validity after maturity) in the
Configuration step Create/Assign Selection
Variants (Alternative) ( SSCUI 102238)
• Enter variant name and click on Format

Param icon

Payment media creation for DMEE based payment format CNAB 750
• Run transaction F110 or Manage

Automatic Payments app in SAP
S/4HANA for Customer invoice with
incoming payment method for format
BR_FEBRABAN_750.
• After Payment run, BoE Payment Request

is created and updated in Customer
invoice

CNAB750 v2 Return files Processing
onPrem
via FF_5

and it contains up to ten rejection error

FEBRABAN CNAB 750
• Error codes are maintained in the view

J_1B_ERROV


posting rule B03D (no posting, just display
the list of error codes)

QR Code update Return File
onPrem
• QR Code update Return File is returned

by bank and it contains EMV QR Code in
the segment 4

FEBRABAN CNAB 750


posting rule B02D with Processing Type
11 (no posting, just update of FI document
with returned QR Code)

• After processing of QR Code update

Return file, BoE Payment Request and
Customer Invoice FI documents are
updated with QR Code
• QR Code form will be generated and sent

to spool (transaction SP01)

onPrem

bank and it contains confirmation of
payment in the segment 5

FEBRABAN CNAB 750


posting rule B06D (Customer invoice is
cleared)

CNAB750 v2 Return files Processing
SAP S/4HANA Cloud
SAP S/4HANA Cloud

and it contains up to ten rejection error

Payment Format
• Error codes are maintained in

configuration step Error Codes (102138)
SAP S/4HANA Cloud
• The error codes are displayed in the

Memo Line of the Bank Statement Item.
SAP S/4HANA Cloud
• QR Code update Return File is returned

by bank and it contains EMV QR Code in
the segment 4

Payment Format
QR Code update Return File – Manage Additional Payment Attributes
• After processing of QR Code update Return file, BoE Payment Request and
Customer Invoice FI documents are updated with QR Code
• QR Code can be viewed by selecting Manage Additional Payment Attributes

in Manage Journal Entries App
SAP S/4HANA Cloud

bank and it contains confirmation of
payment in the segment 5

Payment Format
Thank you.
Follow us
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.

Mudança de Mindset

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mudança de Mindset

Uploaded by

Copyright:

Available Formats

PIX Payments

SAP PIX payments solution for FI

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

• Component for Incident Processing:

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

• Run the report IDFI_PIX_CREATE_BANK to create

and insert them into the table BNKAIN with the

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

• In the transaction FIPAYTSYST create at

• Enter Bank Key and Bank name

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

• In the FIORI App Manage Banks create

• Enter Bank Key, Bank name and Bank

• Technical Bank must have Bank Category

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

• In the IMG Cross-Applications Components – Bank Account Aliases – Define Alias

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

Examples of regular expression used for validation:

• Email with limited length to 77:

• Any string of length 32 characters:

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

In the IMG Cross-Applications Components – Bank Account Aliases – Define Payment

1. Define Payment System

2. Define country in which Payment System is valid

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

3. Assign Alias Types to Payment System

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19

Examples of regular expression used for validation:

• Email with limited length to 77:

• Any string of length 32 characters:

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

• Configuration activity Define Payment systems in the configuration environment

1. Define Payment System

2. Define country in which Payment System is valid

(only one country is allowed per Payment System)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21

3. Assign Alias Types to Payment System

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24

• Prefix <ALIAS> is a must to identify these special bank details

• The PIX key is maintained in the Account Holder field

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 26

To maintain Bank Account Alias in BP Master Data:

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 28

Or App Manage Business Partner Master Data:

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 29

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 30

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 32

• When the company receives the PIX invoice

• The information from the QR Code have to

• PIX URL and Transaction ID are stored in

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 33

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 35

• When the company receives the PIX invoice

• The information from the QR Code have to

• PIX URL and Transaction ID are stored in

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 36

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 37

• Enter URL Link (Dynamic QR Code) or Transaction ID (Static QR Code)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 38