SaaS Integration Testing For Mow Ops
Budget: $30 – $250 AUD
Mow Ops Accounting Integration Brief
Purpose
Engage a third-party tester to validate the invoice and payment flows between Mow Ops and the connected accounting platforms: MYOB, Xero, and Intuit (QuickBooks Online).
Test Environment
Mow Ops: Pro developer account
SMS: Disabled
Accounting systems: Trial or demo account for each of MYOB, Xero, and Intuit
Out of scope: Tap To Pay
Pre application note.
If you have questions ask them in your proposal Prices submitted are not for negotiations the brief is clear. if you wish to change offer post proposal then offer will be rejected, not here to spend 5 hours discussing a clear connie breif. Provider will be give an account to review but the demo account is available now, for those that want to view before proposal. will be awarded in 11:00 AWST 9/062026
What To Test
Run the same test set against each integration pair:
Mow Ops + MYOB
Mow Ops + Xero
Mow Ops + Intuit
1. Account Connection
Connect each accounting account to Mow Ops
Confirm the correct organisation/company file is selected
Verify permission/consent flow completes successfully
Disconnect and reconnect the integration
Confirm the connection survives token refresh or re-authentication where required
2. Customer / Contact Sync
Create a new customer/contact in Mow Ops and confirm it appears in the accounting platform
Update customer/contact details in Mow Ops and confirm the changes sync
Confirm duplicate customer creation is avoided
Confirm existing contacts are matched correctly on re-sync
3. Invoice Creation
Create a new invoice in Mow Ops and confirm it is created in the accounting platform
Verify invoice number/reference mapping
Verify customer linkage
Verify invoice dates, due dates, and status mapping
Verify line items, quantities, rates, and totals
Verify tax/GST/VAT treatment
Verify discounts, surcharges, and rounding
Verify attachments or invoice PDFs if supported
4. Invoice Updates
Edit an invoice in Mow Ops after initial sync
Confirm changes flow through to the accounting platform
Test status changes such as draft, approved, sent, paid, partially paid, voided, or cancelled where supported
Confirm updates do not create duplicate invoices
5. Payment Processing
Record a full payment in Mow Ops and confirm it posts to the accounting platform
Record a partial payment and confirm the remaining balance is correct
Record multiple payments against one invoice and confirm allocation is correct
Test payment date mapping
Test payment method mapping where available
Test payment reversal, refund, or void handling where supported
Confirm payment references and totals reconcile correctly
6. Sync Behaviour and Error Handling
Confirm the integration handles duplicate submissions safely
Confirm failed syncs return clear errors
Retry a failed sync and confirm it completes cleanly
Confirm manual re-sync works if available
Confirm audit/history entries are visible or traceable
7. Tax and Ledger Mapping
Verify tax codes map correctly between Mow Ops and each accounting system
Verify income account or ledger mapping is correct
Verify the integration handles tax-inclusive and tax-exclusive amounts correctly
8. Negative and Edge Cases
Missing customer details
Missing tax code
Zero-value invoice
Credit note or negative adjustment, if supported
Attempted duplicate invoice number
Connectivity interruption during sync
Acceptance Criteria
Invoices created in Mow Ops appear correctly in the connected accounting system
Payments created in Mow Ops appear correctly and are applied to the right invoice
Updates, partial payments, and error cases behave consistently across MYOB, Xero, and Intuit
No duplicate invoices, duplicate payments, or broken customer links are created
Tap To Pay remains excluded from test coverage
Notes
The tester should perform the same scenarios across all three accounting platforms and record any platform-specific differences.
SMS-dependent flows cannot be validated in this setup because SMS is disabled on the Mow Ops developer account.
As start SaaS is dev.mowops.com.au. you will be responsible for your creation or accessing the the three accounting softwares. All three are to be tested. Australian based so prefer Australian based when you select accounting software so it matches tax codes etc.
Purpose
Engage a third-party tester to validate the invoice and payment flows between Mow Ops and the connected accounting platforms: MYOB, Xero, and Intuit (QuickBooks Online).
Test Environment
Mow Ops: Pro developer account
SMS: Disabled
Accounting systems: Trial or demo account for each of MYOB, Xero, and Intuit
Out of scope: Tap To Pay
Pre application note.
If you have questions ask them in your proposal Prices submitted are not for negotiations the brief is clear. if you wish to change offer post proposal then offer will be rejected, not here to spend 5 hours discussing a clear connie breif. Provider will be give an account to review but the demo account is available now, for those that want to view before proposal. will be awarded in 11:00 AWST 9/062026
What To Test
Run the same test set against each integration pair:
Mow Ops + MYOB
Mow Ops + Xero
Mow Ops + Intuit
1. Account Connection
Connect each accounting account to Mow Ops
Confirm the correct organisation/company file is selected
Verify permission/consent flow completes successfully
Disconnect and reconnect the integration
Confirm the connection survives token refresh or re-authentication where required
2. Customer / Contact Sync
Create a new customer/contact in Mow Ops and confirm it appears in the accounting platform
Update customer/contact details in Mow Ops and confirm the changes sync
Confirm duplicate customer creation is avoided
Confirm existing contacts are matched correctly on re-sync
3. Invoice Creation
Create a new invoice in Mow Ops and confirm it is created in the accounting platform
Verify invoice number/reference mapping
Verify customer linkage
Verify invoice dates, due dates, and status mapping
Verify line items, quantities, rates, and totals
Verify tax/GST/VAT treatment
Verify discounts, surcharges, and rounding
Verify attachments or invoice PDFs if supported
4. Invoice Updates
Edit an invoice in Mow Ops after initial sync
Confirm changes flow through to the accounting platform
Test status changes such as draft, approved, sent, paid, partially paid, voided, or cancelled where supported
Confirm updates do not create duplicate invoices
5. Payment Processing
Record a full payment in Mow Ops and confirm it posts to the accounting platform
Record a partial payment and confirm the remaining balance is correct
Record multiple payments against one invoice and confirm allocation is correct
Test payment date mapping
Test payment method mapping where available
Test payment reversal, refund, or void handling where supported
Confirm payment references and totals reconcile correctly
6. Sync Behaviour and Error Handling
Confirm the integration handles duplicate submissions safely
Confirm failed syncs return clear errors
Retry a failed sync and confirm it completes cleanly
Confirm manual re-sync works if available
Confirm audit/history entries are visible or traceable
7. Tax and Ledger Mapping
Verify tax codes map correctly between Mow Ops and each accounting system
Verify income account or ledger mapping is correct
Verify the integration handles tax-inclusive and tax-exclusive amounts correctly
8. Negative and Edge Cases
Missing customer details
Missing tax code
Zero-value invoice
Credit note or negative adjustment, if supported
Attempted duplicate invoice number
Connectivity interruption during sync
Acceptance Criteria
Invoices created in Mow Ops appear correctly in the connected accounting system
Payments created in Mow Ops appear correctly and are applied to the right invoice
Updates, partial payments, and error cases behave consistently across MYOB, Xero, and Intuit
No duplicate invoices, duplicate payments, or broken customer links are created
Tap To Pay remains excluded from test coverage
Notes
The tester should perform the same scenarios across all three accounting platforms and record any platform-specific differences.
SMS-dependent flows cannot be validated in this setup because SMS is disabled on the Mow Ops developer account.
As start SaaS is dev.mowops.com.au. you will be responsible for your creation or accessing the the three accounting softwares. All three are to be tested. Australian based so prefer Australian based when you select accounting software so it matches tax codes etc.