Mow Ops Accounting+Stripe Integration Testing
Budget: $30 – $250 AUD
Important Before Bidding
Placeholder bids and bot-generated proposals are not acceptable. The full scope is provided, so bid the real cost. Do not submit a low placeholder price then try to renegotiate after award.
You must be able to work independently with common sense. This task requires someone who can create/use accounting test accounts, follow scenarios, find issues, record evidence, and complete the work without step-by-step hand-holding.
Brief: Mow Ops Accounting + Stripe Connect Integration Testing
I need an independent tester to validate Mow Ops customer, invoice, payment, accounting sync, and Stripe Connect flows.
I will provide a Mow Ops test account. You must provide your own test/trial/demo accounts for:
- MYOB AccountRight
- Xero
- Intuit QuickBooks Online
- Stripe Connect
Australian accounting setup is preferred where possible for GST/tax code relevance. Use test/sandbox/demo mode where possible. Do not use real customer data or live production payments.
Goal
Confirm Mow Ops connects correctly to each provider, syncs customers, invoices, payments, provider status, handles errors safely, and avoids duplicate records.
Test against:
- Mow Ops + MYOB
- Mow Ops + Xero
- Mow Ops + Intuit QuickBooks Online
- Mow Ops + Stripe Connect
1. Mow Ops Setup
Confirm the supplied Mow Ops account can:
- Log in
- Access correct tenant/workspace
- Create/edit clients
- Create/edit properties
- Create and finalise invoices
- Create invoices with normal service lines, surcharges, zero-value/no-charge lines, and payment test cases
Expected: data saves correctly, invoice numbers/totals are correct, no wrong-tenant data appears.
Fail if: login fails, invoice cannot be finalised, totals are wrong, links are missing, wrong tenant data appears.
2. Provider Connection
For MYOB, Xero, QuickBooks, and Stripe Connect:
- Start connection from Mow Ops
- Complete OAuth/onboarding/consent
- Confirm correct organisation/company file/account
- Refresh status
- Disconnect/reconnect
- Confirm token refresh/re-auth works where applicable
Expected: correct provider identity stored, reconnect/refresh works, disconnect blocks sync.
Fail if: wrong account linked, bad callback, token failure, duplicate active connections, disconnected provider still used.
3. Reference Data / Setup
For MYOB, Xero, and QuickBooks:
- Confirm accounts, tax codes, items, and customers/contacts load
- Save income account, tax code, payment/cash/clearing account settings
- Sync provider items into Mow Ops
- For MYOB, verify invoice layouts and form templates
Expected: data loads, settings persist, items are available for invoice mapping.
Fail if: lists are empty when provider has data, invalid IDs save, settings do not persist, MYOB layout/template is wrong.
4. Customer / Contact Sync
For Xero Contacts, QuickBooks Customers, and MYOB Customers:
- Export Mow Ops client to provider
- Confirm provider customer/contact is created
- Confirm Mow Ops stores external provider link
- Import or match existing provider customer/contact
- Confirm duplicates are avoided
- Confirm one provider link is not silently overwritten by another
Expected: name, email, phone, address, and external link are correct.
Fail if: wrong customer linked, duplicate created, provider link overwritten, missing external ID, inactive/supplier contacts imported incorrectly.
5. Invoice Sync
For MYOB, Xero, and QuickBooks:
- Sync finalised Mow Ops invoice
- Confirm provider invoice is created
- Confirm external invoice ID is stored
- Check invoice number/reference, customer, dates, due date, status, lines, quantities, rates, totals, GST/tax, surcharges, zero-value/no-charge lines
- Re-run sync and confirm no duplicate invoice
MYOB-specific: check invoice layout, form template, PDF where available, and void/credit-note handling where safe.
Expected: provider invoice materially matches Mow Ops and re-sync is idempotent.
Fail if: wrong customer/number/date/tax/total, duplicate invoice, rejected zero-value line, wrong MYOB layout/template.
6. Provider Invoice Email
For MYOB, Xero, and QuickBooks:
- Send unsynced invoice through provider delivery
- Confirm Mow Ops syncs first, then sends provider email
- Send already linked invoice
- Confirm delivery status and recipient handling
- Test retryable/non-retryable errors
Expected: provider send is triggered, Mow Ops status updates, errors are clear.
Fail if: email sends before invoice exists, wrong recipient, Mow Ops says sent but provider does not, raw/unhelpful errors.
7. Payment Sync
For MYOB, Xero, and QuickBooks:
- Record full, partial, and multiple payments in Mow Ops
- Confirm payments post to correct provider invoice
- Confirm remaining balance, date, method, reference, and amount
- Retry payment sync and confirm no duplicate payment
Expected: payments allocate correctly and reconcile.
Fail if: payment not linked, wrong account/date/reference/amount, duplicate payment, silent failure.
8. Provider Reconciliation
For MYOB, Xero, and QuickBooks:
- Pay/part-pay invoice in provider and confirm Mow Ops reconciles
- Confirm provider balance/status reflects in Mow Ops
- Test credit/adjustment/reversal/refund where supported
- Re-run reconciliation and confirm no duplicate imported payment
Expected: Mow Ops status/balance reflects provider state.
Fail if: provider-paid invoice remains unpaid, partial marked fully paid, duplicate import, reversal ignored, balances differ.
9. Webhooks / Background Sync
For Xero and QuickBooks:
- Verify webhook/change-event handling where available
- Confirm invoice/payment changes trigger reconciliation
- Confirm unknown/invalid tenant events skip safely
- Confirm queued events process once
For MYOB: confirm polling/status reconciliation works.
Fail if: wrong tenant updated, events stuck, duplicate processing, unsafe event handling.
10. Stripe Connect
For Stripe Connect:
- Connect account
- Confirm connected account ID and charges/payout capability
- Refresh status
- Generate dashboard/login link
- Disconnect/reconnect
- Confirm payment flow is blocked when disconnected
If Tap to Pay/Terminal testing is available:
- Check readiness
- List/create Terminal locations
- Create connection token
- Create PaymentIntent for invoice amount
- Check metadata has Mow Ops invoice/payment IDs
- Capture/cancel payment
- Confirm Mow Ops invoice/payment state updates
Expected: Stripe account and payments map to correct Mow Ops tenant/invoice.
Fail if: wrong account, wrong amount, missing metadata, Stripe paid but Mow Ops unpaid, invoice locked after cancellation.
11. Stripe Events
Where possible, test/verify:
- payment_intent.succeeded
- payment_intent.payment_failed
- payment_intent.canceled
- charge.refunded
- charge.dispute.*
- payout.paid
Expected: payments, failures, refunds, disputes, and payouts update/record correctly without duplication.
12. Cross-System Tests
Where possible, test:
- Stripe payment then Xero payment sync
- Stripe payment then QuickBooks payment sync
- Stripe payment then MYOB payment sync
- Stripe refund after accounting sync
- Stripe payout with Xero/QuickBooks connected
Expected: Stripe creates Mow Ops payment, then Mow Ops syncs/reconciles accounting provider payment correctly.
General Failure Criteria
Fail if any occur:
- Wrong provider/company/account connected
- Cross-tenant data visible
- Duplicate invoices, payments, customers, contacts, or items
- Mow Ops says synced/sent/paid but provider disagrees
- Provider says paid/refunded/disputed but Mow Ops does not reconcile
- Invoice totals, GST/tax, due dates, customer, or lines are wrong
- Disconnected provider still used
- Failed sync has unclear error
- Retry creates duplicates
- Payment captured but invoice remains unpaid/locked
Out Of Scope As Standalone Sync Objects
Properties, bookings/jobs, runsheets, quotes, job reports, equipment, areas, and schedules. These may affect invoice content but are not tested as separate synced records.
Deliverables
Provide:
1. Completed test matrix for MYOB, Xero, QuickBooks, and Stripe Connect.
2. Pass/fail for each item.
3. Screenshots/video showing Mow Ops record, provider record, and matching IDs where available.
4. Defect list with steps, expected result, actual result, provider, severity, and evidence.
5. Final summary of passed/failed providers, limitations, and incomplete tests with reasons.
Proposal Requirements
Confirm you can provide your own MYOB, Xero, QuickBooks, and Stripe Connect test/demo accounts, can test Australian GST where possible, understand this is testing not development, and will provide evidence for each pass/fail item. Ask all questions in your proposal before acceptance.
Placeholder bids and bot-generated proposals are not acceptable. The full scope is provided, so bid the real cost. Do not submit a low placeholder price then try to renegotiate after award.
You must be able to work independently with common sense. This task requires someone who can create/use accounting test accounts, follow scenarios, find issues, record evidence, and complete the work without step-by-step hand-holding.
Brief: Mow Ops Accounting + Stripe Connect Integration Testing
I need an independent tester to validate Mow Ops customer, invoice, payment, accounting sync, and Stripe Connect flows.
I will provide a Mow Ops test account. You must provide your own test/trial/demo accounts for:
- MYOB AccountRight
- Xero
- Intuit QuickBooks Online
- Stripe Connect
Australian accounting setup is preferred where possible for GST/tax code relevance. Use test/sandbox/demo mode where possible. Do not use real customer data or live production payments.
Goal
Confirm Mow Ops connects correctly to each provider, syncs customers, invoices, payments, provider status, handles errors safely, and avoids duplicate records.
Test against:
- Mow Ops + MYOB
- Mow Ops + Xero
- Mow Ops + Intuit QuickBooks Online
- Mow Ops + Stripe Connect
1. Mow Ops Setup
Confirm the supplied Mow Ops account can:
- Log in
- Access correct tenant/workspace
- Create/edit clients
- Create/edit properties
- Create and finalise invoices
- Create invoices with normal service lines, surcharges, zero-value/no-charge lines, and payment test cases
Expected: data saves correctly, invoice numbers/totals are correct, no wrong-tenant data appears.
Fail if: login fails, invoice cannot be finalised, totals are wrong, links are missing, wrong tenant data appears.
2. Provider Connection
For MYOB, Xero, QuickBooks, and Stripe Connect:
- Start connection from Mow Ops
- Complete OAuth/onboarding/consent
- Confirm correct organisation/company file/account
- Refresh status
- Disconnect/reconnect
- Confirm token refresh/re-auth works where applicable
Expected: correct provider identity stored, reconnect/refresh works, disconnect blocks sync.
Fail if: wrong account linked, bad callback, token failure, duplicate active connections, disconnected provider still used.
3. Reference Data / Setup
For MYOB, Xero, and QuickBooks:
- Confirm accounts, tax codes, items, and customers/contacts load
- Save income account, tax code, payment/cash/clearing account settings
- Sync provider items into Mow Ops
- For MYOB, verify invoice layouts and form templates
Expected: data loads, settings persist, items are available for invoice mapping.
Fail if: lists are empty when provider has data, invalid IDs save, settings do not persist, MYOB layout/template is wrong.
4. Customer / Contact Sync
For Xero Contacts, QuickBooks Customers, and MYOB Customers:
- Export Mow Ops client to provider
- Confirm provider customer/contact is created
- Confirm Mow Ops stores external provider link
- Import or match existing provider customer/contact
- Confirm duplicates are avoided
- Confirm one provider link is not silently overwritten by another
Expected: name, email, phone, address, and external link are correct.
Fail if: wrong customer linked, duplicate created, provider link overwritten, missing external ID, inactive/supplier contacts imported incorrectly.
5. Invoice Sync
For MYOB, Xero, and QuickBooks:
- Sync finalised Mow Ops invoice
- Confirm provider invoice is created
- Confirm external invoice ID is stored
- Check invoice number/reference, customer, dates, due date, status, lines, quantities, rates, totals, GST/tax, surcharges, zero-value/no-charge lines
- Re-run sync and confirm no duplicate invoice
MYOB-specific: check invoice layout, form template, PDF where available, and void/credit-note handling where safe.
Expected: provider invoice materially matches Mow Ops and re-sync is idempotent.
Fail if: wrong customer/number/date/tax/total, duplicate invoice, rejected zero-value line, wrong MYOB layout/template.
6. Provider Invoice Email
For MYOB, Xero, and QuickBooks:
- Send unsynced invoice through provider delivery
- Confirm Mow Ops syncs first, then sends provider email
- Send already linked invoice
- Confirm delivery status and recipient handling
- Test retryable/non-retryable errors
Expected: provider send is triggered, Mow Ops status updates, errors are clear.
Fail if: email sends before invoice exists, wrong recipient, Mow Ops says sent but provider does not, raw/unhelpful errors.
7. Payment Sync
For MYOB, Xero, and QuickBooks:
- Record full, partial, and multiple payments in Mow Ops
- Confirm payments post to correct provider invoice
- Confirm remaining balance, date, method, reference, and amount
- Retry payment sync and confirm no duplicate payment
Expected: payments allocate correctly and reconcile.
Fail if: payment not linked, wrong account/date/reference/amount, duplicate payment, silent failure.
8. Provider Reconciliation
For MYOB, Xero, and QuickBooks:
- Pay/part-pay invoice in provider and confirm Mow Ops reconciles
- Confirm provider balance/status reflects in Mow Ops
- Test credit/adjustment/reversal/refund where supported
- Re-run reconciliation and confirm no duplicate imported payment
Expected: Mow Ops status/balance reflects provider state.
Fail if: provider-paid invoice remains unpaid, partial marked fully paid, duplicate import, reversal ignored, balances differ.
9. Webhooks / Background Sync
For Xero and QuickBooks:
- Verify webhook/change-event handling where available
- Confirm invoice/payment changes trigger reconciliation
- Confirm unknown/invalid tenant events skip safely
- Confirm queued events process once
For MYOB: confirm polling/status reconciliation works.
Fail if: wrong tenant updated, events stuck, duplicate processing, unsafe event handling.
10. Stripe Connect
For Stripe Connect:
- Connect account
- Confirm connected account ID and charges/payout capability
- Refresh status
- Generate dashboard/login link
- Disconnect/reconnect
- Confirm payment flow is blocked when disconnected
If Tap to Pay/Terminal testing is available:
- Check readiness
- List/create Terminal locations
- Create connection token
- Create PaymentIntent for invoice amount
- Check metadata has Mow Ops invoice/payment IDs
- Capture/cancel payment
- Confirm Mow Ops invoice/payment state updates
Expected: Stripe account and payments map to correct Mow Ops tenant/invoice.
Fail if: wrong account, wrong amount, missing metadata, Stripe paid but Mow Ops unpaid, invoice locked after cancellation.
11. Stripe Events
Where possible, test/verify:
- payment_intent.succeeded
- payment_intent.payment_failed
- payment_intent.canceled
- charge.refunded
- charge.dispute.*
- payout.paid
Expected: payments, failures, refunds, disputes, and payouts update/record correctly without duplication.
12. Cross-System Tests
Where possible, test:
- Stripe payment then Xero payment sync
- Stripe payment then QuickBooks payment sync
- Stripe payment then MYOB payment sync
- Stripe refund after accounting sync
- Stripe payout with Xero/QuickBooks connected
Expected: Stripe creates Mow Ops payment, then Mow Ops syncs/reconciles accounting provider payment correctly.
General Failure Criteria
Fail if any occur:
- Wrong provider/company/account connected
- Cross-tenant data visible
- Duplicate invoices, payments, customers, contacts, or items
- Mow Ops says synced/sent/paid but provider disagrees
- Provider says paid/refunded/disputed but Mow Ops does not reconcile
- Invoice totals, GST/tax, due dates, customer, or lines are wrong
- Disconnected provider still used
- Failed sync has unclear error
- Retry creates duplicates
- Payment captured but invoice remains unpaid/locked
Out Of Scope As Standalone Sync Objects
Properties, bookings/jobs, runsheets, quotes, job reports, equipment, areas, and schedules. These may affect invoice content but are not tested as separate synced records.
Deliverables
Provide:
1. Completed test matrix for MYOB, Xero, QuickBooks, and Stripe Connect.
2. Pass/fail for each item.
3. Screenshots/video showing Mow Ops record, provider record, and matching IDs where available.
4. Defect list with steps, expected result, actual result, provider, severity, and evidence.
5. Final summary of passed/failed providers, limitations, and incomplete tests with reasons.
Proposal Requirements
Confirm you can provide your own MYOB, Xero, QuickBooks, and Stripe Connect test/demo accounts, can test Australian GST where possible, understand this is testing not development, and will provide evidence for each pass/fail item. Ask all questions in your proposal before acceptance.