Skip to main content

Test your InvoiceNow workflow from invoice to reconciliation

Test the whole record journey: creation, review, delivery or receipt, accounting and the applicable GST submission. Include a failed record and its recovery. A successful send is one checkpoint; the useful acceptance evidence shows where each record ended up and how your team handles the exceptions.

Written and reviewed by MUST TechnologyReviewed

Agree the test conditions before sending

Confirm the environment, entity, test participants and expected outcomes with your provider. Establish how test documents are identified and whether any action reaches a live recipient or IRAS. Use the provider’s agreed test procedure; do not send invented invoices into production to discover how the connection behaves.

Assign a finance reviewer and a technical contact. For every case, record the source reference, expected result, actual result, evidence location and issue owner. Begin with one simple transaction that everyone can explain, then add cases that reflect your actual business.

IRAS’s onboarding checklist recommends end-to-end testing of different submission flows and a defined support route.

Source: IRAS onboarding guide, readiness check (PDF, page 9).

Include both network and non-network records

Where GST submission applies, receiving a Peppol invoice does not remove the buyer’s purchase-data submission step. The IRAS guide distinguishes these four routes. Use the relevant rows to scope your test pack with the provider.

Submission routes in the IRAS onboarding guide
CaseRouteEvidence to inspect
Sale through InvoiceNowType 1A: copy accompanies network transmission.Recipient delivery and submission outcome.
Purchase through InvoiceNowType 1B: buyer submits purchase data separately.Received bill, recorded purchase and submission.
Sale outside InvoiceNowType 2: seller submits the invoice data.Source invoice and extracted record.
Purchase outside InvoiceNowType 3: buyer submits the invoice data.Source bill and extracted record.

Source: IRAS onboarding guide, submission flows (PDF, page 7).

Illustrative example: your customer receives a regular PDF invoice while your supplier sends a Peppol invoice. Keep two test cases. Check the sales record’s reporting path and the purchase record’s reporting path independently; one successful exchange cannot stand in for both.

Make corrections and retries part of acceptance

Ask the provider to demonstrate a controlled recipient or field-validation failure. The reviewer should be able to find the error, identify the responsible person, correct the source and follow the retry. Verify that the retry does not create a second accounting document or duplicate customer invoice.

  • Compare dates, currency, line values, tax and totals with the agreed sample.
  • Receive a supplier bill and check the review and posting steps.
  • Test a credit note and confirm its relationship to the original invoice.
  • Check how delayed or unknown statuses are investigated before resending.
  • Reconcile payment separately using a controlled sample bank reference.

Keep the original failure and the recovered result together. A final green status alone does not show whether staff can repeat the recovery. Have someone other than the person who configured the system perform the walkthrough.

Reconcile reporting and approve the handover

IRAS distinguishes reportable transactions, exclusions and permitted aggregation. Confirm the treatment of your point-of-sale, simplified tax-invoice and petty-cash records rather than assuming every source document follows the same route.

Invoice data is due by the earlier of filing the relevant GST return or its filing due date. Review the detailed rules for your circumstances with the finance owner.

Source: IRAS guidance on transactions and submission due dates.

For a sample period, compare the source records, accounting entries and submitted data. Investigate differences and retain explanations; IRAS recognises that legitimate reconciliation differences can occur.

Source: IRAS e-Tax Guide, section 12.1: reconciliation (PDF).

Close with a signed test log, assigned open issues and a named support contact. Schedule an operating review after launch. The MUST workflow lab can introduce staff to illustrative sending, receiving and payment scenarios; provider-connected acceptance testing must establish the actual system outcomes.

Official sources

Sources checked on . Use the linked guidance for current requirements and your business’s circumstances.

Give every test an owner and an outcome

Use the implementation kit to organise testing, evidence, handover and go-live responsibilities.

Open the implementation kit
Built and maintained by MUST Technology, Singapore.Explore MUST InvoiceNow

Speak to our team.

Tell us what you need. We reply within 3 business days.

  1. 1Your business
  2. 2Contact details
Your business
Contact details

A conversation about your requirements. No obligation.