Documente Academic
Documente Profesional
Documente Cultură
Please select Yes to join the integrated voice conference when prompted:
If you have joined the Integrated Voice Conference, and still cannot hear
the presentation, try this: click "More Options" on the control panel and
click the speaker/microphone audio test. Then select your preferred speakers.
If you already selected No, in the WebEx Menu, click on Audio> Integrated Voice Conference> Join Conference.
Becky Alvarez
Director Product Strategy
Cloud Financials Development
October 10, 2018
Payments Overview
Invoice Selection Building Payments Formatting Payments Printing / Transmission
Global Banking Model Visibility & Control Straight Through Processing Reporting Capabilities
Bank/Branch/Account Logic Payment Approval, Usability Remittance Advice, Positive Pay
Extensive Selection, Validation Model
Format Framework
Disbursement XML Extract Structure
• Based on standard XML technology
• Templates stored in Oracle BI Publisher
• Template applied to Oracle Payments XML data file
• Templates can be easily created and edited
• Fixed position and delimited eText formats
• Rich library of seeded formats
Modified Template
• Secured • PGP
protocols - Encryption
SFTP, HTTPS • PGP Digital
POST, UCM Signature
• Two Factor
Authentication
• Master Encryption Key: Automatically generated using AES • SFTP: Using HTTPS proxy that allows transmission without
algorithm and stored in Oracle Platform Security Services requiring approval of port
• Chain Key Approach: Master Encryption Key encrypts Subkey • Two Factor Authentication: Allows SSL public key import
and Subkey encrypts payment instrument data
• UCM: Oracle Universal Content Management for outbound and
• Encryption: Payment instrument data and other sensitive inbound integrations. ERP Cloud Integration Services can be
payment data used to automate the file transfer.
• Masking: Payment instrument data and supplemental data • PGP Encryption and Digital Signature: Allows payment file
masking with last four digits unmasked security for both outbound and inbound payment files. Keys can
be generated or imported.
• Tokenization: Credit card data tokenization with CyberSource
Payment File 1
Payment Batch 1
Which Currency? USD, EUR
Which BU? USD, EUR Electronic
Which Payment Method?
Electronic BU1, BU2, BU3
Pool of Built
BU1, BU2 Payment File 2
User Payments
Payment
Payment Batch
Batch 2 USD, EUR
Printed
Invoice USD, EUR BU1, BU2, BU3
Selection Printed
BU1, BU2 Format Payments
BU B
BU B BU B
Payment Factory
Invoice Invoice Centralized
BU A Selection BU A Payment Processing
Entry
BU A & B
BU B BU B BU A & B
Invoice entered Invoices selected Invoices built Payments built into Payment file File transmitted Auxiliary
and validated for payment into payments payment file(s) formatted or printed reporting
Supplier
Shared Services model – Improves
flexibility and responsiveness.
Better control over suppliers and their
payments.
Improved supplier relation
management
Reduced transaction and
Consolidated Payment (250 USD) administration costs for payments
Notifications
Rejected Approved
Processing setup
Reporting setup
Usage rules
Transmission details