SAP Integration: The ANZ Reality#
If you're implementing SAP in New Zealand or Australia, integration isn't an afterthought—it's a core architecture decision that will determine whether your ERP becomes a strategic asset or an isolated island of data. ANZ organisations face unique integration challenges: specific banking formats, government reporting systems, and regional marketplaces that don't appear in standard SAP documentation.
The integration reality: Most SAP implementations in ANZ require 10-25 integrations. Each integration is cost, risk, and ongoing maintenance. The organisations that succeed are those that plan integration architecture before implementation begins—not those who discover integration gaps during go-live.
This guide covers SAP integration architecture specifically for ANZ organisations—helping you understand the options, plan for local requirements, and build an integration strategy that scales.
---
SAP Integration Architecture Options#
SAP Integration Suite (SAP Cloud Platform Integration)#
SAP's strategic integration platform—cloud-native, comprehensive, and the recommended approach for modern SAP implementations.
Key Components:
Cloud Integration: Design, deploy, and monitor integration flows. Pre-built integration packages for common scenarios.
API Management: Publish, manage, and analyse APIs. Rate limiting, analytics, and developer portal.
Open Connectors: Pre-built connectors to 150+ non-SAP applications.
Integration Advisor: Design guidance and best practices for integration patterns.
Advantages: - SAP's strategic direction - Pre-built content for SAP-to-SAP integration - Managed cloud service - Strong monitoring and error handling
Considerations: - Additional licensing cost - Learning curve for development team - Requires cloud connectivity
SAP Process Orchestration (PI/PO)#
The on-premise integration platform—still widely used but not SAP's strategic direction.
Components: - Integration Engine - Business Process Management - B2B Integration
When to consider: - Heavy investment in existing PI/PO landscape - Air-gapped environments without cloud connectivity - Specific compliance requirements preventing cloud integration
Reality check: For new implementations, SAP Integration Suite is the recommended path.
Point-to-Point Integration#
Direct connections between SAP and individual systems.
When it works: - Small number of integrations (<5) - Simple data exchange requirements - Limited budget for integration platform
When to avoid: - Growing integration landscape - Complex transformation requirements - Need for monitoring and error handling
---
Integration Patterns for ANZ#
Batch Integration#
Data exchanged in scheduled batches.
Common use cases: - Bank statement processing (daily) - Payroll file generation (weekly/fortnightly) - Customer/product master synchronisation
ANZ examples: - Direct credit files to NZ/AU banks - BAS data preparation - EDI with trading partners
Implementation: - SAP Application Interface Framework (AIF) - File-based interfaces - Scheduled batch jobs
Real-Time Integration#
Immediate data exchange via APIs.
Common use cases: - Credit checks during order entry - Inventory availability for e-commerce - Customer validation during creation
ANZ examples: - Real-time payment verification - Address validation (NZ Post, Australia Post) - Credit bureau queries
Implementation: - OData services - REST APIs - SAP Gateway
Event-Driven Integration#
Systems react to events as they occur.
Common use cases: - Order status notifications - Invoice approval workflows - Master data changes
Implementation: - SAP Event Mesh - Webhooks - Message queues
---
ANZ-Specific Integration Requirements#
Banking Integration#
New Zealand:
Direct Credit Files: - Standard format for batch payments - All major banks support - SAP configuration: Payment medium format (NZ format)
Bank Statement Import: - Bank-specific formats or MT940 - Electronic Bank Statement (EBS) configuration - Auto-matching rules for reconciliation
Real-time Payments: - Emerging APIs for instant payments - Not yet universal—verify bank capabilities
Australia:
Direct Entry (DE) Files: - ABA format for batch payments - BPAY for bill payments - SAP configuration: Payment medium format (AU format)
Bank Statement Import: - BAI2 format common - MT940 also used - Bank-specific variations exist
New Payments Platform (NPP): - Real-time payments via PayID or account number - API-based integration - Check with your bank for API availability
Government Integration#
New Zealand:
Inland Revenue (IR): - GST returns: IR Gateway services - Payroll filing: Employment Information (EI) filing - Integration via IR's Gateway API
Companies Office: - Annual return filing - Company information lookup
Statistics NZ: - Survey data submission
Australia:
Australian Taxation Office (ATO): - Business Activity Statement (BAS) - Single Touch Payroll (STP) - Taxable Payments Reporting System (TPRS) - SBR (Standard Business Reporting) integration
Australian Business Register: - ABN validation
ASIC: - Company registration and annual statements
Marketplace Integration#
Trade Me (NZ): - Product listing management - Order import - Inventory synchronisation - Integration via Trade Me API
E-Commerce Platforms: - Shopify, WooCommerce, Magento - Product and inventory sync - Order import to SAP - Shipment tracking export
Address Validation#
New Zealand: - NZ Post Address Verification API - Electoral Roll validation (where permitted)
Australia: - Australia Post Address API - AusPost validation services
---
Technical Integration Approaches#
IDocs (Intermediate Documents)#
SAP's traditional electronic document interchange format.
Common uses: - EDI with trading partners - Legacy system integration - Master data distribution
Configuration: - Partner profiles (WE20) - Message control - Port definition
Consideration: Mature and well-understood, but legacy technology. Prefer APIs for new integrations.
BAPIs and RFCs#
Remote function calls for direct SAP access.
Common uses: - Real-time data retrieval - Transaction posting - Master data creation
Consideration: Requires SAP security configuration. Can impact performance if not designed carefully.
OData Services#
SAP Gateway exposes OData REST APIs.
Common uses: - Fiori applications - Mobile applications - External system integration
Advantages: - Standard REST protocol - JSON or XML formats - Query capabilities - Mobile-friendly
Web Services (SOAP)#
Traditional SOAP-based web services.
Common uses: - Legacy integration requirements - Systems requiring SOAP - Enterprise service bus integration
Consideration: SOAP is declining in favour of REST/OData.
---
Integration Governance#
Design Principles#
Standardise on patterns: Choose 2-3 integration patterns and use them consistently.
Document everything: Integration specifications, data mappings, error handling.
Plan for failure: Every integration will fail at some point. Design retry logic and alerting.
Monitor actively: Integration health is system health. Monitor proactively.
Error Handling#
Categories: - Transient errors: Network timeouts, temporary unavailable services - Business errors: Validation failures, missing data - System errors: Configuration problems, authentication failures
Approaches: - Retry logic for transient errors - Dead letter queues for failed messages - Alert routing to appropriate teams - Self-healing where possible
Testing Strategy#
Unit testing: Test individual integration components.
Integration testing: Test end-to-end data flow.
Performance testing: Verify integration can handle peak volumes.
Failure testing: Verify error handling and recovery.
---
ANZ Integration Implementation Checklist#
Before Implementation#
- [ ] Inventory all systems requiring SAP integration
- [ ] Document data flow direction and frequency for each
- [ ] Identify ANZ-specific requirements (banking, government)
- [ ] Verify SAP support for local formats
- [ ] Assess integration platform requirements
Banking Integration#
- [ ] Confirm bank file format requirements
- [ ] Configure payment medium formats
- [ ] Set up bank statement processing
- [ ] Test with bank test environments
- [ ] Document reconciliation procedures
Government Integration#
- [ ] Register for government APIs (IR, ATO)
- [ ] Understand authentication requirements
- [ ] Configure reporting formats
- [ ] Test in government test environments
- [ ] Plan go-live timing with reporting cycles
General Integration#
- [ ] Define error handling approach
- [ ] Configure monitoring and alerting
- [ ] Document all integration specifications
- [ ] Train support team on integration troubleshooting
- [ ] Establish integration change management process
---
Monday Morning Action Plan#
This week:
- Inventory Your Integrations: List every system that must connect to SAP. Include banking, government, marketplaces, internal systems, and third parties.
- Assess ANZ Requirements: Identify which integrations require NZ or AU-specific formats or APIs. These are often underestimated.
- Choose Your Integration Platform: For most organisations, SAP Integration Suite is the right choice. Evaluate against your specific requirements.
- Check Banking Format Support: Verify SAP supports your bank's payment and statement formats before implementation.
- Register for Government APIs: Start the registration process for IR (NZ) or ATO (AU) integration. Lead times can be significant.
- Budget for Integration: Integration typically represents 10-20% of implementation cost. Budget accordingly.
---
Conclusion: Integration Determines Value#
An SAP implementation is only as valuable as its integration with your broader business ecosystem. For ANZ organisations, the specific requirements of banking systems, government reporting, and regional marketplaces add complexity that must be planned for from the start.
Success with SAP integration requires: - Early identification of all integration points - Selection of appropriate integration patterns and platform - Specific attention to ANZ requirements - Robust error handling and monitoring - Ongoing governance and maintenance
The organisations that treat integration as a core architecture decision—rather than an implementation afterthought—are the ones that realise the full value of their SAP investment.