Skip to content
  • There are no suggestions because the search field is empty.

How to Fix the ‘Index Out of Range’ Error During Payout Posting in Webgility Desktop

This article helps Webgility Desktop users resolve the ‘Index out of range’ error encountered in Webgility Desktop during payout posting, which is often caused by duplicate or deleted credit memos in QuickBooks Desktop that create conflicts during synchronization.

Issue Overview

  • Error: Index out of range

  • Occurs during: Payout posting

  • Common cause: Deleted or duplicate credit memos disrupting Webgility’s payout transaction structure.

Root Cause

This error typically results from:

  • A credit memo that was deleted after being synchronized.

  • A duplicate credit memo is present in QuickBooks but not correctly handled by Webgility.

In a confirmed support case, deleting a problematic credit memo immediately resolved the error.

Steps for Resolution

1. Confirm Error Details

  • Ask the customer for:

    • The exact error message (screenshot preferred).

    • Details of the affected order or payout.

  1. Check for Credit Memo Issues
  • Ask the customer to:

    • Review recent credit memos linked to the error in both QuickBooks Desktop and Webgility Desktop.

    • Look for credit memos that have been modified, duplicated, or deleted recently.

  1. Review Order Sync
  • Sync Sales Receipts and Credit Memos.

  • Review the sync summary to identify:

    • Missing or unmatched records

    • Errors related to credit memos or customer entries

  1. Identify Duplications or Inconsistencies

In QuickBooks:

  • Set an appropriate date range.

  • Compare the results with Webgility’s posted credit memos.

  1. Attempt Payout Posting Again
  • If any problematic credit memos were deleted or corrected:

    • Try posting the payout again in Webgility Desktop.

    • Confirm whether the error has been resolved.