Skip to main content

Try the workflow.
Understand the next step.

Explore four everyday invoice situations. Make a decision, see what changes and learn what your team needs to check.

A safe place to explore.Illustrative sample data. No invoices, payments or business records leave this page.

MUST / Workflow LabIllustrative workspace

From review to delivery.

Review the sample, then follow it to the recipient. Delivery is one step in the process; payment is a separate event.

Customer invoiceDraft

INV-SAMPLE-0042

Customer
Example customer
Currency
SGD
Sample services1 × S$1,000.00S$1,000.00
GST · sample calculationS$90.00
Total including GSTS$1,090.00
Payment statusNot paid

Activity record

  1. Invoice prepared

    The reference, customer, line items and total are ready for a reviewer.

    Current step
  2. Details reviewed

    Sample recipient details and totals have been reviewed. The next step demonstrates delivery.

    Next in this example
  3. Delivery simulated

    The sample is marked received by the customer’s system. No actual invoice has been sent.

    Next in this example

Take this into your implementation

For your setup, agree who reviews the invoice, how delivery is confirmed and who handles a failed transmission.

Resolve the issue before retrying.

An incomplete recipient record needs attention. Confirm the correct details before trying the transmission again.

Customer invoiceNeeds attention

INV-SAMPLE-0043

Customer
Example customer
Currency
SGD
Sample services1 × S$1,000.00S$1,000.00
GST · sample calculationS$90.00
Total including GSTS$1,090.00
Payment statusNot paid

Activity record

  1. Recipient not confirmed

    This sample is missing a confirmed recipient Peppol ID. The invoice has not been delivered.

    Current step
  2. Sample details corrected

    The fictional recipient record is now complete. In a real case, verify the details with the trading partner or directory.

    Next in this example
  3. Retry simulated

    The corrected sample is marked delivered. Your real provider determines the retry and duplicate-check procedure.

    Next in this example

Take this into your implementation

Check the trading partner’s registered Peppol details and supported document type. Follow your provider’s retry process to avoid duplicates.

Received does not mean approved.

A structured invoice can arrive in the inbox while still needing a business review. Keep that approval step visible.

Supplier billReceived as draft

BILL-SAMPLE-0086

Supplier
Example supplier
Currency
SGD
Sample services1 × S$1,000.00S$1,000.00
GST · sample calculationS$90.00
Total including GSTS$1,090.00
Payment statusNot authorised

Activity record

  1. Sample bill received

    The supplier bill is available for review. Receipt alone does not approve the purchase or authorise payment.

    Current step
  2. Purchase details checked

    This example assumes the supplier, purchase reference and totals match the supporting records.

    Next in this example
  3. Approval recorded

    The sample is approved for posting. Payment authorisation remains a separate control.

    Next in this example

Take this into your implementation

Match the bill to the purchase and your approval policy. Verify bank-detail changes through your usual trusted channel before arranging payment.

Delivered and paid are different.

Start with a delivered invoice. Match a sample receipt before recording the payment against it.

Customer invoiceDelivered · sample

INV-SAMPLE-0042

Customer
Example customer
Currency
SGD
Sample services1 × S$1,000.00S$1,000.00
GST · sample calculationS$90.00
Total including GSTS$1,090.00
Payment statusAwaiting payment

Activity record

  1. Delivery already recorded

    The customer’s system has received the sample invoice. No payment is recorded yet.

    Current step
  2. Sample receipt matched

    A fictional receipt for S$1,090.00 matches this sample invoice. No bank account has been accessed.

    Next in this example
  3. Sample payment recorded

    The sample payment status is now paid. This action moves no money and changes no real records.

    Next in this example

Take this into your implementation

Reconcile payment using bank or payment records. A Peppol delivery status by itself is not evidence that money has arrived.

These examples illustrate business decisions, not a live product connection. Confirm your provider’s actual workflow, registration and GST submission setup. GST submission is a separate requirement where applicable and is not demonstrated by a delivery status here.

Turn the walkthrough into your plan.

Check where your business stands, then use the implementation kit to assign the work.

Check my readiness Get the implementation kit

Have a workflow to discuss? Talk to the MUST team

A closer look at the workflow

One invoice. A clearer journey.

Follow a sample invoice from preparation and review to the sending step and status view. See the workflow, then explore the right setup for your business.

Preview of the illustrative MUST InvoiceNow workflowWatch product film 0:36
Illustrative product workflow · sample dataMusic & sound design · English captions
  1. 01 / PREPARE

    Start with the details

    Build a sample customer invoice.

  2. 02 / REVIEW

    Check before sending

    Review the recipient, items and total.

  3. 03 / SEND

    Follow the next step

    See an illustrative sending sequence.

  4. 04 / TRACK

    Keep the record in view

    Explore the sample status and activity view.

Illustrative sample only. Registration, deployment scope and IRAS reporting availability are confirmed with our team. Watch with transcript

MUST InvoiceNow

Illustrative product workflow · 36 seconds · sample data

Press play to watch. Captions are available in the video controls.

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.