N
×
MeyLoop

MeyLoop ×
Oracle
NetSuite

Vendor · Bills · Payments · Subsidiaries

MeyLoop delivers a complete, pre-built integration between PaymentWorks and Oracle NetSuite — covering vendor management, bill processing, payment runs, and subsidiary configurations out of the box. NetSuite's SuiteTalk REST/SOAP APIs and SuiteScript 2.x are used natively. Custom fields and saved searches are handled by the AI Mapping Engine with no code required.

Out-of-the-Box Coverage
Vendor Record8 / 8 mapped
Bank / Payment Info7 / 7 mapped
Vendor Bill8 core + AI-mappable
Vendor Payment8 / 8 mapped
Mapped out-of-the-box AI-mappable Optional
31
Fields Mapped
4
Data Domains
Real-Time
API Mode
Meyro
Meyro handles the rest Custom extensions, tenant-specific fields, and complex transformations are handled automatically by Meyro's AI Mapping Engine.
Real-Time REST API
NetSuite's SuiteTalk REST API enables real-time vendor sync and bill creation — no batch processing required for critical AP operations.
🏢
Multi-Subsidiary
MeyLoop AI maps PaymentWorks data to the correct NetSuite Subsidiary automatically — supporting OneWorld multi-entity deployments.
🔧
Custom Fields via AI
NetSuite's custom field architecture (custentity_, custbody_, custcol_) is handled by the AI Mapping Engine — no SuiteScript needed.
Field-Level Mapping

What's mapped. Out of the box.

Every field in the PaymentWorks → Oracle NetSuite integration — showing the exact NetSuite record type, field ID, and mapping status.

Vendor Record 8
Bank / Payment Info 7
Vendor Bill 8
Vendor Payment 8
PaymentWorks FieldNetSuite Record / Field IDStatusNotes
Vendor IDVendor → externalid✓ Out-of-boxExternal ID for idempotent upsert operations
Company NameVendor → companyname✓ Out-of-boxRequired; matched on companyname for dedup
Tax ID / TINVendor → taxidnum✓ Out-of-boxMaps to EIN/SSN field; format validated
AddressVendor → addressbook (defaultbilling)✓ Out-of-boxFull address subrecord; sets as billing default
Contact Name / EmailVendor → email / contactslist◎ OptionalMaps to primary email or contact sublist
Vendor StatusVendor → isinactive (inverted)✓ Out-of-boxActive maps to isinactive:false
SubsidiaryVendor → subsidiary⚙ AI-MappableAI maps to correct subsidiary ID for OneWorld tenants
1099 EligibleVendor → is1099eligible◎ OptionalDerived from PaymentWorks tax classification
Record Type: vendor
API: SuiteTalk REST PATCH/POST · SOAP upsert
Method: Upsert by externalid
Trigger: Real-time on vendor approval
PaymentWorks FieldNetSuite Record / Field IDStatusNotes
Bank NameVendor Payment Method → bankname✓ Out-of-boxStored on payment method subrecord
Account NumberVendor Payment Method → accountnumber✓ Out-of-boxEncrypted; masked in NetSuite UI
Routing NumberVendor Payment Method → abaroutingnumber✓ Out-of-box9-digit ABA routing; SWIFT for international
Account TypeVendor Payment Method → bankaccounttype✓ Out-of-boxCHECKING / SAVINGS enum
CurrencyVendor → currency✓ Out-of-boxMust match NetSuite-enabled currencies; ISO 4217
Payment MethodVendor → paymentoption (EFT / Wire / Check)✓ Out-of-boxMaps to NetSuite payment method list
Bank StatusVendor Payment Method → isdefault / isinactive✓ Out-of-boxActive bank accounts set as default
Record Type: vendor (paymentmethod subrecord)
API: SuiteTalk REST sublists · SOAP
Security: OAuth 2.0 · TLS · AES-256 banking data
PaymentWorks FieldNetSuite Record / Field IDStatusNotes
Invoice IDVendor Bill → externalid / tranid✓ Out-of-boxExternal ID for dedup; tranid shown in UI
Vendor IDVendor Bill → entity (vendor internalid)✓ Out-of-boxResolved via externalid lookup
Invoice DateVendor Bill → trandate✓ Out-of-boxRequired; MM/DD/YYYY format for NetSuite
Invoice AmountVendor Bill → usertotal (derived from lines)✓ Out-of-boxDerived from line items; currency-precision validated
CurrencyVendor Bill → currency✓ Out-of-boxISO 4217; must match vendor currency setup
Payment TermsVendor Bill → terms◎ OptionalReferences NetSuite terms list; defaults to vendor terms
Line ItemsVendor Bill → item / expense sublists⚙ AI-MappableItem-based or expense-based lines; GL account mapping via AI Designer
Approval StatusVendor Bill → approvalstatus⚡ Real-timeOnly approved bills synced; status tracked bidirectionally
Record Type: vendorbill
API: SuiteTalk REST POST · SOAP · SuiteScript 2.x
Trigger: Real-time REST or batch per AP cycle
PaymentWorks FieldNetSuite Record / Field IDStatusNotes
Payment IDVendor Payment → externalid✓ Out-of-boxUnique identifier for idempotent payment creation
Vendor IDVendor Payment → entity✓ Out-of-boxResolved from PaymentWorks vendor externalid
Invoice ReferenceVendor Payment → apply (bill internalid)✓ Out-of-boxLinks payment to Vendor Bill via apply sublist
Payment AmountVendor Payment → payment✓ Out-of-boxValidated against outstanding bill amount
Payment DateVendor Payment → trandate✓ Out-of-boxRequired; must be within open accounting period
Payment MethodVendor Payment → paymentmethod✓ Out-of-boxEFT / Wire / Check from NetSuite payment method list
CurrencyVendor Payment → currency✓ Out-of-boxMust match bill currency
Bank AccountVendor Payment → account (AR/AP account)✓ Out-of-boxReferences AP bank account in Chart of Accounts
Record Type: vendorpayment
API: SuiteTalk REST POST · SOAP · SuiteScript 2.x
Trigger: Per payment batch or real-time ACH
Integration Flow

PaymentWorks → Oracle NetSuite

End-to-end flow from PaymentWorks through MeyLoop's Gateway and AI Engine into NetSuite's native record model via SuiteTalk REST and SOAP.

PAYMENTWORKS Vendor Data Bill / Invoice Payment 1 MEYLOOP GATEWAY 🔐 🔄 Auth · Validate · Transform · Dedupe CANONICAL DATA MODEL • Vendor externalid · companyname • Bank subrecord · Bill tranid • Payment apply · Subsidiary • Custom field prefix mapping 2 AI MAPPING ENGINE 🧠 SuiteTalk REST Builder Custom Field Resolver custentity_ / custbody_ Subsidiary Assignment GL Account Mapping REST · SOAP · SuiteScript 2.x 3 ORACLE NETSUITE Vendor Record entity · externalid · taxidnum paymentmethod subrecord Vendor Bill vendorbill · tranid · trandate item / expense sublists Vendor Payment vendorpayment · apply sublist paymentmethod · account Custom Fields custentity_ / custbody_ custcol_ (AI-resolved) Vendor → Bill → Payment · Subsidiary-aware · SuiteTalk REST / SOAP OneWorld Multi-Subsidiary Supported 4
Design Considerations

Built for NetSuite at scale

MeyLoop's NetSuite integration handles OneWorld multi-subsidiary, SuiteTalk rate limits, and custom field resolution natively.

🌐
OneWorld Multi-Subsidiary
  • AI maps vendors to correct subsidiary automatically
  • Intercompany transactions supported
  • Per-subsidiary currency and AP account mapping
  • Vendor sharing across subsidiaries handled
🔧
Custom Field Resolution
  • custentity_, custbody_, custcol_ prefix handled
  • AI resolves custom field types and enums
  • No SuiteScript 2.x code required for custom mapping
  • Saved search schemas imported automatically
SuiteTalk Rate Limits
  • Queue-based batching respects concurrency limits
  • Exponential backoff on 429 / rate limit responses
  • Bulk operations use SOAP where REST limits apply
  • Peak-hour scheduling configurable per tenant
📋
Audit & Reconciliation
  • Full log of all SuiteTalk API calls with response
  • Payment reconciliation exports match NetSuite GL
  • Vendor bill status tracked bidirectionally
  • All transactions traceable to PaymentWorks origin
🔐
Security
  • OAuth 2.0 Token-Based Authentication (TBA)
  • TLS 1.3 for all SuiteTalk connections
  • Bank account numbers AES-256 encrypted
  • NetSuite role permissions respected
Version Resilience
  • NetSuite 2× annual releases tracked automatically
  • SuiteTalk version pinning with auto-upgrade path
  • Custom field changes detected via schema diff
  • Zero manual intervention on NetSuite upgrades
Ready to connect Oracle NetSuite?

See a live demo of the MeyLoop NetSuite integration — pre-mapped SuiteTalk fields, OneWorld subsidiary support, and the AI mapping designer in action.

View All Integrations