Integration Research Prompts
Purpose: Deep decomposition prompts for ERP, Banking, and Platform integrations Target Audience: Integration architects, connector developers, data engineers CODITECT Application: Universal Connector Hub product development
Part 1: ERP Integration Prompts
INT-ERP-001: QuickBooks Online Integration
Objective: Build comprehensive QuickBooks Online connector for US SMB market
Research Scope:
1. API Architecture
- OAuth 2.0 authentication flow
- Authorization code grant
- Refresh token management
- Token expiration handling
- Multi-company support
- API endpoints
- Accounting API (Company, Account, JournalEntry)
- Payments API (Payment, Bill Payment)
- Reports API (BalanceSheet, ProfitAndLoss)
- Rate limits: 500 calls/minute, 10 concurrent requests
- Webhook subscriptions
2. Data Extraction
- Chart of accounts sync
- Journal entries extraction
- Trial balance pull
- Customer/Vendor master data
- Invoice and bill data
- Bank transactions
- Attachments and documents
3. Data Transformation
- QBO account types to platform COA mapping
- Journal entry normalization
- Multi-currency handling
- Class and Location dimension mapping
- Department to cost center mapping
4. Incremental Sync Strategy
- Change data capture via SyncToken
- Full refresh vs incremental
- Deleted record handling
- Conflict resolution
5. Bi-directional Sync (Optional)
- Journal entry posting to QBO
- Budget push to QBO
- Reconciliation confirmation
Deliverables:
□ Airbyte source connector specification
□ OAuth 2.0 implementation guide
□ Data model mapping document
□ Sync strategy decision matrix
□ Rate limit handling patterns
□ Error recovery procedures
□ Sample dbt transformations
Technical Integration:
- Airbyte source connector
- dbt transformation models
- PostgreSQL staging tables
Estimated Effort: 24 hours Priority: P0 (Core US market)
INT-ERP-002: NetSuite Integration
Objective: Enterprise-grade NetSuite connector for mid-market and enterprise
Research Scope:
1. Authentication Options
- Token-Based Authentication (TBA)
- OAuth 2.0 (newer)
- Role-based permissions
- Multi-subsidiary access
2. Integration Methods
- SuiteTalk SOAP Web Services
- Search operations
- CRUD operations
- Async processing
- REST Web Services
- SuiteQL queries
- Record API
- SuiteScript for custom extracts
- SuiteAnalytics Connect (ODBC/JDBC)
3. Data Extraction
- GL transactions
- Account hierarchy with subsidiaries
- Multi-book accounting data
- Custom segments and dimensions
- Advanced revenue management data
- Fixed assets
- Project accounting
4. Transformation Complexity
- Multi-subsidiary consolidation logic
- Elimination entries handling
- Intercompany transaction mapping
- Custom record types
- Saved search result normalization
5. Performance Optimization
- Saved search vs SuiteQL performance
- Pagination strategies
- Concurrent request management
- Governance limits handling
Deliverables:
□ NetSuite connector architecture
□ TBA vs OAuth decision matrix
□ Multi-subsidiary mapping strategy
□ Custom segment handling guide
□ SuiteQL query library
□ Governance limits documentation
□ Consolidation logic specification
Technical Integration:
- Airbyte source connector
- SuiteQL for efficient extraction
- dbt for consolidation transforms
Estimated Effort: 40 hours Priority: P1 (Enterprise expansion)
INT-ERP-003: SAP S/4HANA Integration
Objective: SAP integration for large enterprise customers
Research Scope:
1. Integration Technologies
- SAP OData APIs
- SAP API Business Hub
- SAP BTP Integration Suite
- RFC/BAPI (legacy)
- CDS views
2. Financial Data Extraction
- General Ledger (ACDOCA)
- Accounts Payable/Receivable
- Asset Accounting
- Controlling (Cost Centers, Profit Centers)
- Cash Management
- Financial Close cockpit data
3. Authorization Model
- SAP Fiori app authorization
- API key management
- Principal propagation
- Data access restrictions
4. Data Model Mapping
- SAP Chart of Accounts to platform
- Company Code hierarchy
- Controlling Area mapping
- Document type classification
- Currency handling (local, group, hard)
5. Real-time vs Batch
- Change pointers for CDC
- IDocs for async
- Near real-time extraction options
Deliverables:
□ SAP integration architecture document
□ OData API catalog for FP&A
□ Authorization requirements matrix
□ ACDOCA extraction specification
□ Company code mapping strategy
□ Real-time integration feasibility
□ Change data capture approach
Technical Integration:
- SAP OData source connector
- Airbyte or custom connector
- Complex transformation layer
Estimated Effort: 48 hours Priority: P2 (Large enterprise)
INT-ERP-004: Microsoft Dynamics 365 Integration
Objective: D365 Finance and Operations connector
Research Scope:
1. API Options
- OData REST APIs
- Data entities
- Custom APIs
- Dataverse (Power Platform)
2. Authentication
- Azure AD OAuth 2.0
- Service-to-service authentication
- App registration requirements
- Multi-tenant considerations
3. Data Extraction
- General ledger entries
- Chart of accounts
- Financial dimensions
- Budget data
- Fixed assets
- Project accounting
4. Dimension Handling
- Financial dimension framework
- Dimension combinations
- Default dimensions
- Advanced rules
5. Integration Patterns
- Data entities for bulk extract
- OData for incremental
- DMF (Data Management Framework)
- Change tracking
Deliverables:
□ D365 F&O connector specification
□ Azure AD configuration guide
□ Data entity catalog for FP&A
□ Financial dimensions mapping
□ Change tracking implementation
□ Error handling patterns
□ Performance optimization guide
Technical Integration:
- Airbyte OData connector
- Azure AD integration
- Dimension normalization layer
Estimated Effort: 32 hours Priority: P1 (Enterprise market)
INT-ERP-005: Sage Intacct Integration
Objective: Sage Intacct connector for US mid-market
Research Scope:
1. API Characteristics
- XML-based Web Services API
- RESTful API (newer)
- Session-based authentication
- Sender ID credentials
2. Core Objects
- General Ledger
- Accounts Payable/Receivable
- Cash Management
- Purchasing
- Order Entry
- Project Accounting
- Multi-entity/Multi-book
3. Dimensional Analysis
- Custom dimensions
- Statistical journals
- User-defined dimensions
- Allocation tables
4. Advanced Features
- Consolidation entities
- Elimination entries
- Global consolidation
- Contracts and Revenue Management
5. Integration Considerations
- API pagination
- Rate limiting
- Async vs sync operations
- Custom fields handling
Deliverables:
□ Sage Intacct connector design
□ API authentication guide
□ Object-to-platform mapping
□ Dimension handling strategy
□ Multi-entity consolidation logic
□ Custom fields extraction
□ Revenue recognition data model
Estimated Effort: 28 hours Priority: P1 (Mid-market US)
INT-ERP-006: Totvs Protheus Integration
Objective: Leading Brazilian ERP connector for local market
Research Scope:
1. Integration Methods
- TOTVS REST APIs
- Web Services (SOAP)
- Database direct access (AdvPL)
- TOTVS Fluig (workflow platform)
2. Financial Modules
- Contabilidade Gerencial
- Contas a Pagar
- Contas a Receber
- Ativo Fixo
- Livros Fiscais
- Planejamento e Controle Orçamentário
3. Brazilian Specifics
- Plano de Contas Referencial
- Centro de Custo structure
- Filial (branch) handling
- SPED integration data
4. Data Extraction
- Query functions (REST)
- Database tables structure
- Custom tables handling
- Transaction log access
5. Multi-company Setup
- Grupo (group) concept
- Empresa (company) handling
- Filial (branch) consolidation
Deliverables:
□ Protheus API connector specification
□ Database extraction alternative
□ Financial module data models
□ SPED-ready data extraction
□ Multi-company mapping
□ Centro de Custo handling
□ Brazilian tax data extraction
Technical Integration:
- Custom Airbyte source connector
- AdvPL API consumption
- Brazilian accounting transform layer
Estimated Effort: 36 hours Priority: P0 (Brazilian market)
INT-ERP-007: Omie Integration
Objective: Cloud-native Brazilian ERP connector
Research Scope:
1. API Structure
- RESTful JSON API
- App key authentication
- Webhook support
- Sandbox environment
2. Core Endpoints
- Financeiro (Financial)
- Contabilidade (Accounting)
- Estoque (Inventory)
- Faturamento (Billing)
- Compras (Purchasing)
- CRM
3. Financial Data
- Lançamentos contábeis (Journal entries)
- Plano de contas
- Centro de custos
- Contas a pagar/receber
- Extrato bancário
4. Integration Features
- Real-time webhooks
- Batch processing
- Full data export
- Change detection
5. Brazilian Compliance
- NF-e integration data
- SPED-ready exports
- Tax calculation data
- Banking integration data
Deliverables:
□ Omie connector specification
□ API endpoint mapping
□ Webhook event handlers
□ Brazilian accounting transform
□ NF-e data extraction
□ Bank reconciliation data model
□ Tax calculation integration
Estimated Effort: 24 hours Priority: P0 (Brazilian market)
INT-ERP-008: Conta Azul Integration
Objective: Brazilian SMB ERP connector
Research Scope:
1. API Characteristics
- OAuth 2.0 authentication
- RESTful API
- Rate limits
- Sandbox testing
2. Available Modules
- Financeiro
- Vendas
- Compras
- Estoque
- Contábil
- Fiscal
3. Data Extraction
- Lançamentos
- Categorias (COA)
- Contas bancárias
- Clientes/Fornecedores
- Notas fiscais
- Boletos
4. Integration Limitations
- API coverage gaps
- Manual reconciliation needs
- Report generation limits
5. SMB Workflow Integration
- Simple accounting workflow
- Basic reporting needs
- Contador collaboration
Deliverables:
□ Conta Azul connector specification
□ OAuth implementation guide
□ Data coverage analysis
□ SMB workflow integration
□ Contador collaboration features
□ Limitation workarounds
Estimated Effort: 20 hours Priority: P1 (Brazilian SMB)
INT-ERP-009: Bling Integration
Objective: Brazilian e-commerce focused ERP connector
Research Scope:
1. API Structure
- REST API v3
- API key authentication
- Webhook callbacks
- Rate limiting
2. E-commerce Focus
- Pedidos (Orders)
- Produtos (Products)
- Estoque (Inventory)
- Logística (Shipping)
- Marketplaces integration
3. Financial Modules
- Contas a pagar
- Contas a receber
- Fluxo de caixa
- Categorias financeiras
- Formas de pagamento
4. Fiscal Integration
- NF-e emission data
- NFC-e for retail
- Tax regime handling
- SPED auxiliary data
5. Marketplace Reconciliation
- Mercado Livre
- Amazon
- Shopee
- Magalu
- Commission tracking
Deliverables:
□ Bling connector specification
□ E-commerce financial mapping
□ Marketplace reconciliation logic
□ Order-to-cash workflow
□ Commission calculation
□ Multi-channel reporting
Estimated Effort: 24 hours Priority: P1 (Brazilian e-commerce)
Part 2: Banking Integration Prompts
INT-BANK-001: Plaid Integration (US)
Objective: US banking data aggregation via Plaid
Research Scope:
1. Plaid Products
- Transactions API
- Historical transactions (24 months)
- Real-time transaction webhooks
- Transaction categorization
- Balance API
- Real-time balance checks
- Available vs current balance
- Auth API (for payment initiation)
- Assets API (income/asset verification)
- Liabilities API (loan data)
2. Link Integration
- Plaid Link UI integration
- OAuth institution connections
- Re-authentication handling
- Multi-account linking
3. Data Synchronization
- Webhook event handling
- Polling fallback strategy
- Error and retry logic
- Item status monitoring
4. Security Requirements
- Tokenization approach
- PCI compliance considerations
- Data retention policies
- Access logging
5. Financial Planning Features
- Cash position aggregation
- Transaction categorization for budgets
- Recurring transaction detection
- Forecasting data enrichment
Deliverables:
□ Plaid integration architecture
□ Link UI implementation guide
□ Webhook handler specification
□ Transaction categorization mapping
□ Balance aggregation service
□ Security and compliance checklist
□ Error handling playbook
Estimated Effort: 32 hours Priority: P0 (US market)
INT-BANK-002: Open Finance Brasil Integration
Objective: Certified Open Finance Brasil banking connector
Research Scope:
1. Certification Process
- Functional certification requirements
- Security certification (DCR, mTLS)
- Performance benchmarks
- Directory registration
2. Phase Implementation
- Phase 2: Account data sharing
- Account balances
- Transaction history
- Identity verification
- Phase 3: Payment initiation
- Pix payments
- TED/TEF transfers
- Boleto payments
- Phase 4: Investment data
- Investment positions
- Yield information
3. Consent Management
- Customer journey design
- Consent scope definition
- Renewal workflows
- Revocation handling
4. Technical Requirements
- mTLS certificate management
- FAPI security profile
- JWS/JWE implementation
- Dynamic client registration
5. Multi-bank Aggregation
- Bank connection management
- Data normalization across banks
- Balance aggregation
- Transaction categorization
Deliverables:
□ Certification roadmap and checklist
□ Consent management module specification
□ mTLS implementation guide
□ FAPI security architecture
□ Multi-bank aggregation service
□ Payment initiation workflow
□ Data normalization schema
Estimated Effort: 48 hours Priority: P0 (Brazilian market differentiator)
INT-BANK-003: Banco do Brasil API Integration
Objective: Direct integration with Brazil's largest public bank
Research Scope:
1. API Portfolio
- Cobrança (Billing/Boleto)
- Pix collection and payment
- Extrato (Bank statements)
- Pagamentos (Payments)
- Débito automático
2. Authentication
- OAuth 2.0 flow
- Client credentials
- Sandbox environment
- Production certification
3. Core Use Cases
- Boleto generation and tracking
- Pix QR code generation
- Bank statement retrieval
- Payment initiation
- Receivables management
4. Reconciliation Features
- Statement-to-GL matching
- Boleto collection tracking
- Pix transaction matching
- Float period handling
5. Treasury Management
- Cash position real-time
- Investment positions
- Currency operations
Deliverables:
□ BB API integration specification
□ Boleto generation workflow
□ Pix collection integration
□ Bank reconciliation automation
□ Cash position dashboard
□ Multi-company treasury
Estimated Effort: 28 hours Priority: P1 (Brazilian market)
INT-BANK-004: Itaú API Integration
Objective: Integration with Brazil's largest private bank
Research Scope:
1. Itaú API Services
- Cobrança boletos
- Pix Cobrança
- Extrato Bancário
- Pagamentos
- Investimentos
2. iti Partnership
- iti digital bank APIs
- B2B payment solutions
- Cash management
3. Integration Flow
- API Gateway registration
- Sandbox testing
- Production certification
- Monitoring requirements
4. Use Cases
- Accounts receivable automation
- Supplier payments
- Payroll processing
- Investment management
Deliverables:
□ Itaú API connector specification
□ Boleto and Pix integration
□ Statement reconciliation
□ Payment workflow automation
□ Investment data extraction
Estimated Effort: 28 hours Priority: P1 (Brazilian market)
INT-BANK-005: Bradesco API Integration
Objective: Integration with third-largest Brazilian bank
Research Scope:
1. Bradesco API Portfolio
- Cobrança registrada
- Pix QR codes
- Consulta de extratos
- Pagamentos diversos
- Cartão de crédito corporativo
2. Certification Process
- API registration
- Homologation environment
- Security requirements
- Go-live procedures
3. Corporate Features
- Multi-company management
- Cost center allocation
- Approval workflows
- Corporate card integration
4. Financial Integration
- Auto-reconciliation
- Cobrança tracking
- Payment scheduling
- Cash flow integration
Deliverables:
□ Bradesco API integration guide
□ Corporate banking features
□ Reconciliation automation
□ Corporate card expense import
□ Payment approval workflow
Estimated Effort: 24 hours Priority: P1 (Brazilian market)
Part 3: Platform Integration Prompts
INT-PLAT-001: Salesforce Integration
Objective: CRM-to-Finance data flow for revenue operations
Research Scope:
1. Salesforce APIs
- REST API
- Bulk API 2.0
- Streaming API (CDC)
- Metadata API
2. Revenue Data
- Opportunities → Revenue forecast
- Closed Won → Revenue recognition
- Quotes/CPQ → Pricing analysis
- Contract data → ASC 606 compliance
3. Financial Use Cases
- Sales forecast to budget
- Commission calculation data
- Customer LTV analysis
- Revenue recognition triggers
4. Integration Patterns
- Real-time CDC streaming
- Batch extract for reporting
- Bi-directional for collections
5. Data Mapping
- Account → Customer master
- Opportunity → Revenue record
- Product → SKU/Service
- Custom objects handling
Deliverables:
□ Salesforce connector specification
□ Revenue data model mapping
□ CDC streaming implementation
□ Commission calculation integration
□ ASC 606 trigger events
□ Forecast reconciliation logic
Estimated Effort: 28 hours Priority: P1 (Revenue operations)
INT-PLAT-002: HubSpot Integration
Objective: Marketing and sales data for SMB revenue analysis
Research Scope:
1. HubSpot APIs
- CRM API
- Marketing API
- Commerce API (for payments)
- Webhooks
2. Financial Data
- Deals → Revenue pipeline
- Payments → Cash receipts
- Subscriptions → MRR/ARR
- Customer data → Receivables
3. Use Cases
- Sales pipeline to forecast
- Marketing spend ROI
- Customer acquisition cost
- Subscription analytics
4. Integration Features
- Deal stage mapping
- Custom properties
- Workflow triggers
- Revenue attribution
Deliverables:
□ HubSpot connector specification
□ Revenue pipeline integration
□ Subscription MRR calculation
□ Marketing ROI dashboard
□ CAC/LTV analysis framework
Estimated Effort: 20 hours Priority: P2 (SMB market)
INT-PLAT-003: Stripe Integration
Objective: Payment processing data for SaaS/e-commerce
Research Scope:
1. Stripe APIs
- Core Payments API
- Billing API (subscriptions)
- Connect API (marketplaces)
- Financial Connections API
- Sigma (SQL analytics)
2. Financial Data
- Charges → Revenue
- Refunds → Revenue adjustments
- Subscriptions → MRR/ARR
- Payouts → Cash receipts
- Fees → Cost of revenue
3. Recognition Timing
- Payment intent timing
- Invoice finalization
- Subscription billing cycles
- Proration handling
4. Reconciliation
- Stripe payout reconciliation
- Fee calculation verification
- Dispute/chargeback handling
- Multi-currency conversion
5. Subscription Metrics
- MRR/ARR calculation
- Churn rate tracking
- Net revenue retention
- Cohort analysis data
Deliverables:
□ Stripe connector specification
□ Revenue recognition mapping
□ Payout reconciliation workflow
□ Subscription metrics engine
□ Fee analysis dashboard
□ Multi-currency handling
Estimated Effort: 32 hours Priority: P0 (SaaS companies)
INT-PLAT-004: Shopify Integration
Objective: E-commerce financial data integration
Research Scope:
1. Shopify APIs
- Admin API (GraphQL)
- Orders API
- Payments API
- Inventory API
- Analytics API
2. Financial Data
- Orders → Revenue
- Refunds → Adjustments
- Fulfillments → COGS timing
- Discounts → Revenue deductions
- Shipping → Revenue/Cost
3. E-commerce Accounting
- Gross vs net revenue
- Marketplace fee handling
- Inventory valuation
- Gift card liability
- Returns reserve
4. Multi-channel
- POS transactions
- Online orders
- B2B wholesale
- Subscription products
5. Tax Implications
- Tax collected liability
- Nexus reporting
- International sales
- Duty/import handling
Deliverables:
□ Shopify connector specification
□ Order-to-revenue mapping
□ Inventory-to-COGS flow
□ Multi-channel consolidation
□ Tax liability tracking
□ Gift card accounting
Estimated Effort: 28 hours Priority: P1 (E-commerce market)
Integration Architecture Summary
Airbyte Connector Catalog
# Airbyte connector configurations
connectors:
# US ERP
quickbooks-online:
type: source
auth: oauth2
sync_modes: [full_refresh, incremental]
streams: [accounts, journal_entries, invoices, bills, customers, vendors]
netsuite:
type: source
auth: tba_oauth2
sync_modes: [full_refresh, incremental]
streams: [transactions, accounts, subsidiaries, custom_records]
sage-intacct:
type: source
auth: session
sync_modes: [full_refresh, incremental]
streams: [gl_accounts, journal_entries, ap_bills, ar_invoices]
# Brazilian ERP
totvs-protheus:
type: source
auth: basic_token
sync_modes: [full_refresh, incremental]
streams: [ct1, ct2, ctb, sa1, sa2, se1, se2]
custom: true
omie:
type: source
auth: api_key
sync_modes: [full_refresh, incremental]
streams: [lancamentos, plano_contas, contas_pagar, contas_receber]
conta-azul:
type: source
auth: oauth2
sync_modes: [full_refresh, incremental]
streams: [financeiro, vendas, compras, fiscal]
# Banking
plaid:
type: source
auth: link_token
sync_modes: [incremental]
streams: [transactions, balances, accounts]
open-finance-brasil:
type: source
auth: mtls_fapi
sync_modes: [incremental]
streams: [accounts, transactions, payments]
certification_required: true
# Platforms
salesforce:
type: source
auth: oauth2
sync_modes: [full_refresh, incremental, cdc]
streams: [opportunities, accounts, contacts, custom_objects]
stripe:
type: source
auth: api_key
sync_modes: [incremental]
streams: [charges, subscriptions, invoices, payouts, balance_transactions]
shopify:
type: source
auth: oauth2
sync_modes: [incremental]
streams: [orders, products, inventory, customers, transactions]
Integration Effort Summary
| Category | Connector | Effort | Priority | Quarter |
|---|---|---|---|---|
| US ERP | QuickBooks | 24h | P0 | Q2 2026 |
| NetSuite | 40h | P1 | Q3 2026 | |
| SAP S/4HANA | 48h | P2 | Q4 2026 | |
| Dynamics 365 | 32h | P1 | Q3 2026 | |
| Sage Intacct | 28h | P1 | Q3 2026 | |
| BR ERP | Totvs Protheus | 36h | P0 | Q3 2026 |
| Omie | 24h | P0 | Q3 2026 | |
| Conta Azul | 20h | P1 | Q4 2026 | |
| Bling | 24h | P1 | Q4 2026 | |
| Banking | Plaid | 32h | P0 | Q2 2026 |
| Open Finance BR | 48h | P0 | Q3 2026 | |
| BB/Itaú/Bradesco | 80h | P1 | Q4 2026 | |
| Platform | Salesforce | 28h | P1 | Q3 2026 |
| HubSpot | 20h | P2 | Q4 2026 | |
| Stripe | 32h | P0 | Q2 2026 | |
| Shopify | 28h | P1 | Q3 2026 |
Total Estimated Effort: 544 hours
CODITECT Universal Connector Hub
Product Features
- 600+ Pre-built Connectors: Airbyte-powered
- AI-Assisted Mapping: Account mapping suggestions
- Real-time CDC: Event-driven sync
- Brazilian ERP Specialization: Totvs, Omie, Conta Azul native
- Open Finance Certified: Brazilian banking advantage
Pricing Tiers
- Starter: 3 connectors, 10K records/mo - $199/mo
- Professional: 10 connectors, 100K records/mo - $599/mo
- Business: Unlimited connectors, 1M records/mo - $1,499/mo
- Enterprise: Custom, real-time CDC, SLA - $4,999+/mo
Generated for CODITECT FP&A Platform Development Version: 1.0 | Date: 2026-02-03