Decoding Dynamics GP: Fix PAYG & BAS Error Messages Like a Pro

Table of Contents

Hey Dynamics GP users! Ever get stuck staring at confusing PAYG and BAS error messages? Don’t worry, we’ve all been there. This guide breaks down those cryptic codes and helps you troubleshoot like a pro. Let’s get those errors fixed and get back to business!

image just illustration

Common Dynamics GP PAYG and BAS Errors: A Troubleshooting Guide¶

Navigating the world of Dynamics GP can sometimes feel like deciphering a secret code, especially when it comes to PAYG (Pay As You Go) and BAS (Business Activity Statement) errors. But fear not! We’re here to decode those pesky messages and empower you to fix them like a seasoned expert.

GST and PAYG Date Errors¶

• 01 GST Processing Start Date is after the End Date: Double-check your GST processing date range. Sounds simple, but it’s a common mistake! Make sure the start date is before the end date.

• 02 PAYG Processing Start Date is after the End Date: Same as above, but for PAYG. Verify that your processing date range is correctly set.

History Transaction Exclusions¶

• 03 History Transactions excluded from GST Processing: This message indicates that historical transactions weren’t included in your GST processing. Check your setup and ensure historical data is included if needed.

• 04 History Transactions excluded from PAYG Processing: Similar to the GST exclusion message, this means historical PAYG transactions were skipped. Review your configuration and adjust accordingly.

RM Transaction Errors (SOP and Invoicing)¶

• 05 RM Transaction appears to come from SOP but is not found in SOP tables: Looks like a Receivables Management (RM) transaction is pointing to a Sales Order Processing (SOP) transaction that’s gone missing. Time for some detective work! Investigate the SOP tables for the missing transaction.

• 06 RM Transaction appears to come from Invoicing but is not found in Invoicing tables: This indicates a similar problem with Invoicing transactions. The RM transaction is referencing an invoice that can’t be found. Dive into the Invoicing tables and try to locate the missing invoice.

• 08 RM Transaction comes from SOP but the SOP transaction is voided: You’ve got an RM transaction linked to a voided SOP transaction. This can create discrepancies. You might need to reverse or adjust the RM transaction.

• 09 RM Transaction comes from Invoicing but the Invoicing transaction is voided: Just like the voided SOP issue, this points to a voided Invoicing transaction linked to an RM transaction. Review and correct as necessary.

PM Transaction Errors (POP)¶

• 07 PM Transaction appears to come from POP but is not found in POP tables: A Payables Management (PM) transaction seems to originate from Purchasing Order Processing (POP), but the corresponding POP transaction is nowhere to be found. Track down the missing POP transaction.

• 10 PM Transaction comes from POP but the POP transaction is voided: The PM transaction is linked to a voided POP transaction. This needs to be addressed to reconcile the records.

POP and SOP Transaction Errors in PM and RM¶

• 13 POP Transaction not found in PM tables: A POP transaction is missing from the PM tables. This can disrupt the flow between purchasing and payables. Investigate the PM tables.

• 14 POP Transaction found in PM tables but PM transaction is voided: The POP transaction exists in PM, but it’s been voided. This can affect related processes. Check for discrepancies.

• 15 POP Transaction found in PM tables but PM transaction is not from POP: Hmm, something’s off. The PM transaction associated with the POP transaction isn’t originating from POP. This requires further investigation.

• 16 SOP Transaction not found in RM tables: An SOP transaction is missing from the RM tables. This can create a disconnect between sales orders and receivables.

• 17 SOP Transaction found in RM tables but RM transaction is voided: The SOP transaction is in RM, but it’s voided, potentially leading to inconsistencies.

• 18 SOP Transaction found in RM tables but RM transaction is not from SOP: The RM transaction linked to the SOP transaction isn’t actually from SOP. Double-check your data.

Invoicing Transaction Errors in RM¶

• 19 Invoicing Transaction not found in RM tables: An Invoicing transaction is absent from the RM tables, which can impact your receivables tracking.

• 20 Invoicing Transaction found in RM tables but RM transaction is voided: The Invoicing transaction exists in RM but is voided, which may need correction.

• 21 Invoicing Transaction found in RM tables but RM transaction is not from Invoicing: The RM transaction linked to the Invoicing transaction isn’t actually coming from Invoicing. This needs further review.

Tax and Calculation Errors¶

Tax Invoice and Detail Issues:

• 11 Tax Invoice Required but not Received, overridden by BAS Option setting: While a tax invoice was required, it wasn’t received. However, this has been overridden by your BAS options. Review your settings to ensure they align with your requirements.

• 12 Transaction contains Tax Amount but no Tax Detail information is available: You have a tax amount, but the supporting details are missing. Investigate why the tax details are absent.

GL and Tax Detail Errors:

• 22 GL Tax Transaction not found in GL tables: A General Ledger (GL) tax transaction can’t be located in the GL tables. Track down the missing GL transaction.

• 23-25 Tax Detail Total Amount is zero with a non zero Tax Detail Tax Amount (1 Field, G Field, W Field): These messages flag inconsistencies where the total tax amount is zero while a tax amount exists in a specific field. Check the tax detail calculations.

• 26-27 Tax Detail Taxable Amount is zero with a non zero Tax Detail Tax Amount (1 Field, G Field): The taxable amount is zero, but a tax amount is present. Review the taxable amount calculations.

• 28-29 Tax Detail Taxable Amount is greater than Tax Detail Total Amount (1 Field, G Field): The taxable amount shouldn’t exceed the total amount. Verify your calculations.

• 30-31 Tax Detail Total Amount is zero with a non zero Tax Detail Taxable Amount (1 Field, G Field): You have a taxable amount, but the total amount is zero. This needs further investigation.

Reporting and Calculation Errors:

• 32 Not Reporting using Tax Collected & Paid amounts (Manual Totaling), this mode is recommended: The system suggests switching to reporting using tax collected and paid amounts. Consider making this change for better accuracy.

• 33-34 Calculated Transaction Total / Tax Total for field G6 is not equal to field G1 - field G5: The calculated totals for G6 don’t match the expected result of G1 minus G5. Review the calculations for these fields.

• 35 Calculated Transaction Total for field G17 is not equal to field G12 - field G16: Similar to the G6 issue, the calculation for G17 (G12 minus G16) isn’t producing the expected result.

What’s Next?¶

This comprehensive guide equips you with the knowledge to tackle Dynamics GP PAYG and BAS errors head-on. Remember, troubleshooting is a process of elimination. Start with the most obvious solutions and work your way through the possibilities. If you’re still scratching your head after trying these tips, don’t hesitate to reach out to your Dynamics GP support team or online forums for expert assistance.

We’d love to hear your experiences! Share your success stories, lingering questions, or additional tips in the comments below. Let’s make the Dynamics GP community a hub of shared knowledge and support!