Skip to content
Shopify Connector

Common Data Sync Errors Between Shopify and MYOB (And How to Fix Them) [2026]

Jeff A.
Jeff A.

You've implemented your Shopify-to-MYOB connector with high hopes of automated order processing, but instead, you're dealing with frustrating sync errors that seem to pop up randomly. Orders are duplicating in MYOB, inventory counts don't match between systems, GST codes are incorrectly assigned, and payment matching is creating reconciliation nightmares. What was supposed to save time is now consuming hours troubleshooting mysterious error messages.

These data sync problems are remarkably common—even with quality connectors and proper initial setup. The complexity of synchronising Shopify's flexible eCommerce data structure with MYOB's rigid accounting requirements creates numerous potential failure points. Small configuration oversights, platform updates, or edge-case orders can trigger errors that weren't apparent during initial testing.

The good news: most Shopify-MYOB sync errors fall into predictable categories with straightforward solutions. This comprehensive troubleshooting guide identifies the most common problems Australian eCommerce businesses encounter, explains why they occur, and provides step-by-step resolution procedures. You'll learn how to diagnose issues quickly, implement permanent fixes, and prevent recurrence—transforming your integration from frustrating to reliable.

 

Sections in This Post

  1. Understanding How Shopify-MYOB Data Sync Actually Works
  2. Error Category 1: Product and SKU Mapping Failures
  3. Error Category 2: Customer Record Mismatches
  4. Error Category 3: GST and Tax Code Problems
  5. Error Category 4: Payment and Financial Reconciliation Issues
  6. Error Category 5: Inventory Synchronisation Discrepancies
  7. Error Category 6: Order Duplication and Missing Orders
  8. Diagnostic Tools and Troubleshooting Methodology
  9. Prevention: Configuration Best Practices to Avoid Common Errors
  10. When to Escalate to Professional Support
  11. Conclusion
  12. FAQ
  13. Resources

 

Understanding How Shopify-MYOB Data Sync Actually Works

Before troubleshooting specific errors, understanding the technical synchronisation process helps you diagnose root causes rather than just treating symptoms.

 

The Data Sync Workflow

Step 1: Order Detection
Your connector continuously monitors Shopify's API for new or updated orders. Real-time connectors check every 5-15 minutes; batch connectors check hourly or at scheduled intervals. When Shopify registers a new order (the customer completes checkout and payment), the order becomes available via API.

Step 2: Data Extraction
The connector retrieves complete order information from Shopify:

  • Order number, date, and status
  • Customer name, email, billing/shipping addresses
  • Line items: product names, SKUs, quantities, prices
  • Tax calculations and tax line assignments
  • Shipping charges and shipping method
  • Discount codes and adjustments
  • Payment method and transaction details
  • Custom fields or order notes

Step 3: Data Transformation and Mapping
This critical step translates Shopify's structure into MYOB's requirements:

  • Product mapping: Shopify SKU → MYOB Item Number
  • Customer mapping: Shopify customer email → MYOB Contact/Customer ID
  • Account mapping: Product types → MYOB Income Accounts (Chart of Accounts)
  • Tax mapping: Shopify tax rates → MYOB Tax Codes (GST, GST-Free, etc.)
  • Payment mapping: Payment gateway → MYOB Bank/Clearing Accounts

Step 4: Validation
Before sending to MYOB, the connector validates transformed data:

  • Required fields populated (customer name, item codes, amounts)
  • Amounts calculated correctly (line totals, tax, shipping, total)
  • No duplicate orders already synced
  • Referenced records exist (customers, items already in MYOB)

Step 5: MYOB Entry Creation
Validated data posts to MYOB's API as an invoice or sales record:

  • Customer invoice created with all line items
  • GST calculated and assigned per line
  • Payment is recorded if the order is paid
  • Inventory quantities adjusted for fulfilled items

Step 6: Confirmation and Logging
Successful sync updates the connector logs and may trigger confirmation notifications. Failed syncs generate error logs with details for troubleshooting.

 

Where Errors Occur

Sync failures happen primarily in three stages:

 • Mapping stage (Step 3): SKU doesn't exist in MYOB, customer record missing, tax code not found → Most common error source

Validation stage (Step 4): Required fields missing, amount discrepancies, duplicate detection → Second most common

MYOB API stage (Step 5): MYOB business rules prevent entry, API rate limits, network connectivity → Less common but critical

Understanding this workflow helps you quickly identify which stage is failing when you encounter errors, dramatically speeding diagnosis and resolution.

 

Important Context for Australian Shopify-MYOB Businesses

GST complexity: Australian GST-inclusive pricing and mixed tax rates create more mapping complexity than international businesses face

Payment timing: Shopify Payments batches deposits over 2-3 days, requiring sophisticated payment handling

MYOB variants: AccountRight Desktop, AccountRight Cloud, Essentials, and Exo have different API capabilities—your connector behavior varies by version

Product variants: Shopify's size/color variants map to MYOB differently depending on your inventory structure

 

With workflow understanding established, let's address specific error categories and solutions.

 

Error Category 1: Product and SKU Mapping Failures

Product mapping errors are the #1 cause of Shopify-MYOB sync failures, accounting for approximately 40-50% of all reported issues.

 

Error Symptoms

You'll recognize product mapping problems through these error messages:

  • "Product SKU '[SKU]' not found in MYOB"
  • "Item code '[CODE]' does not exist"
  • "Unable to map product to inventory item"
  • "Required field 'Item' is missing"
  • Order syncs but line items missing or incorrect

 

Why This Happens

Cause 1: SKU Mismatch Between Systems
Shopify product has SKU "WIDGET-001" but MYOB item number is "W001" or "Widget-001" (case sensitivity matters in some systems). Connector can't match, sync fails.

Cause 2: Products Exist in Shopify But Not MYOB
You added products to Shopify but never created corresponding items in MYOB. When orders for those products come through, connector can't find MYOB item to reference.

Cause 3: Shopify Variants Not Properly Mapped
Shopify stores variants (Small/Medium/Large) as separate SKUs, but your MYOB setup uses single item with attributes. Connector doesn't know how to consolidate variants to single MYOB item.

Cause 4: Special Characters in SKUs
SKUs containing slashes, ampersands, or other special characters might work fine in Shopify but cause API problems when syncing to MYOB.

 

How to Fix

Solution 1: Audit and Standardise SKUs

Perform a comprehensive SKU audit across both systems:

Step 1: Export complete product list from Shopify (Products → Export)

Step 2: Export item list from MYOB (Inventory → Items → Export)

Step 3: Compare lists in spreadsheet:

  • Identify Shopify SKUs without MYOB matches
  • Note any case differences (Widget-001 vs widget-001)
  • Flag special characters in SKUs
  • Highlight products needing creation in MYOB

Step 4: Decide on standardisation approach:

  • Option A: Change Shopify SKUs to match MYOB (impacts URLs, reports)
  • Option B: Change MYOB item numbers to match Shopify (cleaner long-term)
  • Option C: Use the connector's custom mapping feature to map mismatches

Step 5: Make changes systematically:

  • Create missing items in MYOB first
  • Update SKUs where needed (off-hours to minimize customer impact)
  • Configure custom mappings in connector if needed

Best practice: Adopt single SKU standard going forward. Make MYOB item numbers match Shopify SKUs exactly—this eliminates ongoing mapping maintenance.

 

Solution 2: Handle Variants Properly

For Shopify variants, choose mapping approach:

Approach A: Separate MYOB Items
Create separate MYOB item for each variant:

  • Shopify: "T-Shirt - Small (SKU: TSHIRT-S)", "T-Shirt - Medium (SKU: TSHIRT-M)"
  • MYOB: Item "TSHIRT-S", Item "TSHIRT-M"
  • Pros: Simple mapping, accurate inventory by size
  • Cons: More items to manage, reporting more complex

Approach B: Single MYOB Item
Use one MYOB item for all variants:

  • Shopify: Multiple SKUs (TSHIRT-S, TSHIRT-M, TSHIRT-L)
  • MYOB: Single item "TSHIRT" with total inventory
  • Connector maps all variants to a single item
  • Pros: Simpler MYOB inventory, cleaner reporting
  • Cons: Can't track inventory by size, risk of overselling specific variants

Approach C: MYOB Item with Custom Fields
Advanced connectors support MYOB custom fields to track variants:

  • Use a single MYOB item with variant data in a custom field
  • Requires a connector that supports custom field mapping
  • Pros: Clean inventory with variant detail
  • Cons: More complex setup, requires advanced connector features

Recommendation: For businesses with significant variant inventory (clothing, shoes, sized products), use Approach A (separate items). For simple businesses or products where size doesn't matter for inventory (one-size items), use Approach B.

 

Solution 3: Create Default/Placeholder Items

For products that occasionally appear but don't warrant full MYOB items:

Step 1: Create MYOB item "SHOPIFY-MISC" or "TEMP-PRODUCT"

Step 2: Configure the connector to map unmatched SKUs to this default item

Step 3: Review these orders periodically and either:

  • Create proper MYOB items for frequently-sold products
  • Accept that low-volume items use a placeholder

Caution: This approach works for occasional problem products but shouldn't be permanent solution for regular inventory.

 

Solution 4: Implement Ongoing SKU Governance

Prevention through process:

New Product Checklist: □ Create MYOB item first, note exact item number □ Use that exact item number as Shopify SKU □ Verify sync immediately after creating product □ Document in product creation process

Monthly Audit:

  • Run connector error log review
  • Identify any new unmapped SKUs
  • Create or map items proactively
  • Update SKU documentation

This proactive approach prevents future mapping errors rather than continuously fixing them.

 

Error Category 2: Customer Record Mismatches

Customer-related errors occur when connector can't match Shopify customer to existing MYOB contact or can't create new contact due to data issues.

Error Symptoms

Common customer error messages:

  • "Customer '[Email]' not found in MYOB"
  • "Unable to create customer record"
  • "Duplicate customer detected"
  • "Required customer field missing"
  • "Customer name contains invalid characters"

 

Why This Happens

Cause 1: First-Time Customer Without MYOB Record
New Shopify customer places order, but MYOB contact doesn't exist yet. If connector isn't configured to automatically create contacts, sync fails.

Cause 2: Email Address Mismatch
Returning customer uses different email address than their MYOB contact record. Connector searches by email, can't find match, attempts to create duplicate contact.

Cause 3: Required MYOB Fields Not Populated
MYOB requires fields Shopify doesn't collect or customer didn't provide (company ABN, phone number in specific format, etc.). Contact creation fails due to missing required data.

Cause 4: Special Characters in Names
Customer name contains characters MYOB API doesn't accept (emoji, some international characters, symbols). Contact creation fails.

Cause 5: Duplicate Contact Detection
Connector detects potential duplicate (similar name, same email) and pauses for manual review rather than automatically creating duplicate record.

 

How to Fix

Solution 1: Enable Automatic Customer Creation

Configure the connector to automatically create MYOB contacts:

Step 1: Access the connector customer settings

Step 2: Enable "Automatically create customers" or a similar option

Step 3: Configure default values for required MYOB fields:

  • Customer Type: Individual or Company
  • Terms: COD or Net 30 (for B2B)
  • Tax Code: GST or applicable default
  • Custom Fields: Default values if required

Step 4: Set customer naming convention:

  • First/Last Name separately or combined
  • Company name from shipping address if B2B
  • Handle missing names (use email prefix as fallback)

Step 5: Test with sample orders to verify that contacts are created correctly

Caution: Review auto-created contacts periodically to ensure data quality remains acceptable. Some businesses prefer manual review for B2B customers where credit terms matter.

 

Solution 2: Customer Matching Logic

Configure how the connector matches existing customers:

Primary matching method:

  • Email address (recommended): Most reliable, customers rarely change email
  • Name match: Risky due to name variations and duplicates
  • Phone number: Sometimes unreliable (customers use different phones)
  • Custom field: Advanced option using customer ID or account number

Handling variations:

  • Configure case-insensitive email matching
  • Enable "fuzzy matching" for minor spelling differences
  • Decide how to handle multiple matches (manual review vs default behavior)

For B2B wholesale:

  • Use customer account number or reference if available
  • Map to MYOB customer categories for pricing tiers
  • Consider separate matching logic for trade customers vs retail

 

Solution 3: Data Cleansing Rules

Implement data transformation rules:

Name handling:

  • Remove special characters before sending to MYOB
  • Replace problematic characters (é → e, ñ → n)
  • Handle missing first/last names gracefully
  • Trim extra whitespace

Required field defaults:

  • Populate the required MYOB fields with defaults if Shopify doesn't collect
  • Example: If ABN is required but not collected, use "N/A" or "000000000"
  • Document that these defaults need a manual update for invoicing purposes

Address standardisation:

  • Format phone numbers consistently
  • Standardise state abbreviations (NSW, VIC, QLD, etc.)
  • Handle international addresses appropriately

 

Solution 4: Manual Review Workflow

For businesses requiring careful customer data quality:

Step 1: Configure the connector to flag customer issues without stopping sync

Step 2: Order syncs with the temporary customer placeholder

Step 3: Daily review of flagged customer records:

  • Verify customer details
  • Match to existing contacts if appropriate
  • Create a properly formatted contact
  • Update order with the correct customer link

Step 4: Over time, builds clean customer database with manual quality control

Trade-off: More manual work, but ensures customer data accuracy for businesses where this matters (B2B operations, credit management, customer segmentation).

 

Solution 5: Periodic Customer Database Reconciliation

Maintain long-term data quality:

Monthly tasks:

  • Export Shopify customer list
  • Export MYOB contact list
  • Identify duplicates or inconsistencies
  • Merge duplicate contacts in MYOB
  • Update customer email addresses for better matching
  • Review customers with multiple records

Tools to help:

  • MYOB's built-in duplicate detection
  • Connector's customer mapping report
  • Excel for comparative analysis

Regular reconciliation prevents customer data from becoming increasingly messy over time.

 

Error Category 3: GST and Tax Code Problems

GST/tax errors are particularly critical for Australian businesses because they create compliance issues, BAS reporting problems, and reconciliation nightmares.

Error Symptoms

Tax-related error messages:

  • "Tax code '[CODE]' not found in MYOB"
  • "Invalid tax code assignment"
  • "GST amount mismatch"
  • "Order total doesn't match line items plus tax"
  • Orders sync, but with incorrect GST codes

 

Why This Happens

Cause 1: Tax Code Mapping Not Configured
Shopify tax rate isn't mapped to the MYOB tax code. Connector doesn't know which MYOB GST code to apply, sync fails.

Cause 2: Mixed Tax Rates on a Single Order
Order contains both GST-inclusive items and GST-free items (fresh food + processed food, or domestic + export shipping). Connector struggles with mixed tax treatment.

Cause 3: Shopify Tax Settings Misaligned with MYOB
Shopify is configured to handle GST one way (tax-inclusive pricing) while MYOB expects different treatment (tax-exclusive). Creates calculation mismatches.

Cause 4: International Orders
Export sales to customers outside Australia should be GST-free, but the connector applies the standard GST code. Creates incorrect tax reporting.

Cause 5: Custom Tax Overrides in Shopify
Manual tax adjustments or override rules in Shopify don't translate properly to MYOB, causing calculation discrepancies.

 

How to Fix

Solution 1: Configure Comprehensive Tax Code Mapping

Map every Shopify tax scenario to correct the MYOB code:

Step 1: Document your tax scenarios:

  • Standard GST (10% on most products)
  • GST-free items (exports, fresh food if applicable)
  • No tax (specific exemptions)
  • Different rates (if any products have special treatment)

Step 2: Ensure matching MYOB tax codes exist:

  • GST (typically "GST" or "N-T")
  • GST Free (typically "FRE" or "GST-Free")
  • Export (typically "EXP" or "Export")
  • Input Taxed (if applicable to your business)

Step 3: Configure connector mapping:

  • Shopify "Australia Tax 10%" → MYOB "GST"
  • Shopify "Exempt" → MYOB "FRE"
  • International orders → MYOB "EXP"

Step 4: Handle product-specific rules:

  • Some connectors allow per-product tax code assignment
  • Map specific products or product types to appropriate codes
  • Configure rules based on customer location (domestic vs international)

Step 5: Test extensively:

  • Process test order with standard GST items
  • Test GST-free products
  • Test international order
  • Verify MYOB entries show correct tax codes
  • Confirm the BAS summary report reflects the correct tax treatment

 

Solution 2: Fix Tax-Inclusive vs Tax-Exclusive Mismatch

Align Shopify and MYOB tax treatment:

Australian standard: Prices displayed to customers include GST (tax-inclusive)

Shopify configuration:

  • Admin → Settings → Taxes and Duties
  • Verify "All prices include tax" is enabled for the Australian tax zone
  • Confirm tax rate configured as 10% GST

MYOB configuration:

  • Verify tax codes configured as tax-inclusive
  • For the GST code, ensure "Tax Inclusive" is selected
  • Rates should be 10/110 (not 10/100) for inclusive calculation

Connector verification:

  • Confirm the connector understands prices are tax-inclusive
  • Test order shows correct GST extraction (not addition)
  • Example: $110 sale should show $100 + $10 GST, not $110 + $11 GST

If a mismatch occurs:

  • Customer charged $110 total
  • MYOB entry might show $110 + $11 GST = $121 (wrong!)
  • Or $100 revenue when the customer actually paid $110 (also wrong!)

Fixing this requires careful configuration adjustment and potentially reprocessing affected orders.

 

Solution 3: Handle International Orders Correctly

Ensure export sales receive proper tax treatment:

Shopify setup:

  • Configure international shipping zones with zero tax
  • Or use tax override rules for international destinations

Connector configuration:

  • Map international orders to MYOB "Export" or "GST-Free" code
  • Can typically use customer country as trigger
  • Test with sample international order

MYOB verification:

  • International sale shows zero GST
  • Correct tax code applied
  • BAS reporting excludes from GST collected

Important: Even though international sales are GST-free, you still report them in your BAS (G1 section). Ensure they're coded correctly for compliance.

 

Solution 4: Product-Level Tax Code Assignment

For businesses with mixed tax products:

Scenario: Selling both GST-applicable processed foods and GST-free fresh foods

Solution approach:

  • Tag products in Shopify by tax treatment
  • Configure the connector to assign tax codes based on tags
  • Or use product type or collection as a trigger

Example configuration:

  • Products tagged "Fresh" → MYOB GST-Free code
  • Products tagged "Processed" → MYOB GST code
  • Default for untagged → GST code

Testing critical:

  • Order with mixed fresh/processed products
  • Verify each line item has correct tax code
  • Confirm total GST calculation matches
  • Check BAS reporting shows items in correct categories

 

Solution 5: Manual Tax Override Handling

For businesses that occasionally adjust tax manually:

Configure: Connector should respect Shopify's final tax calculation rather than recalculating

Option A: Sync Shopify tax exactly

  • Whatever tax Shopify charged, sync to MYOB exactly
  • Simplest but may create odd tax codes or amounts

Option B: Flag for manual review

  • Detect when tax doesn't match expected calculation
  • Pause sync for manual review and adjustment
  • Provides quality control for unusual situations

For most businesses: Option A works fine and avoids unnecessary manual intervention.

 

Prevention: Tax Configuration Checklist

Set up correctly from the beginning:

□ Shopify taxes configured for tax-inclusive GST
□ All products assigned the correct tax status
□ MYOB tax codes properly configured
□ Connector mapping complete for all scenarios
□ International shipping rules exclude GST
□ Test orders processed for every tax scenario
□ Monthly BAS reconciliation to catch issues early

Proper tax configuration is non-negotiable for Australian businesses—get expert help if uncertain.

 

Error Category 4: Payment and Financial Reconciliation Issues

Payment-related errors are among the most frustrating because they create reconciliation problems that compound over time if not addressed quickly.

Error Symptoms

Payment sync error indicators:

  • "Payment method not mapped"
  • "Bank account not found"
  • "Payment amount mismatch"
  • Orders sync, but payments don't match
  • Bank reconciliation shows gaps or duplicates
  • Clearing account balances growing over time

 

Why This Happens

Cause 1: Payment Gateway Not Mapped
Shopify Payments, PayPal, Afterpay, or other gateways aren't mapped to MYOB bank accounts. The connector doesn't know where to record the payment, syncs the invoice, but not the payment.

Cause 2: Batch Deposit Timing Mismatch
Shopify Payments batches deposits over 2-3 days. Individual orders sync immediately, but bank deposit happens days later. Matching becomes complicated.

Cause 3: Payment Fees Not Handled
Payment gateway fees (2.5% + $0.30 for Shopify Payments, 2.9% + $0.30 for PayPal) aren't recorded in MYOB, causing net deposit amounts to not match invoice totals.

Cause 4: Refunds Not Syncing Properly
Customer refund processed in Shopify doesn't create a corresponding credit note in MYOB. The customer account shows an incorrect balance.

Cause 5: Split Payments
Order paid with gift card + credit card, or partial payment scenarios. Connector doesn't handle complex payment splits.

 

How to Fix

Solution 1: Proper Payment Gateway Mapping

Map each payment method to correct MYOB accounts:

Step 1: Identify your payment methods:

  • Shopify Payments
  • PayPal
  • Afterpay/Zip
  • Bank transfer/direct deposit
  • Cash (if retail POS)
  • Gift cards/store credit

Step 2: Create or identify MYOB accounts:

Option A: Direct to bank account

  • Map each gateway directly to the actual bank account
  • Works if bank deposits are timely and consistent
  • Simplest approach

Option B: Clearing accounts (recommended)

  • Create a MYOB clearing account for each gateway
  • Example: "Shopify Payments Clearing"
  • Payments post to the clearing account first
  • Match to the actual bank deposit separately

Step 3: Configure connector payment mapping:

  • Shopify Payments → MYOB "Shopify Clearing" account
  • PayPal → MYOB "PayPal Clearing" account
  • Map each method systematically

Step 4: Test payment sync:

  • Process test order with each payment method
  • Verify payment appears in the correct MYOB account
  • Check the invoice shows as paid
  • Confirm amounts match

Why is clearing accounts recommended? Payment timing and fee deductions make direct-to-bank complicated. Clearing accounts let you record full order payment immediately, then reconcile actual net deposit when it arrives in bank.

 

Solution 2: Handle Payment Gateway Fees

Record fees properly for accurate profitability:

Approach A: Net recording

  • Record net payment (gross - fees) in MYOB
  • Simplest but doesn't track fee expense
  • Payment matches bank deposit automatically

Approach B: Gross recording with fee expense (recommended)

  • Record gross payment amount
  • Create separate expense transaction for fees
  • Accurately tracks payment processing costs
  • Requires configuration or automation

 

Implementation:

Step 1: Create MYOB expense account:

  • "Payment Processing Fees" or "Merchant Fees"
  • Type: Expense
  • Tax Code: FRE (fees are GST-free input)

Step 2: Configure connector to split payment:

  • Record full payment to clearing account
  • Record fee to expense account
  • Net amount available for bank reconciliation

Step 3: Verify accounting flow:

  • Customer payment: $100 to Shopify Clearing
  • Gateway fee: $3.20 to Merchant Fees
  • Bank deposit: $96.80 to Business Bank Account
  • Clearing account nets to zero after reconciliation

Benefit: Accurate expense tracking, proper profitability analysis, and clean reconciliation.

 

Solution 3: Refund Processing

Ensure refunds sync correctly:

Full refund scenario:

Step 1: Process refund in Shopify

Step 2: Connector should automatically:

  • Create MYOB credit note matching original invoice
  • Record refund payment from original payment account
  • Adjust inventory back (if refund due to return)

Step 3: Verify credit note created:

  • Matches original invoice exactly
  • Properly dated
  • Reduces customer account balance
  • Inventory adjusted if return involved

Partial refund scenario:

Complexity: Partial refund (single item from multi-item order) harder to handle

Connector approaches vary:

  • Some create credit note for partial amount
  • Others require manual adjustment
  • May need to manually adjust line items

Best practice: Test partial refund processing during initial setup. If connector doesn't handle well, document manual procedure for team.

 

Solution 4: Complex Payment Handling

Split payments and special scenarios:

Gift card + credit card:

  • Some connectors split into separate payment records
  • Others combine into single payment with notes
  • Verify how your connector handles and if that matches your needs

Layby/payment plans:

  • Multiple partial payments over time
  • Requires careful tracking
  • May need MYOB sales quote → invoice conversion workflow
  • Advanced connectors support, basic connectors might not

Account credit:

  • Using store credit from previous return
  • Should reduce amount requiring payment from bank
  • Verify accounting treatment correct

Manual testing critical: Process representative complex scenarios during testing. Don't discover limitations after going live.

 

Solution 5: Bank Reconciliation Workflow

Establish efficient reconciliation process:

Daily:

  • Review connector sync log for payment errors
  • Note failed payment syncs for investigation

Weekly:

  • Download bank statement transactions
  • Match deposits to clearing account payments
  • Investigate discrepancies immediately
  • Journal entry to move cleared amounts from clearing to bank account

Monthly:

  • Full bank reconciliation in MYOB
  • Clearing accounts should net close to zero
  • Investigate any significant clearing account balances
  • Review payment fee expenses for reasonableness

Automation opportunity: Tools like bank feed integrations can match deposits to clearing accounts automatically, further reducing manual work.

 

Prevention: Payment Configuration Best Practices

□ Use clearing accounts for all payment gateways
□ Configure fee recording from the start
□ Test every payment method during implementation
□ Document refund procedures
□ Establish weekly reconciliation rhythm
□ Monitor clearing account balances monthly
□ Address discrepancies within 48 hours

Payment configuration complexity justifies professional implementation for most businesses—getting this wrong creates months of cleanup work.

Web Ninja's Shopify-MYOB connectors include sophisticated payment handling with clearing accounts, automated fee recording, and comprehensive refund support. Our Australian-specific configuration understands Shopify Payments, PayPal Australia, Afterpay, and other regional payment gateways.

 

Learn More About Web Ninja's Payment Reconciliation Features →

 

[Continue with sections 6-13 covering Inventory Synchronisation, Order Duplication, Diagnostic Tools, Prevention Practices, When to Escalate, Conclusion, FAQ, and Resources...]

 

Conclusion

Data sync errors between Shopify and MYOB are frustrating but manageable once you understand the root causes and systematic resolution approaches. The six error categories—product mapping, customer records, GST codes, payment handling, inventory synchronisation, and order duplication—account for 95%+ of sync problems Australian eCommerce businesses encounter.

The key to transformation from constant firefighting to reliable automation is addressing root causes rather than just symptoms. Fixing individual failed orders doesn't help if the underlying configuration issue causes the same error on tomorrow's orders. Invest time in proper mapping configuration, establish data governance processes, and implement prevention best practices.

For businesses processing 100+ orders weekly, even occasional sync errors create significant operational drag. Professional connector configuration and ongoing support prevent most problems before they occur and resolve issues quickly when they do appear. The cost of expert setup and support is negligible compared to the time and stress saved troubleshooting mysterious errors.

If you're currently struggling with Shopify-MYOB sync errors, work systematically through the diagnostic methodology in this guide. Most issues are resolvable with configuration adjustments rather than requiring connector changes. However, if you've addressed obvious issues and problems persist, escalating to professional integration support often resolves in hours what might take weeks of DIY troubleshooting.

Web Ninja's Shopify-MYOB integration specialists have resolved thousands of sync errors for Australian eCommerce businesses. We understand the nuances of Australian GST, Shopify Payments, MYOB versions, and the common configuration oversights that create problems. Our team can diagnose issues quickly, implement permanent fixes, and optimize your configuration for reliable long-term operation.

 

Get Expert Help Resolving Your Shopify-MYOB Sync Errors →

 

FAQ

How do I know if sync errors are connector problems vs configuration issues?

Configuration issues show patterns—same type of error recurring with specific products, customers, or order characteristics. Connector problems are typically random, affect many orders simultaneously, or started immediately after platform updates. Check connector status page for known issues. If problems are systematic and patterned, likely configuration. If random and widespread, likely connector or platform issue.

Should I try to fix errors manually or wait for root cause resolution?

For immediate orders, manually process to unblock customers and fulfillment. Simultaneously investigate root cause for permanent fix. Don't just manually process hundreds of orders without fixing underlying issue—you'll waste enormous time. Fix configuration, then address backlog of failed orders by re-syncing if possible.

How long should I spend troubleshooting before getting professional help?

If you've invested 4-6 hours troubleshooting without clear progress, escalate to connector support or integration professional. Your time is valuable, and experts can often diagnose in 30 minutes what might take you days to uncover. For critical payment or tax issues affecting compliance, escalate immediately rather than experimenting.

Can sync errors cause ATO compliance problems?

Yes, particularly GST coding errors. If GST errors go unnoticed and you prepare BAS from incorrect data, you risk audit issues. Monthly reconciliation between Shopify sales reports and MYOB GST reports helps catch problems before BAS lodgement. If you discover historical tax coding errors, work with accountant to determine if correction/amendment needed.

What's the acceptable error rate for eCommerce-accounting sync?

Quality connectors with proper configuration should achieve 98-99%+ success rates. 1-2% of orders requiring manual review due to edge cases is normal. If you're seeing 5%+ error rates, configuration definitely needs optimization. 10%+ indicates serious problems requiring immediate attention. Track error rate monthly to ensure it stays acceptably low.

Do I need to reprocess historical orders after fixing the configuration?

Depends on error type. Product mapping fixes can often be applied to failed orders by re-syncing. Customer or payment errors might require manual cleanup. GST coding errors definitely need correction for compliance. Generally: fix configuration, then tackle backlog systematically. For tax errors, prioritise current fiscal year corrections.

      

Resources

For more information about Shopify-MYOB integration and troubleshooting:

  1. Shopify Help Center - API & Integration Support
    https://help.shopify.com/en/api
    Official documentation for Shopify's API and integration capabilities
  2. MYOB API Documentation
    https://developer.myob.com/api/
    Technical documentation for MYOB's API across AccountRight, Essentials, and Exo
  3. Australian Taxation Office - GST for Online Businesses
    https://www.ato.gov.au/business/gst/
    Official guidance on GST compliance for eCommerce businesses
  4. Web Ninja - Shopify-MYOB Integration Support
    https://webninja.com.au/shopify-connector?hsLang=en
    Australian-specific integration support and troubleshooting services

Share this post