All reports are shown in the following local currencies:
Text Enclosure: Not Enclosed, Single Quote and Double Quote. Field Delimiter: Comma, Semicolon and Tab
Technical Processing Combined
Time zone: UTC/GMT.
Frequency: daily, weekly, fortnightly and monthly.
All Reports are transferred via sFTP between 4AM to 5AM UTC/GMT.
Compliance reports include all successful transactions with financial impact, in accordance with the local Central Banks’ compliance requirements:
Types = DB, CP, RC, CR, RF, RV, CB
Status = Success/90
The reports are created according to payout and processed date:
• Compliance Accounting: present all successful transactions based on the processed date. In addition, it includes the payout due date. The file name format is:
• Compliance Financial: present all successful transactions based on the payout due date. The file name format is:
Merchant _Country_AMS_Compliance_Financial_ With_Installments_ Report_DD.Month.YYYY_to_DD.Month.YYYY
These reports include the following fields:
Values WO Taxes
CPF (shows local customer tax ID, not required in Mexico)
Number of Installments
Additional information fields are described as follows:
Taxes: total amount of taxes applicable to each transaction;
ValuesWOTaxes: net amount of sales after deduction of taxes;
Fees: total amount of PPRO fees applicable to each transaction, including acceleration fees in case of transactions with installments;
NetPayOut: net amount of sales after deduction of taxes and PPRO fees;
PayOutWOWht: net payout as percentage of gross transaction amount;
PayOutWithWHT: net payout as percentage of gross transaction amount, if withholding taxes are recoverable.
The Technical Processing Report presents the number of transactions processed during the related period, per type. It counts both successful and unsuccessful transactions and calculates the total amount of the technical processing fees.
The report includes the following transaction types:
Initial registration of a customer. Later Debit (DB) transactions can always reference to a valid registration.
Changes the registered data of a registration (RG).
In order to deactivate a prior registration, a deregistration transaction can be submitted to the system.
Is automatically generated for a successful Registration (RG)
In case of card transactions, authorizes and reserves an amount, which will be effectively charged with a following Capture (CP) transaction. In case of prepayment transactions, issues a payment order which will later trigger a Receipt (RC) transaction if the order is actually settled by the customer.
Captures a preauthorized amount (PA), and the charge for the cardholder becomes effective.
Payment confirmation for Prepayment methods (typically Boleto Bancário).
Preauthorization (PA) and Capture (CP) in a single step. The charge becomes immediately effective.
Reverses an already processed Preauthorization (PA) or Debit (DB) transaction.
Credits the account of the end customer with a reference to a prior Debit (DB), Capture (CP) or Receipt (RC) transaction.
Debits the account of the end customer with a reference to a prior Debit (DB) transaction.
Schedules upcoming payment transactions of the same type and amount (recurring).
Reschedules a prior scheduled (recurring) job while the job is already running.
Cancels a running (recurring) job.
A negative booking on the merchant account, which is generally triggered by the end customer or bank.
Chargeback Reversal (CR)
A positive booking on the merchant account to offset a previous Chargeback (CB) which was reversed by the bank.
In order to make the information accessible to the merchant, PPRO includes all reports in the combined reports file, which presents:
• Financial flows overview: showing the total financial open balance, cash-in, PPRO service fees, taxes, payouts and closing balance. • Compliance Financial report: with the list of transactions by payout date. • Accounting flows overview: showing the total revenues, PPRO service fees, taxes and net revenues. • Compliance Accounting report: with the list of transactions by processed date. • Technical processing report: with the number of transactions and applicable PPRO processing fees.