GST Notice Mismatch Software Testing

I have built a notice-mismatch investigation tool that should pull real GST notices directly from our accounting software, spot mismatches, suggest explanations for every discrepancy, and then post the final entries back into the books.

What I need now is a fresh set of eyes to put the system through its paces with actual GST notices. You will:

• Feed a representative sample of genuine GST notices into the platform through the accounting-software connector.
• Validate that the notice mismatch identification engine flags every difference correctly.
• Check whether the explanation-finding module surfaces a clear, logical reason for each mismatch.
• Confirm that once a mismatch is resolved, the book-processing routine updates ledgers exactly as expected.

Please document any bugs, false positives/negatives, or confusing workflows you encounter and suggest practical fixes or improvements. Screenshots or short screen recordings of issues are ideal.

Acceptance criteria
• All three feature areas—mismatch identification, explanation finding, and book processing—have been exercised with real data.
• A concise report lists each defect or UX hurdle, the notice that triggered it, and steps to reproduce.
• Final confirmation that the system can handle a full end-to-end GST notice cycle without manual intervention.

If you are comfortable working with GST-related data and can test against live accounting-software feeds, your feedback will be invaluable.