QuickBooks for Wild Apricot - Never miss an entry and have peace of mind knowing your books are always up-to-date with accurate transactions. Reduce stress and errors with automated, categorized entries from Wild Apricot to your QuickBooks accounts.
Edge case: When a single WA payment has a valid settlement to an Invoice AND has a remaining unsettled amount, the Unsettled amount of this payment does not show up inside QBO. A single WA payment that is completely unsettled, does show up correctly inside QBO as an unsettled payment.
Current v0.7 QBWA relies on Payment allocations to drive bundles and proper linkage of payments to invoices. This approach is needed for a single payment that settles to multiple invoices.
An "empty" allocation bundle is created for an unsettled payment because no WA Allocation exists. When looking up the Invoice for an empty Allocation bundle, logic in QBWA exists to recognize there is no Invoice and to treat the Payment as Unsettled.
A payment with valid settlement produces an allocation bundle for that related invoice. However, if that Payment has an additional unsettled amount, there is no logic to create a "fake" partial empty allocation bundle. i.e. There is no logic to check that the summed allocation "amounts" equal to the total paid "amount".
This will likely require inserting an iterator and/or aggregator to check the summed amounts and create a "fake" bundle. This may require significant rework of the Core scenario. Leaving this as a known bug for the moment.
Edge case: When a single WA payment has a valid settlement to an Invoice AND has a remaining unsettled amount, the Unsettled amount of this payment does not show up inside QBO. A single WA payment that is completely unsettled, does show up correctly inside QBO as an unsettled payment.
Current v0.7 QBWA relies on Payment allocations to drive bundles and proper linkage of payments to invoices. This approach is needed for a single payment that settles to multiple invoices.
An "empty" allocation bundle is created for an unsettled payment because no WA Allocation exists. When looking up the Invoice for an empty Allocation bundle, logic in QBWA exists to recognize there is no Invoice and to treat the Payment as Unsettled.
A payment with valid settlement produces an allocation bundle for that related invoice. However, if that Payment has an additional unsettled amount, there is no logic to create a "fake" partial empty allocation bundle. i.e. There is no logic to check that the summed allocation "amounts" equal to the total paid "amount".
This will likely require inserting an iterator and/or aggregator to check the summed amounts and create a "fake" bundle. This may require significant rework of the Core scenario. Leaving this as a known bug for the moment.