×
MeyLoop

MeyLoop ×
Oracle
Fusion Cloud

Supplier · Payments · Invoices · Procurement

MeyLoop delivers a complete, pre-built integration between PaymentWorks and Oracle Fusion Cloud Financials — covering supplier onboarding, bank accounts, invoices, and payment processing across all four core AP data domains out of the box. Custom Oracle Fusion fields and Business Unit configurations are handled by the AI Mapping Engine.

Out-of-the-Box Coverage
Supplier / Vendor7 / 7 mapped
Bank Account7 / 7 mapped
Invoice / AP8 core + AI-mappable
Payment Run8 / 8 mapped
Mapped out-of-the-box AI-mappable Optional
30
Fields Mapped
4
Data Domains
AI Custom Fields
Meyro
Meyro handles the rest Any fields outside the pre-mapped set — custom extensions, tenant-specific fields, and complex transformations — are handled by Meyro's AI Mapping Engine.
Field-Level Mapping

What's mapped. Out of the box.

Every field in the PaymentWorks → Oracle Fusion Cloud integration — pre-mapped, AI-configurable, or optional.

Supplier / Vendor 7
Bank Account 7
Invoice / AP 8
Payment Run 8
PaymentWorks FieldOracle Fusion Object / FieldStatusNotes
Vendor IDSupplier → Supplier Number✓ Out-of-boxExternal supplier identifier; maps to Party Number
Company NameSupplier → Supplier Name✓ Out-of-boxRequired; matched against existing party records
Tax ID / TINSupplier → Tax Registration Number✓ Out-of-boxEIN / TIN validated; format enforced per country
AddressSupplier Site → Address (HZ_LOCATIONS)✓ Out-of-boxFull address object; country code ISO 3166 validated
Contact Name / EmailSupplier Contact → Contact Point◎ OptionalMaps to Party Contact; not required
Vendor StatusSupplier → Supplier Status✓ Out-of-boxActive / Inactive — only approved vendors synced
Business UnitSupplier Site → Business Unit Assignment⚙ AI-MappableMaps to BU via AI; configurable per tenant structure
Module: Oracle Procurement Cloud
Object: Supplier (AP_SUPPLIERS)
API: Suppliers REST v1 · FBDI for bulk
Trigger: Event-driven (on approval)
PaymentWorks FieldOracle Fusion Object / FieldStatusNotes
Bank NameExternal Bank Account → Bank Name✓ Out-of-boxMatched against CE_BANKS_V
Account NumberExternal Bank Account → Account Number✓ Out-of-boxAES-256 encrypted in transit and at rest
Routing / SWIFT / IBANExternal Bank Account → Bank Branch✓ Out-of-boxABA routing, SWIFT BIC, or IBAN; format-validated
Account TypeExternal Bank Account → Account Type✓ Out-of-boxChecking / Savings enum
CurrencyExternal Bank Account → Currency Code✓ Out-of-boxISO 4217; must match Fusion-enabled currencies
Payment MethodPayment Method → IBY_PAYMENT_METHODS✓ Out-of-boxEFT / Wire / Check — maps to IBY payment methods
Bank StatusExternal Bank Account → Active Flag✓ Out-of-boxOnly active accounts synced
Module: Oracle Cash Management / Payments
Object: External Bank Accounts (IBY_EXT_BANK_ACCOUNTS)
API: External Bank Accounts REST · SOAP
Security: OAuth2 · TLS 1.3 · Field-level encryption
PaymentWorks FieldOracle Fusion Object / FieldStatusNotes
Invoice IDAP Invoice → Invoice Number✓ Out-of-boxUnique per supplier; deduplicated on insert
Vendor IDAP Invoice → Supplier Reference✓ Out-of-boxLinks to AP_SUPPLIERS via Supplier Number
Invoice DateAP Invoice → Invoice Date✓ Out-of-boxRequired; ISO 8601 format
Invoice AmountAP Invoice → Invoice Amount✓ Out-of-boxValidated against currency precision rules
CurrencyAP Invoice → Invoice Currency Code✓ Out-of-boxISO 4217; must match enabled ledger currencies
Payment TermsAP Invoice → Payment Terms (AP_TERMS)◎ OptionalDefaults to supplier site terms if not passed
Invoice Line ItemsAP Invoice Lines → AP_INVOICE_LINES_ALL⚙ AI-MappableDescription, qty, unit price, account coding — via Mapping Designer
Tax AmountAP Invoice → Tax Lines (ZX_LINES)◎ OptionalMaps to E-Business Tax module when configured
Module: Oracle Payables Cloud
Object: Invoices (AP_INVOICES_ALL)
API: Invoices REST v1 · FBDI bulk load · SOAP
Trigger: Batch (daily / per AP cycle)
PaymentWorks FieldOracle Fusion Object / FieldStatusNotes
Payment IDPayment → Payment Reference Number✓ Out-of-boxUnique identifier per payment
Vendor IDPayment → Supplier Reference✓ Out-of-boxLinks to AP_SUPPLIERS
Invoice IDPayment → Invoice Reference✓ Out-of-boxInvoice must exist; AP_INVOICES_ALL reference
Payment AmountPayment → Payment Amount✓ Out-of-boxValidated against invoice amount
Payment DatePayment → Payment Date✓ Out-of-boxRequired; validated against AP period
Payment MethodPayment → Payment Method (IBY)✓ Out-of-boxEFT / Wire / Check via IBY_PAYMENT_METHODS
CurrencyPayment → Payment Currency Code✓ Out-of-boxISO 4217 matching invoice currency
Bank Account UsedPayment → External Bank Account Ref✓ Out-of-boxReferences IBY_EXT_BANK_ACCOUNTS
Module: Oracle Payments Cloud (IBY)
Object: Payment Requests (IBY_PAYMENTS_ALL)
API: Payments REST v1 · SOAP · Payment Process Request
Trigger: Batch (per payment run)
Integration Flow

PaymentWorks → Oracle Fusion Cloud

End-to-end data flow through the MeyLoop Gateway, Canonical Data Model, and AI Mapping Engine into Oracle Fusion's AP, IBY, and Procurement modules.

PAYMENTWORKS Vendor Data Invoice Data Payment Data 1 MEYLOOP GATEWAY 🔐 🔄 Auth · Validate · Transform · Dedupe CANONICAL DATA MODEL • Vendor ID · Name · Tax ID · Address • Bank Info · Invoice · Payment refs • Business Unit · Ledger assignments 2 AI MAPPING ENGINE 🧠 Semantic Field Matching Confidence Scoring FBDI / REST Payload Build Business Unit Mapping SOAP · REST · FBDI Bulk Oracle Cloud APIs 3 AI-Driven Mapping ORACLE FUSION CLOUD Procurement Cloud AP_SUPPLIERS · Supplier Sites Business Units · Supplier Groups Cash Management (IBY) External Bank Accounts IBY_EXT_BANK_ACCOUNTS Payables Cloud (AP) AP_INVOICES_ALL · AP Lines ZX Tax · AP_TERMS Payments Cloud (IBY) IBY_PAYMENTS_ALL Payment Process Request Supplier → Bank Account → Invoice → Payment · FBDI Bulk or REST API 4
Design Considerations

Built for Oracle Fusion at scale

MeyLoop's Oracle Fusion integration includes enterprise-grade patterns for multi-BU deployments, ledger alignment, and Fusion-specific security.

🏢
Multi-Business Unit
  • AI maps vendor data to correct BU automatically
  • Supplier site created per BU as required
  • Ledger-aligned invoice coding per BU rules
  • Payment runs separated by Business Unit
🔗
Data Dependencies
  • Supplier must exist before bank account creation
  • Bank account must exist before invoice or payment
  • Invoice validated before payment run initiated
  • Oracle Party model (HZ) respected throughout
Real-Time vs. Batch
  • Vendors: event-driven via REST on approval
  • Invoices: FBDI bulk load or REST per AP cycle
  • Payments: Payment Process Request per run
  • Bank accounts: event-driven on change
📋
Audit & Compliance
  • Full log of all PaymentWorks → Fusion API calls
  • Invoice audit trail per SOX requirements
  • Reconciliation exports on demand
  • Immutable transaction records
🔐
Security
  • OAuth2 for all Oracle Cloud API calls
  • TLS 1.3 enforced; banking data AES-256 encrypted
  • Field-level masking for account numbers in logs
  • Fusion role-based access controls respected
Upgrade Resilience
  • Quarterly Oracle Fusion updates tracked automatically
  • API version changes detected; mappings validated
  • AI Knowledge Registry stores successful mapping patterns
  • Zero manual re-mapping required post-upgrade
Ready to connect Oracle Fusion Cloud?

See a live demo of the MeyLoop Oracle Fusion integration — pre-mapped fields, multi-BU support, and the AI mapping designer in action.

View All Integrations